| Groups | Blog | Home |
sql server reporting services : Cannot install SP1
My Win2003 server won't let me install RS SP1. It gets about two thirds of the way through the initial progress bar, then tells me this: SQL Setup failed to connect to the database service for server configuration. Refer to the Server error logs and setup logs for more detailed error information. I am logged into the server as the same user (a Domain Admin) that installed RS in the first place. I've even tried using the rssetupaccount and rssetuppassword parameters to make it install as the 'sqlservice' user on our domain (the one that runs the SQL Server service). Our 'Domain Admins' group, as well as the 'sqlservice' user, has dbo rights to the ReportServer database. I've even tried adding 'BUILTIN\Administrators' to the user-list of the db and giving it dbo rights, then logging in as the local Administrator user on the server - still get the same error. What else can I try? Thanks in advance,
Try using a sql account when passing in the rssetupaccount and
rssetuppassword. Do you have Terminal services for applications turned on? That may be causing this issue as well. Even so, using a sql account during setup should solve the issue. -- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Matt Hamilton" <Matt Hamilton@discussions.microsoft.com> wrote in message configuration. Refer to the Server error logs and setup logs for morenews:F34F7448-4D94-468C-A362-E809BE1B56EE@microsoft.com... > Hi folks, > > My Win2003 server won't let me install RS SP1. > > It gets about two thirds of the way through the initial progress bar, then tells me this: > > SQL Setup failed to connect to the database service for server detailed error information. [quoted text, click to view] > installed RS in the first place. I've even tried using the rssetupaccount> I am logged into the server as the same user (a Domain Admin) that and rssetuppassword parameters to make it install as the 'sqlservice' user on our domain (the one that runs the SQL Server service). [quoted text, click to view] > rights to the ReportServer database. I've even tried adding> Our 'Domain Admins' group, as well as the 'sqlservice' user, has dbo 'BUILTIN\Administrators' to the user-list of the db and giving it dbo rights, then logging in as the local Administrator user on the server - still get the same error. [quoted text, click to view] > > What else can I try? > > Thanks in advance, > Matt
[quoted text, click to view]
"Daniel Reib [MSFT]" wrote: > Try using a sql account when passing in the rssetupaccount and > rssetuppassword. > > Do you have Terminal services for applications turned on? That may be > causing this issue as well. Even so, using a sql account during setup > should solve the issue. The only TS thing we're using is the Remote Desktop functionality. I tried running this: e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa password> And it still threw the same error. Interestingly, it also brings up a prompt to send an error report to MS when I click OK on the error dialog. I've installed SP1 with no problems at all on one of our other servers (running Win2k rather than Win2003). Argh! Please help!
The parameters are case sensitive. Did you use RSSETUPACCOUNT &
RSSETUPPASSWORD? -- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Matt Hamilton" <Matt Hamilton@discussions.microsoft.com> wrote in message news:13231C67-50A3-4A59-9D15-040E24183592@microsoft.com... > "Daniel Reib [MSFT]" wrote: > > > Try using a sql account when passing in the rssetupaccount and > > rssetuppassword. > > > > Do you have Terminal services for applications turned on? That may be > > causing this issue as well. Even so, using a sql account during setup > > should solve the issue. > > The only TS thing we're using is the Remote Desktop functionality. > > I tried running this: > > e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa password> > > And it still threw the same error. > > Interestingly, it also brings up a prompt to send an error report to MS when I click OK on the error dialog. > > I've installed SP1 with no problems at all on one of our other servers (running Win2k rather than Win2003). Argh! Please help! > > Matt
No! I didn't!
I'll try that next. Thanks, Daniel. Case-sensitive parameters, eh? That's a first. [quoted text, click to view] "Daniel Reib [MSFT]" wrote:
> The parameters are case sensitive. Did you use RSSETUPACCOUNT & > RSSETUPPASSWORD? > > -- > -Daniel > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "Matt Hamilton" <Matt Hamilton@discussions.microsoft.com> wrote in message > news:13231C67-50A3-4A59-9D15-040E24183592@microsoft.com... > > "Daniel Reib [MSFT]" wrote: > > > > > Try using a sql account when passing in the rssetupaccount and > > > rssetuppassword. > > > > > > Do you have Terminal services for applications turned on? That may be > > > causing this issue as well. Even so, using a sql account during setup > > > should solve the issue. > > > > The only TS thing we're using is the Remote Desktop functionality. > > > > I tried running this: > > > > e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa password> > > > > And it still threw the same error. > > > > Interestingly, it also brings up a prompt to send an error report to MS > when I click OK on the error dialog. > > > > I've installed SP1 with no problems at all on one of our other servers > (running Win2k rather than Win2003). Argh! Please help! > > > > Matt > >
Actually not for Windows Installer. They use case to determine scope.
-- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Matt Hamilton" <MattHamilton@discussions.microsoft.com> wrote in message news:AD74DFAD-9735-465F-B75C-214E982D07AB@microsoft.com... > No! I didn't! > > I'll try that next. Thanks, Daniel. > > Case-sensitive parameters, eh? That's a first. > > "Daniel Reib [MSFT]" wrote: > > > The parameters are case sensitive. Did you use RSSETUPACCOUNT & > > RSSETUPPASSWORD? > > > > -- > > -Daniel > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > > > > "Matt Hamilton" <Matt Hamilton@discussions.microsoft.com> wrote in message > > news:13231C67-50A3-4A59-9D15-040E24183592@microsoft.com... > > > "Daniel Reib [MSFT]" wrote: > > > > > > > Try using a sql account when passing in the rssetupaccount and > > > > rssetuppassword. > > > > > > > > Do you have Terminal services for applications turned on? That may be > > > > causing this issue as well. Even so, using a sql account during setup > > > > should solve the issue. > > > > > > The only TS thing we're using is the Remote Desktop functionality. > > > > > > I tried running this: > > > > > > e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa password> > > > > > > And it still threw the same error. > > > > > > Interestingly, it also brings up a prompt to send an error report to MS > > when I click OK on the error dialog. > > > > > > I've installed SP1 with no problems at all on one of our other servers > > (running Win2k rather than Win2003). Argh! Please help! > > > > > > Matt > > > > > >
In case anyone's interested:
One of our techies, when trying to resolve something else, uninstalled and reinstalled IIS on our server the other day, breaking RS. So I uninstalled and reinstalled RS ... and then (thinking, "what the hell?") tried installing SP1 - and this time it worked. We changed nothing, so I have no idea what was stopping us from installing SP1 in the first place. So if you have similar problems, try uninstalling & reinstalling. Cheers,
In case anyone's interested:
One of our techies, when trying to resolve something else, uninstalled and reinstalled IIS on our server the other day, breaking RS. So I uninstalled and reinstalled RS ... and then (thinking, "what the hell?") tried installing SP1 - and this time it worked. We changed nothing, so I have no idea what was stopping us from installing SP1 in the first place. So if you have similar problems, try uninstalling & reinstalling. Cheers,
In case anyone's interested:
One of our techies, when trying to resolve something else, uninstalled and reinstalled IIS on our server the other day, breaking RS. So I uninstalled and reinstalled RS ... and then (thinking, "what the hell?") tried installing SP1 - and this time it worked. We changed nothing, so I have no idea what was stopping us from installing SP1 in the first place. So if you have similar problems, try uninstalling & reinstalling. Cheers,
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |