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

Replication between SQL Express 2005

Hi All,

I am trying to do a Replication between a network SQL Server Express Edition 2005 DB with a client SQL Server Express Edition 2005 DB. My question is

1. Can we do replicaiton between SQL Server Express Edition 2005. (No SQL SERVER present)

2. If yes can any of you provide me some guidance or some pointers on how to achieve it.

Thanks

Suresh

Quick answer is no. Check out the following posting for more info.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=941980&SiteID=1

Gary

Replication and IP addresses

I want to replicate between 2 servers not on the same network. One has to be addressed by IP. Currently replication does not support IPs - anyone have a workaround. Will this be resolved in the future? Seems this is a pretty common scenario if your db is on a hosted site.

-cg

Please refer this thread n hope this will help you.I also did experience this issue b4 but i already solved that. :)

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1018513&SiteID=1

Best Regards,

Hans

Replication - Mirroring - Clustering?

Hi,
I'm not the network guy, just asking the question for him.
Here's the scenario:
We manage our own server and have a SQL 2000 database.
All database transactions are done through our website.
What the boss wants:
If one of the servers goes down, database server or the IIS server,
everything should be switched over to another server.
The data must be up-to-date at all times in the backup server.
I just need a suggestion as to the best method to implement this.
Any websites where I can get the information?For Web Servers, use NLB. Its Network Load Balancer and for database, use
MSCS Clustering.
"Raymond D'Anjou" wrote:

> Hi,
> I'm not the network guy, just asking the question for him.
> Here's the scenario:
> We manage our own server and have a SQL 2000 database.
> All database transactions are done through our website.
> What the boss wants:
> If one of the servers goes down, database server or the IIS server,
> everything should be switched over to another server.
> The data must be up-to-date at all times in the backup server.
> I just need a suggestion as to the best method to implement this.
> Any websites where I can get the information?
>
>

Replication - can subscriber objects be pre-existing?

My manager does not want to go through the process of moving 40 GB of data to the subscriber database over the network as would occur during the initialization phase of replication (exact method of replication has yet to be determined). The subscriber db is for Web Access and will be read-only. He wants to back up a db and use tapes to restore the db on the subscriber db server, and then activate replication. I have told him that you have to allow SQL Server to create the objects on the subscriber side and you have to allow SQL Server to control the data flow, that manually creating the objects on the subscriber side will not work. He says that I am incorrect.

Who is right? I haven't been able to find an answer from the Microsoft site and news groups.

Thanks,I hate to be the bearer of bad news for you, but your manager is correct in this instance.

Here's the link to get you started:

http://support.microsoft.com/kb/320499/en-us

It really does speed things up!

Tom

Replicating over VPN to non trusted workgroup

I have a situation where a client connects to our network via VPN has set up
a SQL Server on a small workgroup that wishes to subscribe (via
transactional replication) to publications on my SQL Publisher.
My stumbling block is permissions to the \\myserver\repldata folder on our
domain. The client machine being a non-trusted domain (in fact not even a
domain) means I can't set up read and list files & folders permissions.
My plan is that I set up the pull subscriptions, create the snapshots and
then copy the entire \\myserver\repldata folder to the client machine and
point the pull subscriptions there.
Is this the best solution in the circumstances? After the initial snapshot,
does transactional replication ever need to access \\myserver\repladat
again?
Cheers!
Simon
Simon,
you can use the alternative snapshot location option - I do it this way for
large snapshots which I zip up before sending over.
If FTP is available this is probably an easier option though to set up the
publication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Many thanks.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OzVonAjYHHA.208@.TK2MSFTNGP05.phx.gbl...
> Simon,
> you can use the alternative snapshot location option - I do it this way
> for large snapshots which I zip up before sending over.
> If FTP is available this is probably an easier option though to set up the
> publication.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
|||Try to use pass-through authentication. This is where you have two identical
local machine accounts with the same name and the same password.
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
"Simon" <simon.gladwell@.gmailNotThisBit.com> wrote in message
news:%23W9Y9siYHHA.448@.TK2MSFTNGP04.phx.gbl...
>I have a situation where a client connects to our network via VPN has set
>up a SQL Server on a small workgroup that wishes to subscribe (via
>transactional replication) to publications on my SQL Publisher.
> My stumbling block is permissions to the \\myserver\repldata folder on our
> domain. The client machine being a non-trusted domain (in fact not even a
> domain) means I can't set up read and list files & folders permissions.
> My plan is that I set up the pull subscriptions, create the snapshots and
> then copy the entire \\myserver\repldata folder to the client machine and
> point the pull subscriptions there.
> Is this the best solution in the circumstances? After the initial
> snapshot, does transactional replication ever need to access
> \\myserver\repladat again?
> Cheers!
> Simon
>
|||That works when I log on that account and browse to the folder. Should I
then run SQL Server and Agent under that local account?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OiI0V2jYHHA.4308@.TK2MSFTNGP05.phx.gbl...
> Try to use pass-through authentication. This is where you have two
> identical local machine accounts with the same name and the same password.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
|||Yes!
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
"Simon" <simon.gladwell@.gmailNotThisBit.com> wrote in message
news:eQmS6QlYHHA.4692@.TK2MSFTNGP04.phx.gbl...
> That works when I log on that account and browse to the folder. Should I
> then run SQL Server and Agent under that local account?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OiI0V2jYHHA.4308@.TK2MSFTNGP05.phx.gbl...
>