Hello Gurus,
Although it is not necessarily Tessitura it is related. We are having a problem with SSRS where I cannot access the configuration manager. Once reporting services are installed and updated to match the environment I try to open the configuration manager and receive the error that the machine name is not found. I installed SSRS on the default SQL instance and both are running on the same machine. I have uninstalled and reinstalled I don't know how many times. Obviously a firewall is not an issue since it is on the same box, any other ideas or things I can do?
Thanks!
Naomi
No change but thanks for the suggestion.
Thank you and have a great day!
Naomi Williams
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matt Winchester Sent: Tuesday, August 17, 2010 2:41 PM To: Naomi Williams Subject: Re: [Tessitura Technical Forum] SSRS Configuration Manager Headache
Try changing the SSRS service credentials to Network Service instead of local system.
From: Naomi Williams <bounce-naomiwilliams9587@tessituranetwork.com> Sent: 8/17/2010 1:51:20 PM
Ryan, when you say am I able to login as a local server admin, do you mean a local admin account on the box? Yes I am.
Matt, I apologize I do mean the Reporting Services Configuration Manager. Reporting Services is running under the local system. I am running SQL Standard 2005, Windows Server 2003 R2 64 bit.
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Hi Naomi,
Good day.
Could you please check "Service" under "Administrator Tools", to make sure the instance you installed on SQL server is running?
have fun.
Ben
Hi Ben,
All SQL Services are running. It is very strange. I think I might be having this problem because I had to do so many rebuilds and switched the OS from 64 bit to 32 bit back to 64 bit. It's been a headache to say the least. I think I might just have to wipe the machine and start all over.
http://support.microsoft.com/kb/934162
I think another possible can cause such problem, it is IIS6.0.
IIS 6.0 32-bit and 64-bit are different.
Another thing is that maybe you can check event log, and then you can check out what the error message is.
have fun