The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, reinitialize all subscriptions to the publication.
The log provider "%1!s!" cannot log messages on the installed %2!s! of SQL Server. The log provider requires %3!s! or higher. ...
The log provider for SQL Server Profiler was unable to load pfclnt.dll. Please check that SQL Server Profiler is installed. ...
The log provider type "%1!s!" specified for log provider "%2!s!" is not recognized as a valid log provider type. This error ...
The log provider type is not recognized as a valid log provider type. This error occurs when an attempt is made to create ...
The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, ...
The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately %1!d! log records have ...
The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %1!s! transactions ...
The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%1!s!:%2!s!:%3!s!}, ...
The Log Reader Agent was unable to connect to the Publisher using the specified login. Make sure that the login used by the ...