Process could not connect to Subscriber

[Robert J]

Hi All,

I happily had replication working from a 6.5 Pub\Dist to about a dozen
other 6.5 servers.

One of the Servers got upgraded to SQL 7, and although it is supposed to be
possible to replicate from 6.5 to 7, I also chose to upgrade the Pub\Dist to
SQL 7.

I have run the scripts that allow replication from 7 to 6.5 as described in
BOL
Setup a test push subscription to one of the 6.5 servers and also the 7
server.

I have created a new NT account called SQLAgent on the Pub\Dist server, and
use
it to start the SQL Server Agent service.

I have all the trusts established, and added the <Domain>\SQLAgent login to
the administrators
group on both servers, and this enabled me to replicate push transactions to
the 6.5 server.

I can't do the same on the SQL 7 server, I get the error:

The process could not connect to subscriber '<server name>'

I have trawled through the groups using google and:

Have the server registered on the Pub\Dist.
Can connect to the server using Query Analyser.

The Pub\Dist is a NT4 sp6 running SQL Server 7

The subscriber that fails is W2k running SQL Server 7
and is a member of a Domain, not the main Domain server.

Any help would be appreciated

Cheers

Robert

[Robert J]

I have been at this for over a week, and it is becoming critical.

I have no problem pushing the publication from SQL 7 to 11 SQL 6.5 servers

I still get the could not connect to the SQL 7 machine, with this log
output.

Microsoft SQL Server Distribution Agent 7.00.623
Copyright (c) 1998 Microsoft Corporation
Microsoft SQL Server Replication Agent: STATION7-jhcarsmaster-BMA2-7

Startup Delay: 2023 (msecs)
Connecting to Distributor 'STATION7'
Connecting to Distributor 'STATION7.'
STATION7.: exec sp_helpdistpublisher N'STATION7'
STATION7.Distribution: select @@SERVERNAME

Server: STATION7
DBMS: Microsoft SQL Server
Version: 07.00.0623
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

STATION7.Distribution: sp_MSgetversion
STATION7.Distribution: execute sp_server_info 18

ANSI codepage: 1
STATION7.Distribution: select datasource, srvid from master..sysservers
where srvname = N'BMA2'
STATION7.Distribution: {?=call sp_MShelp_subscriber_info (N'STATION7',
N'BMA2')}
Subscriber security mode: 1, login name: sa, password: .
STATION7.Distribution: select datasource, srvid from master..sysservers
where srvname = N'STATION7'
STATION7.Distribution: {call sp_MShelp_distribution_agentid(0,
N'jhcarsmaster', NULL, 12, N'jhcarsbma', 0)}
STATION7.Distribution: {call
master..sp_MScheck_agent_instance(N'STATION7-jhcarsmaster-BMA2-7', 3)}
Initializing
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 1, ?, ?, 0,
0, 0.00, 0x00, 1, ?, 0, 0x01, 0x01)}
STATION7.Distribution: {call sp_MSsubscription_status(7)}
STATION7.Distribution: execute sp_MShelp_profile 7, 3, N''
Pull subscriber working directory: C:\WINNT\repldata r
Connecting to Subscriber 'BMA2'
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 3, ?, ?, 0,
0, 0.00, 0x00, 1, ?, 0, 0x01, 0x01)}
Connecting to Subscriber 'BMA2.jhcarsbma'
Login failed for user 'CORUSCANT\SQLAgent'.
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 6, ?, ?, 0,
0, 0.00, 0x00, 1, ?, 0, 0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 0,
Transaction Seqno = , Command ID = 0
Message: Replication-Distribution: agent STATION7-jhcarsmaster-BMA2-7
failed. Login failed for user 'CORUSCANT\SQLAgent'.STATION7.Distribution:
{call sp_MSadd_repl_alert(3, 7, 0, 14151, ?, 0, N'STATION7',
N'jhcarsmaster', N'BMA2', N'jhcarsbma', ?)}
Agent message code 20084. The process could not connect to Subscriber
'BMA2'.
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 6, ?, ?, 0,
0, 0.00, 0x01, 1, ?, 0, 0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 2,
Transaction Seqno = , Command ID = 0
Message: Replication-Distribution: agent STATION7-jhcarsmaster-BMA2-7
failed. The process could not connect to Subscriber
'BMA2'.STATION7.Distribution: {call sp_MSadd_repl_alert(3, 7, 2, 14151, ?,
0, N'STATION7', N'jhcarsmaster', N'BMA2', N'jhcarsbma', ?)}
ErrorId = 2, SourceTypeId = 5
ErrorCode = '18456'
ErrorText = 'Login failed for user 'CORUSCANT\SQLAgent'.'
STATION7.Distribution: {call sp_MSadd_repl_error(2, 0, 5, ?, N'18456', ?)}

Category:SQLSERVER
Source: BMA2
Number: 18456
Message: Login failed for user 'CORUSCANT\SQLAgent'.
Disconnecting from Subscriber 'BMA2'
Disconnecting from Distributor History 'STATION7'

I am also getting a similar error when trying to one of my SQL 6.5 servers:

Login failed- User: CORUSCANT_SQLAgent Reason: Not defined as a valid user
of a trusted SQL Server connection.

I thought Replication was supposed to be easier in SQL Server 7......

Thanks

Robert

Post by Robert J
Hi All,
I happily had replication working from a 6.5 Pub\Dist to about a dozen
other 6.5 servers.
One of the Servers got upgraded to SQL 7, and although it is supposed to be
possible to replicate from 6.5 to 7, I also chose to upgrade the Pub\Dist to
SQL 7.
I have run the scripts that allow replication from 7 to 6.5 as described in
BOL
Setup a test push subscription to one of the 6.5 servers and also the 7
server.
I have created a new NT account called SQLAgent on the Pub\Dist server, and
use
it to start the SQL Server Agent service.
I have all the trusts established, and added the <Domain>\SQLAgent login to
the administrators
group on both servers, and this enabled me to replicate push transactions to
the 6.5 server.
The process could not connect to subscriber '<server name>'
Have the server registered on the Pub\Dist.
Can connect to the server using Query Analyser.
The Pub\Dist is a NT4 sp6 running SQL Server 7
The subscriber that fails is W2k running SQL Server 7
and is a member of a Domain, not the main Domain server.
Any help would be appreciated
Cheers
Robert

[Robert J]

Still waiting for some help on this problem.

Only things I can add is that the server that is Pub\Dist was upgraded to 7
from 6.5
and the 6.5 and 7 Subscribers that fail are not PDC's and were both moved
from
an original server.

Robert

