February 25, 2009 at 10:05 am
This is the second try at moving to Sql Server 2008 and Reporting Services. I made a backup of the Encryption Keys as well as a backup of the Report Server Database and the ReportServerTemp database. I had switched over to a backup server earlier without backing up the encryption Keys and as a result the only way to get that server working was to delete the encryption keys and redo all my Data Sources and Subscriptions. That upgrade is now working fine. I took the old Production server and had it wiped and then loaded a fresh install of Windows 2008 server. I then installed Sql Server 2008 including Reporting Services. Once everything was installed I restored my ReportServer and ReportserverTemp databases from my 2005 installation. I then went to the Configuration page and Restored my Encryption Keys from the 2005 installation. When I try to bring up the http://localhost/reports I get the following error:
The report server installation is not initialized.
Have I done something wrong and if so is there a way to get this new install working without having to once again delete the encryption keys and then redo all the datasources and Subscriptions??? The steps for this seem very cryptic for some reason (no pun intended)...Thanks for any advice...:w00t:
February 25, 2009 at 10:57 am
The not initialized error means the new SQL Server does not know the ReportServerDB and ReportServerTempDB so the relational engine cannot start reporting services. But in migration it is related to the encryption. Check the thread below for the fix.
http://www.sqlservercentral.com/Forums/Topic651732-147-2.aspx#bm651915
Kind regards,
Gift Peddie
February 25, 2009 at 2:39 pm
For some reason in the "Reporting Services Configuration Manager under Scale-out-Deployment I had the same server listed twice. I deleted one of the entries and the web page displaying all my reports came up. I checked the data Sources and they were fine and all the subscriptions were fine to.
Unfortunately when I go to run any of the reports I am getting the following error...
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online Help Invalid column name 'ProcessingFlags'.
This error occurs immediately so I am pretty sure it is not a timeout or low disk since nothing else is on this server but Reporting Services...
I checked the error log and see the following or at least a snippet of what is in the error log:
library!ReportServer_0-6!70c!02/25/2009-13:29:24:: Call to GetPropertiesAction(/SDSD Help Desk Reports/SDSD Daily Logging Report/SDSD Daily Logging, PathBased).
library!ReportServer_0-6!70c!02/25/2009-13:29:24:: i INFO: Attempting republishing of item '/SDSD Help Desk Reports/SDSD Daily Logging Report/SDSD Daily Logging'.
library!ReportServer_0-6!70c!02/25/2009-13:29:24:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database., ;
library!ReportServer_0-6!70c!02/25/2009-13:29:24:: e ERROR: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: Invalid column name 'ProcessingFlags'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand. b__0()
at Microsoft.ReportingServices.Library.SqlBoundaryWithReturn`1.Invoke(Method m)
--- End of inner exception stack trace ---
Any ideas???
February 26, 2009 at 2:03 pm
You may have SSRS 2008 bug so check the thread below and see if the hotfix is relevant to you because the previous user did not run into code related errors.
Kind regards,
Gift Peddie
February 26, 2009 at 2:15 pm
I saw that posting and downloaded the Hotfix but did not install as I have several reports that are giving me the error mentioned above but at most contain several hundred rows of data. I have another RS 2008 installation that I upgraded rather than migrated and it is running just fine. I have been researching the web all day looking for any reference to this problem and so far have come up empty. I will continue to research for another day. If nothing comes to light I will then try to uninstall everything I have done and do another install. It seems rather straightforward but for the life of me I cannot track down this error...
Thanks for the response
February 26, 2009 at 2:20 pm
If it is some reports giving you that error then SSRS may just have dropped the connectionsting credential so check the connection sting property in BIDs if it is empty SSRS have dropped the datasource database connection user info. That is a known issue, add it back.
Kind regards,
Gift Peddie
February 26, 2009 at 3:12 pm
I checked several reports in BIDS and all the data sources are in tack. I ran/pre-viewed these reports and was able to get data to be returned and displayed in the report...
I went ahead and reset one of my data sources since I used shared data sources for all my reports and tried to re-run the report still get the same error...
Again thanks for the suggestion...
February 26, 2009 at 4:45 pm
I have found the reason for your error it is related to Windows 2008 and your subscriptions because Windows 2008 runs IIS 7 which is now owned by the developers division within Microsoft and not Windows so there is no SMTP so SSRS which is a Windows division through SQL Server decided all SMTP using features are not supported. So you need to either use free SMTP or modify your reports to remove CC and other related setup in your reports. I found someone posted your error as subscription related so I know because that was added to many bugs I gave to the SSRS team which they labled as depreciated.
http://msdn.microsoft.com/en-us/library/ms143380.aspx
Kind regards,
Gift Peddie
February 27, 2009 at 6:26 am
Gift,
Thanks again for replying...I have about 200 plus reports and only 5% of those have subscriptions. The reports are failing when I merely click them for display and not during execution of a subscription. As a matter of fact I have shut down SQL-Server Agent so the subscription jobs will not try and execute. I have my e-mail setup to forward mail to a server inhouse that has smtp installed, I do not run smtp on the server I have RS installed on...Once again thanks for the tip...
February 27, 2009 at 6:56 am
There are extra security requirements for Win2008 deployment both for you the operator and SSRS and other configurations.
http://technet.microsoft.com/en-us/library/bb630430.aspx
Kind regards,
Gift Peddie
February 27, 2009 at 7:57 am
Gift,
I think I may have stumbled onto the reason for my error. I think I mentioned somewhere above that when I did my installation I had the RS portion go ahead and create a database and have everything setup so all I had to do was restore over the empty database with my 2005 RS database and everything would be good. I went back to look at the steps for Migrating and saw this...
Install a new report server instance in files-only mode so that you can configure it to use non-default values. For command line installation, use the FilesOnly argument. In the Installation Wizard, select the Install but do not configure option.
When I first read that I was under the impression the files only installation was for someone who wanted RS but at a future date and so they would choose this option. Now I believe this is the only way to migrate a 2005 RS installation or am I off base??? Anyway I am having our Sysadmin reload my virtual server with a fresh install of the OS and I am going to try this all over again but in Files only mode and see if I have better success...
I will post here when I am done as to the results...
February 27, 2009 at 9:03 am
I did not remember your post about empty database because you cannot use that in moving so I know you cannot do that in migration.
So here is what you need to do read my conversation with the other user because that migration in Win2003 worked. Then read the requirements for Win2008 like keeping port 80 open and admin permissions. When you add the Win2008 requirements to the standard migration requirements, then your migration will work. When you have finished post a solution because Microsoft needs to create a separate Win2008 migration guide including known issues.
Kind regards,
Gift Peddie
February 27, 2009 at 3:13 pm
Gift,
I have re-installed Sql Server 2008 and RS 2008 but this time time I did a files only RS install. I also had to create the RSExecRole and configure according to the Steps on the MSDN Website for Installing RS 2008. Once I had restored my RS 2005 Database onto my new RS 2008 installation I ran the RS Configuration tool. This time nothing was set up and I had to do each one manually. But once again when I got to the Scale-out Deployment I found 2 entries under Server both were identical. When I tried to display a report it errored out on me. I deleted the first Server under the Scale-out Deployment entry and then everything worked fine.
So I did two things differently this time. One was a files only install and the other was to create a RSExecRole before restoring my 2005 ReportServer and ReportServerTempDB database to my RS 2008 installation. While I am curious to try it one more time I think I will let sleeping dogs lie and just press on, now that everything is working properly...
Thanks again for all your help...
February 27, 2009 at 4:11 pm
I am glad I could help and thanks for posting the detailed steps because I think all the problems are related to permissions in Windows 2008.
Kind regards,
Gift Peddie
May 17, 2011 at 6:48 am
Just to add, that I had similar issues. I ran the following and it fixed the issue...
USE [ReportServer]
GO
EXEC sp_addrolemember N'db_owner', N'RSExecRole'
GO
USE [ReportServerTempdb]
GO
EXEC sp_addrolemember N'db_owner', N'RSExecRole'
GO
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply