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.

Error 3221225794

Updated: 23 May 2010 | 4 comments
Florian Spisla's picture
0 0 Votes
Login to vote

When installing software using Software Delivery Solution I get more and more packages that sometimes run into return code 3221225794. The same package may install flawlessly on one client and with that return code on another.



I haven't found anything so far.



It looks as if NS doesn't even start the script (normally I use *.cmd files for installations).



Any ideas? I'm not that good at debugging ;-)



Thanks

Florian

Comments

Dominiqueg's picture
30
Oct
2008
0 Votes 0
Login to vote

Hello,



You might want to check the KB33303 as there could be time to time some issues distributing packages even the same one to various machines.



Thanks

Florian Spisla's picture
27
Nov
2008
0 Votes 0
Login to vote

Hey Dominique... That Article doesn't describe my problem. No VBS involved.

My installations are wrapped into a CMD-File.

jharings's picture
27
Nov
2008
0 Votes 0
Login to vote

I don't know if it applies to .cmd files, but I know with .bat files, I always listed the full path to cscript or wscript, much like msiexec to ensure stuff would run. This would mean, %windir%\system32\wscript.exe "xxx.cmd"

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

rlgura's picture
06
Mar
2009
0 Votes 0
Login to vote

Sorry for reviving this old thread, but I've been seeing this problem more lately too although this is the first time I've seen the 3221225794 error code.

After some digging around, I found this error code means that "this installation cannot proceed because the workstation is shutting down."

I've noticed that after applying one of the latest patches (I think R8), some of my software delivery tasks that are set to "only run when no user is logged in" start to fire off as soon as the user logs off or restarts. This usually results in a "completed asynchronously" message and more often than not, the package did not install (unless it was really quick). It seems Altiris may have fixed the issue with the agent taking a long time (5-15 min) to realize that a machine was logged off too well!



Anyone else seeing this? have a work-around or solution?