Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Queue was full - CMS 7.1 SP 2.

Created: 27 Sep 2012 • Updated: 01 Oct 2012 | 6 comments
cec.kadu's picture
This issue has been solved. See solution.

Guys,

Recently I migrate of 7.1 SP1 to SP2, and now I have this problema on my logviewer.

The error started after 2 days of the migration.

 

<event date="Sep 27 12:35:36 +00:00" severity="2" hostName="CMSSERVER" source="Altiris.NS.EventRouter.ProcessAgentHttpPostEvent" module="w3wp.exe" process="w3wp" pid="5164" thread="267" tickCount="64082933"><![CDATA[Event not processed. IP: 0.0.0.00; Error description: Altiris.NS.EventRouter+ServerBusyException: Queue was full.
at Altiris.NS.EventRouter.<>c__DisplayClass3.<RegisterDelivery>b__0(IDatabaseContext ctx)
at Altiris.Database.DatabaseContext`1.PerformWithDeadlockRetryHelper(Int32 retries, Boolean inTransaction, Getter`1 getContext, Action`1 action, Action`1 retry)
at Altiris.Database.DatabaseContext`1.PerformWithDeadlockRetry(Int32 retries, Boolean startNewTransaction, IsolationLevel isolationLevel, Boolean independentContext, Action`1 action, Action`1 retry)
at Altiris.NS.EventRouter.RegisterDelivery(Boolean fileInLine, String tempFile, Int64 fileSize, Guid source, Int32 priority)
at Altiris.NS.EventRouter.DeliverStream(Stream input, Guid source, Int32 priority)
at Altiris.NS.EventRouter.DeliverPostedDataImpl()
at Altiris.NS.EventRouter.ProcessAgentHttpPostEvent()]]></event>

 

Do you have any idea ?

Regards

Custodio

Comments 6 CommentsJump to latest comment

andykn101's picture

You need to look at the queue to check it is processing events, c:\programdata\symantec\SMP\EventQueue\EvtQueue.

If it is processing events you need to check why there are so many or why it's slow; if it isn't processing events you may need to restart services.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

cec.kadu's picture

I know, but my queue have 10.000 files and the processing is very slow.

I execute the article of KB, stop all services and truncate tables, by the moment the error stop, but after 1 day it back.

Carlos Eduardo CUSTODIO

Altiris Consultant

andykn101's picture

Apart from the queue full message, are there other processing errors? I found on v6 that Bad nse's took ten times as long for the NS to process as good ones.

One thing I always do is go to the global settings of the agent and turn off most of the event notifications - I can do without dowload started/stopped and execution started/stopped messages, perhaps you had these off before but they got turned on again in the upgrade.

 

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

cec.kadu's picture

Now the logviewer show me this error messages.

<event date="Sep 27 14:28:37 +00:00" severity="4" hostName="CMSSERVER" source="Altiris.NS.ClientMessaging.EventQueueDispatcher.DispatchLoop" module="AeXSVC.exe" process="AeXSvc" pid="11344" thread="56" tickCount="70863407"><![CDATA[Database is not ready, event queue dispatcher sleeping while it waits.]]></event>

Tks

Custodio

Carlos Eduardo CUSTODIO

Altiris Consultant

andykn101's picture

Ah, that looks like you've problems with the SQL Server, that would explain why events are processing slowly. If you can't see an obvious problem try the SQL query here to identify blocking:

http://www.symantec.com/docs/HOWTO9817

And you might need to check your table sizes, when I used the above I found very large HP Client Manager Solution event tables:

http://www.symantec.com/docs/HOWTO74893

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

SOLUTION
cec.kadu's picture

Thank You Andykn101,

Really the problem was on my database, I resolved this problem executing a repair on database by SIM and after one day the console started processing the events.

Regards

 

Carlos Eduardo CUSTODIO

Altiris Consultant