locked
Web service request CreateReport to Report Server RRS feed

  • Question

  • I created a report in Visual Studio 2008, on a SQL Server 2008 platform in development. I can load the report to the develppment server via the CRM 4.0 UI. Now when I attempt to move the report to production I get the following error. Production is the same setup with Visual Studio 2008, on a SQL Server 2008 ? Any ideas?

    Web service request CreateReport to Report Server http://CRM01/reportserver/ReportService2005.asmx failed with SoapException. Error: The report definition is not valid.  Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' which cannot be upgraded.

    Tuesday, December 14, 2010 5:27 PM

Answers

  • You don't need VS2010 to create a 2010 RDL file.  BIDS (VS that comes with SQL Server) 2008 R2 can generate 2010 RDL files, which is obviously what you've managed to do.

    You can use VS 2008 R2 to create your project.  After you've created it:

    1. Right-click on the project name
    2. Select 'Properties'
    3. Change 'TargetServerVersion' to suit your Production environment

    To re-iterate; your choices for a report already written are:

    • Try to hack the RDL file in plaintext; fraught with danger and recommended only if it is likely to take considerably longer to regenerate the report
    • Start again using the steps listed above to ensure it will work in production

    --pogo (pat)
    Wednesday, December 15, 2010 10:42 PM

All replies

  • is production 2008 sql?
    http://mscrmblog.net
    Microsoft Certified Business Management Solutions Specialist
    Microsoft Certified CRM Developer
    Tuesday, December 14, 2010 10:55 PM
  • The 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' indicates that your report has been authored with the 2010 version of RDL.  Support for this was introduced with SQL Server 2008 R2.

    I'm guessing that your development environment is SQL Server 2008 R2, but that production is SQL Server 2008.

    There are no supported methods for converting RDL formats to previous versions (at least not with 2008 -> 2005 that has caught me out in the past).  It will likely depend on how much of the new functionality you have made use of and how complex the report is, whether you would want to bother with converting vs re-writing.

    This link indicates that hacking at the RDL file in notepad or similar can work; again, this will depend on whether you've made use of any 2010 specific functionality.


    --pogo (pat)
    Tuesday, December 14, 2010 11:33 PM
  • pogo69,

    Yes my development enviornment is SQL Server 2008 R2, and production is SQL Server 2008 but I do not have Vistual Studio 2010 installed at all. In addition I did notice that prodution has a different report viewer control.

    Production shows: Microsoft Report Viewer Redistributable 2008 (KB71119).

    Development shows: Microsoft Report Viewer Redistributable 2008 SP1 and Microsoft Report Viewer Redistributable 2005

    The report isn't very intense, I suppose your suggesting I need to recreate it in VS2005 vs. 2008? I can look at the work around this morning.

     

    --

    Ibrahim, Yes porudction is SQL Server 2008 with windows server 2008. Production isn't R2 as it was created before my development enviornent (and the R2 release) which I had to rebuild.

    Wednesday, December 15, 2010 1:33 PM
  • You don't need VS2010 to create a 2010 RDL file.  BIDS (VS that comes with SQL Server) 2008 R2 can generate 2010 RDL files, which is obviously what you've managed to do.

    You can use VS 2008 R2 to create your project.  After you've created it:

    1. Right-click on the project name
    2. Select 'Properties'
    3. Change 'TargetServerVersion' to suit your Production environment

    To re-iterate; your choices for a report already written are:

    • Try to hack the RDL file in plaintext; fraught with danger and recommended only if it is likely to take considerably longer to regenerate the report
    • Start again using the steps listed above to ensure it will work in production

    --pogo (pat)
    Wednesday, December 15, 2010 10:42 PM
  • Thanks I ended up changing the 'TargetServerVersion', then recreating the report within the same project. To anyone else who ever reads this, changing the 'TargetServerVersion' after you've created the report does NOT retro update the files in the project.

     

    Thanks pogo!

    Thursday, December 16, 2010 5:31 PM