Help!
Hi Jamie,
There’s two things you can try to get you up and running. You can either re-save the repository or delete it and re-create it. If one of those solves the problem it looks like something is up with out repository checking code. I can’t think of anything else that causes a build to be stuck at Build Initialising but I’ll setup a test and see what I find.
Here is an exception message.
Cannot get new changsets for Iims-Vault-Repo: Running vault.exe failed with return code: -1 and error output:
System.Exception: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. System.Web.Services.Protocols.SoapException: Server was unable to process request.
---> System.NullReferenceException: Object reference not set to an instance of an object.
at VaultServiceSQL.VaultSqlSystem.GetLoginInfo(VaultSqlConn conn, String strLogin, String strHostname, String strSessionID, VaultUser vu, String& strDbHashPwd, Int32& nAttempts)
at VaultServiceAPILib.VaultServiceAPI.AuthenticateAndLogin(VaultSqlConn conn, Boolean allowwebonly, String strLogin, String strDecryptedPassword, String strHostname, String strSessionID, VaultUser vu, String strDomain, Guid& gSessionGUID, Int32& nValidUserAttempts)
at VaultServiceAPILib.VaultServiceAPI.Login(VaultSqlConn conn, Boolean allowwebonly, String strLogin, String strDecryptedPassword, String strHostname, String strSessionID, String strDomain, String& strToken, VaultUser& vu, Int32& nValidUserAttempts)
at VaultServiceAPILib.VaultServiceAPISystem.DoLogin(Boolean allowwebonlyusers, Boolean bAdminLogin, HttpSessionState hss, String strHostname, String strLogin, String strPassword, String strRMKey, String& strAuthToken, String strDomain)
at VaultServiceAPILib.VaultServiceAPISystem.DoLogin(Boolean allowwebonlyusers, Boolean bAdminLogin, HttpSessionState hss, String strHostname, String strLogin, String strPassword, String strRMKey, String& strAuthToken)
at VaultService.VaultService.Login(String strHostname, Boolean bUseFullFiles, String username, String strEncryptedPassword, String strRMKey, String& strAuthToken)
--- End of inner exception stack trace --- ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at VaultServiceSQL.VaultSqlSystem.GetLoginInfo(VaultSqlConn conn, String strLogin, String strHostname, String strSessionID, VaultUser vu, String& strDbHashPwd, Int32& nAttempts)
at VaultServiceAPILib.VaultServiceAPI.AuthenticateAndLogin(VaultSqlConn conn, Boolean allowwebonly, String strLogin, String strDecryptedPassword, String strHostname, String strSessionID, VaultUser vu, String strDomain, Guid& gSessionGUID, Int32& nValidUserAttempts)
at VaultServiceAPILib.VaultServiceAPI.Login(VaultSqlConn conn, Boolean allowwebonly, String strLogin, String strDecryptedPassword, String strHostname, String strSessionID, String strDomain, String& strToken, VaultUser& vu, Int32& nValidUserAttempts)
at VaultServiceAPILib.VaultServiceAPISystem.DoLogin(Boolean allowwebonlyusers, Boolean bAdminLogin, HttpSessionState hss, String strHostname, String strLogin, String strPassword, String strRMKey, String& strAuthToken, String strDomain)
at VaultServiceAPILib.VaultServiceAPISystem.DoLogin(Boolean allowwebonlyusers, Boolean bAdminLogin, HttpSessionState hss, String strHostname, String strLogin, String strPassword, String strRMKey, String& strAuthToken)
at VaultService.VaultService.Login(String strHostname, Boolean bUseFullFiles, String username, String strEncryptedPassword, String strRMKey, String& strAuthToken)
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at Syst
em.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.Login(String strHostname, Boolean bUseFullFiles, String username, String strEncryptedPassword, String strRMKey, String& strAuthToken)
at VaultClientNetLib.VaultConnection.Login(String strURLBase, String strUserLogin, String strPassword)
at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String username, String password)
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
--- End of inner exception stack trace ---
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
False
Now I initially thought it might be a http://{VaultServer:port} issue as per the repo configuration bellow.
I also let this run overnight to see how well the timeout of 60 minutes worked. But that failed as it was still at build initialising this morning (8 hours or so later). I suspect there is a threading/callback issue here.
Hi Jamie
We have been able to reproduce this here and have made some major improvements. We’re still tweaking things and trying different ways to break the repositories but it should behave better with the next build (hopefully later today).
Yeah baby, love this continuous build idea! 
I’ve deleted all my projects, configurations and most of the repo’s to try and remove any poor data triggering the problems I’ve been getting. I just can’t wait to get stuck into the stage actions at this stage of my testing.