Skip to main content

Invalid Report Source

The error message appears because the incorrect versions of the Crystal DLL files are referenced.

To correct this behavior reference the correct version of Crystal DLL files.


Adding the Correct References
-----------------------------

1. Open the VS .NET project.

2. In the 'Solution Explorer' window, right-click the 'References' folder and choose the 'Add Reference' command. The 'Add Reference' window appears.

3. Verify the References for all Crystal DLLs are version 9.1.5000. If they are not version 9.1.5000, select the 9.1.5000 version DLLs and click the 'Select' button.

4. Click the 'OK' button.

5. Save and run your application.


If running the application you find the DLLs revert to the version observed prior to your updates, complete the following steps:


Reverting DLLs Back to Version 9.1.5000
---------------------------------------

1. Right-click the project name in the solution explorer and select the 'Properties' command. The 'Properties' window appears.

2. Under the 'Common Properties' folder, select 'References Path'. The 'Reference Path' window appears.

3. Delete all entries in this window and click 'OK'.

4. Repeat steps 2 through 4 of the 'Steps to Add the Correct References Section'.

Upon completing the listed steps, the application runs and reflects the correct References.


she send me this thru my mail i have copied and pasted it here

so it may be helpful to other who visit this forum

Thanks a lot for all those who tried to solve this problem.

dont forget to rate my post

Comments

Popular posts from this blog

The sign-in method you're trying to use isn't allowed. For more info, contact your network administrator

Above problem occur when you have not added a group (of which User try to login)  in your local policy login. To resolve the issue, follow the steps,
Log in as the administrator on the server, then start the Group Policy Management Editor by running the  gpmc.msc command from PowerShell or the Command Line window. 1. In the Group Policy Management window on the left hand side, select Group Policy Management. 2. Click to expand the  Forest tree node.
3. Click Domains.
4. Select your domain name.
5. Click Group Policy Objects. 6. In the right-hand window, double-click Default Domain Controllers Policy.
7. Right-click Default Domain Controllers Policy and Select Edit.
8. In the Group Policy Management Editor window, click Default Domain Controllers Policy.
9. Click Computer Configuration, and then click Policies.
10. Click Windows Settings, and then click Security Settings. 11. Click Local Policies and then click User Rights Assignments.
12. In the right pane, click Allow log on locally. 12. Cli…

ORA-38104: Columns referenced in the ON Clause cannot be updated

In my case, this error pertains to Oracle Merge query. After 30 minutes of time wastage and a lot of hunting on different forums, I come to know that where and why was my merge query throwing exception.

I was giving multiple criteria in ON clause of merge query, and was also trying to update a column which I have mentioned in ON clause. Once I remove that column from update clause of merge query, it executed successfully.

I hope that this will also works for you.

In case if this post help you, then please comment on it.

Thanks.

Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405)

Yesterday, I start SQL Server 2005 and try to connect with sa user but was enable to connect with the 'sa' user and got this error:

Cannot use the special principal 'sa' (Microsoft SQL Server, Error: 15405)After doing some google, I found out the solution which I am sharing so that others can get all the possible solutions from this article.
The titled message mean that your sa user is disabled. To enable it, you have to follow below mentioned steps:1) you have to change the authentication mode: go to Management Studio and open Object Explorer. Connect to your server and right-click on the server name, then select Properties. Go to Security tab and under Server Authentication select "SQL Server and Windows Authentication Mode".2) Also, after you follow the directions above, you will also need to explicitly enable the sa account as well. Go to Security->Logins. Right-click on the "sa" account, select "Properties". In the list on the lef…