 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Services / Reporting Services / July 2008installing ssrs 2005 on server 2008 aka longhorn
the set up behaves ...interesting. SERVER1: sql server 2005 ee sp2a fix 6 on server 2008 aka longhorn. server is a VM. DB version: Microsoft SQL Server 2005 - 9.00.3228.00 (Intel X86) Feb 9 2008 09:47:16 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 6.0 (Build 6001: Service Pack 1) SERVER2: SSRS only installed on longhorn as well. VM, same os version. spplied sp2a fix6 as well. trying to make native configuration, nothing special, all virtual directories by default and remote db on server1. Creating a new database ReportServer, it does create it. Then I'm asking the configuration tool to use domain login of ssrs service (which was not changed, neither the password was changed) to connect to the database. the user is nicely registered in the database, and then I'm getting the error System.Runtime.InteropServices.COMException (0x800706B3) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementObject.Get() at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetDatabaseConnection(String server, String database, ConfigurationCredentialsType credsType, String userName, String password) ok then. Can not save your credentials through GUI, taht's ok with me I have rsconfig for that. executed rsconfig -c -s DEVSQL -d reportserver -a Windows -u mydomain\myrs -p mypassword (real things are replaced :)) no errors. firing the GUI agai. The SSRS can not initialize and gives me WMI error with login failed. Ok then, let's put the password in there as long as the GUI does not seem to have any habit of keeping it in there. getting error ReportServicesConfigUI.WMIProvider.WMIProviderException: The report server cannot open a connection to the report server database. The logon failed. (rsReportServerDatabaseLogonFailed) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ListReportServersInDatabase(RSReportServerInfo[]& serverInfos) And I'm not making a farm, 1 remote db for 1 ssrs. did dig through internet and premier. I do see complains on SP1 and prior SP1 (aka it does not live on longhorn at all) the closest thing is https://premier.microsoft.com/default.aspx?scid=kb;en-us;922577 but I'm not performing any stress test at all, I'm just doing initial set up. Anybody has seen anything like it on longhorn? I do not remember such a stuff on server 2003... not sql connectivity issue so. have all my remote connections nice and open, even enabled named pipes, makes no difference. and I can connect from SERVER2 to SERVER1 with sql tools just fine with windows authentication  SignatureThanks, Liliya http://blogs.msdn.com/bimusings/archive/2005/08/23/455263.aspx Double check the named pipes is enabled. It fixed my problem where I had Reporting services running under a service account, and was trying to set the service credentials as the credentials type. > the set up behaves ...interesting. > SERVER1: [quoted text clipped - 58 lines] > makes no difference. and I can connect from SERVER2 to SERVER1 with sql tools > just fine with windows authentication has nothing to do with named pipes. and I'm not enabling them anyways... tcp/ip only and that's all they are getting. period. however, the trouble was on the domain level indeed. sysadmin did not create the service accounts as it was requested, so it was a simple gpo issue that took a ton of time to track down, because ... I kinda expected the job done according the specs, not like I just feel like giving no rights and messing things up. So if anybody sees the same error, check your GPO first, do not try digging through all the ssrs configs first like I did. If the GPO has no CONFLICTS AND ALL THE RIGHTS ARE SET PROPER, THEN START SSRS DIGGING... SignatureThanks, Liliya > http://blogs.msdn.com/bimusings/archive/2005/08/23/455263.aspx > [quoted text clipped - 3 lines] > account, and was trying to set the service credentials as the credentials > type. has nothing to do with named pipes. and I'm not enabling them anyways... tcp/ip only and that's all they are getting. period. however, the trouble was on the domain level indeed. sysadmin did not create the service accounts as it was requested, so it was a simple gpo issue that took a ton of time to track down, because ... I kinda expected the job done according the specs, not like I just feel like giving no rights and messing things up. So if anybody sees the same error, check your GPO first, do not try digging through all the ssrs configs first like I did. If the GPO has no CONFLICTS AND ALL THE RIGHTS ARE SET PROPER, THEN START SSRS DIGGING... SignatureThanks, Liliya > http://blogs.msdn.com/bimusings/archive/2005/08/23/455263.aspx > [quoted text clipped - 3 lines] > account, and was trying to set the service credentials as the credentials > type. SignatureThanks, Liliya |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.