Deployment Solution

Hello,

I'd like to ask you out there if you have/had this issue with DS ? Seems like something is not working well. It started out of nowhere and it's occuring more and more preventing our swap operations. Only about 60% of the daily plan is done every day, the rest fails with this mysterious error.

I usually troubleshoot SMP so I have not much experience with DS. Can you let me know what I can check (apart from the Windows event logs) to get closer to this problem?

Or if you have a solution right away that would be a blast ;)

Thanks!

Petr

on random steps could mean ... a lot of things.  Error 128 "means" there wasn't a child process waiting - nonsence.  Maybe DB busy? Deadlocking?  There is logging for the DB but it can be and ... "interesting" challenge to decipher (If you thought the NS A.Logs were bad...)  See if you can find any sort of pattern.  Cut the # of clients in half, or roll it in waves and see if the problem goes away.  Watch system resources to see if during execution you see CPU spiking or something.  Check the windows logs on the destination systems to see if something ther.  That's where I'd start anyway...

Thanks for the hints Thomas! I will check it. Currently we have a case at Symantec support with this issue. Where did you get the description of the error 128? 

Ahhh - that was dumb - I didn't include the link.  Having worked inside for many years, I knew there were KB's with error codes in them, looked one up, and found that.  Then I was stupid and didn't post where, probably because it told me nothing.

If you still can't find it, let me know and I'll go dig it up again.  :D

OK found it.. Thanks!

https://www-secure.symantec.com/connect/downloads/altiris-microsoft-error-codes-and-descriptions

ok, so apparently our monitoring system went crazy and created a huge amount of cmd.exe processes (perhaps could not end them) and that's why DS had troubles creating it's own subprocesses at some level. Anyway this kb (http://support.microsoft.com/kb/960266/en-us) we had already installed, even with higher version already..  I guess it was bigger amount of child processes than the operating system expected.

cool - i mean, not in a good way cool, but glad you found it!