Post reply

Snapshot error

  • October 19, 2010 at 7:04 am

    #228106

    I'm getting an error in the snapshot creation job of replication process. Running MSSQL Server 2005, SP3 on Windows 2003 cluster, active/passive. AWE enabled.

    Job had been running successful before.

    Any help is greatly appreciated.

    Job history details:

    Date 10/19/2010 3:00:01 AM

    Log Job History (Replication xxxx-Snapshot)

    Step ID 2

    Server server\instance

    Job Name Replication xxxx-Snapshot

    Step Name Run agent.

    Duration 00:00:05

    Sql Severity 0

    Sql Message ID 0

    Operator Emailed

    Operator Net sent

    Operator Paged

    Retries Attempted 0

    Message

    2010-10-19 08:00:03.62 -QueryTimeout 1800

    2010-10-19 08:00:03.62 ---------------------------------------------

    2010-10-19 08:00:03.65 Connecting to Publisher 'server\instance'

    2010-10-19 08:00:03.70 Publisher database compatibility level is set to 90.

    2010-10-19 08:00:03.72 Retrieving publication and article information from the publisher database 'server\instance.db'

    2010-10-19 08:00:04.20 [0%] Validating the synchronization view for article 'table1'

    2010-10-19 08:00:04.22 [0%] The replication agent had encountered an exception.

    2010-10-19 08:00:04.22 Source: Replication

    2010-10-19 08:00:04.22 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException

    2010-10-19 08:00:04.22 Exception Message: A transport-level error has occurred when receiving results from the server. (provider: Named Pipes Provider, error: 0 - Insufficient system resources exist to complete the requested service.)

    2010-10-19 08:00:04.22 Message Code: 1450

    2010-10-19 08:00:04.22

  • October 19, 2010 at 7:11 am

    #1239015

    Might be related to this? -> http://blogs.msdn.com/b/psssql/archive/2008/07/10/sql-server-reports-operating-system-error-1450-or-1452-or-665-retries.aspx

    From the article:

    The error cause is related to a depleted system resource (non-paged pool, paged pool ,...). These issues have to be tracked down at the operating system level. This involves collection of system level performance monitor counters and evaluating the basic health of the overall system.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply