Application deployment fails on 1st attempt, successful on 2nd - Exit Code 16389

[horshamit]

Hello

I'm looking for some advice on a problem I am having when trying to deploy an application that has dependencies on other applications. Please bear with me while I try to explain the problem.

I am trying to deploy an application called SAP, that has a dependency on 2 other applications - .net Framework and Visual C++ Redist. When the application is deployed, if it detects if one of the 2 other apps are missing and then it will automatically deploy those first.

If I deploy SAP to a client that has both dependencies, the deployment works fine. If i deploy to a client that does not have .net installed the deployment fails with exit code 16389.

After some research I discovered that i need to change the deployment setting to "run installation and uninstall program as 32-bit processes on 64-bit clients". This now seems to get further but is still failing.

I'm deploying SAP and using notifications in Software Centre to monitor the deployment. The packages are downloaded successfully, it detects that .net framework isn't installed, but as soon as it tries to deploy .net it fails again with exit code 16389. However, if i then click "retry" within Software Centre the entire deployment works fine - .net and SAP installation!

When I look through the appenforce.log file i can see both attempts at the deployment, the 1st with the error exit code, and the second one going through fine. The only differences that i can see between them in the log file are the session ID's:

The 1st attempt session ID is 4294967295

The 2nd attempt session ID is 1

Any idea why this would be happening? I've attached some screenshots if that helps at all.

Thanks in advance

Andrew

[adurrant]

Hi there,

 

Is there any issues when you try to install .net framework manually?

[horshamit]

If I run the following manually it works fine:

 

NDP452-KB2901907-x86-x64-AllOS-ENU.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT

 

Seems to be only via SCCM deployment thats having a problem.

 

I also get the same error if i deploy the application for .net only, and not as a dependency for SAP

[adurrant]

What windows OS are you attempting to deploy this to? It might be that you have to enable net framework 4.0 from within programs and features. Could use DISM for that.

[horshamit]

Trying to deploy to a mixture of Windows 7 Enterprise and Pro, 95% are x86

 

The test VM's i'm using are Windows 7 Enterprise x86 with SP1 and all other latest updates

[adurrant]

by the looks of it, network 4.5.2 is required? what version of net framework is on these machines to begin with? Try taking a look at these:

 

http://fearthemonkey.co.uk/889/

http://www.nowmicro.com/deploying-net-framework-4-5-2-configmgr-application/

[horshamit]

Thanks, these are actually the two sites I used to create the package in the first place.

 

The machines i'm attempting to deploy to have no version of .net installed

[horshamit]

Notice something else now...

 

If i make the application available to the client, and then click install from software centre, the application deploys and installs ok

 

If I make it required, it fails, and then only works if i click retry in software centre

[adurrant]

Could be worth checking your detection methods, an application is only classed as successful, if after the install it's detected.

[horshamit]

Would it not be an issue there after the installation though? The application isn't even installing so it wouldn't have anything to detect

[adurrant]

Is there anything the netframework installation logs, normally there here:

 

“%temp%\Microsoft .NET Framework 4.5*.txt”

“%temp%\Microsoft .NET Framework 4.5*.html”

&

C:\Windows\Temp\dd_NDP452-KB2901907-x86-x64-AllOS-ENU_decompression_log.txt

This might help you to see what's going on.

[horshamit]

I've tried a few options now:

 

1. Expanding the .net package, and then re-zipping it as a self-extracting .exe. I then created a bat file to expand the file, install .net, and then delete the expanded files. This installed .net but SCCM returns a failed code
2. Then I tried writing an AutoIT script to expand the files and install, but after it expands SCCM fails stating that an installation is already in progress
3. Finally, i tried writing an AutoIT script that installs from the normal .net install file. Like above, this installed .net successfully but SCCM returns a failed code as it can't detect the installation after completion. I've double checked the Detection Rule is correct, and the registry key is in place after the installation, so I don't know why its not working

Any ideas?

[horshamit]

I've noticed that whenever i try any other install option other than the standard NDP452-KB2901907-x86-x64-AllOS.exe the installation is successful, but SCCM reports it as failed as it can't detect the program.

 

I thought that the detection method was only used before the installation takes place? I've double checked my detection rule and it seems to be correct, and indeed after the installation completes the registry that its looking for is in place.

 

Any other ideas?