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.
Related
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.
I've got this error when I tried to deploy SSRS report in Visual Studio.
(DAX 2012 kernel 6.0.1108.6510 app 6.0.1108.670 solution 6.1.1108.670)
Error 1 A call to the Microsoft Dynamics AX SRSFrameworkService service failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.43.6.57:8201. C:\Program Files (x86)\MSBuild\Microsoft\DynamicsTools\Microsoft.Dynamics.Framework.Design.Reporting.Modeling.targets 466
10.43.6.57:8201 is old address new should be 10.43.6.91:8201
Where I can change it?
In AX form SSRSServerFarm address is new:(NLDDAXDBS02TR, http://NLDDAXDBS02TR/Reports, 01#NLDDAXDBS02TR)
I run Visual Studio like this "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /AxConfig "c:\Users\Username\Desktop\DEV.axc" with correct config file
in axc file I don't have 10.43.6.57 or old dns NLDDAXDBS01T
I scanned and replaced values in registry on client and server machine, checked all files on client and server machine, checked all values in database.
Also restarted AOSes, SSRS service, and client RDP session.
Microsoft Dynamics AX 2012 Configuration and perform a Refresh Configuration didn't help
Full CIL Compilation, Deactivate BIServices, Activate BIServices also didn't help
Running Visual Studio as Admin - same result
nslookup says: NLDDAXDBS01T - 10.43.6.57 NLDDAXDBS02TR - 10.43.6.91
System Administration > Setup > Business intelligence > Report Servers is correct because i tried to deploy from another rdp server and it works fine
Are you certain the default report server is setup correctly in Ax?
Found under:
System Administration > Setup > Business intelligence > Report
Servers
Check your business connector configuration to make sure it's connecting to the right environment, see https://technet.microsoft.com/en-us/library/aa569654.aspx
I think Visual Studio deploys to AX based on that business connector AXC, so if that's pointed to an incorrect environment that has the "old" SSRS setup, it would explain your issue.
I got this problem one time due to multiple AOS and SSRS instance, or you might stop AOS service while user still using.
First, you need to make sure Report servers configuration point correctly to SSRS instance.
Then, stop all AOS service, go to reporting service login with correct instance and check everything again.
Then, perform full compilation using AXbuild.exe , Full CIL.
Start AOS service and check.
Let us know result.
I have some custom control flow and data flow tasks that are not showing up in the SSIS Toolbox. When I open a package in SSDT containing the custom tasks I get several errors loading the package.
Error loading MyModuleTemplate1.dtsx: Cannot create a task from XML for task "__ECT Fetch Configuration", type "MyEncryptedConfiguration, MyCustomTasks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2bdffe791d57af79" due to error 0x80070057 "The parameter is incorrect.".
I've followed Russ' and Matt's replies from the following post http://social.msdn.microsoft.com/Forums/sqlserver/en-US/5fdf9243-7e38-401e-bf4a-9251738877f9/how-to-browse-the-installed-custom-task-in-sql-server-2012-ssis-ie-custom-ssis-control-flow-task, however, the tasks still don't show.
I'm using SQL Server 2012 x64 with SSDT on Windows Server 2008 R2 x64. I have verified that the tasks are in the GAC and that the assemblies are in the appropriate SQL Server\110\DTS directories. The assemblies have been compiled as 32-bit since I kept getting a warning about targeting Any CPU while referencing 32-bit assemblies (the SQL reference assemblies).
I'm able execute the packages with the custom tasks, on the target server successfully through command line. Additionally, these tasks work fine on my development machine. I can see the tasks in the SSIS Toolbox and can open packages with the tasks without issue. My dev machine is nearly identical to the target machine except that I have full installation of Visual Studio 2010.
Am I missing something?
This problem is the result of WiX installer not properly installing the custom tasks. Below is what I did to verify this.
For test purposes I created an empty custom task and manually deployed it to the target server by copying the files and the DTS\Tasks directory. This worked so I added the .cs file of one of the tasks that was throwing errors, to the test custom task and re-deployed. I was able to see both tasks. After cleaning the solution with the original custom tasks, I manually deployed the original custom task to the target server, like the test custom tasks and was able see the tasks in the SSIS toolbox. I then uninstalled the custom tasks and deployed them to the target server using a WiX installer -- the problem resurfaced. So the problem is with the installer. My previous attempts at manually installing the custom tasks failed because I was using the assemblies installed from the WiX installer, although I don't know why.
I have multiple reports that have been created over the years and anytime a RDLC file is opened in the VS2010, it is asking for an upgrade. I have seen many posts about changing the .config file, but these files are not using config files since they are application based. I have Microsoft.ReportViewer.Winforms, .Common, .ProcessingObjectModel and, .WebForms 9.0 and 8.0 installed on the lab machine.
After upgrading a report and trying to run it on the lab machine ( ms server 2008) I am returned an error of: "The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition' which cannot be upgraded.
Does Report Viewer 2010 Redistributable Package fix this issue? I cannot find a distinct answer. If not, is there another workaround without changing server modes from local to server?
You should really be opening those using the SQL Server Business Intelligence Development Studio (BIDS), which can be found under the Microsoft SQL Server 2008R2 folder on the Programs menu.
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