We use different servers for SQL and Vault , both databases and file stores are replicated and servers run windows server 2008 r2 standard. File store replication takes place about 1 hour before first user starts to work.
Some of my users are complaining about slow performance when getting files, when I check the vault logs after the replication entries I find this:
9/13/2012 6:59:59 AM *******************************************************************
Error: Soap Exception ( mesg-id = 111111111111111111111 )
Exception: BadAuthenticationToken [300]
Stacktrace:
Server stack trace:
at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)
at System.Threading.Thread.InternalCrossContextCallback(Context ctx, InternalCrossContextDelegate ftnToCall, Object[] args)
at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)
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.Document.Services.FolderService.GetFolderByPath(String path)
at Connectivity.Web.Services.DocumentService.GetFolderByPath(String path)
9/13/2012 7:00:00 AM Acquired license(111111111) for username(yyyy), userId(000), host(0.0.0.0).
*You can observe that exception and acquired license lines have same hour* then almost for every user that starts a session I have the same pattern:
Error: Soap Exception ( mesg-id = 11111111111111111111)
Exception: BadAuthenticationToken [300]
Stacktrace:
......
at Connectivity.Web.Services.DocumentService.GetFolderByPath(String path)
9/13/2012 7:00:00 AM Acquired license(111111111) for username(yyyy), userId(000), host(0.0.0.0).
Almost every time someone gets a license is preceded by a BadAuthenticationToken [300] message. Also in some users that pattern is repeated every hour. I checked in the ISS options that regular time interval is set in 1740. Also some users are able to just get a license without having any exception being thrown before. Log file has about 114 instances of that error in a 8 hours period
I haven't troubleshoot windows, SQL or ISS yet
My questions would be: - Can that error impact the server performance?
- Reinstalling IIS may help?
- I'm going to upgrade to vault 2013 pro, is it recommendable to address that issue before upgrading?
