I am trying to setup replication on my server, but was getting an error that said:
"The Distributor is not available Error 6. Specified SQL Server not found"
So, I did some searching and found a couple things to check and found
sp_helpserver...the server with id of 0 was a remote server, not the local server instance...and
select @.@.servername also returned the name of that remote server!!
I'm assuming this is my problem, but how did it get this way and how do I fix it?
ThanksOk, I fixed the @.@.servername issue with:
use master
go
exec sp_dropserver 'incorrect server name'
go
exec sp_addserver 'servername','local'
go
Restart sql server service.
sp_helpserver now lists the local server as id of 0 and @.@.servername returns the correct server.
HOWEVER, the same error is there for replication?!?!
There is an entry in sp_helpserver for this:
repl_distributor repl_distributor rpc,dist,rpc out,use remote collation 6 NULL 0 0
Not sure if that helps with anybody trying to help me but anyway...|||Can you describe how you setup the Replication? At which step you get the error and how did you prepare your db server?|||Thanks for the help.
I did not do anything except for click on the server instance->Tools->Wizards and then click Replication->Configure Publishing and Distribution Wizard
I'm new to this server. It appears it has been messed with before but I cannot give you the details of that.|||Joe,
I was able to get it working. For those that find this post, here is what I did.
First, using the commands above, make sure your server is iniitally setup correct!
Next, I disabled publishing on the local server. Tools->Replication->Publishing
Next, I then configured the distributor for the local server. Tools->Replication->Configure Publishing, Subscribers and Distribution
Thanks
Showing posts with label specified. Show all posts
Showing posts with label specified. Show all posts
Thursday, March 29, 2012
Friday, March 23, 2012
Error when making a transactional replication
Hi,
I'm making a transactional replication.
I get the following error:
Could not bulk insert. Bulk data stream was incorrectly specified as sorted.
(Source: SQL4 (Data source); Error number: 4819)
Function sequence error
(Source: ODBC Driver Manager (ODBC); Error number: S1010)
Anyone that knows how to solve the problem?
Thanks in advance
Anders
your collation on your publication database is different from your collation
on the subscriber database.
To solve your problem use the same collation on both databases.
"Anders Johansson" <anders.johansson@.nospam.se> wrote in message
news:OQ9CtRuJEHA.1096@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I'm making a transactional replication.
> I get the following error:
> Could not bulk insert. Bulk data stream was incorrectly specified as
sorted.
> (Source: SQL4 (Data source); Error number: 4819)
> ----
--
> --
> Function sequence error
> (Source: ODBC Driver Manager (ODBC); Error number: S1010)
> ----
--
> --
> Anyone that knows how to solve the problem?
> Thanks in advance
> Anders
>
|||Hi Hilary!
The publication database had a different collation than the subscriber.
But I didnt change the whole subscriber collation - just the article that
went wrong. (There was an alternative in the Publication properties).
Thanks!
"Hilary Cotter" <hilaryk@.att.net> skrev i meddelandet
news:%23tQRaguJEHA.3944@.tk2msftngp13.phx.gbl...
> your collation on your publication database is different from your
collation
> on the subscriber database.
> To solve your problem use the same collation on both databases.
> "Anders Johansson" <anders.johansson@.nospam.se> wrote in message
> news:OQ9CtRuJEHA.1096@.TK2MSFTNGP10.phx.gbl...
> sorted.
> ----
> --
> ----
> --
>
|||damn, why didn't I think of that. Good idea!
"Anders Johansson" <anders.johansson@.nospam.se> wrote in message
news:uYQGUquJEHA.3380@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary!
> The publication database had a different collation than the subscriber.
> But I didnt change the whole subscriber collation - just the article that
> went wrong. (There was an alternative in the Publication properties).
> Thanks!
> "Hilary Cotter" <hilaryk@.att.net> skrev i meddelandet
> news:%23tQRaguJEHA.3944@.tk2msftngp13.phx.gbl...
> collation
> ----
> ----
>
I'm making a transactional replication.
I get the following error:
Could not bulk insert. Bulk data stream was incorrectly specified as sorted.
(Source: SQL4 (Data source); Error number: 4819)
Function sequence error
(Source: ODBC Driver Manager (ODBC); Error number: S1010)
Anyone that knows how to solve the problem?
Thanks in advance
Anders
your collation on your publication database is different from your collation
on the subscriber database.
To solve your problem use the same collation on both databases.
"Anders Johansson" <anders.johansson@.nospam.se> wrote in message
news:OQ9CtRuJEHA.1096@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I'm making a transactional replication.
> I get the following error:
> Could not bulk insert. Bulk data stream was incorrectly specified as
sorted.
> (Source: SQL4 (Data source); Error number: 4819)
> ----
--
> --
> Function sequence error
> (Source: ODBC Driver Manager (ODBC); Error number: S1010)
> ----
--
> --
> Anyone that knows how to solve the problem?
> Thanks in advance
> Anders
>
|||Hi Hilary!
The publication database had a different collation than the subscriber.
But I didnt change the whole subscriber collation - just the article that
went wrong. (There was an alternative in the Publication properties).
Thanks!
"Hilary Cotter" <hilaryk@.att.net> skrev i meddelandet
news:%23tQRaguJEHA.3944@.tk2msftngp13.phx.gbl...
> your collation on your publication database is different from your
collation
> on the subscriber database.
> To solve your problem use the same collation on both databases.
> "Anders Johansson" <anders.johansson@.nospam.se> wrote in message
> news:OQ9CtRuJEHA.1096@.TK2MSFTNGP10.phx.gbl...
> sorted.
> ----
> --
> ----
> --
>
|||damn, why didn't I think of that. Good idea!
"Anders Johansson" <anders.johansson@.nospam.se> wrote in message
news:uYQGUquJEHA.3380@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary!
> The publication database had a different collation than the subscriber.
> But I didnt change the whole subscriber collation - just the article that
> went wrong. (There was an alternative in the Publication properties).
> Thanks!
> "Hilary Cotter" <hilaryk@.att.net> skrev i meddelandet
> news:%23tQRaguJEHA.3944@.tk2msftngp13.phx.gbl...
> collation
> ----
> ----
>
Labels:
bulk,
database,
error,
errorcould,
following,
incorrectly,
insert,
microsoft,
mysql,
oracle,
replication,
server,
specified,
sql,
stream,
transactional
Subscribe to:
Posts (Atom)