I have just installed Vault 8.0 on Windows 2012 using the databases from Vault 6.1. (I restored the databases on the new server and installed Vault 7.2.1 Then I upgraded to 8.0.)
Now I am seeing SQL server login issues:
Login failed for user 'sgvaultuser'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Additonally, and probably associated with this error, I am seeing a number of crashes in IIS:
Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e
Exception code: 0xe0434352
Fault offset: 0x000000000000606c
Faulting process id: 0xfa0
Faulting application start time: 0x01d029c6d14a5591
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 0f622af6-95ba-11e4-80c0-005056b6577d
Faulting package full name:
Faulting package-relative application ID:
... and ...
Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: VaultLib.VaultDbException
Stack:
at VaultIndexService.VaultIndexServiceSQL.GetRepositoryIndexSettings(Int32, VaultLib.RepositoryIndexInfo ByRef)
at VaultIndexService.VaultIndexManager.MoveItemToProcessRequestList(VaultIndexService.RepositoryIndexStateChange)
at VaultIndexService.VaultIndexManager.RepositoryIndexStateChgProc()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
... and ...
An unhandled exception occurred and the process was terminated.
Application ID: DefaultDomain
Process ID: 4000
Exception: System.Runtime.Serialization.SerializationException
Message: Type 'VaultLib.VaultDbException' in Assembly 'VaultLib, Version=8.0.0.192, Culture=neutral, PublicKeyToken=a74d7badb9387c36' is not marked as serializable.
StackTrace: at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeObject(Object obj, MemoryStream stm)
at System.AppDomain.Serialize(Object o)
at System.AppDomain.MarshalObject(Object o)
Otherwise, the Client and Visual Studio work properly.
Can you help please?
Password did not match that for the login provided
Moderator: SourceGear
Re: Password did not match that for the login provided
Do you happen to have the install log? vault_install.log is usually found in the %temp% directory of the user which did the install. Also, can you check for some of the log files (sgvault.log, vaultshadowfolderservice.txt, vaultindexservice.txt, vaultnotifyservice.txt), found in sub directories under %windir%\temp\.
If you could mail all of these to support AT sourcegear DOT com, with a reference to this support post, we can take a closer look at your system settings.
If you could mail all of these to support AT sourcegear DOT com, with a reference to this support post, we can take a closer look at your system settings.
Jeff Clausius
SourceGear
SourceGear