I am getting the terribly non elightening 0x80070643 when executing packages in an OSD task sequence. Normally I would try tracking it down using MSI logging, if nothing else to maybe give me a clue why it's happening. But here's the weird part it doesn't consistently fail. On some of the computers it works just fine, on others it fails. I can run the OSD task sequence again and it very well may work on the machines that it failed on. I've seen this on several packages, some of which are very simple nature (e.g. Visual Studio C++ runtimes 2005 and 2008). Now interestingly if VC++ 2005 fails, so will 2008. The packages are set to download and execute, I'lll have to pull the logs to look to see if there's anything going on.Bob

Error code 643 (hex) = 1603 which is a generic MSI install fail. You must always examine the log file from the install to determine the cause. This is not a failure in the task seqeunce but in the msi being installed ad so you must troubleshoot the problem there. As to why it seems to be inconsistent, there must be some other variable at play that is leadig to the inconsistency -- until you track down the exact cause though, figuring out what this variable is may be difficult.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Thanks Jason, I figured that out already. What I was hoping is that someone may have seen something that might be causing the MSI to fail. I suspect the package may come down corrupt, incomplete or something else. I'm pretty sure there isn't anything wrong with the package since the TS runs the package just fine on other machines. Bob

do yo uinstall framework as part of your Update step, or are they added to the image?? Michaelhttp://kongkuba1.spaces.live.com

Error code 643 (hex) = 1603 which is a generic MSI install fail. You must always examine the log file from the install to determine the cause. This is not a failure in the task seqeunce but in the msi being installed ad so you must troubleshoot the problem there. As to why it seems to be inconsistent, there must be some other variable at play that is leadig to the inconsistency -- until you track down the exact cause though, figuring out what this variable is may be difficult. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys For most 643 error, it's a Windows Update/Microsoft Update/Service Pack/.Net Framework installation issue. It could be caused by: 1. setup package corrupt. 2. Original program have corrupt file/registry key Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Turns out you are very close Robinson, turns out it was HP SoftPaqs that weren't cleaning up properly. I stuck a reboot in the task sequence right after they installed and the problems went away. So another thing to add to the standard list of things to try is a adding a reboot.Bob