Symantec Management Platform (Notification Server)

OK, this is getting silly since SP2 came out or I am just losing my mind. I have something causing an exception I want to look at...easy enough right look at the bad NSE...WRONG

Since sp2 I have no idea where they are going. I have checked C:\ProgramData\Symantec\SMP\EventQueue which is where NSEs were going before the upgrade and I see some bad ones in there from before that. I also checked. E:\Program Files\Altiris\Notification Server\NSCap which is where our nscap is on our server... nothing in either one...I searched all 3 partitions for *.nse nothing found but the old ones. 

Did they move them again or is yet something else fubar with my 7.1 SP2 Install?

You didn't move the queues, did you?  You can check by reviewing this KB:
http://www.symantec.com/docs/TECH161370

If you check the registry, does it point you to where your NSE's really are?  It's possible your NS is having trouble processing NSE's post SP2, which is a relatively common problem after a Service Pack.

I hadn't redirected them because that Support article wasn't available when I upgraded so I knew you could but wasn't sure how.

What exception are you getting? Would you expect it to generate a Bad nse?

Im guessing its a bad inventory policy from machines we are cutting over from ns6. But thats what I want to check mostly just saying the guid doesnt exist. 

ITs still set to c:\programdata\symantec\smp\eventqueue so it appears to be yet another thing fubar in this patch. 

It appears they are going there but its might not be keeping the bad ones. I set it to eventqueue1 restarted the services it created the folders. Then I stopped it and set it back and saw this.

If you set it to EventQueue1, it doesn't appear to be using it according to the log entry you posted.

You may want to contact support about the Bad queues being empty -- might be a known issue with SP2.  I don't have any data on it and haven't seen it yet in my upgrades, but I also hadn't gone poking into the queues looking for corrupt NSE's, either.

I only set it to queue1 long enough to create it then set it back to the default and restarted the services again.

Yeah I may have to create another support call this will be like the 3rd since SP2 came out...great. 

...and I just got an email back from Symantec yesterday about the subject. Apparently they've rewritten the Event Queue system in SP2 to use a single folder, C:\ProgramData\Symantec\SMP\EventQueue. I've got a long and relatively detailed email from support as to why they did so, but I'm not sure if I'm at liberty to copy and paste that here on Connect. The long and short of it is that these changes were made to speed up the processing of NSEs in the Event Queue. I'm finding exactly the opposite myself though.

In our case a server that was, with some judicious tweaking of application pools and the queue settings, keeping up with the flow is now perpetually falling behind. I've asked for some updated performance tuning recommendations from Symantec (since I'm guessing that adjusting the various MaxConcurrentSpeedQueues isn't going to do anything anymore) but so far I haven't been given any suggestions. If I hear back, I'll be sure to update this thread.

Wonder what else got missed?

I see that they are going in there but that still leaves the question where are the bad ones going. There is no bad folder in there... looking at bad nse's is a keystone to looking for errors .... 

This KB explains that bad queues can be re-enabled, if you would prefer to see what's not being processed. Otherwise, they are automatically retried three times by the NS:
http://www.symantec.com/docs/HOWTO65758

I hope this answers your question, David!

Yep that answers it, thanks