Quantcast
Channel: Cracking the Vault
Viewing all articles
Browse latest Browse all 167

SiteSigninError 8004

$
0
0

You might see several of these messages appearing in the AVFS Logs

11.11.2013 00:01:37 ******************************************************************* Error: SiteSigninError [8004] (<SourceServername>, <DestinationServername>) Exception: SiteSigninError [8004] (<SourceServername>, <DestinationServername>)) Stacktrace:   

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)   

at Connectivity.Filestore.Licensing.GetProductTier()    at Connectivity.Filestore.Licensing.Initialize()

11.11.2013 00:01:37 ******************************************************************* Error: Soap Exception ( mesg-id = 635197248979893987 ) Exception: SiteSigninError [8004] (<SourceServername>, <DestinationServername>) Stacktrace:   

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)   

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.ProcessMessage31(MessageRpc& rpc)   

at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

 

Try this

1.  Delete SiteConfiguration.xml from C:\ProgramData\Autodesk\VaultServer\Configuration
2.  Perform an IIS reset.
3.  Try your command again. 

The XML should be regenerated with a correct key and allow the action to continue.

 

Thanks to Andy Spivey for sharing this solution


Viewing all articles
Browse latest Browse all 167

Trending Articles