Confusing, non-working db copy in 2005 - "specified subsystem"?

I really wanted to be enthusiastic about SQL Server 2005. I'm not off to a
great start with that. I'm stymied by yet another wizard that is anything
but.
I tried to copy a database from a 2000 server to a 2005 server using the new
"Management Studio" - I got a cryptic message about "Integration SSIS proxy"
accounts not existing and stuff about subsystems, so I looked around
newsgroups, and realized that I had not installed "Integration Services",
needed to make this happen. So I did.
After installing this component, I went into the proxies, to SSIS Package
Execution, got told I had to make a credential, which I went and did... then
it bombed out on me with a "specified @.subsystem_id (11) does not exist"
message. When I tried again, it asserted that the proxy exists... but I
could see no evidence of this new proxy name, nor does it show up in this
newfangled copy wizard afterwords. I tried all this again with a new proxy
name, this time clicking "script" instead of the "OK" button. When I run the
script I still get the message about @.subsystem_id.
This is a real step down from the old DTS wizard... mainly in that I could
get that to work without all these confusing runarounds. Is there anyone who
can help me to get where I need to go with this? I just want to copy some
databases... is there a simple way? Can I, if nothing else, at least copy
and attach? At least that I can understand...
I've never been a fan of the CDW in 2000 or 2005. Much simpler to
backup/restore or detach/attach. Note that this will leave your database in
80 compatability mode so you'll need to run
EXEC sp_dbcmptlevel 'database name', '90'
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Richard K Bethell" <softdev@.spammingisevil.bad> wrote in message
news:OP%23TK1G7FHA.1028@.TK2MSFTNGP11.phx.gbl...
>I really wanted to be enthusiastic about SQL Server 2005. I'm not off to a
>great start with that. I'm stymied by yet another wizard that is anything
>but.
> I tried to copy a database from a 2000 server to a 2005 server using the
> new "Management Studio" - I got a cryptic message about "Integration SSIS
> proxy" accounts not existing and stuff about subsystems, so I looked
> around newsgroups, and realized that I had not installed "Integration
> Services", needed to make this happen. So I did.
> After installing this component, I went into the proxies, to SSIS Package
> Execution, got told I had to make a credential, which I went and did...
> then it bombed out on me with a "specified @.subsystem_id (11) does not
> exist" message. When I tried again, it asserted that the proxy exists...
> but I could see no evidence of this new proxy name, nor does it show up in
> this newfangled copy wizard afterwords. I tried all this again with a new
> proxy name, this time clicking "script" instead of the "OK" button. When I
> run the script I still get the message about @.subsystem_id.
> This is a real step down from the old DTS wizard... mainly in that I could
> get that to work without all these confusing runarounds. Is there anyone
> who can help me to get where I need to go with this? I just want to copy
> some databases... is there a simple way? Can I, if nothing else, at least
> copy and attach? At least that I can understand...
>
|||It appears to have gotten worse in 2005, even. :-) Thanks for the
compatibility tip! I probably would have forgotten about that...
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OeCleBH7FHA.1140@.tk2msftngp13.phx.gbl...
> I've never been a fan of the CDW in 2000 or 2005. Much simpler to
> backup/restore or detach/attach. Note that this will leave your database
> in 80 compatability mode so you'll need to run
> EXEC sp_dbcmptlevel 'database name', '90'
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Richard K Bethell" <softdev@.spammingisevil.bad> wrote in message
> news:OP%23TK1G7FHA.1028@.TK2MSFTNGP11.phx.gbl...
>
|||I should also have said a couple more things
1) Update all your statistics
2) Run DBCC UPDATEUSAGE (0)
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Richard K Bethell" <softdev@.spammingisevil.bad> wrote in message
news:OJMDWSH7FHA.2484@.TK2MSFTNGP10.phx.gbl...
> It appears to have gotten worse in 2005, even. :-) Thanks for the
> compatibility tip! I probably would have forgotten about that...
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:OeCleBH7FHA.1140@.tk2msftngp13.phx.gbl...
>

configuring a publishing and distribution wizard

