Installation and start service

AVEVA Integration Service Installation ends prematurely.

Description: Required Windows Features are not enabled.

Resolution: Make sure .NET Frameworks 3.5 and 4.0 are enabled in Windows Features.

Unable to run the PowerShellScriptToSetIISForAIS. ps1 script - Error "Set-ItemProperty : Cannot find drive. A drive with the name 'IIS' does not exist."

Description: The following error message is displayed: Set-ItemProperty : Cannot find drive. A drive with the name 'IIS' does not exist.

Resolution: Reset the parameter in the script in all three places. You can reset the parameter by simply deleting and reinserting the space before "IIS".

SSL related issues (Server Certificate)

Description: Secure Sockets Layer (SSL) issues related to Internet Information Services (IIS).

Resolution:

• If the Hosting Bundle is installed before enabling IIS feature, then the bundle installation must be repaired. Run the Hosting Bundle installer again after enabling IIS.

• Troubleshooting SSL related issues (Server Certificate) - Internet Information Services

Unable to start service when using AVEVA's LaaS - Internet Explorer pop-up Error - Enhanced Security Configuration

Description: If you try to start the Service using AVEVA's LaaS by clicking Start on Integration Settings Editor, the Service does not start. While no error message is displayed by the Service currently, based on the settings, your browser may display an error message similar to this.

Resolution: This issue occurs because of the enhanced security configurations of your computer and/or browser. To resolve the issue, add the CONNECT websites to the list of trusted websites.

You can also open Server Manager and turn the IE Enhanced Security Configuration off.

Unable to connect to Configuration API/Data API endpoints - SSL Error

Description: This could be because of the configuration API and Data APi are not running.

Resolution:

• Make sure http://ASP.NET Core 6.0 Runtime (v6.0.29 or above) Windows Hosting Bundle is installed as mentioned in System Requirements.

• If the Hosting Bundle is installed before enabling IIS feature, then the bundle installation must be repaired. Run the Hosting Bundle installer again after enabling IIS.

• Make sure that the script PowerShellScriptToSetIISForA IS.ps1 is run as mentioned in Post-Installation Tasks.

• Check whether you able to browse the website Config & Data API.

Unable to view previous data sources Integration Settings Editor after upgrading.

Description: Data sources not migrated to version 3.0.

Resolution: Run the Migration Tool as mentioned in AVEVA Integration Service Guide.

Unable to complete the SSL Settings configurations - Error “There was an Error while performing this operation.”

Description: While performing tasks such as configuring the SSL settings, the following error message is displayed. This issue occurs because the computer does not have the required software for performing the given operation.

Resolution:

• Make sure all the requirements in System Requirements are met.

• Did you get a pop-up when you browsed to the website to enter username and password. If not

  • Windows Authentication IIS Feature Turned-On but not working properly. Turn the feature off, restart computer and activate the Turned-On feature again.

• After installing Windows the Hosting Bundle 6.0.29 or above must be installed. The server must have only one version of the Windows hosting Bundle so remove any previous versions.

• Windows hosting bundle might have installed before IIS. If the Hosting Bundle is installed before enabling the IIS feature, then the bundle installation must be repaired. Run the Hosting Bundle installer again after enabling IIS.

Error in running PowerShellScript PowerShellScriptToSetIISForAIS.ps1 - UnAuthorizedAccess

Description: PowerShell cannot be loaded because running scripts is disabled on this system. Error is shown below

Resolution: Due to IT policies, some server / machine may require polices to be bypassed to enable features which are required for browsing and connecting to APIs. In Windows PowerShell ISE, run the command Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass and click Yes to All. Then execute again PowerShellScriptToSetIISForAIS.ps1.

Unable to browse config API - HTTP Error 401.2 Unauthorized or 401.4 Forbidden or 500.30 - ASP.NET Core app failed to start or HTTP 500.21 Internal Server Error

Description: You do not have permission to view this directory or page using the credentials that you supplied.

Resolution:

• Did you get a pop-up when you browsed to the website to enter username and password. If not

  • Windows Authentication IIS Feature Turned-On but not working properly. Turn the feature off, restart computer and activate the Turned-On feature again.

• After installing Windows the Hosting Bundle 6.0.29 or above must be installed. The server must have only one version of the Windows hosting Bundle so remove any previous versions.

• Windows hosting bundle might have installed before IIS. If the Hosting Bundle is installed before enabling the IIS feature, then the bundle installation must be repaired. Run the Hosting Bundle installer again after enabling IIS.

Unable to Browse Config API - Your Connection is not private - NET::ERR_CERT_AUTHORITY_INVALID

Description: View the certificate in the Trusted Root Certificate Authorities. Also, when you click the lock icon in your address bar, you see this:

Resolution:

• Create a new Self-Signed Certificate for AVEVA Integration Service APIs Usage. Create Digital signature Self-signed Certificate.

• To do that Run Windows PowerShell ISE as Admin user and run the following command.

New-SelfSignedCertificate -FriendlyName <giveCertficateAName> -DnsName <yourHostName> -KeyUsage DigitalSignature

