Cannot install SP1

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 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,
MattTry 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.
"Matt Hamilton" <Matt Hamilton@.discussions.microsoft.com> wrote in message
news: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
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,
> Matt|||"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|||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|||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
>
>|||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.
"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,
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,
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,
Matt

Cannot fine the object “MSmerge_ctsv_... Because it does not exists or you do not have permissio

I keep getting the following error message during the initial merge agent.

· “The merge process was unable to deliver the snapshot to the subscriber.If using Web synchronization, the merge process may have been unable to create or write the message file, when troubleshooting, restart the sychronzation with verbose history loggin and specify an output file to write.

· Cannot fine the object “MSmerge_ctsv_B5ECD41086F24A64B8040A41A75B2DC4”, Because it does not exists or you do not have permission.(source: MSSQLServer, Error number 15151)

I do see this view in the publication and if I run the following command on the publisher I get…

select * from Msmerge_ctsv_B5ECD41086F24A64B8040A41A75B2DC4

I get

tablenick rowguid generation partchangegen lineage colv1 marker logical_record_parent_rowguid logical_record_lineage

(0 row(s) affected)

I have another publication working on this same server that is working, both are from a copy from a template database.Please advise to what this problem could be and what I can do to resolve this.

Thank you,

Pauly C

The issue was the mobile server name was changed but not dropped and re-added back so the values of@.@.servername and serverproperty(‘servername’) did not match. Once I fixed this everything replicated fine. Not a very intuitive error but if the error returns somethign like "Cannot fine the object “MSmerge_ctsv_..." check the subscriber server name by running

select @.@.servername as oldservername, serverproperty('servername') as newservername, case when @.@.servername <> serverproperty('servername') then '*** Error - Server name changed, replication will not work' else 'Replication friendly' end as cMessage

also this is a script I use to run the procs to drop and add the server...

Use Master

IF (select SERVERPROPERTY('ServerName')) <> (SELECT @.@.Servername )

begin

DECLARE @.SQL VARCHAR(256), @.oldsvrname varchar(128), @.newsvrname varchar(128)

select @.oldsvrname = cast(@.@.servername as varchar(128)), @.newsvrname = cast(SERVERPROPERTY('ServerName') as varchar(128))

set @.SQL = 'Sp_DropServer @.server = ''' + @.oldsvrname + ''', @.droplogins =''droplogins'''

exec( @.SQL)

SET @.SQL = 'Sp_Addserver @.server =''' + @.newsvrname + ''', @.local= ''LOCAL'' , @.duplicate_ok = ''duplicate_OK'' '

exec(@.SQL )

end

** must restart services at this point.

Thank you,

Pauly C

|||Maybe if you would run the agent with a higher OutputVerboseLevel, perhaps it may have given you clues.|||Actually I did that but it gave the same error message.