Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Vault Server 2018 Error 8005 after 2018.8.3 Patch

Anonymous

Vault Server 2018 Error 8005 after 2018.8.3 Patch

Anonymous
Not applicable

Today we applied patches 2018.8 and 2018.8.3 patches to our server and now users are not able to retrieve any files from the server. The below error results when we try to perform actions such as trying to  view a file or trying to edit a user account.

 

error.png

 

This event also generates the following exception in the File Store Logs:

 

 

10/7/2020 5:01:39 PM *******************************************************************
Error: Soap Exception ( mesg-id = 637376868997742488 )
Exception: WebServiceError [8005] (https://serverName/)
Stacktrace:    at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)
   at Connectivity.Filestore.FilestoreScheduler.GetCurrentEvents(ICollection`1 eventClasses)
   at Connectivity.Server.Common.Services.Scheduler.ExecuteScheduledEvents()
   at SyncInvokeNotify(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Exception(Inner): Could not establish trust relationship for the SSL/TLS secure channel with authority 'serverName'.
Stacktrace(Inner): 
Server stack trace: 
   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   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 System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Connectivity.Server.Proxies.SiteService.SiteService.SignInSite2(SignInSite2Request request)
   at Connectivity.Server.Proxies.SiteAuthenticator.SignIntoSite(String remoteServer, String vaultname)
   at Connectivity.Server.Proxies.ServerTokenCache.Get(Lazy`1 authenticator, String remoteServer, IResourceStore vault, SecurityHeader expiredToken)
   at Connectivity.Server.Proxies.ServiceAccessor`3._service(String remoteServer, Boolean reSignin)
   at Connectivity.Server.Proxies.ServiceAccessor`3.tryexecute(String remoteServer, Action`1 action, Int32 attemptCount)
   at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)

Exception(Inner): The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Stacktrace(Inner):    at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

Exception(Inner): The remote certificate is invalid according to the validation procedure.
Stacktrace(Inner):    at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)

 

 

Finally, I get the following message when I try to open the Administration from the ADMC I get the following error:

 

error2.png

 

I have tried reboots, IISRESET, did an installation Repair, and it looks like the IIS Application pools are as they should.  Nothing has fixed the issue.  Also, the certificate is signed by a known entity and it was working before the patch. 

 

Please help, I am running out of ideas.  Thanks!

0 Likes
Reply
Accepted solutions (1)
893 Views
1 Reply
Reply (1)

Anonymous
Not applicable
Accepted solution

Well, it looks like I was able to fix the problem.

 

This error message in the ADMSConsoleLog led me to take another look at how the console was connecting to the server:

10/9/2020 9:07:56 AM Connectivity.Application.VaultManager.LoginErrorException: Autodesk Data Management Server Console 2018 could not find the Data Management Services on servername. ---> Autodesk.Connectivity.WebServices.VaultServiceCommunicationException: The handshake failed due to an unexpected packet format. ---> System.ServiceModel.CommunicationException: An error occurred while making the HTTP request to https://serverName:80/AutodeskDM/Services/Filestore/v23/AuthService.svc?op=SignIn2&currentCommand=Connectivity.Application.VaultManager.UserAdministrationCommand. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   --- End of inner exception stack trace ---

  The fact that it was trying to connect on port 80 was what caught my eye.  It should be port 443.

 

That led me to this article: 

Configuring SSL for Vault Server 

 

I already have a good certificate so I just did the steps listed in section 3.  Mainly the one dealing with Connectivity.ADMSConsole.exe.config and Web.config changes.

 

Once I made this change it allowed me to open the Administration section of the ADMSConsole.  The client issues still remained.

 

From the ADMSConsole I unchecked the "Enable compatibility with SSL" checkbox under the "Other" in the "Advanced Settings" tab.  This fixed the client issues.  I can now open and download files attached to items and open items for viewing from the Vault Client. 

 

Hope this helps someone else some day.  Thanks to everyone who took the time to read over my post.

0 Likes