Replication between SQL server 2000 and MSDE (error 20084)

Hello,
We have an application to do some replication between SQL Server 2000 and
MSDE. After a good install of MSDE, we have this error : "20084 The process
could not connect to Subscriber" when we try to synchronyse data.
So, the replication is OK on another PC (they don't have the same network)
What do you think about that ? Any idea ?
Thank you very much.
Pascal.
Are you using transactional or merge? push or pull?
Does the error also give you a reason why the connection failed? Login
failed etc?
First of all make sure that you are able to connect to the subscriber server
from the machine where the agent is running using osql etc using the same
security context that the agent is using.
I would suggest you look at the sqlserveragent startup account on the server
where the job is running (assuming you are running this as a job) to see if
it has access to the subscriber.
Also try changing the subscriber login to use SQL authentication to see if
that helps.
"pascal.psion" wrote:

> Hello,
> We have an application to do some replication between SQL Server 2000 and
> MSDE. After a good install of MSDE, we have this error : "20084 The process
> could not connect to Subscriber" when we try to synchronyse data.
> So, the replication is OK on another PC (they don't have the same network)
> What do you think about that ? Any idea ?
> Thank you very much.
> Pascal.
|||Can the publisher see the subscriber? Can you run an xp_cmdshell 'ping
subscriberName'?
Have your subscriber been enabled as a subscriber on the publisher how is it
accessing the subscriber - the impersonate the SQL Server agent option or
the SQL account option?
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
"pascal.psion" <pascalpsion@.discussions.microsoft.com> wrote in message
news:689ABC01-23B4-4B67-AAE1-73C5F4C80D23@.microsoft.com...
> Hello,
> We have an application to do some replication between SQL Server 2000 and
> MSDE. After a good install of MSDE, we have this error : "20084 The
> process
> could not connect to Subscriber" when we try to synchronyse data.
> So, the replication is OK on another PC (they don't have the same
> network)
> What do you think about that ? Any idea ?
> Thank you very much.
> Pascal.
|||Thank you so much for your help.
No, he can't. But why ? We dont understand why.
Our subscriber are anonymous one.
"Hilary Cotter" wrote:

> Can the publisher see the subscriber? Can you run an xp_cmdshell 'ping
> subscriberName'?
> Have your subscriber been enabled as a subscriber on the publisher how is it
> accessing the subscriber - the impersonate the SQL Server agent option or
> the SQL account option?
> --
> 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
> "pascal.psion" <pascalpsion@.discussions.microsoft.com> wrote in message
> news:689ABC01-23B4-4B67-AAE1-73C5F4C80D23@.microsoft.com...
>
>
|||Thank you so much for your help.
We use merge replication.
No it doesn't, we have only this raison : "The process could not connect to
subscriber".
For the rest of your reply, we're going to see that to day.
So we answer you on next monday.
thank you very much.
pascal.
"gopal" wrote:
[vbcol=seagreen]
> Are you using transactional or merge? push or pull?
> Does the error also give you a reason why the connection failed? Login
> failed etc?
> First of all make sure that you are able to connect to the subscriber server
> from the machine where the agent is running using osql etc using the same
> security context that the agent is using.
> I would suggest you look at the sqlserveragent startup account on the server
> where the job is running (assuming you are running this as a job) to see if
> it has access to the subscriber.
> Also try changing the subscriber login to use SQL authentication to see if
> that helps.
> "pascal.psion" wrote:
|||Hi,
We try that you have said, but we have always the same error. (We can't run
an xp_cmdshell 'ping subscriberName' )
We continue ours research.
Thank you.
Pascal.
"gopal" wrote:
[vbcol=seagreen]
> Are you using transactional or merge? push or pull?
> Does the error also give you a reason why the connection failed? Login
> failed etc?
> First of all make sure that you are able to connect to the subscriber server
> from the machine where the agent is running using osql etc using the same
> security context that the agent is using.
> I would suggest you look at the sqlserveragent startup account on the server
> where the job is running (assuming you are running this as a job) to see if
> it has access to the subscriber.
> Also try changing the subscriber login to use SQL authentication to see if
> that helps.
> "pascal.psion" wrote: