Enterprise Installation Troubleshooting

<< Click to Display Table of Contents >>

Navigation:  Enterprise > Installation > New Installation >

Enterprise Installation Troubleshooting

This article contains troubleshooting information for errors that may occur during the installation process.

 

Installation Ends Prematurely

Error Occurs During Deploy Step

Installer Fails upon Launch

Workflow Service Fails to Start

 

Installation Ends Prematurely

Symptom: During the installation, the installation wizard ends, but displays the following text:

 

EarthSoft EQuIS Enterprise 7 Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard.

 

Cause/Details: This error typically occurs when IIS does not contain a website named "Default Web Site" under Sites.

 

Resolution/Workaround: Temporarily adding a site named "Default Web Site" in IIS prior to running the installation will allow the installer to complete.

 

 

Error Occurs During Deploy Step

Symptoms: During deployment, an error occurs when loading the URL:

 

HTTP Error 500.19 - Internal Server Error

 

The requested page cannot be accessed because the related configuration data for the page is invalid.

 

Cause/Details: This error typically occurs when the server has not been properly configured to enable ASP.NET applications.

 

Resolution/Workaround:  ASP.NET needs to be installed and enabled on the Enterprise application server. For Server 2012 and 2012 R2, this feature can be installed at the following location:

 

Server Manager -> Add Roles and Features Wizard

oWeb Server (IIS)

Web Server

Application Development

oASP.NET 4.7

 

To enable this feature on previous versions of Windows Server, consult the Microsoft Documentation on installing and enabling ASP.NET 4.7.

 

 

Installer Fails upon Launch

Symptoms: The Enterprise installer fails upon launch. The following error displays in the installer:

 

EarthSoft EQuIS Enterprise 7 Setup: Please install IIS with ASP.NET first.

 

EarthSoft EQuIS Enterprise 7 Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard.

 

Cause/Details: EQuIS Enterprise requires the Internet Information Services ASP.NET Application Development Feature to be enabled on the target machine.

 

Resolution: ASP.NET needs to be installed and enabled on the Enterprise application server. For Server 2012 and 2012 R2, this feature can be installed at the following location:

 

Server Manager -> Add Roles and Features Wizard

oWeb Server (IIS)

Web Server

Application Development

oASP.NET 4.7

 

To enable this feature on previous versions of Windows Server, consult the Microsoft Documentation on installing and enabling ASP.NET 4.7.

 

 

Workflow Service Fails to Start

Symptoms: The following error may occur when attempting to start the EQuIS Enterprise workflow services through Windows Services

 

Error 1053: The service did not respond to the start or control request in a timely fashion.

 

Cause/Details: Typically this error occurs when one of the Enterprise configuration files (Web.config, EarthSoft.Workflow.Services.exe.config, or connectionstrings.config), has been manually edited and contains a syntax error and as a result, the Enterprise workflow services are unable to process the configuration file and start.

 

Resolution/Workaround: To test the configuration file to see if it contains a syntax error, recreate the connection string with the structure outlined in Step 4d of New Enterprise Installation Instructions.

 

If that does not resolve the issue, copy the config files into a new directory. Rename the .config extension to .xml for each file, and attempt to open them in a web browser. If the file indeed contains a syntax error in the xml, the file will display an error inside a web browser and will often note the line with errors.

 

To correct the error, compare the install configuration files to the configuration files of a clean install (such as in the xcopy package) and correct the altered syntax.