Quantcast
Channel: ProjectWise Design Integration Wiki
Viewing all articles
Browse latest Browse all 994

Login to ProjectWise fails using Windows account type when logging in from the one of the ProjectWise Design Integration Servers in a cluster

$
0
0
Current Revision posted to Content Management Wiki by Andzej Prokopovic on 10/14/2020 11:26:08 AM

In a clustered ProjectWise Server environment Windows account logins to the datasource may fail when done on one of the servers in the cluster.

The issue is related to Microsoft security. Security feature prevents access to an application using a fully qualified domain name (FQDN) or a host name if an attempt to access it, takes place from the machine that hosts that application.

This feature can be disable by introducing the following registry key to the servers in a cluster:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DisableLoopbackCheck:DWORD=1

However disabling this feature is not the suggested solution. There is another way around it. In the following registry key “HKLM:\System\CurrentControlSet\Control\Lsa\MSV1_0” a Multi-String Value named “BackConnectionHostNames” should be created and FQDN of the cluster put as a value there.

You may execute this PowerShell script on each of the ProjectWise Servers in a cluster, it will add this value into the registry.

New-ItemProperty “HKLM:\System\CurrentControlSet\Control\Lsa\MSV1_0” -Name “BackConnectionHostNames” -Value “projectwise.mycluster.com” -PropertyType multistring

Tags: explorer, ProjectWise Client, ProjectWise, login, Cluster, ProjectWise Integration Server

Viewing all articles
Browse latest Browse all 994

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>