SCCM Application Deployment fails 1st time (code 16389) but successful 2nd time - Session ID numbers?


I am trying to deploy an application that has a dependency on another application .net framework being installed.

When i deploy the application, it recognises that .net framework needs to be installed, but then fails with exit code 16389.  If i then open Software center on the client, "retry" the installation, it works fine.

When i look at appenforce.log the only differences that i can see between the two attempts in the Session ID.  The first attempt runs as session ID 4294967295 and the second attempt runs as session ID 1

Before this, i was getting error code 16389 when attempting to deploy the application at all, and this was fixed by selecting the option "run installation and uninstall program as 32-bit processes on 64-bit clients", but now it fails the first time and works the 2nd.

Any suggestions why a retry works?

Thanks in advance
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rick HobbsRETIREDCommented:
More than likely the initial attempt is making some change that then allows it to install.  Install Revo uninstaller and do a logged install.  Examine the log and see if you can discern the reason.
fyi: session id 4294967295 is 0xffffffff in hex is -1 as a signed integer and is an invalid id therefore.

i agree with Rick. if a setup always succeeds at second attempt, the components were installed in the wrong order in the first attempt.

that means you need to reorder your dependencies. for example it could be necessary to install .net as one of the first components if some setup code is dependent on a .net service as well.

WolfAuthor Commented:
This ended up being an issue with the .net framework installation options I was using.  When installing .net framework i was using /ADMINDEPLOYMENT which after checking with Microsoft needed to be removed.

Once this was done i was able to install .net 1st time 100% of the time

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WolfAuthor Commented:
Solution provided by Microsoft Support
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.