I am having a problem with configuring publiushed and distributor .i am
selecting the option to make the local server its own distibutor.
After competing the task, I am getting an enterprise manager error stating
that
Sql server manager could not configure the "SQLSERVER' as distibutore for
"SQLSERVER'
error 18483 could not connect th the server 'SQLSERVER' becouse
Distibutor_admin' is ot defined as a remote login at the server...
Need help!!
what happens if you do a select @.@.servername on the local server?
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:7B19D769-EFF7-4DB6-A2F0-9CBEE75BCC6D@.microsoft.com...
>I am having a problem with configuring publiushed and distributor .i am
> selecting the option to make the local server its own distibutor.
> After competing the task, I am getting an enterprise manager error stating
> that
> Sql server manager could not configure the "SQLSERVER' as distibutore for
> "SQLSERVER'
> error 18483 could not connect th the server 'SQLSERVER' becouse
> Distibutor_admin' is ot defined as a remote login at the server...
> Need help!!
|||As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
If this is the case, you will need to run the sp_addserver procedure with
the local parameter to set it correctly. You may also need to run
sp_dropserver as well.
After doing this, you will need to stop and restart SQL Server for the
change to take effect.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Guys,
I have tried the sp_addserver and sp_dropserver procedure, restarted the
server and i still have the sa me issue
"Rand Boyd [MSFT]" wrote:

> As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
> If this is the case, you will need to run the sp_addserver procedure with
> the local parameter to set it correctly. You may also need to run
> sp_dropserver as well.
> After doing this, you will need to stop and restart SQL Server for the
> change to take effect.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||what happens when you issue a select @.@.servername now
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:E443C6F1-24E8-4074-98CD-388AA6529D0E@.microsoft.com...[vbcol=seagreen]
> Hi Guys,
> I have tried the sp_addserver and sp_dropserver procedure, restarted the
> server and i still have the sa me issue
>
> "Rand Boyd [MSFT]" wrote:
incorrect.[vbcol=seagreen]
with[vbcol=seagreen]
rights.[vbcol=seagreen]

Configure web synchronization wizard error

I am trying to confugure SQL Server 2005 (wrokgroup edition) for merge
replication with web synchronisation. The server will be publisher and
distributor and the remote client will be running SQL Server 2005
Express.
I have set up two directories under Inetpub on the server. The access
directory is set up as a virtual directory for web access and the
snapshot directory is set up as a network share.
I have set up a local account for replication / synchronization.
The SQL Agent runs under the admin account, I have logged on to SQL
management studio under the admin account and created the publication.
When I run the configure web synchronisation wizard I keep getting an
error occuring when it gets to the step "Setting the snapshot share
permissions" which then rolls back the previous actions.
A message comes up for each user I have specified (three in the last
case) saying "Setting the snapshot share permissions (error)" and then
"The operation completed successfully. (Exception from HRESULT:
0x8007) (mscorlib)" for each user.
I have tried manually configuring both directories for permissions for
all three accounts (admin account running SQL agent, local account for
replication/synchronisationand login on remote client). Starting to
clutch at straws!
Any help greatly appreciated. It appears to be something to do with
permissions but I am not sure what to set for which account and where.
Many thanks.
On 1 Jun, 10:37, JDS <a...@.jeremysage.com> wrote:
> I am trying to confugure SQL Server 2005 (wrokgroup edition) for merge
> replication with web synchronisation. The server will be publisher and
> distributor and the remote client will be running SQL Server 2005
> Express.
>...
> A message comes up for each user I have specified (three in the last
> case) saying "Setting the snapshot share permissions (error)" and then
> "The operation completed successfully. (Exception from HRESULT:
> 0x8007) (mscorlib)" for each user.
>
I think problem solved but just in case anyone else comes across the
same thing (I have seen a few similar post with no resolution) the
change that seemed to make the difference was the specification of the
location of the snapshot folder. I clicked on the "Browse..." button
to specify the location but this does not seem to insert the correct
reference - it gives the full path - I changed this to //ServerName/
ShareName and the wizard complete OK.
I hope this was of use to someone.