Errors in Client Log-File

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
VaultUser675
Posts: 6
Joined: Thu Jan 12, 2017 2:37 am

Errors in Client Log-File

Post by VaultUser675 » Fri Jan 13, 2017 5:27 am

Hi there,

the client logfile contains many errors and stack traces.

Also we have sometimes the problem, that the connection goes lost, and we have to reconnect. There are also sometimes problems with our build where we got errors on Vault operations:

Code: Select all

VAULT INTERNAL EXCEPTION: System.Exception: Wait timeout for mutex after 30000 milliseconds.
   bei VaultClientIntegrationLib.ServerOperations.SetRepository(String repositoryName)
   bei VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
   bei VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
   bei VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)

VAULT INTERNAL EXCEPTION: System.Exception: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. Die Anforderung konnte vom Server nicht verarbeitet werden. ---> Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. ---> System.Web.Services.Protocols.SoapException: Die Anforderung konnte vom Server nicht verarbeitet werden. ---> Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   bei VaultClientNetLib.ClientService.VaultService.Login(String strHostname, Boolean bUseFullFiles, String username, String strEncryptedPassword, String strRMKey, String& strAuthToken)
   bei VaultClientNetLib.VaultConnection.Login(String strURLBase, String strUserLogin, String strPassword)
   bei VaultClientOperationsLib.ClientInstance.Login(String urlbase, String username, String password)
   bei VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
   bei VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
   bei VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
Remarks:
We use FinalBuilder as a Build-Management-Tool which uses vault.exe.
The mutex error doesn't occur at the moment, seems to be that this corresponds to parallel client actions?


System Information:

Code: Select all

Client Information
    Vault Standard Client Version: 9.1.0.584
    .NET Framework Version: 2.0.50727.8009
    Operating System: Microsoft Windows Server 2012 R2 Standard
    Service Pack: 0.0
    OS Version: 6.3.9600
    Total Physical Memory: 6 GB
    Time Zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
    
Server Information
     Server Version: 9.1.0.584
    .NET Framework Version: 4.0.30319.42000
    Operating System: Microsoft Windows Server 2012 R2 Standard
    Service Pack: 0.0
    OS Version: 6.3.9600
    Timezone: (UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
    SQL Version: Microsoft SQL Server 2012 - 11.0.5343.0 (X64)


Client logfile VaultCLC.txt:

Code: Select all

12.01.2017 09:06:15 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:21 <generic>: [<No Name>:2] SimpleLogger finalized
12.01.2017 09:06:22 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:27 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
12.01.2017 09:06:27 <generic>: [<No Name>:2] SimpleLogger finalized



12.01.2017 09:06:36 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:44 <generic>: [GetUpdate:7] Setting last write time on D:\WR32_SQL\u32\U\uVCL\uCtrls_uDBEdit.pas to 11.01.2017 13:01:08
12.01.2017 09:06:44 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenFolderName(ClientInstance ci, String folderName)
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenStateFilename()
   bei VaultClientOperationsLib.WorkingFolder.LoadState()
   bei VaultClientOperationsLib.WorkingFolder..ctor(ClientInstance ci, String diskFolderPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.FindOrCreateWorkingFolder(String diskPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenFolderName(ClientInstance ci, String folderName)
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenStateFilename()
   bei VaultClientOperationsLib.WorkingFolder.LoadState()
   bei VaultClientOperationsLib.WorkingFolder..ctor(ClientInstance ci, String diskFolderPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.FindOrCreateWorkingFolder(String diskPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

12.01.2017 09:06:44 <generic>: [<No Name>:2] SimpleLogger finalized

12.01.2017 09:06:45 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:52 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

12.01.2017 09:06:52 <generic>: [<No Name>:2] SimpleLogger finalized
Could you help us with this?

Thanks.
Top
Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:
Contact Beth

Re: Errors in Client Log-File

Post by Beth » Fri Jan 13, 2017 9:09 am

If you run a lot of builds simultaneously on the same client, it's possible for one to get the first error. Offsetting each build by a second can help or run them sequentially.

The last one is odd because it has multiple stops and starts.

This is a start:
12.01.2017 09:06:36 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null

This is a stop;
12.01.2017 09:06:44 <generic>: [<No Name>:2] SimpleLogger finalized

Is the last piece from the Vault CLC log or something else?
Beth Kieler
SourceGear Technical Support
Top
VaultUser675
Posts: 6
Joined: Thu Jan 12, 2017 2:37 am

Re: Errors in Client Log-File

Post by VaultUser675 » Tue Jan 17, 2017 5:40 am

The VaultCLC-Log previously was shortened. The following code shows the full log between 9:06:15 and 09:06:59 (Next log entry on 09:07:28 seems to be a new operation). I only replaced the filenames with xxx.

Client logfile VaultCLC.txt:

Code: Select all

12.01.2017 09:06:15 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:21 <generic>: [<No Name>:2] SimpleLogger finalized
12.01.2017 09:06:22 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:27 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

12.01.2017 09:06:27 <generic>: [<No Name>:2] SimpleLogger finalized
12.01.2017 09:06:28 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:34 <generic>: [GetUpdate:7] Setting last write time on xxx to 18.06.2008 16:37:19
12.01.2017 09:06:34 <generic>: [GetUpdate:7] Setting last write time on xxx to 02.11.2015 08:27:14
12.01.2017 09:06:34 <generic>: [GetUpdate:7] Setting last write time on xxx to 22.07.2011 13:23:29
12.01.2017 09:06:34 <generic>: [GetUpdate:7] Setting last write time on xxx to 10.01.2017 11:51:33
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 23.04.2010 12:09:45
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 22.06.2016 10:48:09
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 10.01.2017 11:25:18
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 10.01.2017 11:25:18
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 10.01.2017 11:51:33
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 02.11.2015 08:27:10
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 02.11.2015 08:16:41
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 10.01.2017 11:58:48
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 22.06.2016 12:09:41
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 26.01.2010 09:47:11
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 23.01.2007 17:45:17
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 01.04.2010 16:30:56
12.01.2017 09:06:35 <generic>: [GetUpdate:7] Setting last write time on xxx to 23.01.2007 17:45:17
12.01.2017 09:06:35 <generic>: [<No Name>:2] SimpleLogger finalized
12.01.2017 09:06:36 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:44 <generic>: [GetUpdate:7] Setting last write time on xxx to 11.01.2017 13:01:08
12.01.2017 09:06:44 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenFolderName(ClientInstance ci, String folderName)
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenStateFilename()
   bei VaultClientOperationsLib.WorkingFolder.LoadState()
   bei VaultClientOperationsLib.WorkingFolder..ctor(ClientInstance ci, String diskFolderPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.FindOrCreateWorkingFolder(String diskPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenFolderName(ClientInstance ci, String folderName)
   bei VaultClientOperationsLib.WorkingFolder.GetHiddenStateFilename()
   bei VaultClientOperationsLib.WorkingFolder.LoadState()
   bei VaultClientOperationsLib.WorkingFolder..ctor(ClientInstance ci, String diskFolderPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.FindOrCreateWorkingFolder(String diskPath, Boolean makeBackups)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

12.01.2017 09:06:44 <generic>: [<No Name>:2] SimpleLogger finalized
12.01.2017 09:06:45 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:52 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

12.01.2017 09:06:52 <generic>: [<No Name>:2] SimpleLogger finalized
12.01.2017 09:06:53 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
12.01.2017 09:06:59 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.IsCheckedOutByMeOnThisMachine(VaultClientFile file, VaultClientCheckOutItem& checkOutItem, VaultClientCheckOutUser& checkOutUser)
   bei VaultClientOperationsLib.WorkingFolder.GetStatusForSingleFile(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file, Boolean& isModified, Boolean& exists, String& strAbsoluteFilename)
   bei VaultClientOperationsLib.WorkingFolder.GetStatus(VaultClientFile file)
   bei VaultClientOperationsLib.ClientInstance.MakeChangeSetItemForKnownChange(VaultClientFile file, WorkingFolder wf, Boolean ignoreCheckedOutFiles)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

12.01.2017 09:06:59 <generic>: [<No Name>:2] SimpleLogger finalized
12.01.2017 09:07:28 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
Do you have any suggestions regarding this errors?
Top
Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:
Contact Beth

Re: Errors in Client Log-File

Post by Beth » Tue Jan 17, 2017 9:06 am

The object reference error is a generic error. It just means it can't get what it asked for, but doesn't say why.

Did you try offsetting when different builds launch?

Something else you can try is using a Vault GUI client to Get on the same files just to make sure Vault can get the files. If it throws errors in that client as well, it would point us to a different problem.

If the Vault GUI client succeeds, then use a command prompt to test out the Vault Get.
Beth Kieler
SourceGear Technical Support
Top
VaultUser675
Posts: 6
Joined: Thu Jan 12, 2017 2:37 am

Re: Errors in Client Log-File

Post by VaultUser675 » Thu Jan 19, 2017 6:28 am

If we use the VaultGUIClient (Operation Get on the folder), then there are many informations but NO exceptions in the logfile (classesToLog = all).

If we use the command line vault.exe for the same repository folder with the same operation and user...

Code: Select all

vault.exe get -user "xxx" -password "xxx" -host "xxx" -repository "xxx" -setfiletime "modification" -merge overwrite "xxx"
...then it logs out the following exception:

Code: Select all

19.01.2017 12:23:28 <generic>: [<No Name>:1] vault, Version=9.1.0.584, Culture=neutral, PublicKeyToken=null
19.01.2017 12:23:58 <generic>: [<No Name>:4] [System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)] Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_Folder(VaultClientFolder folder, Hashtable alreadySearchedFolderPaths, Boolean recursive)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)

Stack Trace:
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Boolean notifyChangeSetItemsChanged)
   bei VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_All(Object notifyChangeSetItemsChanged)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

19.01.2017 12:23:58 <generic>: [<No Name>:2] SimpleLogger finalized
This exception seems to have no impact to the result at all:

Code: Select all

<vault>
  <result>
    <success>True</success>
  </result>
</vault>
It looks like that there are exceptions, which have an impact to the overall process, and others which doesn't have. Can you give us some informations about this behaviour?

btw: What says the information "<No Name>:x"?

Thank you.
Top
VaultUser675
Posts: 6
Joined: Thu Jan 12, 2017 2:37 am

Re: Errors in Client Log-File

Post by VaultUser675 » Fri Jan 27, 2017 8:39 am

Hi Beth,

could you please give us some feedback about this errors and how to interpret that?
Top
Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:
Contact Beth

Re: Errors in Client Log-File

Post by Beth » Fri Jan 27, 2017 9:46 am

I can't exactly tell just yet. I might be able to identify what is happening if I can see the entire server and client log together. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread? Also please include the Vault Server Log and your client log file.
Beth Kieler
SourceGear Technical Support
Top
Post Reply

Return to “Support (Vault)”