SCCM Application Deployment fails 1st time (code 16389) but successful 2nd time - Session ID numbers?
Hello
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
ScreenHunter_269-Oct.-09-11.49.jpg
ScreenHunter_270-Oct.-09-11.49.jpg
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
ScreenHunter_269-Oct.-09-11.49.jpg
ScreenHunter_270-Oct.-09-11.49.jpg
Rick Hobbs
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.
Sara
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.
Sara
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Solution provided by Microsoft Support