Troubleshooting
Problem
How do you resolve the Windows install error 1935?
Cause
Resolving The Problem
The Windows install error 1935 can prevent you from being able to install WebSphere MQ.
In general, this error means that Windows Installer encountered an error while trying to install assemblies to the Global Assembly Cache (GAC). This error is considered fatal and causes setup to fail.
When running the setup in interactive mode, you may see a message box indicating that a 1935 error occurred, and it will list the HRESULT value and the Windows Installer component of the assembly that caused the error.
Where to find the log files
In order to diagnose the cause of a 1935 error, locate the Windows Installer log. The log files will provide useful information and can be found in the following location:
C:\Documents and Settings\<userid>\Local Settings\Temp\
or
C:\Users\<userid>\AppData\Local\Temp
The file name will begin with MQv7x_Install.
Where to find error information in the log file
To pinpoint the cause of a 1935 error, search for the string return value 3 as in the example below. This will show the exact point in which setup failed. The following is an example of the information written to a Windows Installer verbose log file in the case of a 1935 error:
MSI (s) (18:DC) Ý08:54:08:801¨: Product: IBM Websphere MQ 32bitSupport
-- Error 1935.An error occurred during the installation of assembly
component {97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}. HRESULT: 0x800736FD.
assembly interface: IAssemblyCacheItem, function: Commit, assembly name:
Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="
1fc8b3b9a1e18e3b",processorArchitecture="x86"
Action ended 8:54:08: InstallFinalize. Return value 3.
In this example, the assembly failed to install properly due to an error with HRESULT value 0x800736FD
This behavior can occur for various reasons such as incorrect registry entries, libraries being reloaded by the installer after a recent install or removal attempt of the assembly, or other issues. In the above example, the HRESULT seen is 0x800736FD, meaning:
"An HRESULT could not be translated to a corresponding Win32 error code"
This is due to Windows Installer behavior on Windows NT platforms but does not tell us why the installation failed.
You can attempt either of the following methods to resolve this problem:
- Restart your computer.
-or- - Stop, then restart the Windows Installer (msiservice) and try the installation again.
1. Open Control Panel.
2. Double-click Administrative Tools.
3. Double-click Services.
4. Right-click the Windows Installer service.
5. Click Stop.
6. Click Start.
If you are still unable to resolve the 1935 error after either of the above two methods, gather the following documents and contact IBM Support for further assistance:
1. Microsoft Support Diagnostic Tool (http://support.microsoft.com/kb/926079)
2. MSI Verbose logging (http://support.microsoft.com/kb/223300)
3. Process Monitor Logs (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx)
The following is a list of possible HRESULT values and their meanings.
Return type | Return code | HRESULT | Description of error |
| TYPE_E_DLLFUNCTIONNOTFOUND | 0x8002802F | -2147319761 | Function not defined in specified DLL |
| ERROR_ACCESS_DENIED | 0x7FF8FFFB | -2147024891 | Access is denied |
| COR_E_MODULE_HASH_CHECK_FAILED | 0x80131039 | -2146234311 | The check of the module's hash failed |
| FUSION_E_REF_DEF_MISMATCH | 0x80131040 | -2146234304 | The located assembly's manifest definition does not match the assembly reference |
| FUSION_E_INVALID_PRIVATE_ASM_LOCATION | 0x80131041 | -2146234303 | The private assembly was located outside the app-base directory |
| FUSION_E_ASM_MODULE_MISSING | 0x80131042 | -2146234302 | A module specified in the manifest was not found |
| FUSION_E_UNEXPECTED_MODULE_FOUND | 0x80131043 | -2146234301 | Modules which are not in the manifest were streamed in |
| FUSION_E_PRIVATE_ASM_DISALLOWED | 0x80131044 | -2146234300 | A strongly-named assembly is required |
| FUSION_E_SIGNATURE_CHECK_FAILED | 0x80131045 | -2146234299 | The check of the signature failed |
| FUSION_E_DATABASE_ERROR | 0x80131046 | -2146234298 | An unexpected error was encountered in the Assembly Cache database |
| FUSION_E_INVALID_NAME | 0x80131047 | -2146234297 | The given assembly name or code-base is invalid |
| FUSION_E_CODE_DOWNLOAD_DISABLED | 0x80131048 | -2146234296 | HTTP download of assemblies has been disabled for this app-domain |
| FUSION_E_UNINSTALL_DISALLOWED | 0x80131049 | -2146234295 | Uninstall of given assembly is not allowed |
| FUSION_E_NGEN_DEPENDENCY_NOT_FOUND | 0x80131050 | -2146234288 | One of the native image dependencies cannot be found |
| FUSION_E_NGEN_INDEX_CORRUPTED | 0x80131051 | -2146234287 | ngen index corrupted |
Product Synonym
WMQ MQ
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21611177