Unable to connect to Vault Pro via Fortinet VPN

Unable to connect to Vault Pro via Fortinet VPN

gerrardhickson
Collaborator Collaborator
471 Views
1 Reply
Message 1 of 2

Unable to connect to Vault Pro via Fortinet VPN

gerrardhickson
Collaborator
Collaborator

Hi All,

I'm setting up a vault server on a remote PC that I access via Fortinet VPN. I have the vault installed, data backup restored and migrated, I can log into the ADMS just fine. When I try to log in via the Vault client (Server: localhost), it fails.

Looking through the vault logs, I see the following error in the Server Logs:

Error: Soap Exception ( mesg-id = 638938684170382767 )
Exception: TransactionInvalidPrincipal [106] 

which seems to indicate a VPN config error (link ) - has anyone had experience with this?

There are also some 306 and 307 errors, but these seem to be from yesterday.

And one other error from this morngng in the Console Logs:

20/09/2025 9:10:54 AM Connectivity.Application.VaultManager.LoginErrorException: Autodesk Data Management Server Console 2026 could not find the Data Management Services on http://127.0.0.1:80/. ---> Autodesk.Connectivity.WebServices.VaultServiceCommunicationException: The remote server returned an error: (500) Internal Server Error. ---> System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (multipart/related; type="application/xop+xml"). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html>
<html>
    <head>
        <title>Could not load file or assembly 'Autodesk.Connectivity.LicenseWrapper' or one of its dependencies. Access is denied.</title>
        <meta name="viewport" content="width=device-width" />
        <style>
         body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} 
         p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
         b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
         H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
         H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
         pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt}
         .marker {font-weight: bold; color: black;text-decoration: none;}
         .version {color: gray;}
         .error {margin-bottom: 10px;}
         .expandable { text-decoration:underline; font-weight:bold; color'. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   --- End of inner exception stack trace ---

Server stack trace: 
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at Autodesk.Connectivity.WebServices.RealProxy`1.Invoke_(MethodInfo methodInfo, Object[] args, T obj)
   at Autodesk.Connectivity.WebServices.ServiceBase`1.ServiceProxy`1.Invoke_(MethodInfo methodInfo, Object[] args, TServiceInterface obj)
   --- End of inner exception stack trace ---

Server stack trace: 
   at Autodesk.Connectivity.WebServices.ServiceBase`1.ServiceProxy`1.Invoke(MethodInfo methodInfo, Object[] args, TServiceInterface obj)
   at Autodesk.Connectivity.WebServices.RealProxy`1.Invoke(IMethodCallMessage methodCallMsg, MethodInfo methodInfo, InvokeDelegate invokeFunc)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Autodesk.Connectivity.WebServices.IAuthService.SignIn2(String userName, String userPassword, String oldSessionId)
   at Autodesk.Connectivity.WebServices.AuthService.SignIn2(String userName, String userPassword, String oldSessionId)
   at Autodesk.Connectivity.WebServicesTools.WebServiceCredentialsBase.SignInHelper(Func`2 SignInVault, Func`1 SignInNoVault)
   at Autodesk.Connectivity.WebServicesTools.UserPasswordCredentials.SignIn(AuthService authSvc, WinAuthService winAuthSvc, AutodeskAuthService autodeskAuthSvc)
   at Autodesk.Connectivity.WebServicesTools.WebServiceManager.WebServiceCredentials_SignIn()
   at Autodesk.Connectivity.WebServicesTools.WebServiceManager.SignIn()
   at Connectivity.Application.VaultManager.ConfigUtil.VdfSignin(String vaultname, LoginInfo vaultLogin, Boolean reportError)
   --- End of inner exception stack trace ---

I'm not sure, but it could be related to an incorrect login attempt, or something that happened while trying to troubleshoot.

I followed the steps here as well, but nothing has helped so far.

I've logged a ticket with the local IT team to see if they can troubleshoot the VPN, but I'd love to know if someone else has overcome this problem.

Thanks

0 Likes
472 Views
1 Reply
Reply (1)
Message 2 of 2

ameliahenry68
Community Visitor
Community Visitor

This issue looks like a typical VPN-related connectivity problem between Fortinet SSL/IPsec VPN and Autodesk Vault services rather than a pure Vault failure. In many cases, FortiGate VPN introduces routing, DNS resolution, or NAT behavior that prevents the Vault client from correctly reaching ADMS services even though basic network access (like ping or RDP) may work. I would suggest verifying that the Vault server is accessed using its correct FQDN instead of localhost, ensuring proper DNS resolution over VPN, and checking that required ports for Vault services (such as 80/443 and SQL-related ports if applicable) are allowed through the VPN tunnel. Also, split-tunneling or internal routing rules on FortiGate can sometimes break localhost-based authentication flows. Testing direct LAN access versus VPN access usually helps isolate whether this is a VPN routing or Vault configuration issue.

0 Likes