Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

This application has failed to start because .dll was not found. Re-installing the application may fix the problem

Created: 20 Oct 2009 • Updated: 22 May 2010 | 3 comments

I am doing a repackaging for one an application. I created MST (wise package studio) for the given MSI. The application installs and launches fine if I install using the MSI & MST through the command line.(normal as well as silent mode)
According to the process in our organisation this MSI and MST will be installed through the VBScript.(silent mode)

The installation with VBScript goes on fine but when I launch the shortcut an error comes up saying that "This application has failed to start because esc11.dll was not found. Re-installing the application may fix the problem". This dll will be in the application folder.

Does anyone have a solution for this..?

Thanks in Advance

Discussion Filed Under:

Comments 3 CommentsJump to latest comment

Jamie.Frisbie@be-intuitive.com's picture

Where is the esc11.dll located? Is this a user specific/profile file? (Possibly under application data). If you are deploying this application using a deployment tool and the file is a CU file, by default, it will not go to all users profiles.
However, It may show up in the folder of the account/profile that was used to push the application.

EdT's picture

Generate a verbose log of the install when you do it from the command line using the same install string as the VBScript uses.
Then generate another verbose log of the install when you do it from the vbscript.
Compare the logs - specifically search for the file esc11.dll in the log.

However, before you start, check that you have the ALLUSERS property set to 1 in the property table. A lot of these issues can be caused by leaving ALLUSERS unset, when it will default to a setting of 0, which is a "per user" install. If the install is using self registration for any DLL files (not recommended by the way), then in a per-user install, the registration is performed to the account that is running the install, and not to ALL Users.
Consequently, running the application using a different user account to the installing account will often cause the application to fail because it cannot see the DLL registration information.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.