Post by Robert J
I have been at this for over a week, and it is becoming critical.
I have no problem pushing the publication from SQL 7 to 11 SQL 6.5 servers
I still get the could not connect to the SQL 7 machine, with this log
output.
Microsoft SQL Server Distribution Agent 7.00.623
Copyright (c) 1998 Microsoft Corporation
Microsoft SQL Server Replication Agent: STATION7-jhcarsmaster-BMA2-7
Startup Delay: 2023 (msecs)
Connecting to Distributor 'STATION7'
Connecting to Distributor 'STATION7.'
STATION7.: exec sp_helpdistpublisher N'STATION7'
Server: STATION7
DBMS: Microsoft SQL Server
Version: 07.00.0623
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
STATION7.Distribution: sp_MSgetversion
STATION7.Distribution: execute sp_server_info 18
ANSI codepage: 1
STATION7.Distribution: select datasource, srvid from master..sysservers
where srvname = N'BMA2'
STATION7.Distribution: {?=call sp_MShelp_subscriber_info (N'STATION7',
N'BMA2')}
Subscriber security mode: 1, login name: sa, password: .
STATION7.Distribution: select datasource, srvid from master..sysservers
where srvname = N'STATION7'
STATION7.Distribution: {call sp_MShelp_distribution_agentid(0,
N'jhcarsmaster', NULL, 12, N'jhcarsbma', 0)}
STATION7.Distribution: {call
master..sp_MScheck_agent_instance(N'STATION7-jhcarsmaster-BMA2-7', 3)}
Initializing
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 1, ?, ?, 0,
0, 0.00, 0x00, 1, ?, 0, 0x01, 0x01)}
STATION7.Distribution: {call sp_MSsubscription_status(7)}
STATION7.Distribution: execute sp_MShelp_profile 7, 3, N''
Pull subscriber working directory: C:\WINNT\repldata r
Connecting to Subscriber 'BMA2'
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 3, ?, ?, 0,
0, 0.00, 0x00, 1, ?, 0, 0x01, 0x01)}
Connecting to Subscriber 'BMA2.jhcarsbma'
Login failed for user 'CORUSCANT\SQLAgent'.
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 6, ?, ?, 0,
0, 0.00, 0x00, 1, ?, 0, 0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 0,
Transaction Seqno = , Command ID = 0
Message: Replication-Distribution: agent STATION7-jhcarsmaster-BMA2-7
{call sp_MSadd_repl_alert(3, 7, 0, 14151, ?, 0, N'STATION7',
N'jhcarsmaster', N'BMA2', N'jhcarsbma', ?)}
Agent message code 20084. The process could not connect to Subscriber
'BMA2'.
STATION7.Distribution: {call sp_MSadd_distribution_history(7, 6, ?, ?, 0,
0, 0.00, 0x01, 1, ?, 0, 0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 2,
Transaction Seqno = , Command ID = 0
Message: Replication-Distribution: agent STATION7-jhcarsmaster-BMA2-7
failed. The process could not connect to Subscriber
'BMA2'.STATION7.Distribution: {call sp_MSadd_repl_alert(3, 7, 2, 14151, ?,
0, N'STATION7', N'jhcarsmaster', N'BMA2', N'jhcarsbma', ?)}
ErrorId = 2, SourceTypeId = 5
ErrorCode = '18456'
ErrorText = 'Login failed for user 'CORUSCANT\SQLAgent'.'
STATION7.Distribution: {call sp_MSadd_repl_error(2, 0, 5, ?, N'18456', ?)}
Category:SQLSERVER
Source: BMA2
Number: 18456
Message: Login failed for user 'CORUSCANT\SQLAgent'.
Disconnecting from Subscriber 'BMA2'
Disconnecting from Distributor History 'STATION7'
Login failed- User: CORUSCANT_SQLAgent Reason: Not defined as a valid user
of a trusted SQL Server connection.
I thought Replication was supposed to be easier in SQL Server 7......
Thanks
Robert

Post by Robert J
Hi All,
I happily had replication working from a 6.5 Pub\Dist to about a dozen
other 6.5 servers.
One of the Servers got upgraded to SQL 7, and although it is supposed to

be

Post by Robert J
possible to replicate from 6.5 to 7, I also chose to upgrade the

Pub\Dist

Post by Robert J
to

Post by Robert J
SQL 7.
I have run the scripts that allow replication from 7 to 6.5 as described

in

Post by Robert J
BOL
Setup a test push subscription to one of the 6.5 servers and also the 7
server.
I have created a new NT account called SQLAgent on the Pub\Dist server,

and

Post by Robert J
use
it to start the SQL Server Agent service.
I have all the trusts established, and added the <Domain>\SQLAgent login

to

Post by Robert J
the administrators
group on both servers, and this enabled me to replicate push

transactions

Post by Robert J
to

Post by Robert J
the 6.5 server.
The process could not connect to subscriber '<server name>'
Have the server registered on the Pub\Dist.
Can connect to the server using Query Analyser.
The Pub\Dist is a NT4 sp6 running SQL Server 7
The subscriber that fails is W2k running SQL Server 7
and is a member of a Domain, not the main Domain server.
Any help would be appreciated
Cheers
Robert

[Robert J]

Walt,

In my eyes you have just achieved SQL Guru status :)

I tried what you said:
Dropped both subscribers that were failing.

Checked that my <DOMAIN>\SQLAgent> had admin rights to the db.

Used the sp_addsubscriber '<SERVER>', 0, '<DOMAIN\SLQAgent>', 'pwd'
to resubscribe to each server

and Bob's your Auntie they both are working.

Thanks for your help I really appreciate it.

Robert

Robert,
I'm no SQl guru but since no one else has replied, here is my
suggestion.
Create a database login on the subscriber with admin rights. Drop the
subscriber from the Dist/Pub and recreate it using the sp_addsubscriber
stored procedure specifying the login and password (see books online for
syntax). Then add your subscription and see what happens. This is not
as secure as NT Authentication but it is more straightforward. If it
works, then you can concentrate on NT athentication issues rather than
database server problems.
That's my 2 cents.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!