Replication - Snapshot Agent "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
-
Some system details: both the publisher and subscriber are Standard Edition (64-bit), Build 10.50.2806.0 (SP1+CU5). The distributor is the subscriber instance.
I received an email alert from my replication monitor this morning with the following information:
DATE/TIME:6/22/2012 11:30:29 AM
DESCRIPTION:Replication-Replication Snapshot Subsystem: agent <name removed> failed. The replication agent had encountered an exception.
Source: Unknown
Exception Type: System.AccessViolationException Exception Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Message Code:
COMMENT:(None)
JOB RUN:(None)
Here is the snapshot agent history:
As you can see, the subsequent sync succeeded. All syncs since the error have succeeded. Searching online did not reveal much, but it's Friday and it has been a long week so I might not be seeing the forest through the trees.
Here is the complete error message:
Error messages:
Source: System.Data
Target Site: Boolean ConvertSidToStringSidW(IntPtr, IntPtr ByRef)
Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack: at System.Data.Common.UnsafeNativeMethods.ConvertSidToStringSidW(IntPtr sid, IntPtr& stringSid)
at System.Data.ProviderBase.DbConnectionPoolIdentity.GetCurrent()
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Replication.Utilities.CreateOpenedSqlConnection(String applicationName, ServerNameParameter serverName, NetworkLibraryParameter networkLibrary, ConnectionEncryptionLevelParameter connectionEncryptionLevel, StringParameter databaseName, SecurityModeParameter securityMode, LoginParameter login, PackableParameter password, LoginTimeoutParameter loginTimeout, PacketSizeParameter packetSize, ServerNameParameter workstationID, String failoverPartner)
at Microsoft.SqlServer.Replication.AgentCore.CreateOpenedSqlConnection(String applicationName, ServerNameParameter serverName, NetworkLibraryParameter networkLibrary, ConnectionEncryptionLevelParameter connectionEncryptionLevel, StringParameter databaseName, SecurityModeParameter securityMode, LoginParameter login, PackableParameter password, LoginTimeoutParameter loginTimeout, PacketSizeParameter packetSize, ServerNameParameter workstationID, DeadlockPriorityParameter deadlockPriority, String failoverPartner)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpLoadHintAndPartitioningResolutionWorkerThreadProvider.Initialize()
at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: System.Data, Error number: 0)
Get help: http://help/0%5B/quote%5D
Has anyone encountered this error message or have any suggestions about what it means and how I should react?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato -
First thing, check your backups are all good, checkdb out the wazoo and then get a hardware check run against the memory modules in your server.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply