Post reply

Reporting Service connection after installation of SP1

  • July 10, 2006 at 10:10 am

    #171519

    We are getting the following error after installation of SP1.

    The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.8.43'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)

    We were successfully connecting to RS, prior to installation of SP1.  I'm not sure how SP1 was installed, probably without admin-rights. In attempt to correct the problem, I have 1) remove the encryption key, 2) upgraded the database, 3) applied the correct security credentials, and backup the newly created encryption key and 4) restarted RS services.  But we are still getting the same message when we attempt to connect.

    Any ideas?

  • July 12, 2006 at 12:01 pm

    #648777

    Check the account that you are using to start the RS services belongs to the RSExecRole on both the ReportServer and ReportServerTempDB databases.

    I had that same error message once before, and re-applying these priviledges took care of it.

    Hope this helps.

    Cesar

  • July 13, 2006 at 9:48 am

    #649014

    Both ReportServer and ReportServerTempDB has the RSExecRole.

    I modified the store procedure GetDBVersion to contain C.0.8.40 on the ReportServer and T.0.8.40 on the ReportServerTempDB, remove encryption key, upgraded the database, backup the encryption key and restarted RS.  This allow me to connect to RS.  But whenever I attempt to run a report I get the following...

    An internal error occurred on the report server. See the error log for more details.

    For more information about this error navigate to the report server on the local

    server machine, or enable remote errors

    This is what's on the logfile on the RS server...

    w3wp!ui!6!7/13/2006-11:05:29:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.

       at System.Threading.Thread.AbortInternal()

       at System.Threading.Thread.Abort(Object stateInfo)

       at System.Web.HttpResponse.End()

       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)

       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at    at System.Threading.Thread.AbortInternal()

       at System.Threading.Thread.Abort(Object stateInfo)

       at System.Web.HttpResponse.End()

       at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)

       at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

    What Now?

  • July 13, 2006 at 10:02 am

    #649026

    But did you re-assign the permissions to the account you are using to manage and run the RS?.

    That's all you need to do.

  • July 13, 2006 at 10:28 am

    #649036

    We are using an NT account to manage the RS service.

    Please explain what you mean by re-assign.

  • July 13, 2006 at 10:44 am

    #649040

    Open Enterprise Manager, select the Security folder, next Logins, and double-click on the account that you're using to manage RS. Click on the last tab (Data Accces), and do for the ReportServer and ReportServerTempDB do the following:

    a) If the Role RSExecRole is selected, click to unselect first. Repeat for both databases. Then hit <Ok> to close the window. Next, open the same properties window for the same user, and this time check the RSExecRole box so it is assigned to it.

    b) If the RSExecRole was not selected for the account, simple check the proper box to include ONLY this account to this particular role.

    Note: No other account should belong to the RSExecRole other than the one managing RS.

    This did the trick for us a couple of times before.

    Let us know if works.

     

     

  • July 13, 2006 at 12:36 pm

    #649079

    Did I mention we are running SQL2005 SP1.

    I tried the under SQL Managment Studio (SQL2005 verion of EM), but the end result is the same...still getting the internal error.

  • July 13, 2006 at 1:32 pm

    #649088

     I'm sorry: we had this issue on RS 2000 and this trick worked; do not know the fix for 2K5.

    But check the BOL and verify that what permissions are needed for the RS Account. Seems to me that somewhere SQL cannot grant permissions to the RS Acct. to do his work.

    Good luck!.

     Cesar

  • July 27, 2006 at 6:08 am

    #651839

    Hey there.  I'm getting the same error when installing RS 2005, and tried all the suggestions I've seen here with no luck so far. Has anyone been able to get past this problem?

     

    Thanks,

    Mike

  • July 27, 2006 at 6:37 am

    #651850

    I was finally able to get by this...

    The person who installed SP1 was not the administrator and in installing they created a new set of files for report server on the box (ie. program files/microsoft sql server/mssql.3/etc).

    I ended stopping IIS and RS, copying the newly upgraded files to its correct location and restarting IIS and RS, reconnected my sources to my reports and eveything started working again.

  • March 13, 2008 at 4:29 am

    #788951

    Hi...

    I am having the same problem that you have! Its great that you managed to get it workin but unfortunate for me I am still having the same problem.

    You mentioned that you copied the newly upgraded files to a correct location, can I know what is the correct location?

    thanks

Viewing 11 posts - 1 through 10 (of 10 total)

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