Troubleshooting VDS Configuration - Integration - Ver. 3.7.0.3 - Administration & Configuration - Hexagon

HxGN VDS Install and Setup

Language
English
Product
Integration
Search by Category
Administration & Configuration
VDS Version
3.13

The log files for the VDS Web Server are in the Windows Event Viewer because it is an IIS process.

The log file for the VDS Application Server processes is located in the %PROGRAMDATA%\HxGN 3D Graphic Data Service\Logs folder.

  • GDSServiceMgr.log - logs messages from the services if one cannot start, cannot connect to the database, and so on.

  • [SiteName_PL_PlantName].log - logs errors that are generated by the process for items that cannot be streamed. A log file is created for each instance of Himalaya.exe (VDS) that the service manager creates.

SHARED Tip For situations when VDS is not working because of some serious system problem, such as when the VDS Windows service is non-responsive, you can reset the VDS Application Server and VDS Web Server. In the VDS Configuration Utility, click Save & Configure. This action resets the selected service. The settings remain unchanged, but the system refreshes the software and recreates and configures the selected VDS components.

Problem: You do not have a Himalaya.exe task in Task Manager for each plant

Solution

  1. Open Task Manager on the server hosting VDS.

  2. In the Details tab check that GDSServiceMgr is running.

  3. Check that there is a Himalaya.exe running for each plant that is supposed to be served.

    • Edit the columns in Task Manager to show the command line of the tasks.

    • The Himalaya.exe tasks should show which site/plant they are supporting.

If the correct processes are not present, check the GDSServiceMgr.log file and ensure that your VDS settings are entered correctly.

Make sure that the user defined in the VDS User Login Name setting in the VDS Configuration Utility (Service Settings page > Workspace Site Settings) can successfully log on to the client application site and that this user account has the Viewer role assigned.

Also, check that the ADS Base URL setting in the VDS Configuration Utility (Service Settings page > Workspace Site Settings) is properly set. If it is, try editing it again and saving it, and then recycle the service and check again.

Problem: VDS Web Server and/or VDS Application Server cannot connect to RabbitMQ

Solution

Check your RabbitMQ configuration to make sure the necessary connections are there:

  • Through the RabbitMQ management application, log on with the username and password provided in VDS Configuration Utility.

  • Verify that the user has administrator access and access to the virtual host.

  • There are two necessary exchanges that should be created automatically: GDSExchange and GDSControl.

  • The number of queues for each plant that is serviced by the VDS.

  • Number of queues and names should correspond to the himalaya.exe tasks on the VDS Application Server machine.

Check that the RabbitMQ user names and passwords are correctly set in the VDS Configuration Utility > Broker Settings page. If they are, try editing them again and save them. Note that user names and passwords are case-sensitive.

Problem: In the log file, a message is reported similar to “Process xxxx Exited with result code -1073741515”

Solution

This message usually indicates that the prerequisite “Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019” has not been installed. Please ensure that all of your prerequisite software is installed before reconfiguring.

Problem: VDS graphics out of date with what has been published

Solution

The VDS will persist its graphic cache to disk after retrieving graphic updates from the client application. This cache is stored in the %PROGRAMDATA%\HxGN 3D Graphic Data Service\Cache folder. If the VDS is shutdown or restarted it will load quickly from this cache instead of pulling all the graphics from the client application and processing them. The service then checks the client application for changes that have been made since the last time it persisted the data. All of your changes are added to the cache. If this process has gotten out of sync, follow these steps:

  1. Stop the HxGN 3D Graphic Data Service Manager Windows service.

  2. Delete any cache files from the %PROGRAMDATA%\HxGN 3D Graphic Data Service\Cache folder that are expected to be out of date.

  3. Start the HxGN 3D Graphic Data Service Manager Windows service to query the database and re-build the cache. For larger databases, this process may take some time.

Problem: Failed to get site access token System.ApplicationException: POST token uri failed. Received HTTP BadRequest -OR- Failed to get site access token System.ApplicationException: POST token uri failed. Received HTTP MethodNotAllowed

These errors are written to the GDSServiceMgr.log file

Solution

Make sure that the values set in the VDS Configuration Utility for the Issuer, VDS Client Identifier, and VDS Client Secret are correct. These errors often occur when these properties contain incorrect values.

Problem: 'ERROR : [VDS Service] Did not find any queries for model'

This error is written to the GDSServiceMgr.log file.

Solution

This error is caused when there are no filters defined in the client application site for the VDS Application Server to monitor. If you intentionally have no filter as part of your implementation, you can ignore this error.

Problem: 'Server not available (500) error' when starting the VDS Web Server

Solution

Start the Windows Programs and Features applet and run a repair on the the .NET Core Hosting Bundle to ensure it is installed and configured properly.

Also, check that the RabbitMQ user name and passwords are properly set in the VDS Configuration Utility. If they are try editing and saving them again. Note that they are case-sensitive.

Problem: '500.19 - Internal Server Error' - The requested page cannot be accessed because the related configuration data for the page is invalid.

This error displays when there is a problem in the software load order.

Solution

Un-install VDS and any prerequisite software. Then re-install the software in the order listed for the VDS Web Server Setup and VDS Application Server Setup