When I try to create a transactional publication, when I select the table I
want to replicate, I get the error "This table cannot be published because it
does not have a primary key column. Primary key columns are required for all
tables in transactional publications".
Then When I try to make the necessary changes to the table, such as adding a
column for the primary key, I get the error "Unable to modify table. Cannot
drop the table "tablename" because it is being used for replication."
I have never successfully replicated this table or any other. I can find no
evidence of any publications to remove.
I'm stuck!
Just answered my own question after reading thru a ton of posts on this forum.
"run sp_removedbreplication on each database..."
Thanks Paul Ibison!
"TahoePete" wrote:
> When I try to create a transactional publication, when I select the table I
> want to replicate, I get the error "This table cannot be published because it
> does not have a primary key column. Primary key columns are required for all
> tables in transactional publications".
> Then When I try to make the necessary changes to the table, such as adding a
> column for the primary key, I get the error "Unable to modify table. Cannot
> drop the table "tablename" because it is being used for replication."
> I have never successfully replicated this table or any other. I can find no
> evidence of any publications to remove.
> I'm stuck!
>
|||Issue the following statements
sp_MSunmarkreplinfo 'ProblemTableName'
Then you need to update the colstat column
sp_configure 'allow updates', 1
go
reconfigure with override
go
UPDATE syscolumns
SET colstat = colstat & ~4096
WHERE colstat & 4096 <>0
go
sp_configure 'allow updates', 2
go
reconfigure with override
go
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
"TahoePete" <TahoePete@.discussions.microsoft.com> wrote in message
news:346CE295-5031-45F3-90DA-9CA7A25424A5@.microsoft.com...
> When I try to create a transactional publication, when I select the table
> I
> want to replicate, I get the error "This table cannot be published because
> it
> does not have a primary key column. Primary key columns are required for
> all
> tables in transactional publications".
> Then When I try to make the necessary changes to the table, such as adding
> a
> column for the primary key, I get the error "Unable to modify table.
> Cannot
> drop the table "tablename" because it is being used for replication."
> I have never successfully replicated this table or any other. I can find
> no
> evidence of any publications to remove.
> I'm stuck!
>
|||I receive the error "ad hoc updates to system catalogues are not allowed"
from the update command.
"Hilary Cotter" wrote:
> Issue the following statements
> sp_MSunmarkreplinfo 'ProblemTableName'
> Then you need to update the colstat column
> sp_configure 'allow updates', 1
> go
> reconfigure with override
> go
> UPDATE syscolumns
> SET colstat = colstat & ~4096
> WHERE colstat & 4096 <>0
> go
> sp_configure 'allow updates', 2
> go
> reconfigure with override
> go
>
> --
> 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
> "TahoePete" <TahoePete@.discussions.microsoft.com> wrote in message
> news:346CE295-5031-45F3-90DA-9CA7A25424A5@.microsoft.com...
>
>
|||I'm not sure what is wrong here - this command should enable this
sp_configure 'allow updates', 1
go
reconfigure with override
go
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
"TahoePete" <TahoePete@.discussions.microsoft.com> wrote in message
news:793A5914-F3E9-4195-9F70-BA7C544E4427@.microsoft.com...[vbcol=seagreen]
>I receive the error "ad hoc updates to system catalogues are not allowed"
> from the update command.
> "Hilary Cotter" wrote:
Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts
Friday, March 30, 2012
Replication Errors
Hello,
I am getting the following error when trying to sync from my local site to
my dr site.
Could not locate entry in sysdatabases for database '10.1.200.70'. No entry
found with that name. Make sure that the name is entered correctly.
(Source: 10.1.200.70 (Data source); Error number: 911)
I am trying to setup replication from my local site to my DR site. I can
register my dr sql box using the IP but not the hostname.
Any thoughts on this error?
Lontae,
try creating an alias for the server's IP address. You might also need an
entry in the hosts/lmhosts (I can't remember which
to locate the snapshot
share.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Alias in DNS?
"Paul Ibison" wrote:
> Lontae,
> try creating an alias for the server's IP address. You might also need an
> entry in the hosts/lmhosts (I can't remember which to locate the snapshot
> share.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Lontae,
alias in the server network utility (I'm sure you now this but if not it's
located at start, programs, microsoft sql server...).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I think Paul means client network utility
Easy mistake to make, I've made it thousands of times, myself.
For netbios resolution use lmhosts (ie a unc snapshot), for ftp use hosts.
name resolution goes through a sequence so it really doesn't matter as both
files are checked, but there are slight performance increases (milli
seconds) if you make the correct entries.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:umx%23oCGvEHA.940@.TK2MSFTNGP14.phx.gbl...
> Lontae,
> alias in the server network utility (I'm sure you now this but if not it's
> located at start, programs, microsoft sql server...).
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks Hilary,
I'm not sure about the setup, but Lontae is registering
the DR site at the local site so I was thinking it was
push rather than pull.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I am getting the following error when trying to sync from my local site to
my dr site.
Could not locate entry in sysdatabases for database '10.1.200.70'. No entry
found with that name. Make sure that the name is entered correctly.
(Source: 10.1.200.70 (Data source); Error number: 911)
I am trying to setup replication from my local site to my DR site. I can
register my dr sql box using the IP but not the hostname.
Any thoughts on this error?
Lontae,
try creating an alias for the server's IP address. You might also need an
entry in the hosts/lmhosts (I can't remember which
to locate the snapshotshare.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Alias in DNS?
"Paul Ibison" wrote:
> Lontae,
> try creating an alias for the server's IP address. You might also need an
> entry in the hosts/lmhosts (I can't remember which
to locate the snapshot> share.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Lontae,
alias in the server network utility (I'm sure you now this but if not it's
located at start, programs, microsoft sql server...).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I think Paul means client network utility
Easy mistake to make, I've made it thousands of times, myself.
For netbios resolution use lmhosts (ie a unc snapshot), for ftp use hosts.
name resolution goes through a sequence so it really doesn't matter as both
files are checked, but there are slight performance increases (milli
seconds) if you make the correct entries.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:umx%23oCGvEHA.940@.TK2MSFTNGP14.phx.gbl...
> Lontae,
> alias in the server network utility (I'm sure you now this but if not it's
> located at start, programs, microsoft sql server...).
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks Hilary,
I'm not sure about the setup, but Lontae is registering
the DR site at the local site so I was thinking it was
push rather than pull.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Replication Errors
I have three questions?
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions?
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account? Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.
See inline
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions?
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions?
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account? Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions?
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account? Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.
See inline
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions?
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions?
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account? Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>
Replication Errors
I have three questions'
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions'
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account' Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.See inline
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions'
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions'
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account' Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>sql
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions'
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account' Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.See inline
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions'
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions'
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account' Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>sql
Replication Errors
I have three questions?
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions?
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account? Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.
Hi Shash Goyal,
Most of your problems relate to having registered your server as "(local)"
in Enterprise Manager. Try reregistering it as the name of your computer
instead. I think that will fix problems 1 and 2. With the 3rd one, all it's
trying to tell you is that if you want to connect to anything outside your
computer, you normally need a domain user account. The "Local Service"
account is a special account on your computer that only applies to that
computer. Try creating a new user that will be used only as a service
account (ie something like "sqlservice" for a name). Make it a domain user
if you are in a domain. Give it appropriate permissions and change SQL
Server and SQL Agent to run as that user (you can do this by right-clicking
each in Enterprise Manager) and choosing the "Security" option.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:%23j6aiu5vEHA.3080@.TK2MSFTNGP12.phx.gbl...
>I have three questions?
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
> replication
> on this instance?
>
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
> goes
> out and looks for the subscription, I tried to remove the subscription,
> but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
> to
> remove this subscriptions?
> 3. When i try to configure the Replication, its says that Server Agent
> uses
> the local service account you need to change the account? Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
>
> Thanks for all your help.
>
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions?
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account? Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.
Hi Shash Goyal,
Most of your problems relate to having registered your server as "(local)"
in Enterprise Manager. Try reregistering it as the name of your computer
instead. I think that will fix problems 1 and 2. With the 3rd one, all it's
trying to tell you is that if you want to connect to anything outside your
computer, you normally need a domain user account. The "Local Service"
account is a special account on your computer that only applies to that
computer. Try creating a new user that will be used only as a service
account (ie something like "sqlservice" for a name). Make it a domain user
if you are in a domain. Give it appropriate permissions and change SQL
Server and SQL Agent to run as that user (you can do this by right-clicking
each in Enterprise Manager) and choosing the "Security" option.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:%23j6aiu5vEHA.3080@.TK2MSFTNGP12.phx.gbl...
>I have three questions?
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
> replication
> on this instance?
>
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
> goes
> out and looks for the subscription, I tried to remove the subscription,
> but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
> to
> remove this subscriptions?
> 3. When i try to configure the Replication, its says that Server Agent
> uses
> the local service account you need to change the account? Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
>
> Thanks for all your help.
>
Replication errors
I have been trying to get replication to work and have been having
nothing but problems.
I have a bunch of jobs set up in my EM and they all have red circles
with an X through it ( I assume this is because they all failed).
I have been trying to set up the publisher and distributer on the same
server.
Here is one of the jobs I can't get to work. I get an error on the
first step if I copy it to Query and run it. But when I right click the
job and look at the history I get the following message:
The job failed. The Job was invoked by User DINO\tfs. The last step to
run was step 3 (Detect nonlogged agent shutdown.).
According to this, I assume that it got to step 3 and died, but if I run
the Query (as I mentioned), it dies at step 1. The error I got was:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
If it couldn't find the stored procedure in Query, how could it find it
in the Job I ran?
Here are the steps that are running.
*******************************************************************
Step 1
Step Name: Log agent startup message.
Type: Transact-SQL Script(TSQL)
Database: Distribution
sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
@.runstatus = 1,
@.comments = 'Starting agent.'
I get an error here when running here from Query:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
Step 2
Step Name: Run Agent
Type: Replication Snapshot
Database: Distribution
-Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
-Publication [Northwind] -DistributorSecurityMode 1
Step 3
Step Name: Detect nonlogged agent shutdown.
Type: Transact-SQL Script(TSQL)
Database: Distribution
sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
***********************************************************************
The messages I get from history are not very helpful as it doesn't tell
me much. I had a job that got an error because a table didn't exist. I
know this because I tried it in Query. But the history of the job
always shows the same type of message. Just that the last step run was
X. But not why it died. Query knows why, why doesn't the Sql Agent?
Thanks,
Tom.Hi,
Check whether you can extract any information from the following url
http://www.cis.usouthal.edu/share/New%20Folder/Microsoft%20SQL%20Server/MSSQL/Install/instdist.sql
This contains the sp_MSdetect_nonlogged_shutdown stored procedure. At
present i am not able to provide any information coz i am unsure of the
setup you have installed there. I will try my best to sort this out.
Regards,
Jagan Mohan
"Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
news:3FC98D38.1020506@.deltanet.com...
> I have been trying to get replication to work and have been having
> nothing but problems.
> I have a bunch of jobs set up in my EM and they all have red circles
> with an X through it ( I assume this is because they all failed).
> I have been trying to set up the publisher and distributer on the same
> server.
> Here is one of the jobs I can't get to work. I get an error on the
> first step if I copy it to Query and run it. But when I right click the
> job and look at the history I get the following message:
> The job failed. The Job was invoked by User DINO\tfs. The last step to
> run was step 3 (Detect nonlogged agent shutdown.).
> According to this, I assume that it got to step 3 and died, but if I run
> the Query (as I mentioned), it dies at step 1. The error I got was:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>
> If it couldn't find the stored procedure in Query, how could it find it
> in the Job I ran?
> Here are the steps that are running.
> *******************************************************************
> Step 1
> Step Name: Log agent startup message.
> Type: Transact-SQL Script(TSQL)
> Database: Distribution
> sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
> @.runstatus = 1,
> @.comments = 'Starting agent.'
> I get an error here when running here from Query:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>
> Step 2
> Step Name: Run Agent
> Type: Replication Snapshot
> Database: Distribution
> -Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
> -Publication [Northwind] -DistributorSecurityMode 1
> Step 3
> Step Name: Detect nonlogged agent shutdown.
> Type: Transact-SQL Script(TSQL)
> Database: Distribution
> sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
> ***********************************************************************
> The messages I get from history are not very helpful as it doesn't tell
> me much. I had a job that got an error because a table didn't exist. I
> know this because I tried it in Query. But the history of the job
> always shows the same type of message. Just that the last step run was
> X. But not why it died. Query knows why, why doesn't the Sql Agent?
> Thanks,
> Tom.
>|||Jagan Mohan wrote:
> Hi,
> Check whether you can extract any information from the following url
> http://www.cis.usouthal.edu/share/New%20Folder/Microsoft%20SQL%20Server/MSSQL/Install/instdist.sql
> This contains the sp_MSdetect_nonlogged_shutdown stored procedure. At
> present i am not able to provide any information coz i am unsure of the
> setup you have installed there. I will try my best to sort this out.
I looked at it, but it won't tell me anything as the error says it can't
find the procedure. But the Server Agent got to the 3rd step, but
failed, so I assume it did step 1 correctly. Not sure what the
difference is.
> Regards,
> Jagan Mohan
> "Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
> news:3FC98D38.1020506@.deltanet.com...
>>I have been trying to get replication to work and have been having
>>nothing but problems.
>>I have a bunch of jobs set up in my EM and they all have red circles
>>with an X through it ( I assume this is because they all failed).
>>I have been trying to set up the publisher and distributer on the same
>>server.
>>Here is one of the jobs I can't get to work. I get an error on the
>>first step if I copy it to Query and run it. But when I right click the
>>job and look at the history I get the following message:
>>The job failed. The Job was invoked by User DINO\tfs. The last step to
>>run was step 3 (Detect nonlogged agent shutdown.).
>>According to this, I assume that it got to step 3 and died, but if I run
>>the Query (as I mentioned), it dies at step 1. The error I got was:
>>Server: Msg 2812, Level 16, State 62, Line 1
>>Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>>
>>If it couldn't find the stored procedure in Query, how could it find it
>>in the Job I ran?
>>Here are the steps that are running.
>>*******************************************************************
>>Step 1
>>Step Name: Log agent startup message.
>>Type: Transact-SQL Script(TSQL)
>>Database: Distribution
>>sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
>>@.runstatus = 1,
>>@.comments = 'Starting agent.'
>>I get an error here when running here from Query:
>>Server: Msg 2812, Level 16, State 62, Line 1
>>Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>>
>>Step 2
>>Step Name: Run Agent
>>Type: Replication Snapshot
>>Database: Distribution
>>-Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
>>-Publication [Northwind] -DistributorSecurityMode 1
>>Step 3
>>Step Name: Detect nonlogged agent shutdown.
>>Type: Transact-SQL Script(TSQL)
>>Database: Distribution
>>sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
>>***********************************************************************
>>The messages I get from history are not very helpful as it doesn't tell
>>me much. I had a job that got an error because a table didn't exist. I
>>know this because I tried it in Query. But the history of the job
>>always shows the same type of message. Just that the last step run was
>>X. But not why it died. Query knows why, why doesn't the Sql Agent?
>>Thanks,
>>Tom.
>>
>
nothing but problems.
I have a bunch of jobs set up in my EM and they all have red circles
with an X through it ( I assume this is because they all failed).
I have been trying to set up the publisher and distributer on the same
server.
Here is one of the jobs I can't get to work. I get an error on the
first step if I copy it to Query and run it. But when I right click the
job and look at the history I get the following message:
The job failed. The Job was invoked by User DINO\tfs. The last step to
run was step 3 (Detect nonlogged agent shutdown.).
According to this, I assume that it got to step 3 and died, but if I run
the Query (as I mentioned), it dies at step 1. The error I got was:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
If it couldn't find the stored procedure in Query, how could it find it
in the Job I ran?
Here are the steps that are running.
*******************************************************************
Step 1
Step Name: Log agent startup message.
Type: Transact-SQL Script(TSQL)
Database: Distribution
sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
@.runstatus = 1,
@.comments = 'Starting agent.'
I get an error here when running here from Query:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
Step 2
Step Name: Run Agent
Type: Replication Snapshot
Database: Distribution
-Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
-Publication [Northwind] -DistributorSecurityMode 1
Step 3
Step Name: Detect nonlogged agent shutdown.
Type: Transact-SQL Script(TSQL)
Database: Distribution
sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
***********************************************************************
The messages I get from history are not very helpful as it doesn't tell
me much. I had a job that got an error because a table didn't exist. I
know this because I tried it in Query. But the history of the job
always shows the same type of message. Just that the last step run was
X. But not why it died. Query knows why, why doesn't the Sql Agent?
Thanks,
Tom.Hi,
Check whether you can extract any information from the following url
http://www.cis.usouthal.edu/share/New%20Folder/Microsoft%20SQL%20Server/MSSQL/Install/instdist.sql
This contains the sp_MSdetect_nonlogged_shutdown stored procedure. At
present i am not able to provide any information coz i am unsure of the
setup you have installed there. I will try my best to sort this out.
Regards,
Jagan Mohan
"Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
news:3FC98D38.1020506@.deltanet.com...
> I have been trying to get replication to work and have been having
> nothing but problems.
> I have a bunch of jobs set up in my EM and they all have red circles
> with an X through it ( I assume this is because they all failed).
> I have been trying to set up the publisher and distributer on the same
> server.
> Here is one of the jobs I can't get to work. I get an error on the
> first step if I copy it to Query and run it. But when I right click the
> job and look at the history I get the following message:
> The job failed. The Job was invoked by User DINO\tfs. The last step to
> run was step 3 (Detect nonlogged agent shutdown.).
> According to this, I assume that it got to step 3 and died, but if I run
> the Query (as I mentioned), it dies at step 1. The error I got was:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>
> If it couldn't find the stored procedure in Query, how could it find it
> in the Job I ran?
> Here are the steps that are running.
> *******************************************************************
> Step 1
> Step Name: Log agent startup message.
> Type: Transact-SQL Script(TSQL)
> Database: Distribution
> sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
> @.runstatus = 1,
> @.comments = 'Starting agent.'
> I get an error here when running here from Query:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>
> Step 2
> Step Name: Run Agent
> Type: Replication Snapshot
> Database: Distribution
> -Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
> -Publication [Northwind] -DistributorSecurityMode 1
> Step 3
> Step Name: Detect nonlogged agent shutdown.
> Type: Transact-SQL Script(TSQL)
> Database: Distribution
> sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
> ***********************************************************************
> The messages I get from history are not very helpful as it doesn't tell
> me much. I had a job that got an error because a table didn't exist. I
> know this because I tried it in Query. But the history of the job
> always shows the same type of message. Just that the last step run was
> X. But not why it died. Query knows why, why doesn't the Sql Agent?
> Thanks,
> Tom.
>|||Jagan Mohan wrote:
> Hi,
> Check whether you can extract any information from the following url
> http://www.cis.usouthal.edu/share/New%20Folder/Microsoft%20SQL%20Server/MSSQL/Install/instdist.sql
> This contains the sp_MSdetect_nonlogged_shutdown stored procedure. At
> present i am not able to provide any information coz i am unsure of the
> setup you have installed there. I will try my best to sort this out.
I looked at it, but it won't tell me anything as the error says it can't
find the procedure. But the Server Agent got to the 3rd step, but
failed, so I assume it did step 1 correctly. Not sure what the
difference is.
> Regards,
> Jagan Mohan
> "Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
> news:3FC98D38.1020506@.deltanet.com...
>>I have been trying to get replication to work and have been having
>>nothing but problems.
>>I have a bunch of jobs set up in my EM and they all have red circles
>>with an X through it ( I assume this is because they all failed).
>>I have been trying to set up the publisher and distributer on the same
>>server.
>>Here is one of the jobs I can't get to work. I get an error on the
>>first step if I copy it to Query and run it. But when I right click the
>>job and look at the history I get the following message:
>>The job failed. The Job was invoked by User DINO\tfs. The last step to
>>run was step 3 (Detect nonlogged agent shutdown.).
>>According to this, I assume that it got to step 3 and died, but if I run
>>the Query (as I mentioned), it dies at step 1. The error I got was:
>>Server: Msg 2812, Level 16, State 62, Line 1
>>Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>>
>>If it couldn't find the stored procedure in Query, how could it find it
>>in the Job I ran?
>>Here are the steps that are running.
>>*******************************************************************
>>Step 1
>>Step Name: Log agent startup message.
>>Type: Transact-SQL Script(TSQL)
>>Database: Distribution
>>sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
>>@.runstatus = 1,
>>@.comments = 'Starting agent.'
>>I get an error here when running here from Query:
>>Server: Msg 2812, Level 16, State 62, Line 1
>>Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>>
>>Step 2
>>Step Name: Run Agent
>>Type: Replication Snapshot
>>Database: Distribution
>>-Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
>>-Publication [Northwind] -DistributorSecurityMode 1
>>Step 3
>>Step Name: Detect nonlogged agent shutdown.
>>Type: Transact-SQL Script(TSQL)
>>Database: Distribution
>>sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
>>***********************************************************************
>>The messages I get from history are not very helpful as it doesn't tell
>>me much. I had a job that got an error because a table didn't exist. I
>>know this because I tried it in Query. But the history of the job
>>always shows the same type of message. Just that the last step run was
>>X. But not why it died. Query knows why, why doesn't the Sql Agent?
>>Thanks,
>>Tom.
>>
>
Replication Errors
I have three questions'
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions'
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account' Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.See inline
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions'
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions'
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account' Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions'
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account' Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.See inline
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions'
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions'
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account' Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>
Replication Error while Configuring Distributor
Hi,
I am trying to setup transactional replication on a database within 1
sql instance. When I try to configure the pulisher/distributor, it errors out
with this message.
"SQL Server Enterprise Manager could not configure 'DZDEV007' as the
distributor for 'DZDEV007'.
Error 14234 : The specified '@.server' in invalid (valid values are returned
by sp_helpserver"
What's going on ? Please help.
TIA
Mohan
Hi Mohan,
The following KB seems to match most of your symptoms although your server
name appear to be too short for the problem occur:
http://support.microsoft.com/default...b;en-us;310639
You may also want to consider some other possibilities such as subtle
comparison issues related to the collation that you are using for your server.
-Raymond
"MO" wrote:
> Hi,
> I am trying to setup transactional replication on a database within 1
> sql instance. When I try to configure the pulisher/distributor, it errors out
> with this message.
> "SQL Server Enterprise Manager could not configure 'DZDEV007' as the
> distributor for 'DZDEV007'.
> Error 14234 : The specified '@.server' in invalid (valid values are returned
> by sp_helpserver"
> What's going on ? Please help.
> TIA
> Mohan
I am trying to setup transactional replication on a database within 1
sql instance. When I try to configure the pulisher/distributor, it errors out
with this message.
"SQL Server Enterprise Manager could not configure 'DZDEV007' as the
distributor for 'DZDEV007'.
Error 14234 : The specified '@.server' in invalid (valid values are returned
by sp_helpserver"
What's going on ? Please help.
TIA
Mohan
Hi Mohan,
The following KB seems to match most of your symptoms although your server
name appear to be too short for the problem occur:
http://support.microsoft.com/default...b;en-us;310639
You may also want to consider some other possibilities such as subtle
comparison issues related to the collation that you are using for your server.
-Raymond
"MO" wrote:
> Hi,
> I am trying to setup transactional replication on a database within 1
> sql instance. When I try to configure the pulisher/distributor, it errors out
> with this message.
> "SQL Server Enterprise Manager could not configure 'DZDEV007' as the
> distributor for 'DZDEV007'.
> Error 14234 : The specified '@.server' in invalid (valid values are returned
> by sp_helpserver"
> What's going on ? Please help.
> TIA
> Mohan
Wednesday, March 28, 2012
Replication error --> General Network Error with 11 & 08S01 errors
HI ,
I found that the replication keeps failing and have logged the replication -
-> scalaDB_MLD (not the Snapshot or logreader agent of that publication) and
got the followings details :
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++
Adding alert to msdb..sysreplicationalerts: ErrorId = 48,
Transaction Seqno = 000005ff00005ce7000400000001, Command ID = 5
Message: Replication-Replication Distribution Subsystem: agent MLDDC1-
scalaDB_MLD-SQL1-24 scheduled for retry. General network error. Check your
network documentation.[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call
sp_MSadd_repl_alert(3, 24, 48, 14152, ?, 5, N'MLDDC1', N'scalaDB_MLD',
N'SQL1', N'scalaDB_MLD', ?)}
ErrorId = 48, SourceTypeId = 1
ErrorCode = ''
ErrorText = 'SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
ANSI_PADDING ON SET ANSI_WARNINGS ON '
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
1, ?, N'', ?)}
Category:COMMAND
Source: Failed Command
Number:
Message: SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
ANSI_PADDING ON SET ANSI_WARNINGS ON
ErrorId = 48, SourceTypeId = 5
ErrorCode = '11'
ErrorText = 'General network error. Check your network documentation.'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
5, ?, N'11', ?)}
Category:SQLSERVER
Source: SQL1
Number: 11
Message: General network error. Check your network documentation.
ErrorId = 48, SourceTypeId = 4
ErrorCode = '08S01'
ErrorText = 'Communication link failure'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
4, ?, N'08S01', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: 08S01
Message: Communication link failure
ErrorId = 48, SourceTypeId = 4
ErrorCode = '08S01'
ErrorText = 'Communication link failure'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
4, ?, N'08S01', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: 08S01
Message: Communication link failure
[11/24/2005 3:52:08 PM]SQL1.scalaDB_MLD: exec dbo.sp_MSupdatelastsyncinfo
N'MLDDC1',N'scalaDB_MLD', N'', 0, 5, N'General network error. Check your
network documentation.'
Disconnecting from Subscriber 'SQL1'
Disconnecting from Distributor 'MLDDC1'
Disconnecting from Distributor History 'MLDDC1'
The agent failed with a 'Retry' status. Try to run the agent at a later time.
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++
i could see there is ODBC SQL Server Driver that caused the communication
link failure, so i have manually created a SQL SERVER odbc link from the data
sources and it seems that i could connect
i have checked the event viewer but could not see any particular details
where it can show connectivity issue
in fact the error happens intermittenly , but previously there's no change of
the settings and it could work
Wherelse can i check to be able to resolve this error once & for all ?
I am using SQL Server 2000 , SP3a , TCP/IP protocol using the default port#
1433
appreciate ur advise
tks & rdgs
Message posted via http://www.droptable.com
Hi,
Refering to the same issue below : i could see the agent profile details
(default) as below
BcpBatchSize - 100000
CommitBatchSize - 100
CommmitBatchThreshold - 1000
Are those in bytes and shld any of the values be decreased/increased ?
tks & rdgs
maxzsim wrote:
>HI ,
> I found that the replication keeps failing and have logged the replication -
>-> scalaDB_MLD (not the Snapshot or logreader agent of that publication) and
>got the followings details :
>+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++
> Adding alert to msdb..sysreplicationalerts: ErrorId = 48,
>Transaction Seqno = 000005ff00005ce7000400000001, Command ID = 5
>Message: Replication-Replication Distribution Subsystem: agent MLDDC1-
>scalaDB_MLD-SQL1-24 scheduled for retry. General network error. Check your
>network documentation.[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call
>sp_MSadd_repl_alert(3, 24, 48, 14152, ?, 5, N'MLDDC1', N'scalaDB_MLD',
>N'SQL1', N'scalaDB_MLD', ?)}
>ErrorId = 48, SourceTypeId = 1
>ErrorCode = ''
>ErrorText = 'SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
>CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
>ANSI_PADDING ON SET ANSI_WARNINGS ON '
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>1, ?, N'', ?)}
>Category:COMMAND
>Source: Failed Command
>Number:
>Message: SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
>CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
>ANSI_PADDING ON SET ANSI_WARNINGS ON
>ErrorId = 48, SourceTypeId = 5
>ErrorCode = '11'
>ErrorText = 'General network error. Check your network documentation.'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>5, ?, N'11', ?)}
>Category:SQLSERVER
>Source: SQL1
>Number: 11
>Message: General network error. Check your network documentation.
>ErrorId = 48, SourceTypeId = 4
>ErrorCode = '08S01'
>ErrorText = 'Communication link failure'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>4, ?, N'08S01', ?)}
>Category:ODBC
>Source: ODBC SQL Server Driver
>Number: 08S01
>Message: Communication link failure
>ErrorId = 48, SourceTypeId = 4
>ErrorCode = '08S01'
>ErrorText = 'Communication link failure'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>4, ?, N'08S01', ?)}
>Category:ODBC
>Source: ODBC SQL Server Driver
>Number: 08S01
>Message: Communication link failure
>[11/24/2005 3:52:08 PM]SQL1.scalaDB_MLD: exec dbo.sp_MSupdatelastsyncinfo
>N'MLDDC1',N'scalaDB_MLD', N'', 0, 5, N'General network error. Check your
>network documentation.'
>Disconnecting from Subscriber 'SQL1'
>Disconnecting from Distributor 'MLDDC1'
>Disconnecting from Distributor History 'MLDDC1'
>The agent failed with a 'Retry' status. Try to run the agent at a later time.
>+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++
>i could see there is ODBC SQL Server Driver that caused the communication
>link failure, so i have manually created a SQL SERVER odbc link from the data
>sources and it seems that i could connect
>i have checked the event viewer but could not see any particular details
>where it can show connectivity issue
>in fact the error happens intermittenly , but previously there's no change of
>the settings and it could work
>Wherelse can i check to be able to resolve this error once & for all ?
>I am using SQL Server 2000 , SP3a , TCP/IP protocol using the default port#
>1433
>appreciate ur advise
>tks & rdgs
Message posted via http://www.droptable.com
|||Hi ,
Futher info is the script in that agent : -Subscriber [SQL1] -SubscriberDB
[scalaDB_MLD] -Publisher [MLDDC1] -Distributor [MLDDC1] -
DistributorSecurityMode 1 -PublisherDB [scalaDB_MLD] -Continuous
appreciate any advise
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi,
> Refering to the same issue below : i could see the agent profile details
>(default) as below
> BcpBatchSize - 100000
> CommitBatchSize - 100
> CommmitBatchThreshold - 1000
> Are those in bytes and shld any of the values be decreased/increased ?
>tks & rdgs
>[quoted text clipped - 80 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200511/1
|||Hi ,
I have checked thru the error details , it was able to applied some of
the schema files xxx.sch before getting the general network error msg
The last command was :
++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++
SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET CONCAT_NULL_YIELDS_NULL ON
SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET ANSI_PADDING ON SET
ANSI_WARNINGS ON
Transaction sequence number and command ID of last execution batch are
0x000005FF00005CE7000400000001 and 20.
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++
does this mean anything ?
appreciate if anyone could point out where it might have gone wrong
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi ,
>Futher info is the script in that agent : -Subscriber [SQL1] -SubscriberDB
>[scalaDB_MLD] -Publisher [MLDDC1] -Distributor [MLDDC1] -
>DistributorSecurityMode 1 -PublisherDB [scalaDB_MLD] -Continuous
>appreciate any advise
>tks & rdgs
>[quoted text clipped - 13 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200511/1
I found that the replication keeps failing and have logged the replication -
-> scalaDB_MLD (not the Snapshot or logreader agent of that publication) and
got the followings details :
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++
Adding alert to msdb..sysreplicationalerts: ErrorId = 48,
Transaction Seqno = 000005ff00005ce7000400000001, Command ID = 5
Message: Replication-Replication Distribution Subsystem: agent MLDDC1-
scalaDB_MLD-SQL1-24 scheduled for retry. General network error. Check your
network documentation.[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call
sp_MSadd_repl_alert(3, 24, 48, 14152, ?, 5, N'MLDDC1', N'scalaDB_MLD',
N'SQL1', N'scalaDB_MLD', ?)}
ErrorId = 48, SourceTypeId = 1
ErrorCode = ''
ErrorText = 'SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
ANSI_PADDING ON SET ANSI_WARNINGS ON '
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
1, ?, N'', ?)}
Category:COMMAND
Source: Failed Command
Number:
Message: SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
ANSI_PADDING ON SET ANSI_WARNINGS ON
ErrorId = 48, SourceTypeId = 5
ErrorCode = '11'
ErrorText = 'General network error. Check your network documentation.'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
5, ?, N'11', ?)}
Category:SQLSERVER
Source: SQL1
Number: 11
Message: General network error. Check your network documentation.
ErrorId = 48, SourceTypeId = 4
ErrorCode = '08S01'
ErrorText = 'Communication link failure'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
4, ?, N'08S01', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: 08S01
Message: Communication link failure
ErrorId = 48, SourceTypeId = 4
ErrorCode = '08S01'
ErrorText = 'Communication link failure'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
4, ?, N'08S01', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: 08S01
Message: Communication link failure
[11/24/2005 3:52:08 PM]SQL1.scalaDB_MLD: exec dbo.sp_MSupdatelastsyncinfo
N'MLDDC1',N'scalaDB_MLD', N'', 0, 5, N'General network error. Check your
network documentation.'
Disconnecting from Subscriber 'SQL1'
Disconnecting from Distributor 'MLDDC1'
Disconnecting from Distributor History 'MLDDC1'
The agent failed with a 'Retry' status. Try to run the agent at a later time.
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++
i could see there is ODBC SQL Server Driver that caused the communication
link failure, so i have manually created a SQL SERVER odbc link from the data
sources and it seems that i could connect
i have checked the event viewer but could not see any particular details
where it can show connectivity issue
in fact the error happens intermittenly , but previously there's no change of
the settings and it could work
Wherelse can i check to be able to resolve this error once & for all ?
I am using SQL Server 2000 , SP3a , TCP/IP protocol using the default port#
1433
appreciate ur advise
tks & rdgs
Message posted via http://www.droptable.com
Hi,
Refering to the same issue below : i could see the agent profile details
(default) as below
BcpBatchSize - 100000
CommitBatchSize - 100
CommmitBatchThreshold - 1000
Are those in bytes and shld any of the values be decreased/increased ?
tks & rdgs
maxzsim wrote:
>HI ,
> I found that the replication keeps failing and have logged the replication -
>-> scalaDB_MLD (not the Snapshot or logreader agent of that publication) and
>got the followings details :
>+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++
> Adding alert to msdb..sysreplicationalerts: ErrorId = 48,
>Transaction Seqno = 000005ff00005ce7000400000001, Command ID = 5
>Message: Replication-Replication Distribution Subsystem: agent MLDDC1-
>scalaDB_MLD-SQL1-24 scheduled for retry. General network error. Check your
>network documentation.[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call
>sp_MSadd_repl_alert(3, 24, 48, 14152, ?, 5, N'MLDDC1', N'scalaDB_MLD',
>N'SQL1', N'scalaDB_MLD', ?)}
>ErrorId = 48, SourceTypeId = 1
>ErrorCode = ''
>ErrorText = 'SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
>CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
>ANSI_PADDING ON SET ANSI_WARNINGS ON '
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>1, ?, N'', ?)}
>Category:COMMAND
>Source: Failed Command
>Number:
>Message: SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
>CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
>ANSI_PADDING ON SET ANSI_WARNINGS ON
>ErrorId = 48, SourceTypeId = 5
>ErrorCode = '11'
>ErrorText = 'General network error. Check your network documentation.'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>5, ?, N'11', ?)}
>Category:SQLSERVER
>Source: SQL1
>Number: 11
>Message: General network error. Check your network documentation.
>ErrorId = 48, SourceTypeId = 4
>ErrorCode = '08S01'
>ErrorText = 'Communication link failure'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>4, ?, N'08S01', ?)}
>Category:ODBC
>Source: ODBC SQL Server Driver
>Number: 08S01
>Message: Communication link failure
>ErrorId = 48, SourceTypeId = 4
>ErrorCode = '08S01'
>ErrorText = 'Communication link failure'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>4, ?, N'08S01', ?)}
>Category:ODBC
>Source: ODBC SQL Server Driver
>Number: 08S01
>Message: Communication link failure
>[11/24/2005 3:52:08 PM]SQL1.scalaDB_MLD: exec dbo.sp_MSupdatelastsyncinfo
>N'MLDDC1',N'scalaDB_MLD', N'', 0, 5, N'General network error. Check your
>network documentation.'
>Disconnecting from Subscriber 'SQL1'
>Disconnecting from Distributor 'MLDDC1'
>Disconnecting from Distributor History 'MLDDC1'
>The agent failed with a 'Retry' status. Try to run the agent at a later time.
>+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++
>i could see there is ODBC SQL Server Driver that caused the communication
>link failure, so i have manually created a SQL SERVER odbc link from the data
>sources and it seems that i could connect
>i have checked the event viewer but could not see any particular details
>where it can show connectivity issue
>in fact the error happens intermittenly , but previously there's no change of
>the settings and it could work
>Wherelse can i check to be able to resolve this error once & for all ?
>I am using SQL Server 2000 , SP3a , TCP/IP protocol using the default port#
>1433
>appreciate ur advise
>tks & rdgs
Message posted via http://www.droptable.com
|||Hi ,
Futher info is the script in that agent : -Subscriber [SQL1] -SubscriberDB
[scalaDB_MLD] -Publisher [MLDDC1] -Distributor [MLDDC1] -
DistributorSecurityMode 1 -PublisherDB [scalaDB_MLD] -Continuous
appreciate any advise
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi,
> Refering to the same issue below : i could see the agent profile details
>(default) as below
> BcpBatchSize - 100000
> CommitBatchSize - 100
> CommmitBatchThreshold - 1000
> Are those in bytes and shld any of the values be decreased/increased ?
>tks & rdgs
>[quoted text clipped - 80 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200511/1
|||Hi ,
I have checked thru the error details , it was able to applied some of
the schema files xxx.sch before getting the general network error msg
The last command was :
++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++
SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET CONCAT_NULL_YIELDS_NULL ON
SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET ANSI_PADDING ON SET
ANSI_WARNINGS ON
Transaction sequence number and command ID of last execution batch are
0x000005FF00005CE7000400000001 and 20.
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++
does this mean anything ?
appreciate if anyone could point out where it might have gone wrong
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi ,
>Futher info is the script in that agent : -Subscriber [SQL1] -SubscriberDB
>[scalaDB_MLD] -Publisher [MLDDC1] -Distributor [MLDDC1] -
>DistributorSecurityMode 1 -PublisherDB [scalaDB_MLD] -Continuous
>appreciate any advise
>tks & rdgs
>[quoted text clipped - 13 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200511/1
Replication Error - SharePoint 2007 DB
I have several SharePoint 2007 SQL 2005 databases that are replicating fine.
However, I have the WSS_Content _db that errors every time as shown below.
This only happens on the table shown, not on any of the other tables.
I am looking for confimation that this is a glitch withing SQL 2005 and there is nothing I can do about it pending a service release.
Anyone else run into this?
Error messages:
Source: Microsoft.SqlServer.Smo
Target Site: System.Collections.Specialized.StringCollection ScriptWithList(Microsoft.SqlServer.Management.Smo.DependencyCollection, Microsoft.SqlServer.Management.Smo.SqlSmoObject[])
Message: Script failed for Table 'dbo.NameValuePair_Hindi_CI_AS'.
Stack: at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList(DependencyCollection depList, SqlSmoObject[] objects)
at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList(SqlSmoObject[] objects)
at Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateLogBasedArticleSchScript(Scripter scripter, BaseArticleWrapper articleWrapper, Table smoTable)
at Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateLogBasedArticleScripts(ArticleScriptingBundle articleScriptingBundle)
at Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateArticleScripts(ArticleScriptingBundle articleScriptingBundle)
at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.GenerateObjectScripts(ArticleScriptingBundle articleScriptingBundle)
at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: Microsoft.SqlServer.Smo, Error number: 0)
Can you exlain your scenario in more detail? Are you using transactional replication? Also, are you using Hindi as table name? What collation are you using?
Gary
The 'Hindi' table is part of the database that was automatically installed by SharePoint, along with numerous others.
Wish I could include a photo.
Some of the other tables are Greek, Hebrew, Hindi, Hungarian, Japanese....etc
They start with Albanian and end with Vietnamese.
The backup works great until it hits the 'Hindi' table and then crashes.
If this wasn't a production environment I would delete the table and see what happened.
Thanks.
Replication error - can not retrieve column information
does anyone have an idea of what generally could be wrong with a pull merge subscription when it errors out with the following:
sql server The merge process could not retrieve column information for table "tablename"
Also, could you tell me where I can get more details of errors (i.e. where the errorlog for replication is located
I found how to output the merge agent errors. Here is the output. Can anyone shed any light on this?
[5/15/2004 6:28:05 PM]BOSERVER-CSC3.vis-csc3: {call sp_MSgetversion }
Connecting to Publisher 'VIVA-SQLHQ.VIS'
Server: VIVA-SQLHQ
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[5/15/2004 6:28:05 PM]VIVA-SQLHQ.VIS: {call sp_MSgetversion }
Percent Complete: 5
Processing article 'viva_visit_qualified_statuses'
Percent Complete: 5
Processing article 'viva_inoffice_statuses'
Percent Complete: 5
Processing article 'Users'
The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
The merge process could not retrieve column information for table 'dbo.viva_inoffice_statuses'.The merge process could not retrieve column information for table 'dbo.Users'.
The merge process could not retrieve column information for table 'dbo.Applicant Requirements'.
Percent Complete: 0
The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSenumcolumns (?,?)}
Percent Complete: 0
Category:SQLSERVER
Source: BOSERVER-CSC3
Number: 2812
Message: Could not find stored procedure 'sp_sel_82D17F3FEACB41DE7A9684009ECD4868'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The merge process could not retrieve column information for table 'dbo.viva_inoffice_statuses'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The process was successfully stopped.
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Distributor 'VIVA-SQLHQ'
sql server The merge process could not retrieve column information for table "tablename"
Also, could you tell me where I can get more details of errors (i.e. where the errorlog for replication is located
I found how to output the merge agent errors. Here is the output. Can anyone shed any light on this?
[5/15/2004 6:28:05 PM]BOSERVER-CSC3.vis-csc3: {call sp_MSgetversion }
Connecting to Publisher 'VIVA-SQLHQ.VIS'
Server: VIVA-SQLHQ
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[5/15/2004 6:28:05 PM]VIVA-SQLHQ.VIS: {call sp_MSgetversion }
Percent Complete: 5
Processing article 'viva_visit_qualified_statuses'
Percent Complete: 5
Processing article 'viva_inoffice_statuses'
Percent Complete: 5
Processing article 'Users'
The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
The merge process could not retrieve column information for table 'dbo.viva_inoffice_statuses'.The merge process could not retrieve column information for table 'dbo.Users'.
The merge process could not retrieve column information for table 'dbo.Applicant Requirements'.
Percent Complete: 0
The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSenumcolumns (?,?)}
Percent Complete: 0
Category:SQLSERVER
Source: BOSERVER-CSC3
Number: 2812
Message: Could not find stored procedure 'sp_sel_82D17F3FEACB41DE7A9684009ECD4868'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The merge process could not retrieve column information for table 'dbo.viva_inoffice_statuses'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The process was successfully stopped.
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Distributor 'VIVA-SQLHQ'
Saturday, February 25, 2012
replicating UDT's to subscribers
I have a sql 2005 publisher and distributor and a sql 2000 subscribers. for some reason on one of the subscribers i'm getting errors that it can't replicate the UDT's. i tried a new snapshot and made sure it was set not to replicate UDT's but i'm still getting Create Type errors.
would anyone have any idea why it's trying to create UDT's at the subscriber when i specify not to replicate UDT's?
Are you trying to exclude the UDT column, so it doesn't replicate to subscriber? How did you specify, so it does not replicate UDT? Did you add a vertical filter? Or?
Gary
|||in the article properties i left it on false for replicate user defined data types. it's UDT on the publisher and the base types on the subscribers.|||
I am not sure if this will solve your problem but you can try re-initializing your subscription before regenerating a new snapshot.
-Raymond
|||how many dba's does it take to change a light bulb?stupid mistake. need to change it to true to convert data types like on all our other publications
Subscribe to:
Posts (Atom)