Error: The server returned an unknown status code (1109).

[Dhominator]

release 3.1.8

Vault client error attempting to connect... The server returned an unknown status code (1109).

Background...
* cancelled a test import yesterday... after 26 hours
* deleted the repo used for test import
* created new repo
* started single solution import
* import client at prompt overnight
* continued/completed import this morning

Vault service on one box, db hosted on different box.

Searched the support forum and didn't see anything that looked related.

Suggestions?

[Dhominator]

set the log level to debug

bounced the server

attempted client connection

----5/25/2006 5:20:42 PM sgvaultsystem--()--
System Started
Version 3.1.8.3771
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Debug
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain = XXX
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://xxx.xxx:nnnn/VaultService
Identity = XXX\someuser
----5/25/2006 5:20:43 PM --()-- Beginning SQL transaction 126
----5/25/2006 5:20:43 PM --()-- SQL transaction 126 successfully committed.
----5/25/2006 5:20:43 PM --()-- Beginning SQL transaction 125
----5/25/2006 5:20:43 PM --()-- SQL transaction 125 successfully committed.
----5/25/2006 5:20:45 PM user--vaultServer(1.1.1.1)--SSL Disabled Beginning SQL transaction 162
----5/25/2006 5:20:45 PM user--vaultServer(1.1.1.1)--SSL Disabled System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or property cannot be called on Null values.
at System.Data.SqlTypes.SqlGuid.get_Value()
at System.Data.SqlClient.SqlDataReader.GetGuid(Int32 i)
at VaultServiceSQL.VaultSqlSystem.LoginUser(VaultSqlConn conn, String strLogin, String strDbHashPwd, Guid& gSession) at System.Data.SqlTypes.SqlGuid.get_Value()
at System.Data.SqlClient.SqlDataReader.GetGuid(Int32 i)
at VaultServiceSQL.VaultSqlSystem.LoginUser(VaultSqlConn conn, String strLogin, String strDbHashPwd, Guid& gSession)
----5/25/2006 5:20:45 PM user--vaultServer(1.1.1.1)--SSL Disabled SQL transaction 162 successfully rolled back.
----5/25/2006 5:20:45 PM user--vaultServer(1.1.1.1)--SSL Disabled Login failed: FailDBUpdate

[jclausius]

Login errors related to the database usually indicate a version mismatch between the schema in the database and the Vault Server.

Is this a brand new database w/ Vault 3.1.8 installation or was it moved / restored onto a Vault 3.1.8 server? What version of SQL Server is being used for the sgvault database?

In any case, let's see if we can solve this problem by forcing the schema of the database to match the Vault Server:

• Uninstall the Vault Server (selecting to KEEP the database).
• Re-install the Vault Server using an account which has Administrative rights to SQL Server (selecting to USE the EXISTING database).

Make note of any errors during the installation, and report anything that looks suspicious during installation or Vault login.

[Dhominator]

thx info, will give that a try.

New install about 2 months ago, 3.1.8. Sql server 2000, sp4, win2k server. Per previous the only thing different is I ran/canceled an import (26hrs), deleted the repo, created a new repo, and started a new [smaller] import.

Import shouldn't futz with the schema version, right?

Will report back.

/jhd

[jclausius]

No, it shouldn't.

How did you cancel the import? In a normal fashion? Hardware restart? When the repository was deleted, did that operation succeed? There have been some issues that SP4 caused when deleting a repository. SP3 works correctly, but the changes Microsoft made to SP4 caused some problems on foreign keys within the database.

It could be the database is in a bad state. You may want to also check the database from a query tool - DBCC CHECKDB('sgvault') - to make sure it is operating correctly.

[Dhominator]

Cancel button. Seemed to stop gracefully. Repo delete appeared fine.

Vault Server is not in the Add/Remove Programs list. Suggestions on uninstalling?

CHECKDB in progress.

[update]
CHECKDB found 0 allocation errors and 0 consistency errors in database 'sgvault'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

[update2]
Found the uninstall string in the registry:

MsiExec.exe /I{FFCEF882-252F-456A-AF63-481BAA0FFE80}

Ran it... message returned was along the lines of... only works if it's installed ya doof... or something like that.

Should I proceed with an Install? Other suggestions?

BTW, the directories exist in prog files and the webservice is still up and running.

[update 3]
Installed vault server on a vm and can connect to the service/repos. Still can't connect thru the real server/webservice. Trying to resist installing over the top [on real server] until I hear back from you...

/jhd

[lbauer]

Jeff's out of the office for a few days.

Just to be clear -- Vault is running fine on the VM?

[Dhominator]

Yeah, server and client worked fine installed in the vm... connected to the existing vault db.

Since our dev staff is down until this is resolved I'm going to install vault server on the db server. People can change their clients [to point to the new vault service] and get back up and running.

I do want to unwind the stack and figure out how we got here. So I'll leave the corrupt installation in place.

/jhd

[jclausius]

So the Vault Server is on a virtual machine, configured to use the real database is that correct?

If so, then we'll need to figure out how to uninstall the Vault server, make sure all the components are in place (IIS and .Net Framework), and then re-install.

[Dhominator]

I did a test with vault service in a vm... because I was unable to uninstall it from our production server (different than our vault db server). Since that worked, I installed vault service on the same [real] server with the database.

Back to the original, broken, install on our production server. I asked the guy who originally installed it to login and see if it shows up in the Add/Remove Programs list. I don't know how to go about uninstalling Vault Server, given it is not in the add/remove list for me.

[jclausius]

Do you have any administrative rights on the machine? If not, can you use an account with admin rights?

If we're lucky, then the Vault Server will show up in this list.

[lbauer]

If you log into the machine with Admin rights and still don't see Vault in Add/Remove programs, you should be able to uninstall it manually:

1) in IIS manager, remove the Vault Service web application under the Default Website. Also remove the Shadow Folder service. 2) delete the following registry keys HKLM\Software\SourceGear Vault Client and HKLM\Software\SourceGear Vault Server
3) Delete the Vault service directory. It should be in C:\inetpub\wwwroot\vaultservice.
4) You can also remove Vault from these IDE integration registry keys HKLM\Software\SourceCodeControlProvider and HKLM\Software\SourceCodeControlProvider\InstalledSCCProviders (if these exist)

Also open this registry key and search for any items related to Vault Server and remove those folders:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

[Dhominator]

neither my account (admin) nor administrator show it in the add/remove programs list. Original installer logged in and he sees it. He'll try to remove it via add/remove programs. Manual uninstall will be the fallback.

Best,
/jhd