Cannot Access report project after db transfer to another SQL instance

  • Hi,

    I have have this problem for days now and still can't figure it out.

    1. I created new instance of sql server 2005

    2. transferred db1 from default instance to the new instance

    3. currently there is a report server installed in the default instance and have several projects connected on it, including a project connect to db1

    4. after i transferred db1, i cannot access my report anymore.

    error:

    An error has occurred during report processing. (rsProcessingAborted)

    Cannot create a connection to data source 'dsOKI'. (rsErrorOpeningConnection)

    For more information about this error navigate to the report server on the local server machine, or enable remote errors

    5. i already modified the connection string of my report project and successfully deployed. but when i access it thru web http://server/reportserver or on my windows application, the above error appears.

    thanks in advance for the help.

    Regards,

    Cesar

  • When you have moved the datasource database to a new server I think it is more than connectionstring change you need to open the base report in BIDs if you are using shared datasource and make sure you code compiles. If you are not using shared datasource then you need to do that for all your reports using that database, I think you old connectionstring is still in some part of the code that is breaking the reports.

    Kind regards,
    Gift Peddie

  • Hi Sir,

    I already did that, open my project in BID, modified connection string and redeployed the project, the execution is successful. But still I can't view it.

    Do i need to install new instance of report server in the new instance of sql server(the one that i installed recently)?

  • Hi,

    Your error is a base error that may later include permissions related actual error which I think could be related to SSRS and Asp.net not having permissions to the new server through Double hop, you have the option to use both SQL and Windows authentication in the new server and adding permissions for at least the Asp.net runtime in both the server and database used by your reports.

    http://msdn.microsoft.com/en-us/library/ms156468.aspx

    Kind regards,
    Gift Peddie

  • Why don't you follow the advice in the error message and enable remote errors?

    http://msdn.microsoft.com/en-us/library/aa337165(SQL.90).aspx

    My recommendation would be to create a shared data source on the server and then modify your report to use that shared data source. But, it all depends upon how you are configuring your data source. If you are using Windows Authentication - you are going to have to setup and configure Kerberos, or you are going to have to change to SQL Authentication or one of the other methods.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply