question

RogerRoger-2394 avatar image
0 Votes"
RogerRoger-2394 asked SimonRenMSFT-3639 answered

Past due- Will be retired error in Software Center

Hi Experts

I am facing issue deploying an application. Currently i have an application(appv4) with version 4.0 deployed on all windows 2012R2, windows 2016 and windows 2019 servers. I want to upgrade this application to version 5.0 only on windows 2016 and windows 2019 servers.

i have created an application with version 5.0 and i am able to successfully update from version 4 to version 5 on all 2016 and 2019 servers.

i have now two application app4.0 and app5.0, on application app4.0 i have removed the requirements settings for 2016 and 2019.
i have selected few test servers for both 2016 and 2019 i have uninstalled app5.0 completely and there is no version installed on it.
What i am trying to achieve is if any server doesn't have any version installed app5.0 should be installed

When i deploy the app5.0 on a server which doesn't have any version, app5.0 is getting installed on 2019 servers but its failing on 2016 servers with the below error error Past due- Will be retired error in Software Center

one one of windows 2016 server i can see the below errors in appenforce.log file.

++++++ App enforcement completed (2 seconds) for App DT "MyApplication - Windows Installer (.msi file)" [ScopeId_D8975DDI-87TR-980Y-GTTT-98TYUIERY878/DeploymentType_k879fgtt-7868-uhyi-86hy-u889jukhtu8i],
Revision: 5, User SID: ] ++++++ AppEnforce 4/9/2021 6:00:07 AM 8184 (0x1FF8)
+++ Starting Install enforcement for App DT "MyApplication - Windows Installer (
.msi file)" ApplicationDeliveryType - ScopeId_D8975DDI-87TR-980Y-GTTT-98TYUIERY878/DeploymentType_k879fgtt-7868-uhyi-86hy-u889jukhtu8i,
Revision - 5, ContentPath - C:\Windows\ccmcache\55, Execution Context - System AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Performing detection of app deployment type MyApplication - Windows Installer (.msi file)(ScopeId_D8975DDI-87TR-980Y-GTTT-98TYUIERY878/DeploymentType_k879fgtt-7868-uhyi-86hy-u889jukhtu8i, revision 5) for system.
AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
+++ Application not discovered. [AppDT Id: ScopeId_D8975DDI-87TR-980Y-GTTT-98TYUIERY878/DeploymentType_k879fgtt-7868-uhyi-86hy-u889jukhtu8i, Revision: 5] AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
App enforcement environment:
Context: Machine
Command line: msiexec /i "appv5.msi" AGREETOLICENSE=Yes DEPLOYMENT_SERVER="server01.contoso.com:8080" /quiet /l*v %windir%\app.log /norestart
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\Windows\ccmcache\55
Working directory: AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Prepared working directory: C:\Windows\ccmcache\55 AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Found executable file msiexec with complete path C:\WINDOWS\system32\msiexec.exe AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i "appv5.msi" AGREETOLICENSE=Yes DEPLOYMENT_SERVER="server01.contoso.com:8080" /quiet /l*v C:\WINDOWS\app.log /norestart /qn AppEnforce
4/9/2021 6:13:23 AM 7760 (0x1E50)
Valid MSI Package path = C:\Windows\ccmcache\55\appv5.msi AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Advertising MSI package [C:\Windows\ccmcache\55\appv5.msi] to the system. AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /i "appv5.msi" AGREETOLICENSE=Yes DEPLOYMENT_SERVER="server01.contoso.com:8080" /quiet /l*v C:\WINDOWS\app.log /norestart /qn with
system context AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Working directory C:\Windows\ccmcache\55 AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Post install behavior is BasedOnExitCode AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Waiting for process 8580 to finish. Timeout = 120 minutes. AppEnforce 4/9/2021 6:13:23 AM 7760 (0x1E50)
Process 8580 terminated with exitcode: 1603 AppEnforce 4/9/2021 6:13:25 AM 7760 (0x1E50)
Looking for exit code 1603 in exit codes table... AppEnforce 4/9/2021 6:13:25 AM 7760 (0x1E50)
Unmatched exit code (1603) is considered an execution failure. AppEnforce 4/9/2021 6:13:25 AM 7760 (0x1E50)
++++++ App enforcement completed (2 seconds) for App DT "MyApplication - Windows Installer (
.msi file)" [ScopeId_D8975DDI-87TR-980Y-GTTT-98TYUIERY878/DeploymentType_k879fgtt-7868-uhyi-86hy-u889jukhtu8i], Revision: 5,
User SID: ] ++++++ AppEnforce 4/9/2021 6:13:25 AM 7760 (0x1E50)

mem-cm-generalmem-cm-applicationmem-cm-co-management
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SimonRenMSFT-3639 avatar image
0 Votes"
SimonRenMSFT-3639 answered

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

The 1603 error code is mostly returned when any action fails during an installation, and most commonly it indicates that one of the custom actions in the MSI failed.

It could occur when a file is being used which this MSI needs in order to finish installation. Or when you have a pending reboot. Best way is first install manually on the Windows 2016 servers and find the error and proceed further.

We can also try to enable Verbose Logging the next time the setup package is executed, like this:
msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log"

Thanks for your time.
 
Best regards,
Simon


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.