Hi,

Application Catalog was working fine. We did some configuration changes on certificates, IIS and Client Settings today. I then noticed Application Catalog was not working installing applications. I tried to restore my old configuration. Now I can list applications on Application Catalog, I can send request and download application but installation fails. Strangely, I can install SAP package (not an application) on the same client but MS Office, Visio, Project applications can not be installed. What should I check? T

Start with the log files on the client, specifically appenforce.log and appdiscovery.log.

Thanks Jason,

AppDiscovery.log says:

    Performing detection of app deployment type Microsoft Visio Professional 2013 - Windows Installer (*.msi file)(ScopeId_1822068D-B6FF-4675-BDDF-3C1DACEE4251/DeploymentType_2c5b1740-49ac-4a03-9280-13f13592575a, revision 1) for user.

+++ MSI application not discovered [MSI Product Code: {90150000-0051-0000-0000-0000000FF1CE}, MSI Product version: ]

+++ Did not detect app deployment type Microsoft Visio Professional 2013 - Windows Installer (*.msi file)(ScopeId_1822068D-B6FF-4675-BDDF-3C1DACEE4251/DeploymentType_2c5b1740-49ac-4a03-9280-13f13592575a, revision 1) for S-1-5-21-3053715753-1702837565-2100719752-7169.

---------------------

AppEnforce.log has some red marked errors and says:

AdvertisePackage - MsiAdvertiseProduct Failed : 0x80070643

AdvertisePackage failed (0x80070643).

Lowright users might fail to install this application if it requires higher privileges

Executing Command line: "C:\Windows\system32\msiexec.exe" /i "visproww.msi" /q with user context

Working directory C:\Windows\ccmcache\1k

Post install behavior is BasedOnExitCode

Process 5716 terminated with exitcode: 1603

Looking for exit code 1603 in exit codes table...

Unmatched exit code (1603) is considered an execution failure.

++++++ App enforcement completed (5 seconds) for App DT "Microsoft Visio Professional 2013 - Windows Installer (*.msi file

(The user account that I am logging computer and logging to Application Catalog has local admin privileges on the computer.)

1603 is a generic MSI error.  Add some logging to the install command line using /l*v <path to log file>.  Alternately,  you can edit the registry and add the following:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Reg_SZ: Logging
Value: voicewarmupx

(see https://support.microsoft.com/en-us/kb/223300)

Then in the resulting log, search for Return Value 3.  Just above will be the failing action.

Jeff

1603 is a generic MSI error.  Add some logging to the install command line using /l*v <path to log file>.  Alternately,  you can edit the registry and add the following:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Reg_SZ: Logging
Value: voicewarmupx

(see https://support.microsoft.com/en-us/kb/223300)

Then in the resulting log, search for Return Value 3.  Just above will be the failing action.

Jeff

• Marked as answer by Yavuz Selim Atmaca 22 hours 26 minutes ago

To add-on, by default, if you don't specify a log file location with an MSI it will log in C:\Windows\Temp.

I found the log files under the following path:

C:\Users\%username%\AppData\Local\Temp

and these logs does not give any useful info about the problem I am having. What else can I check?

MSI (s) (7C:EC) [02:01:15:105]: Product: Microsoft Visio Professional 2013 -- Installation operation failed.
MSI (s) (7C:EC) [02:01:15:107]: Windows Installer installed the product. Product Name: Microsoft Visio Professional 2013. Product Version: 15.0.4420.1017. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

I created WinRAR msi file and succesfully deployed it to my client machine. Then I deleted deployments, applications that belong to Visio2013 and recreated and tried  to deploy again and it failed.

I guess I can not deploy only Microsoft products. :( 

Any help would be appreciated.

In verbose MSI log files showing 1603 errors, you need to search for the text "return code 3" and then start reading the lines above that. It's not magic, you'll need to actually review and read the log file.

I figured out that I was missing one step while creating my application. I forgot to type in "Setup.exe" in Installation Program field. After I corrected it, it started working.

Thank you all, I really appreciate your help.

http://selimatmaca.comoj.com/images/AppDeployment/AppDeployment16.png