Troubleshooting for Application Server Environment

If AVEVA Enterprise Resource Management server does not start correctly:

• Open http://localhost:<http port>/Health and run the tests.

• Open http://localhost:<http port>/StartupService.svc.

• Check the Windows Event Viewer.

• Check the AVEVA Enterprise Resource Management server log at C:\ProgramData\AvevaErm\Logs\<Environment>\Server\log_full.txt.

• Check the WCF log at C:\ProgramData\AvevaErm\Logs\<Environment>\Server\tracelog_*.svclog (choose last modified file).

If Net.Tcp Port Sharing Service does not automatically start:

• Repair the component by opening a Command Prompt with Administrator privileges, changing directory to C:\Windows\Microsoft.NET\Framework64\v4.0.30319 and running servicemodelreg.exe –r.

For common errors:

• For Cannot obtain Oracle client information from registry. Make sure that Oracle Client Software is installed, or use Direct mode of connecting to server error.

  • The issue is that the AVEVA Enterprise Resource Management server is compiled as a 64-bit application, but the server is currently used with a 32-bit Oracle Client. To resolve the issue uninstall the 32-bit Oracle Client and install the x64 version of the Oracle Client.

• For Internal IIS error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false" error

  • The issue is that the ASP.NET is not installed correctly. To resolve the issue install ASP.NET feature through Add Roles/Features.

If AVEVA Enterprise Resource Management Scheduler is not running 24/7:

• Check the Scheduler logs at C:\ProgramData\AvevaErm\Logs\<Environment>\Scheduler\full-log.txt

  • For AVEVA Enterprise Resource Management versions earlier than 15.3.4, to enable logging for the AVEVA Enterprise Resource Management Scheduler, perform the following:

    • Create a folder logs in the ERM Scheduler directory. For example: C:\AVEVA\ERM-Scheduler_PROD\logs.

    • After the log folder is created, edit the web.config file and change the value of the stdoutLogEnabled property (line 8) from false to true.

• Check if the Preload Enabled property is set to True for the AVEVA Enterprise Resource Management-Scheduler website in IIS. In the IIS Manager, in Sites, in AVEVA Enterprise Resource Management Scheduler, you can find Advanced Settings.

• Ensure that the ApplicationInitializationModule (%windir%\System32\inetsrv\warmup.dll) is installed in IIS, in the IIS Manager, in the server/root node, in the Modules.

  The module is installed automatically by AVEVA Enterprise Resource Management Deployment Manager. If the module is not present, perform one of the following to install the module:

  • Run the following command in an elevated PowerShell console: Enable-WindowsOptionalFeature -FeatureName IIS-ApplicationInit -Online -All -NoRestart

  • Enable the feature in the Server Manager, in the Add Roles and Features, in the Server Roles, in the Web Server (IIS), in the Web Server, in the Application Development, in the Application Initialization.

• In the IIS Manager, in the Application Pools, in the AVEVA Enterprise Resource Management Scheduler, in the Advanced Settings, check the settings for the AVEVA Enterprise Resource Management-Scheduler application pool is configured as follows:

  • The Start Mode field is set to AlwaysRunning.

  • The Idle Time-out field is set to 0.

• Ensure that the AlwaysRunning functionality in IIS is operational by configuring a temporary test scenario. Configure a scheduled restart of the AVEVA Enterprise Resource Management Scheduler application pool to occur after 2 minutes to confirm that the application pool starts successfully after recycling, without waiting until the next scheduled restart.

  • In IIS Manager, in Application Pools, in AVEVA Enterprise Resource Management Scheduler, in Recycling, change the Specific time(s) setting from the default 2:00 AM to a time shortly ahead. For example, if the current time is 10:00 AM, set time to 10:02 AM.

  • After the scheduled restart occurs, review the Scheduler logs and then restore the scheduled restart time to the default value 2:00 AM. In the logs, confirm that the AVEVA Enterprise Resource Management Scheduler starts successfully following the scheduled application pool recycling.