March 5, 2012 at 2:03 pm
Hi BI Folks,
The system administrators were pushing to move this last server off old hardware into a virtualized environment.
The server has the following specs before and after:
-- before --
Windows 2000 SP4
SQL Server 2005 - SSIS & SSRS
-- after --
Windows 2003 SP2
SQL Server 2005 - SSIS & SSRS
The users are complaining about the reports not working. I tried to manage the server and recieved the following error:
The report web service is unable to access secure information in the report server. Please verify that the web service account is specified correctly in the report server config file. Things I noticed in the SSRS log files.
1 – There is not web service account defined therefore it is defaulting to Network Service account. If I look via the SSRS configuration tool, it should be the <server>/ASPNET account which is defined.
2 – The server was working correctly on 3/3 but now thinks that the evaluation period is expired on 3/5.
Has anyone run across this issue before?
Any help is appreciated.
Sincerely
John
John Miner
Crafty DBA
www.craftydba.com
March 5, 2012 at 2:18 pm
When they moved it, I am assuming they did not use a P2V utility but instead treated it as a migration.
When migrating an SSRS install, the encryption key needs to be backed up from the original server and restored to the new server. Was this step performed?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 5, 2012 at 2:37 pm
was the Windows upgrade an in place upgrade?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 5, 2012 at 3:07 pm
Hi Guys,
We finally figured this one out but do not understand why it worked in WIN 2000 but not in WIN 2003.
1 - Keys did not need to be backed up since they used the migration tool.
2 - A in place upgrade of the OS was performed.
Before the virtualization, there was a line in the main log that stated a web service account was not specified but it defaulted to the correct one (ASPNET).
After the virtualization, I could not even manage SSRS via SSMS. Using the RS Configuration manager, you could see the ASPNET account selected. However, it was defaulting to Local Network Service account.
Adding the following change to the RSReporting.config file made all my worries go away.
<WebServiceAccount><server name>\ASPNET</WebServiceAccount>
I guess my main question is why did it work in 2000 but not in 2003 w/o the change.
Oh well, back to the task list.
Thanks again for your suggestions.
John
John Miner
Crafty DBA
www.craftydba.com
March 5, 2012 at 3:28 pm
pretty sure this is IIS related.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply