Using Visual Studio 2010, I am reporting on my local computer vith SAP Crystal Reports. Everything works on the local computer very well.
However, when I upload my project to highh security remote hosting after publishing the project, I get the specified warning as mentioned below.
In this case, I would like to ask; am I making a mistake in the coding or my Crystal Report versions is wrong? or this is the hosting server's company problem?
Thank you.
Configuration Error
Parser Error Message: Could not load file or assembly 'CrystalDecisions.Web, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
Source Error:
An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Source File: D:\IISDIRS\web.config Line: 29
Assembly Load Trace: The following information can be helpful to determine why the assembly 'CrystalDecisions.Web, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' could not be loaded.
The machine has a Crystal runtime engine that is incompatible with the way your application was built (the Crystal references in your application).
Reference/Version=13.0.2000.0 works with Crystal runtimes 0 to 24
Reference/Version=13.0.3500.0 works with Crystal runtimes 21 to 25
Reference/Version=13.0.4000.0 works with Crystal runtimes 26 and later (for now)
For example, if your Crystal references in your project show 13.0.2000.0, then you need to install Crystal runtime engine SP20.
If you need to remove a Crystal runtime engine service pack and install another, this link has great instructions for cleaning it up:
https://help.jeff-net.com/knowledgebase/article/uninstalling-a-crystal-runtime-service-pack-manually-removing-the-crystal-runtime-engine
Please be careful removing Crystal runtime engines, too. OTHER software may be dependent on a specific version. For example, SAGE apps only work with SP21 currently.
Related
I have a domain controller on which I have SQL Server installed. All databases are setup to automatically backup everyday. Recently the error found in the footer started popping up whenever I login to an instance of the SQL Server Management Studio, and hence it disabled the automated backups. I searched the internet for a solution and the majority of the solutions were to "format" the pc! which I can't due to many complications.
I read somewhere on microsoft support blog that the solution was to "Uninstall SP1"
What SP1? can anyone help?
The error
TITLE: Microsoft SQL Server Management Studio
The type initializer for 'Microsoft.SqlServer.Management.Dmf.PolicyStore' threw an exception. (Microsoft.SqlServer.Dmf)
ADDITIONAL INFORMATION:
Could not load file or assembly 'Microsoft.SqlServer.Diagnostics.STrace, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (Microsoft.SqlServer.Dmf)
Instead of formatting your PC, just fire up the installer package for your version of SQL Server (in my case, I accidentally uninstalled VS 2010 Shell, which it SQL Server Management Studio needs).
From the SQL Server Installation Center:
Maintenance Section
Repair
That should fix any problems you're having.
I had this problem when I uninstalled SQL Server Management Studio. Reinstalling fixed.
Just install the Shared Management Objects MSI file (32 or 64-bit based on your system architecture) It'll surely fix this issue.
I have some rdl reports that work fine with Report Builder 2. However, when I deploy my wpf application (and reports with it) on windows 8 machine, I get Report Definition Error. The Error Message says The definition of the report '' is invalid. The reports work fine even on my development machine under VS 2010. The reports are running under Processing Mode Local. Here are a few things that I tried to resolve this issue.
Checked that the ReportViewer dll's are in the bin directory of the deployment machine
Checked that the Report Definition is correct by running them successfully in Report Builder 2 and SQLServer 2008R2.
There is a doubt that I am not sure of. The windows 8 deployment machine has a program entry "Microsoft Report Viewer Redistributable 2008 SP1" in the control panel. Can this be an issue. I think that, since I copied the ReportViewer dll in the bin(executable) directory of the deployed machine, these dll should be loaded and not the GAC. At this stage I am out of ideas as to why I an unable to generate reports on the deployed machine.
I had not copied the "Microsoft.ReportViewer.ProcessingObjectModel.dll into the bin directory thinking that it is not required for the winforms version of report viewer. In my developement machine this file was in the GAC and hence I did not get any errors for the same. This made me think that the dll is not required. But it is required and so had to copy this into the executable directory of my wpf application.
Nirvan.
We have a reportserver on sql server 2005, it has previously been working on computer X which we are replacing with a computer Y. Computer X only had one default sql instance as our test environment, machine Y is a new machine with 2 sql instances, Y\TEST and Y\DEV. Both machines run Windows Server 2003 and Both have Sql Server 2005 installed together with Report Server
We have not currently done any work on the DEV instance, just on the TEST instance. The reportserver is installed for TEST. SSRS previously worked as intended on X machine, and on Y\TEST its working for reports not using any custom code. However for some of the reports we are loading a custom assembly Localization. This assembly currently exists in following folders on server:
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\bin
Also in rssrvpolicy.config, the entry for Report_Expressions_Default_Permissions has been changed from Execution to FullTrust (Although this was not necessary on the machine X).
When attempting to upload the rdl files through the web interface, we get the following errors:
Error while loading code module: ‘Localization, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e302ddd55ecd694a’. Details: Could not load file or assembly 'Localization, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e302ddd55ecd694a' or one of its dependencies. The system cannot find the file specified. (rsErrorLoadingCodeModule) Get Online Help
There is an error on line 14 of custom code: [BC30451] Name 'Localization' is not declared. (rsCompilerErrorInCode) Get Online Help
Does anyone know any other places with potential errors?
I've been scouring the Internet trying to solve this problem. I created the example projects exactly as instructed on tons of websites, copied my DLL to the folders cited, but to no avail. Still get the error.
Finally it dawned on me to check the Program Files (x86) folder, and sure enough there is the same folder path here as in the Program Files folder that everyone cites.
So instead of:
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
I copied to:
C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
And my assembly works. Is nobody but me using a 64-bit Windows?
I have three things to comment that might help (granted this is with 2008 R2 and I don't know if it will entirely translate versions):
1) I know that I was able to get assemblies recognized on the report server when referenced from the GAC. Perhaps throw it in there to ensure that doesn't work.
2) Ensure that there are not more than one instance of Reporting Services on the deployment server. I once distributed a file to the wrong bin.
3) I don't think the issue is with your rssrvpolicy.config because that would give you errors with CAS permissions not assembly missing errors.
The first things that come to mind is that the file is in the wrong location or the report files that are referencing the dll are referencing a file with an incorrect public key token.
Hope I was able to help. Let me know if you need anything else.
Frank
How can I add reference to an external assembly from within a script task and deploy the package to a server along with the newly added external assembly?
If this is in reference to your other recent question, then the only proper way to get the correct version of a Word DLL on the server where you want to deploy to is to install the proper product onto the server. Most DLL's (especially from products like Microsoft Office) are not redistributable (meaning you are not legally allowed to copy them from machine to machine without the underlying product installed). If a DLL from Microsoft is redistributable, then there will be a document accompanying the DLL that tells which DLL's are allowed to be copied from machine to machine and what the correct process for doing so is.
If this is not in reference to that question, then can you provide more detail about what it is you are trying to do so that we can help you more.
Assuming you are using SSIS 2008 (it was a bit different for SSIS 2005) -
the referenced assembly needs to be installed into GAC (Global Assembly Cache)
on target machine where you run the package.
I'm trying to add a third party reporting chart control in to my project. I'm using visual studio 2005 and i've installed SQL Server 2005 along with the Reporting Services. When i try to add the third party dll to the tool box, i get the error message
'Could not load file or assembly 'Microsoft.ReportingServices.ProcessingCore, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.'
I checked out the assembly and i was not able to find any dlls starting with Microsoft.ReportingServices.
Any ideas?
Thank you
NLV
I see this is a bit late, but I wanted to share something I learned for future possibilities of this error for others. I experienced a similar issue after some software was installed that appears to have updated SQL for VS and/or SQL assemblies in general. It appears this caused a mismatch of what assembly SSRS was trying to use vs what it could find.
I found the following workaround:
You can go to the appropriate reportserver bin and add/replace the Microsoft.ReportingServices.ProcessingCore.dll with the appropriate version one. The location for this bin is
Drive(ex. C):\Program Files\Microsoft SQL Server\MSRS__.MSSQLSERVER(or
whatever report server name is)\Reporting Services\ReportServer\bin.
I just copied the .dll here and then went to Reporting Services Configuration and stopped and re-started the report server.
If there is enough disk space on the DB server but this message still appears, restart the SQL Server Reporting Services (MSSQLSERVER) service