Problem: In some customer node the application does not start after installation. It crashes at the startup. What are the possible common reasons to investigate in such cases?
Analysis: As per my experience, most probable causes are as follows:
Analysis: As per my experience, most probable causes are as follows:
- Pre-requisites software of the application are missing.- It is not always possible to package all the pre-requisites of an application in installation package. Hence it is documented in the installation and configuration manual.Check in the add and remove programs if all the software are installed. One of the pre-requisite software may be missing on the node. Use the dependency viewer or dependency tool to find the missing dependent binaries on the node. Or use Windbg tool and start the application, it may give some idea on the pre-requisite software. Compare the loaded binaries of the application process with the list that it is supposed to load. For example, compare it with the list of binaries loaded by the application on a working node.Some of the companies have their own tool to check all the software installed on a node.
- Check in the event list of the application, it may have important pointers to solve the issue.
- Some times the certificate may not be valid, check for the certificate related information from the call stack.
- Some times the correct .NET framework may not be installed. In newer Windows operating systems some of the older .NET feature has to be enabled from the programs and features option.
- Check for access rights or domain policy, firewall, anti virus software, ports etc that might be preventing the application from launching.
- Some times, the 64 bit version of the pre-requisite may be installed while the application may need 32 version of the software or vice versa. For example Visual Studio run time.
- Application may need VB run time support
- Issue with the license of the product. The Windows OS is not licensed, using unlicensed windows version may lead to unexpected behavior in applications. Even unlicensed version of software's can cause unreliable behaviors, like excel may instigate issues with add-ins.
- Issue with device drivers, some times I have seen issue with the graphics driver preventing the graphics from displaying. check which device drivers are supported by the application.
- Not enough OS resource like memory, CPU etc
- In case of COM, sometimes the problem of GUID being reused by more than one COM module (DLL hell issue). DLL may not be registered or present in GAC.
- Signing related issues with the binaries. For example, binaries signed with SHA2 will no longer work until .Net 4.5 or above is installed on the node.
Comments
Post a Comment