Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

CSMFAgent_Agent Errors

Updated: 21 May 2010 | 3 comments
kevin.wilson@valerent.com's picture
0 0 Votes
Login to vote

Hey all,

Just ran into a new error and cannot find any info on it.

"Unexpected exception processing Agent Policies during wakeup - HR=800410000d Failed to create thread Not enough Storage is available to process this command."

I checked and have plenty of drive space available, so I am not sure what the deal is.

Thanks,
Kevin

Comments

TheSmiz's picture
08
Apr
2009
0 Votes 0
Login to vote

Did you ever solve this?

Did you happen to ever solve this?  I saw the same error and rebooted the server and all was well.  I am guessing the server service was running out of memory either from AV (McAfee) or the Altiris Agent or maybe a little of both.

Just thought I would see what you were experiencing and see if you found a good resolution.

RS

MitchInOmaha's picture
15
Jul
2009
0 Votes 0
Login to vote

Same problem here

I've started seeing this same error on some of our devices as well.  Had Symantec support on the phone when we ran across it (error coming from theNS's agent no less). 

CSMF is Software Management; Symantec support disabled our Software Inventory job and the error went away, but now we're not getting Software Inventories, at least for now.  Unfortunately, the support agent didn't have any explanation for why this was an issue.  He also indicated that they were going to search through code for this error, but after we connected two hours later, they hadn't found it.

-- Mitch

-- Mitch

If your question has been resolved, please be sure to "Mark as Solution"! Thank you.

mtaber's picture
17
Jul
2009
1 Vote +1
Login to vote

Potential solution

I believe that this is due to an excessive number of I/O requests in the network stack and the buffer is getting overloaded because it can't keep up. That's why it complains about "Not enough Storage is available to process this command". This is most likely indicative of something else going on performance wise, but I've seen this happen on VMWare images as well because they're a bit slower to begin with.

Go into the registry of the server and manually set the IRPStackSize as a DWORD in the following location:

HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

Set the value to 0x32 hex or 50 decimal. Do not set it higher, as Microsoft's documentation indicates that a larger value is ignored. I think the default is something like 15, but I didn't pay enough attention as to whether that was hex or decimal. Once you create or set this value, reboot the machine and you should be good to go.

If you search for IRPStackSize and Symantec on Google, you'll find this is something of a prevalent problem.

Mike Taber
Moon River Consulting, Inc.
http://www.moonriverconsulting.com