Issue With Deploying An Application From Configuration Manager

[dpitchers]

I am trying to install an msi from Configuration Manager. My install program is msiexec /i "msodbcsql.msi"

From Software Center the install fails with code 1603. Looking at the log it is failing at Timeout = 120 minutes. I have tried adding the /q switch before the /i switch and get the same error. If I put the /q switch after the  /i switch the install will hang for the 120 minutes and then fail.

Looking for recommendations as to what I can do to get this to work.

[#2]

Add a log to your msi command line, then review the log.

[#3]

I added a log and it tells me nothing. Shows the install getting to the 120 minute timeout and then failing with error code 1603.

[#4]

The MSI log should show that it is waiting for input or something like that. if you are hitting the 2 hour timeout, there is a prompt that isn't silent or it is a HUGE install.

[#5]

Did you tried to install this MSI with the same parameters outside of ConfigMgr? E. g. via CMD Box. Maybe it shows you then what is happening.

[#6]

@dpitchers 

if you still havent figured this out, you could try adding this to the end of your MSI to get the MSI log to see what it is sticking on
msiexec /i "msodbcsql.msi" /qn /L*vx "C:\Temp\Logs\Install.log"

searching for that MSI name, it looks like there may be some other parameters needed
MSIEXEC.EXE /I "msodbcsql.msi" /L*v "%temp%\msodbcsql.log" /qn IACCEPTMSODBCSQLLICENSETERMS=YES ALLUSERS=1

I would guess it's prompting for the EULA, and since it's hidden, it's sitting until it times out.

[#7]

It appears that you are encountering issues while trying to install an MSI package using Configuration Manager. The error code 1603 typically indicates a generic installation failure. In your case, where the installation hangs and then fails with a timeout, there are a few potential troubleshooting steps you can take:

1. Check MSI Package: Ensure that the MSI package you are trying to install is not corrupted and is compatible with the target system. You might want to try installing the MSI manually on a test machine to see if it works outside of Configuration Manager.

2. Logging: Review the installation logs generated during the deployment. These logs can provide more detailed information about the failure. Look for any specific error messages or issues mentioned in the logs.

3. Command Line: It seems you've already experimented with the /q switch. Instead of placing it after the /i switch, try using it before the /i switch like this: msiexec /q /i "msodbcsql.msi". The /q switch is for quiet mode, which suppresses most UI elements during installation.

4. Use a Transform File: If the MSI package supports it, you could consider using a transform (MST) file to customize the installation behavior. This might help address any issues that the default installation settings might be causing.

5. Check Dependencies: Ensure that there are no missing dependencies required for the MSI installation. Some packages might require certain prerequisites to be installed before they can be successfully deployed.

6. Permissions: Make sure the user account or system account running the installation has the necessary permissions to install software on the target machine.

7. Test on a Different Machine: If possible, try deploying the MSI package to a different machine to see if the issue is specific to the target machine or a more widespread problem.

8. Update Configuration Manager: Ensure that you are using the latest version of Configuration Manager. Sometimes, updating the software can resolve compatibility issues.

9. Contact Support: If none of the above steps resolve the issue, consider reaching out to Microsoft or your IT support for further assistance. They might be able to provide more specific guidance based on your environment and setup.

Remember that troubleshooting software deployment issues can sometimes be complex, and it might require a combination of these steps to identify and resolve the underlying problem.