Someone here inadvertantly removed the distribution database leaving the
replication configs hosed & also some orphan publications. I figured out how
to clean all that up using the repl stored procs & the @.ignore_distributor
flag. Now, however we are unable to re-configure replication - can someone
please help? When trying to configure replication thru server properties it
gets to the configure distributor step & we get "SQL Ent Mgr could not
configure <server> as the Distributor for <server> - Error 14114: 'null' is
not configured as a Distributor - any help is greatly appreciated - thanks!
John F.
I got it, sorry to post & answer my own question - the servername was 'null'
so a simple sp_addserver fixed it - *DOH*
John F.
"John F." wrote:
> Someone here inadvertantly removed the distribution database leaving the
> replication configs hosed & also some orphan publications. I figured out how
> to clean all that up using the repl stored procs & the @.ignore_distributor
> flag. Now, however we are unable to re-configure replication - can someone
> please help? When trying to configure replication thru server properties it
> gets to the configure distributor step & we get "SQL Ent Mgr could not
> configure <server> as the Distributor for <server> - Error 14114: 'null' is
> not configured as a Distributor - any help is greatly appreciated - thanks!
> --
> John F.
|||John F. drukte met precisie uit :
> Someone here inadvertantly removed the distribution database leaving the
> replication configs hosed & also some orphan publications. I figured out how
> to clean all that up using the repl stored procs & the @.ignore_distributor
> flag. Now, however we are unable to re-configure replication - can someone
> please help? When trying to configure replication thru server properties it
> gets to the configure distributor step & we get "SQL Ent Mgr could not
> configure <server> as the Distributor for <server> - Error 14114: 'null' is
> not configured as a Distributor - any help is greatly appreciated - thanks!
Try :
exec sp_dropserver '<servername>'
GO
exec sp_addserver '<servername>','local'
GO
SELECT @.@.SERVERNAME
GO
You must STOP en START the SQL Server Service after this
(from www.sqlteam.com)
Showing posts with label replication. Show all posts
Showing posts with label replication. Show all posts
Thursday, March 29, 2012
Thursday, March 22, 2012
Can't Add Reference to Microsoft.SQLServer.RMO.dll
Hi All,
I'm trying to add a reference to this DLL in Visual Studio 2003 so I
can programmatically trigger replication. When I try and add the
reference I get the following exception:
"A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
\Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
not a valid assembly or COM component. Only assemblies with extension
'dll' and COM components can be referenced. Please make sure that the
file is accessible, and that it is a valid assembly or COM component."
As you can see it does have a .dll extension.
The file I try to reference indicates it was created on 14 October
2005, 03:43:34 and is version 9.0.1399.0
C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
\Microsoft.SqlServer.Rmo.dll
Can I doenload another version of the DLL from somewhere?
Any help appreciated!
Thanks
Rajl
On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
> Hi All,
> I'm trying to add a reference to this DLL in Visual Studio 2003 so I
> can programmatically trigger replication. When I try and add the
> reference I get the following exception:
> "A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
> \Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
> not a valid assembly or COM component. Only assemblies with extension
> 'dll' and COM components can be referenced. Please make sure that the
> file is accessible, and that it is a valid assembly or COM component."
> As you can see it does have a .dll extension.
> The file I try to reference indicates it was created on 14 October
> 2005, 03:43:34 and is version 9.0.1399.0
> C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
> \Microsoft.SqlServer.Rmo.dll
> Can I doenload another version of the DLL from somewhere?
> Any help appreciated!
> Thanks
> Rajl
Also got a newer version of the file version 9.0.242.0, created 10th
Feb 2007 but that has the same problem
|||On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
>
>
>
>
>
>
>
> Also got a newer version of the file version 9.0.242.0, created 10th
> Feb 2007 but that has the same problem- Hide quoted text -
> - Show quoted text -
OK, this is resolved now. I think the issue is to do with the fact I'm
using VS2003. I tried adding the reference to a VS2005 project and
that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
not compatible against VS2003?
|||If you want to programmatically start replication, you probably will also
need to add a reference to the "Replication Agent Library" assembly.
For more information, see
http://msdn2.microsoft.com/de-de/library/ms146869.aspx.
Cheers!
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"rajpatel50@.hotmail.com" wrote:
> On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> OK, this is resolved now. I think the issue is to do with the fact I'm
> using VS2003. I tried adding the reference to a VS2005 project and
> that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
> not compatible against VS2003?
>
I'm trying to add a reference to this DLL in Visual Studio 2003 so I
can programmatically trigger replication. When I try and add the
reference I get the following exception:
"A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
\Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
not a valid assembly or COM component. Only assemblies with extension
'dll' and COM components can be referenced. Please make sure that the
file is accessible, and that it is a valid assembly or COM component."
As you can see it does have a .dll extension.
The file I try to reference indicates it was created on 14 October
2005, 03:43:34 and is version 9.0.1399.0
C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
\Microsoft.SqlServer.Rmo.dll
Can I doenload another version of the DLL from somewhere?
Any help appreciated!
Thanks
Rajl
On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
> Hi All,
> I'm trying to add a reference to this DLL in Visual Studio 2003 so I
> can programmatically trigger replication. When I try and add the
> reference I get the following exception:
> "A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
> \Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
> not a valid assembly or COM component. Only assemblies with extension
> 'dll' and COM components can be referenced. Please make sure that the
> file is accessible, and that it is a valid assembly or COM component."
> As you can see it does have a .dll extension.
> The file I try to reference indicates it was created on 14 October
> 2005, 03:43:34 and is version 9.0.1399.0
> C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
> \Microsoft.SqlServer.Rmo.dll
> Can I doenload another version of the DLL from somewhere?
> Any help appreciated!
> Thanks
> Rajl
Also got a newer version of the file version 9.0.242.0, created 10th
Feb 2007 but that has the same problem
|||On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
>
>
>
>
>
>
>
> Also got a newer version of the file version 9.0.242.0, created 10th
> Feb 2007 but that has the same problem- Hide quoted text -
> - Show quoted text -
OK, this is resolved now. I think the issue is to do with the fact I'm
using VS2003. I tried adding the reference to a VS2005 project and
that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
not compatible against VS2003?
|||If you want to programmatically start replication, you probably will also
need to add a reference to the "Replication Agent Library" assembly.
For more information, see
http://msdn2.microsoft.com/de-de/library/ms146869.aspx.
Cheers!
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"rajpatel50@.hotmail.com" wrote:
> On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> OK, this is resolved now. I think the issue is to do with the fact I'm
> using VS2003. I tried adding the reference to a VS2005 project and
> that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
> not compatible against VS2003?
>
Monday, March 19, 2012
can't "allow peer to peer" - SQL Server 2005
I'm trying to set up the first distribution server for a peer to peer transactional replication (updateable subscription) between two SQL Server 2005 instances on one machine (for testing). Can this be done without "virtual servers", and if so how do I enable the "Allow peer-to-peer subscriptions" option in the Subscription Options folder of the Publication Properties dialog box?
I've got:
Independent Distribution Agent True (not selectable)
Allow anonymous subscriptions False
Attachable subscription database False
Allow pull subscriptions False
Allow initialization from backup files True
Allow non-SQL Server Subscribers False
Allow data transformations False (not selectable)
Replicate schema changes True
Allow peer-to-peer subscriptions False (not selectable)
Allow immediate updating subscriptions True (not selectable)
Allow queued updating subscriptions True (not selectable)
Report conflicts centrally True
Conflict resolution policy Keep the Publisher
I've tried various combinations of options, but think these are correct. Also, the snapshot database is in a local (not network) directory; I got a warning on this, although in this special case the snapshot should be available to both instances.
Thanks...
I applied SQL Server 2005 SP1 and the problem went away!
Liston
Thursday, March 8, 2012
Cannot update replication once live - have to recreate!
I have set up a transactional replication from SQL2000 (W2K) to SQL2005
(W2K3). Once it's running, if I add a new field to the publisher, it doesn't
appear in the subscriber tables. I have tried everything including
re-inititalising the job, stopping and starting agents - nothing works. All I
am left with is deleting then recreating the entire replication job which is
time consuming and annoying.
Somebody out there must have the answer to me inadequacy!
Thanks in advance,
Will, Leeds UK
Will,
I need to understand how you did this. How did you add the new field? Did
you use sp_repladdcolumn?
Also, when you say reinitializing the job I'm not sure what you mean. Do you
mean restart the snapshot agent? If so, this is not reinitialization. If the
subscription is marked for reinitialization, this is something different.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi, basically we replicate live databases onto a separate server for
reporting. Occasionally we modify the live database (add a new field say) and
need the replication job to reflect this change. At the moment, every time we
make a change we have to remove replication, delete the reporting database
copy, then re-add replication. The live databases are on SQL 2000 and
reporting copies on SQL2005.
I haven't tried sp_repladdcolumn yet. I have just been using various actions
from SQL Management Studio.
I am a little confused as to the 'official method' to achieve what I want!
What I do know is that our current method works BUT is very tedious...
Thanks
Will
"Paul Ibison" wrote:
> Will,
> I need to understand how you did this. How did you add the new field? Did
> you use sp_repladdcolumn?
> Also, when you say reinitializing the job I'm not sure what you mean. Do you
> mean restart the snapshot agent? If so, this is not reinitialization. If the
> subscription is marked for reinitialization, this is something different.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
(W2K3). Once it's running, if I add a new field to the publisher, it doesn't
appear in the subscriber tables. I have tried everything including
re-inititalising the job, stopping and starting agents - nothing works. All I
am left with is deleting then recreating the entire replication job which is
time consuming and annoying.
Somebody out there must have the answer to me inadequacy!
Thanks in advance,
Will, Leeds UK
Will,
I need to understand how you did this. How did you add the new field? Did
you use sp_repladdcolumn?
Also, when you say reinitializing the job I'm not sure what you mean. Do you
mean restart the snapshot agent? If so, this is not reinitialization. If the
subscription is marked for reinitialization, this is something different.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi, basically we replicate live databases onto a separate server for
reporting. Occasionally we modify the live database (add a new field say) and
need the replication job to reflect this change. At the moment, every time we
make a change we have to remove replication, delete the reporting database
copy, then re-add replication. The live databases are on SQL 2000 and
reporting copies on SQL2005.
I haven't tried sp_repladdcolumn yet. I have just been using various actions
from SQL Management Studio.
I am a little confused as to the 'official method' to achieve what I want!
What I do know is that our current method works BUT is very tedious...
Thanks
Will
"Paul Ibison" wrote:
> Will,
> I need to understand how you did this. How did you add the new field? Did
> you use sp_repladdcolumn?
> Also, when you say reinitializing the job I'm not sure what you mean. Do you
> mean restart the snapshot agent? If so, this is not reinitialization. If the
> subscription is marked for reinitialization, this is something different.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
Cannot Update Identity Column 'xxxx'
Hi,
I have transaction replication setup and the initial snap shot works fine. However after that updates are giving me the above error. Any help would be appreciated. Thanks.
Jeff
Jeff,
this error is not specific to replication - updates of identity columns are
prohibited in all cases, even when the table isn't published (there's a set
IDENTITY_INSERT on but no set IDENTITY_UPDATE on).
HTH,
Paul Ibison
|||Look at the table on the subscriber and verify that the identity column on
the table has the NOT FOR REPLICATION option set. Based on the error, I
would say it does not. Turn this on and see if that resolves the problem.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have transaction replication setup and the initial snap shot works fine. However after that updates are giving me the above error. Any help would be appreciated. Thanks.
Jeff
Jeff,
this error is not specific to replication - updates of identity columns are
prohibited in all cases, even when the table isn't published (there's a set
IDENTITY_INSERT on but no set IDENTITY_UPDATE on).
HTH,
Paul Ibison
|||Look at the table on the subscriber and verify that the identity column on
the table has the NOT FOR REPLICATION option set. Based on the error, I
would say it does not. Turn this on and see if that resolves the problem.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Cannot truncate table because it is being referenced by another ob
I recieve the following error after configuring replication between two servers. I am not sure how to resolve it. Does anyone have any ideas?
Thanks in advance,
Peter
Cannot TRUNCATE TABLE 'TwAccType' because it is being referenced by object 'TwAccTypeUserNotNull'.
(Source: TUMIME2 (Data source); Error number: 3729)
Event Type:Information
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:203
Date:6/15/2004
Time:10:42:06 AM
User:N/A
Computer:TUMIME1
Description:
SubSystem Message - Job 'TUMIME1-IME-TUMIME2-2' (0x73197FC085876B4BB39379788ECBA652), step 2 - Cannot TRUNCATE TABLE 'TwAccType' because it is being referenced by object 'TwAccTypeUserNotNull'.
Thanks Paul-
I will get back to you.
"Paul Ibison" wrote:
> Truncate Table can't be done if the table has FKs
> depending on it. If you look on the article properties,
> snapshot tab there is a naming conflicts section. Is yours
> set to 'Delete all data in existing table?'. If so then
> this is the cause of your error. You could drop the
> constraint in a pre-script and add it back if nesessary in
> a postscript. These options are available on the
> Publication Properties, Snapshot Tab.
> HTH,
> Paul Ibison
>
Thanks in advance,
Peter
Cannot TRUNCATE TABLE 'TwAccType' because it is being referenced by object 'TwAccTypeUserNotNull'.
(Source: TUMIME2 (Data source); Error number: 3729)
Event Type:Information
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:203
Date:6/15/2004
Time:10:42:06 AM
User:N/A
Computer:TUMIME1
Description:
SubSystem Message - Job 'TUMIME1-IME-TUMIME2-2' (0x73197FC085876B4BB39379788ECBA652), step 2 - Cannot TRUNCATE TABLE 'TwAccType' because it is being referenced by object 'TwAccTypeUserNotNull'.
Thanks Paul-
I will get back to you.
"Paul Ibison" wrote:
> Truncate Table can't be done if the table has FKs
> depending on it. If you look on the article properties,
> snapshot tab there is a naming conflicts section. Is yours
> set to 'Delete all data in existing table?'. If so then
> this is the cause of your error. You could drop the
> constraint in a pre-script and add it back if nesessary in
> a postscript. These options are available on the
> Publication Properties, Snapshot Tab.
> HTH,
> Paul Ibison
>
Saturday, February 25, 2012
Cannot start Log Reader Agent and Snapshot Agent
I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.
For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).
This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"
Any ideas?
Also this domain account is a member of
SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER
SQLServer2005MSAgentUser$ServerName$MSSQLSERVER
Sunday, February 19, 2012
cannot set name conflicts
For a snapshot replication.
I set the Name conflicts from the defualt-DROP the existing tables and
re-create it
to Delete All data in the existing table.
and set check in Include declared refertial integrity in Copy objects to
destination secton.
After I close these perperties window and reopen the publiction property
window to check the property on snapshop tab on article properties. I found
both the properties goes back to default values again
I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also which
sp?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chen" <mxchen100@.hotmail.com> wrote in message
news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
> For a snapshot replication.
> I set the Name conflicts from the defualt-DROP the existing tables and
> re-create it
> to Delete All data in the existing table.
> and set check in Include declared refertial integrity in Copy objects to
> destination secton.
> After I close these perperties window and reopen the publiction property
> window to check the property on snapshop tab on article properties. I
found
> both the properties goes back to default values again
>
>
|||on SQL 2000
Table
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also
which[vbcol=seagreen]
> sp?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Chen" <mxchen100@.hotmail.com> wrote in message
> news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
property
> found
>
>
|||which sp? can you do a select @.@.version from QA?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chen" <mxchen100@.hotmail.com> wrote in message
news:uUXNF7w2FHA.2292@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> on SQL 2000
> Table
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> which
to
> property
>
>
I set the Name conflicts from the defualt-DROP the existing tables and
re-create it
to Delete All data in the existing table.
and set check in Include declared refertial integrity in Copy objects to
destination secton.
After I close these perperties window and reopen the publiction property
window to check the property on snapshop tab on article properties. I found
both the properties goes back to default values again
I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also which
sp?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chen" <mxchen100@.hotmail.com> wrote in message
news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
> For a snapshot replication.
> I set the Name conflicts from the defualt-DROP the existing tables and
> re-create it
> to Delete All data in the existing table.
> and set check in Include declared refertial integrity in Copy objects to
> destination secton.
> After I close these perperties window and reopen the publiction property
> window to check the property on snapshop tab on article properties. I
found
> both the properties goes back to default values again
>
>
|||on SQL 2000
Table
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also
which[vbcol=seagreen]
> sp?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Chen" <mxchen100@.hotmail.com> wrote in message
> news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
property
> found
>
>
|||which sp? can you do a select @.@.version from QA?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chen" <mxchen100@.hotmail.com> wrote in message
news:uUXNF7w2FHA.2292@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> on SQL 2000
> Table
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> which
to
> property
>
>
Sunday, February 12, 2012
Cannot run snapshot agent from command line
I have a transactional replication running and it's running well.
But now i'm writing a script so I can start the Snapshot Agent from
distance. therefore I want to run it from the command prompt.
I'm using this command: C:\Program Files\Microsoft SQL Server\80\COM
\snapshot.exe -Publisher <server> -PublisherDB <pubDB> -Publication
<pub> -DistributorLogin <login> -DistributorPassword <pwd>
And this is my output:
==== Output start ======
Microsoft SQL Server Snapshot Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
The process could not create file '\\<server>\ReplData\unc'.
Finished with exit code 2
==== Output end ======
When I start the agent from SQL Server itself it works fine.
the location of the snapshot folder is defined as '\\<server>
\ReplData' and (for testing now) this folder has full access.
Can somebody tell mee what;s going wrong and what I can do about it?
Can you create your command as text in a batch file then use RunAs (or log on
again if RunAs is disabled). The user to select is the sql server agent
login...
HTH,
Paul Ibison
|||You need to check to ensure that the share permissions are full for the
account which the SQL Server Agent runs under, or the account the snapshot
agent is proxied under, and the underlying security is full for the path and
all child objects.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"acsnaterse" <snaterse@.gmail.com> wrote in message
news:1184079506.481076.126000@.22g2000hsm.googlegro ups.com...
>I have a transactional replication running and it's running well.
> But now i'm writing a script so I can start the Snapshot Agent from
> distance. therefore I want to run it from the command prompt.
> I'm using this command: C:\Program Files\Microsoft SQL Server\80\COM
> \snapshot.exe -Publisher <server> -PublisherDB <pubDB> -Publication
> <pub> -DistributorLogin <login> -DistributorPassword <pwd>
> And this is my output:
> ==== Output start ======
> Microsoft SQL Server Snapshot Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> The process could not create file '\\<server>\ReplData\unc'.
> Finished with exit code 2
> ==== Output end ======
> When I start the agent from SQL Server itself it works fine.
> the location of the snapshot folder is defined as '\\<server>
> \ReplData' and (for testing now) this folder has full access.
> Can somebody tell mee what;s going wrong and what I can do about it?
>
|||On 10 jul, 17:58, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
> Can you create your command as text in a batch file then use RunAs (or log on
> again if RunAs is disabled). The user to select is the sql server agent
> login...
> HTH,
> Paul Ibison
Hi,
Thanks! With the runas commando it works great!
Hint: in combination with Sanur (http://www.commandline.co.uk/
sanur_unsupported/index3.html) you can automate the password fill-in.
But now i'm writing a script so I can start the Snapshot Agent from
distance. therefore I want to run it from the command prompt.
I'm using this command: C:\Program Files\Microsoft SQL Server\80\COM
\snapshot.exe -Publisher <server> -PublisherDB <pubDB> -Publication
<pub> -DistributorLogin <login> -DistributorPassword <pwd>
And this is my output:
==== Output start ======
Microsoft SQL Server Snapshot Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
The process could not create file '\\<server>\ReplData\unc'.
Finished with exit code 2
==== Output end ======
When I start the agent from SQL Server itself it works fine.
the location of the snapshot folder is defined as '\\<server>
\ReplData' and (for testing now) this folder has full access.
Can somebody tell mee what;s going wrong and what I can do about it?
Can you create your command as text in a batch file then use RunAs (or log on
again if RunAs is disabled). The user to select is the sql server agent
login...
HTH,
Paul Ibison
|||You need to check to ensure that the share permissions are full for the
account which the SQL Server Agent runs under, or the account the snapshot
agent is proxied under, and the underlying security is full for the path and
all child objects.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"acsnaterse" <snaterse@.gmail.com> wrote in message
news:1184079506.481076.126000@.22g2000hsm.googlegro ups.com...
>I have a transactional replication running and it's running well.
> But now i'm writing a script so I can start the Snapshot Agent from
> distance. therefore I want to run it from the command prompt.
> I'm using this command: C:\Program Files\Microsoft SQL Server\80\COM
> \snapshot.exe -Publisher <server> -PublisherDB <pubDB> -Publication
> <pub> -DistributorLogin <login> -DistributorPassword <pwd>
> And this is my output:
> ==== Output start ======
> Microsoft SQL Server Snapshot Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> The process could not create file '\\<server>\ReplData\unc'.
> Finished with exit code 2
> ==== Output end ======
> When I start the agent from SQL Server itself it works fine.
> the location of the snapshot folder is defined as '\\<server>
> \ReplData' and (for testing now) this folder has full access.
> Can somebody tell mee what;s going wrong and what I can do about it?
>
|||On 10 jul, 17:58, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
> Can you create your command as text in a batch file then use RunAs (or log on
> again if RunAs is disabled). The user to select is the sql server agent
> login...
> HTH,
> Paul Ibison
Hi,
Thanks! With the runas commando it works great!
Hint: in combination with Sanur (http://www.commandline.co.uk/
sanur_unsupported/index3.html) you can automate the password fill-in.
Cannot Run Replication Setup From EM in SQL server 2000 EE
When we try to run the Configure Publishers, Subscribers, and Distribution
from the EM Wizrd, we get the Error 208 invalid Object
msdb.dbo.MSDitsributiondbs and the setup quits. The server is a Cluster,
with Log Shipping. Select @.@.Servername returns the correct server name. The
interesting thing is that we have three other servers with the same
configuration that are working just fine.Any ideas? Thanks.
Is this table present in msdb?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
news:uNhWwMi$FHA.912@.TK2MSFTNGP11.phx.gbl...
> When we try to run the Configure Publishers, Subscribers, and Distribution
> from the EM Wizrd, we get the Error 208 invalid Object
> msdb.dbo.MSDitsributiondbs and the setup quits. The server is a Cluster,
> with Log Shipping. Select @.@.Servername returns the correct server name.
> The
> interesting thing is that we have three other servers with the same
> configuration that are working just fine.Any ideas? Thanks.
>
|||No the table is not. I see the table in the stand alone servers that we have
Transactional Replication running on but not on the SQL Server 2000 Clusters
which are also running replication. This is the puzzle for us. By the way
good book you put out Hilary. Do you plan one for SQL 2005? if so please
hurry up!
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ev75WZl$FHA.2156@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Is this table present in msdb?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
> news:uNhWwMi$FHA.912@.TK2MSFTNGP11.phx.gbl...
Distribution
>
|||There is something very wrong with the latest sp upgrade. Please reapply it.
I have to push out the SQL 2000 merge volume before 2005.
I am working on some tutorials for SQL 2005 replication for sswug.com.
I think I knew you from swynk.com in one of the nt groups.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
news:u3KclHp$FHA.1600@.TK2MSFTNGP11.phx.gbl...
> No the table is not. I see the table in the stand alone servers that we
> have
> Transactional Replication running on but not on the SQL Server 2000
> Clusters
> which are also running replication. This is the puzzle for us. By the way
> good book you put out Hilary. Do you plan one for SQL 2005? if so please
> hurry up!
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ev75WZl$FHA.2156@.TK2MSFTNGP11.phx.gbl...
> Distribution
>
|||The server is SP4 on Win2k Adv Svr. Are you suggesting re-applying the SP4?
Becuase that is the revision level that it is at now. It is a production
server with clusterign and log shipping on it already. So we are beign
cautious here. I remember you too from the early Stven Wynkoop Days. It dont
visit as often as it has taken a different tone as a site. Just an old DBA
here.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OYrMgxy$FHA.3852@.TK2MSFTNGP14.phx.gbl...
> There is something very wrong with the latest sp upgrade. Please reapply
it.[vbcol=seagreen]
> I have to push out the SQL 2000 merge volume before 2005.
> I am working on some tutorials for SQL 2005 replication for sswug.com.
> I think I knew you from swynk.com in one of the nt groups.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
> news:u3KclHp$FHA.1600@.TK2MSFTNGP11.phx.gbl...
way[vbcol=seagreen]
name.
>
|||I am looking for information from others that may have run into issues with
SP4 and SQL Server 2000 Replication. I am suspicious that this may have been
the culprit in my inablility to configure publishing on one of my servers.
Please share you knowledge on this one. Thanks.
"Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
news:uIY$sg6$FHA.2736@.TK2MSFTNGP11.phx.gbl...
> The server is SP4 on Win2k Adv Svr. Are you suggesting re-applying the
SP4?
> Becuase that is the revision level that it is at now. It is a production
> server with clusterign and log shipping on it already. So we are beign
> cautious here. I remember you too from the early Stven Wynkoop Days. It
dont[vbcol=seagreen]
> visit as often as it has taken a different tone as a site. Just an old DBA
> here.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OYrMgxy$FHA.3852@.TK2MSFTNGP14.phx.gbl...
> it.
we[vbcol=seagreen]
> way
please
> name.
>
from the EM Wizrd, we get the Error 208 invalid Object
msdb.dbo.MSDitsributiondbs and the setup quits. The server is a Cluster,
with Log Shipping. Select @.@.Servername returns the correct server name. The
interesting thing is that we have three other servers with the same
configuration that are working just fine.Any ideas? Thanks.
Is this table present in msdb?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
news:uNhWwMi$FHA.912@.TK2MSFTNGP11.phx.gbl...
> When we try to run the Configure Publishers, Subscribers, and Distribution
> from the EM Wizrd, we get the Error 208 invalid Object
> msdb.dbo.MSDitsributiondbs and the setup quits. The server is a Cluster,
> with Log Shipping. Select @.@.Servername returns the correct server name.
> The
> interesting thing is that we have three other servers with the same
> configuration that are working just fine.Any ideas? Thanks.
>
|||No the table is not. I see the table in the stand alone servers that we have
Transactional Replication running on but not on the SQL Server 2000 Clusters
which are also running replication. This is the puzzle for us. By the way
good book you put out Hilary. Do you plan one for SQL 2005? if so please
hurry up!
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ev75WZl$FHA.2156@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Is this table present in msdb?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
> news:uNhWwMi$FHA.912@.TK2MSFTNGP11.phx.gbl...
Distribution
>
|||There is something very wrong with the latest sp upgrade. Please reapply it.
I have to push out the SQL 2000 merge volume before 2005.
I am working on some tutorials for SQL 2005 replication for sswug.com.
I think I knew you from swynk.com in one of the nt groups.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
news:u3KclHp$FHA.1600@.TK2MSFTNGP11.phx.gbl...
> No the table is not. I see the table in the stand alone servers that we
> have
> Transactional Replication running on but not on the SQL Server 2000
> Clusters
> which are also running replication. This is the puzzle for us. By the way
> good book you put out Hilary. Do you plan one for SQL 2005? if so please
> hurry up!
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ev75WZl$FHA.2156@.TK2MSFTNGP11.phx.gbl...
> Distribution
>
|||The server is SP4 on Win2k Adv Svr. Are you suggesting re-applying the SP4?
Becuase that is the revision level that it is at now. It is a production
server with clusterign and log shipping on it already. So we are beign
cautious here. I remember you too from the early Stven Wynkoop Days. It dont
visit as often as it has taken a different tone as a site. Just an old DBA
here.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OYrMgxy$FHA.3852@.TK2MSFTNGP14.phx.gbl...
> There is something very wrong with the latest sp upgrade. Please reapply
it.[vbcol=seagreen]
> I have to push out the SQL 2000 merge volume before 2005.
> I am working on some tutorials for SQL 2005 replication for sswug.com.
> I think I knew you from swynk.com in one of the nt groups.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
> news:u3KclHp$FHA.1600@.TK2MSFTNGP11.phx.gbl...
way[vbcol=seagreen]
name.
>
|||I am looking for information from others that may have run into issues with
SP4 and SQL Server 2000 Replication. I am suspicious that this may have been
the culprit in my inablility to configure publishing on one of my servers.
Please share you knowledge on this one. Thanks.
"Patrick Ikhifa" <patisi@.pacbell.net> wrote in message
news:uIY$sg6$FHA.2736@.TK2MSFTNGP11.phx.gbl...
> The server is SP4 on Win2k Adv Svr. Are you suggesting re-applying the
SP4?
> Becuase that is the revision level that it is at now. It is a production
> server with clusterign and log shipping on it already. So we are beign
> cautious here. I remember you too from the early Stven Wynkoop Days. It
dont[vbcol=seagreen]
> visit as often as it has taken a different tone as a site. Just an old DBA
> here.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OYrMgxy$FHA.3852@.TK2MSFTNGP14.phx.gbl...
> it.
we[vbcol=seagreen]
> way
please
> name.
>
Subscribe to:
Posts (Atom)