Starting Client message appears but file does not open (retired) - SmartPlant Foundation - SmartPlant Foundation - Reference - Hexagon

The following applies if you are using a version of the software before Update 33 and SmartPlant Markup Plus Server 2019 SP 1 or earlier. For the latest information, see File viewing problems.

Problem

The viewer displays a Starting Client message, but you cannot view a non-Hexagon file using the View and Markup page.

Errors

The following error appears in your browser console:

The client encountered a problem with the previous view request. For more detailed information please review the JavaScript console.

Unable to publish the requested document for viewing.

The following error appears in the job logging file created by the Brava! Job Processor:

Polling Queue: https://BravaServer:8443/BravaServer/Pop: error attempting to request a job from url: The underlying connection was closed: An unexpected error occurred on a receive.

An error similar to the following appears in the heartbeat.txt file:

Warning=Notification Error: The request was aborted: Could not create SSL/TLS secure channel.

How do I find the heartbeat.txt file?

Cause

Properties in the job processor configuration file are set to secure connections (SSL). These connections might fail if the Microsoft .NET framework is using TLS 1.0 instead of TLS 1.2 to connect to the Brava! Enterprise Server.

Solution: Update properties in the job processor configuration file to use non-secure connections instead

Update the queue.url.2 and done.servlet.url properties in the job processor configuration file.

You can prevent network traffic from being seen outside the network by configuring these URLs to use localhost (127.0.0.1).

1. Log on to the SmartPlant Markup Plus server as an administrator.

2. Open the JobProcessor.config file delivered to the [installation location]/SmartPlant/Markup/Brava! Enterprise\JobProcessor folder.

3. Set queue.url.2 to http://SPMApplicationServer.domain.com:8080/BravaServer/Pop.

4. Set done.servlet.url to http://SPMApplicationServer.domain.com:8080/BravaServer.

5. Click Start > Administrative Tools > Services.

6. Restart the Brava! Job Processor service.

Solution: Force the Microsoft .NET framework to use TLS 1.2

You can edit the registry on the server running the Brava! Job Processor service.

Manually editing the registry incorrectly can cause problems that may require you to reinstall the operating system. Problems created by the incorrect editing of the registry may not be possible to solve. Edit the registry at your own risk. You should back up the registry before you edit it.

1. Start the Registry Editor (regedit.exe).

2. Click Edit > Find.

3. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 key.

4. Right-click the key, click New, and select DWORD Value.

5. Right-click NewValue#1, and select Rename.

6. Enter SchUseStrongCrypto.

7. Double-click SchUseStrongCrypto, set Value data to 00000001, and click OK.

8. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 key.

9. Right-click the key, click New, and select DWORD Value.

10. Right-click NewValue#1, and select Rename.

11. Enter SchUseStrongCrypto.

12. Double-click SchUseStrongCrypto, set Value data to 00000001, and click OK.

13. Click Registry > Exit to close the Registry Editor.

14. Click Start > Administrative Tools > Services.

15. Restart the Brava! Job Processor and Apache Tomcat services.