locked
SMS status Message issue RRS feed

  • Question

  • Hi Team,

    Now currently i am facing the problem with SMS 2003 primary site server. Status messager under this folder is not processing

     

    SMS intallation drive \SMS\inboxes\statmgr.box\statmsgs - this folder has 1155524 files.

    I have checked the datbase connection and all are fine and no backlog sql is present in SMS installation drive:\SMS\inboxes\statmgr.box\retry

    Please adivcse me how to resolve this issue.

     

     

     

     

    Wednesday, October 12, 2011 4:23 PM

Answers

  • Yes, You can create or Just copy all the files from that location to a temp folder.. also works..........

    But remember if there is a problem like a backlogs ...in that situation Yes it will still continue to place the upcoming file to the  inbox.......


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, November 9, 2011 9:41 AM

All replies

  • Did you check the the files are getting processed or NOT getting processed at all ?

    Have you checked statmgr.log?


    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Wednesday, October 12, 2011 5:30 PM
  • The is not getting processed at all.

     

    In queue folder also having 103666 files.

    No error in statmsg.log and compusumm.log.

    Thursday, October 13, 2011 8:53 AM
  • Give a restart of SMS related  Services and monitor the Statmgr.log

    As Anoop requested you can post the Statmgr.log file.

     


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, October 13, 2011 8:57 AM
  • i am unable to restart the SMS_Executive service, its going to Stopped mode frequently while restarting the SMS_Excutive serivce.

    Thursday, October 13, 2011 9:33 AM
  • Hello - I think your SMS exec service is getting crashed.

    Below article may help to start troubleshooting on the issue....

    http://www.myitforum.com/articles/2/view.asp?id=2697


    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Thursday, October 13, 2011 9:37 AM
  • Hi Anoop,

    i have checked, no recent SMS executive crash history or folder and also i have checked the ddm.log, all the files are processing with any error.

    Could you please help on this.

    Thursday, October 13, 2011 10:22 AM
  • DDR files are processing with error or without any errors?

    If you can see some errors then provide the details.

    Check the SQL connectivity? And the SMS exec service started now ?


    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.


    Thursday, October 13, 2011 10:27 AM
  • How to enable status message make it process every 1 hour in sms2003.
    Thursday, October 13, 2011 2:27 PM
  • Sorry, you didn't answer my questions?

    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Thursday, October 13, 2011 6:36 PM
  • Not sure what you mean. We process status messages when the arrive, there is no schedule for processing them. There is a scheduled task for summariation o status messages.
    Wally Mead
    Sunday, October 16, 2011 12:37 PM
  • DDR files are processing, withour any errors.

    now the status messge count is 1180532. Please help on this. If you want i can provide log information also.

    Monday, October 17, 2011 10:01 AM
  • But did you check the Statmgr.log for any errors ? Did you whether the status messages are getting process or still stuck ?

    I think, you are having SQL connectivity issue.

    I would suggest you to raise a Microsoft CSS call if this is very critical to you.


    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Monday, October 17, 2011 10:14 AM
  • SQL server and SMS are in the same box. could you pleaes tell me how check the connectivity issue.
    Monday, October 17, 2011 12:29 PM
  • First step should be to check the log file mentioned above to know about any errors or not.

    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Monday, October 17, 2011 12:32 PM
  • Please find hte statusmsg.log file, i am unable to find any errors.

     

    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 1 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 3 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to replicate the batch of medium-priority status messages, because at least 300000 have elapsed since we started building the batch. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Successfully instructed SMS_REPLICATION_MANAGER to replicate a medium-priority, 3249-byte batch of 27 status messages to our parent site UEU. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 912-byte SQL transaction to insert 4 status messages and their 5 insertion strings and 4 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 5 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Starting to batch up status messages for medium-priority replication.  The replication job will be created in 300000 milliseconds, or when the batch reaches 1048576 bytes in size, whichever comes first. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 5 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 2291-byte SQL transaction to insert 10 status messages and their 16 insertion strings and 12 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 4 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 3 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to replicate the batch of medium-priority status messages, because at least 300000 have elapsed since we started building the batch. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Successfully instructed SMS_REPLICATION_MANAGER to replicate a medium-priority, 2169-byte batch of 17 status messages to our parent site UEU. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 1799-byte SQL transaction to insert 7 status messages and their 13 insertion strings and 10 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 6 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Starting to batch up status messages for medium-priority replication.  The replication job will be created in 300000 milliseconds, or when the batch reaches 1048576 bytes in size, whichever comes first. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 5 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 2563-byte SQL transaction to insert 11 status messages and their 19 insertion strings and 10 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 8 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to replicate the batch of medium-priority status messages, because at least 300000 have elapsed since we started building the batch. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Successfully instructed SMS_REPLICATION_MANAGER to replicate a medium-priority, 2531-byte batch of 19 status messages to our parent site UEU. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 9 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Starting to batch up status messages for medium-priority replication.  The replication job will be created in 300000 milliseconds, or when the batch reaches 1048576 bytes in size, whichever comes first. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 4190-byte SQL transaction to insert 17 status messages and their 33 insertion strings and 18 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 5 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 6 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to replicate the batch of medium-priority status messages, because at least 300000 have elapsed since we started building the batch. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Successfully instructed SMS_REPLICATION_MANAGER to replicate a medium-priority, 2947-byte batch of 20 status messages to our parent site UEU. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 2677-byte SQL transaction to insert 11 status messages and their 19 insertion strings and 12 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 6 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Starting to batch up status messages for medium-priority replication.  The replication job will be created in 300000 milliseconds, or when the batch reaches 1048576 bytes in size, whichever comes first. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 4 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 2954-byte SQL transaction to insert 10 status messages and their 23 insertion strings and 18 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 5 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to replicate the batch of medium-priority status messages, because at least 300000 have elapsed since we started building the batch. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Successfully instructed SMS_REPLICATION_MANAGER to replicate a medium-priority, 2423-byte batch of 15 status messages to our parent site UEU. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 8 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Starting to batch up status messages for medium-priority replication.  The replication job will be created in 300000 milliseconds, or when the batch reaches 1048576 bytes in size, whichever comes first. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 3801-byte SQL transaction to insert 13 status messages and their 29 insertion strings and 19 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 8 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 5 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to replicate the batch of medium-priority status messages, because at least 300000 have elapsed since we started building the batch. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Successfully instructed SMS_REPLICATION_MANAGER to replicate a medium-priority, 3257-byte batch of 19 status messages to our parent site UEU. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to commit the SQL transaction we've been building, because at least 60000 milliseconds have elapsed since we started building it. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Beginning a 3664-byte SQL transaction to insert 13 status messages and their 30 insertion strings and 17 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Committed the transaction for asynchronous execution.  We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Removed 5 status messages from the in-memory queue for processing. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Starting to batch up status messages for medium-priority replication.  The replication job will be created in 300000 milliseconds, or when the batch reaches 1048576 bytes in size, whichever comes first. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Processing complete. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    It is now time to check the progress of the currently-executing SQL transaction. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    The currently-executing transaction completed successfully. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Sleeping until an event is signalled... SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)
    Status messages might be available in the in-memory queue. SMS_STATUS_MANAGER 1/1/1601 12:00:00 AM 5364 (0x14F4)

    Monday, October 17, 2011 12:44 PM
  • Is it possible to rename the old statemgr.box and create new structure similarlly by stopping SMS executive service?..

     

    sasi

     


    sasi
    Wednesday, November 9, 2011 9:38 AM
  • Yes, You can create or Just copy all the files from that location to a temp folder.. also works..........

    But remember if there is a problem like a backlogs ...in that situation Yes it will still continue to place the upcoming file to the  inbox.......


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, November 9, 2011 9:41 AM
  • Yes, I know this is an old post, trying to clean them up before CM12 is released. J

     

    Did you ever get this fixed, if so how?


    http://www.enhansoft.com/
    Sunday, February 5, 2012 4:11 PM