Example:

<giveCertficateAName> AIS01

<yourHostName> MYHOST

New-SelfSignedCertificate -FriendlyName AIS01 -DnsName MYHOST -KeyUsage DigitalSignature

• Verify that the certificate is available in Server Certificates in IIS

  • Open Internet Information Services Manager, locate Server Certificate and double Click on it.

    

    

• Bind Website in IIS and configure SSL Certificate

  • Navigate to website (IntegrationServiceConfigAPI), go to Edit Site -> Bindings -> Select the Certificate Created SSL Certificate.

    

• Note: If you still get the above error message, you need to verify the Bindings Host Name:

  • Option 0- Host Name empty

  • Option 1- Host Name

  • Option 3- Hostname@domain or domain\hostname.

• Browse Website and Export Certificate

  • Browse website in your browser in private mode, you should receive a prompt to enter your windows username and password.

  • Click on Certificate Not Valid Option

• In the Certificate Viewer, Go to Details Export the Certificate and save it.

  • Note: The example screenshot is from Chrome. Your browser may display this differently.

• In the Certificate Viewer, Go to Details Export the Certificate and save it.

  • Note: The example screenshot is from Chrome. Your browser may display this differently.

    

• Import the Certificate into Trusted Root Certificate on the AVEVA Integration Service Server

  

  

• Import the Certificate into Trusted Root Certificate on the client machine where you want to access the website

• Go to the AVEVA Integration Settings Editor and configure the endpoint.

Unable to Browse Config API - The Process cannot access the file because it is being used by another process.

Description: The World Wide Web Publishing Service (WWW Service) did not register the URL prefix https://:60920*/ for site 3. The site has been disabled.

The data field contains the error number.

Resolution: Use a different port number and start the service.

IIS - The Process Cannot Access the File Because it is Being Used by Another Process

Unable to browse REST API - Error “Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified”

Description: While browsing AVEVA Integration Service-related APIs from IIS, the following error is encountered: Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified. This can be caused if the Newtonsoft.Json.dll is missing from C:\Program Files (x86)\AVEVA\Shared\IntegrationServiceRESTAPI\bin.

Resolution: Repair the AVEVA Integration Service installation, and the missing Newtonsoft.Json.dll will be available.

Unable to browse Integration Service Config API - HTTP error 503 - "The Module DLL C:\Windows\System32\inetsrv\warmup.dll failed to load. The data is the error. "

Description: "Application Initialization" is necessary for usage of AVEVA Integration Service. Without this feature, HTTP error 503 appears when trying to browse IntegrationServiceConfigAPI. This message is output: The Module DLL C:\Windows\System32\inetsrv\warmup.dll failed to load. The data is the error.

Resolution: To keep AVEVA Integration Service REST API alive/active, a ping service is run in the background. The "Application Initialization" feature must be enabled before running ApplicationHostUpdateForRestAPI.ps1.

Unable to Open Integration Client and Integration Settings editor

Description: Users need to have local admin privileges to run the AVEVA Integration Client and the Integration Settings Editor tool. Standard access permissions for system folders such as Program Files and System32 do not grant standard users write access. Elevated privilege is an essential requirement.

Resolution: User must be in the Admin and User group on the local server/machine.

Unable to browse REST API Website - HTTP Error 500.24 - Internal Server Error - system.web/identity@impersonate is set to True.

Description: When browsing the REST API website this error is seen in the browser:

Resolution:

• Turn off Authentication in the IIS website, only enable “Windows Authentication”.

• Stop and Start Website.

  

Unauthorized access to setting the password

Description: This can occur in the rare event of installing everything, and then deleting and recreating the AISAdministrators group. Even if the users in the group are the same, when AVEVA Integration Service is reinstalled, the users will not have access to setting the password.

This happens due to following scenario:

• User creates a group “AISAdministrators”, adds desired users.

• User installs PCS.

• User installs AVEVA Integration Service 3.1.2

• AVEVA Integration Service sets secrets to DBs and to PCS.

• User deletes the group “AISAdminstrators” (which is not recommended).

• PCS is locked with secrets (Key & Value with the group).

• The user recreates the group “AISAdminstrators” with desired users.

• The user installs AVEVA Integration Service again, user will get an error saying unauthorized access to setting the password.

Resolution:

• Uninstall AVEVA Integration Service

• Delete the folder C:\Windows\ServiceProfiles\ArchestrADataStore\AppData\Roaming\AVEVA\PCS Data Store V4.

• Install AVEVA Integration Service again

Unable to retrieve data for the SQL Product - error Timeout Expired

Description: When you try to retrieve data from a SQL product where the execution of the query takes more than 30 seconds, a timeout error occurs. A message similar to the following is logged to the log file:

Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Resolution:

To resolve this, you must increase the timeout limit.

To increase the timeout limit:

1. Open the AVEVA.IntegrationService.Settings.config file available at the installation location of Integration Client.

2. For the DBTimeOut parameter, increase the value according to your requirements. The value must be specified in minutes. The default value is 10.

3. Save the file.