June 11, 2008 at 11:21 pm
Hi, anybody can help...
In my Sql server Transaction Replication following error is comming frequently and my Schedule job (for incremental data) is failing.
Error messages:
The process could not execute 'sp_MSadd_replcmds' on 'REPOSITORY'. (Source: MSSQLServer, Error number: 1007)
Get help: http://help/1007
The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions. (Source: MSSQLServer, Error number: 1007)
Get help: http://help/1007
IDistPut Interface has been shut down. (Source: MSSQL_REPL, Error number: MSSQL_REPL2000)
Get help: http://help/MSSQL_REPL2000
The last step did not log any message! (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037
Regards
June 12, 2008 at 2:26 pm
You must check the locks on the distribution database or on the Server in general. Too many locks can make that stored procedure time-out!
* Noel
July 14, 2009 at 10:04 pm
We are getting same error in of our servers.
but error slightly differs
"The transaction log for database "distribution" is full. To find out why sp= ace in the log cannot be reused, see the log_reuse_wait_desc column in sys.= databases 1007: The process could not execute "sp_MSadd_replcmds" on server"
even after shrinking logfiles again they are growing in minutes and filling up the logs frequently..
Is there any configuration settings i need to look at or is this a common issue which cant fixed permanently??
Immediate response appreciated!!!
January 5, 2010 at 8:59 am
Hi replication experts
Old thread but same problem here...
We did a lot of updates and inserts in the database and the protocoll reader gives us that same error message as sekhar has written above.
First I've realised that I had to free some disk space but the problem persisted.
Can you telll me what is causing those locks because this seems to be the root problem. It's counting them up until the process fails and starts again with new locks.
I also noticed that the distribution database has grown in size it is now almost 22 GB whereas it was about 3 GB before the data changes.
I appreciate every help because I'm not that familiar with replication and need to solve this issue as soon as possible.
Thanks a lot!
Roger
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply