Admin login fails after upgrade to 3.0.2

bahoover · Post by **bahoover** » Wed Feb 09, 2005 8:48 pm

We just upgraded from 2.0.5 to 3.0.2. When we try to connect with the admin tool, we get "The username or password supplied is invalid."

We even uninstalled then re-installed which didn't seem to help. So now I can't get into the admin tool to update keys.

Any clues?

thanks

Brett

Post by **jclausius** » Wed Feb 09, 2005 9:11 pm

Try to bring up the normal web service within a browser on the server machine - http://localhost/vaultservice/vaultservice.asmx

Do you get the description page? If so, then let's look somewhere else. Is there any indication within the server's error log of a problem?

bahoover · Post by **bahoover** » Wed Feb 09, 2005 10:44 pm

Yes, we can get the descriptions page.

From the admin tool, it just appears the password isn't authenticating.

When we log in using the client, we get the message: "Your serial number is not a valid serial number. User logins are currently disabled."

We did have some issues with the upgrade failing w/ an "sgvaultuser" error. We bypassed the problem by first upgrading to version 3.0.0, then after it was complete, we upgraded to version 3.0.2

Here is a some lines of our install log that look peculiar. We did have to recreate the virtual directory after install. And we run on an odd port -- which we have been for a while, so I don't think that is the issue.

--- FROM LOG FILE ---
The selected website is 'Vault'
You chose to put Vault on website: 'IIS://LocalHost/W3SVC/12/Root/Root'
Creating the Virtual Directory, VaultService...The webserver path 'IIS://LocalHost/W3SVC/12/Root/Root' was not found.
Failed. Web Server not found.
Creating the Virtual Directory, VaultShadowFolder...The webserver path 'IIS://LocalHost/W3SVC/12/Root/Root' was not found.
Failed. Web Server not found.
Entered SetInstallationSettings().
Exit SetInstallationSettings() success
Entered GetServerBindings()
Error getting server bindings: Exception from HRESULT: 0x80005006.
Exit GetServerBindings()
Entered MakeUrl()
Hostname lookup returned: <servername>
Port is default, 80
Exit MakeUrl() - <servername>
Creating the Vault Server Home Page...Read serverInstall.html from our resources.
Entered GetAssemblyVersion()
GetAssemblyVersion completed successfully.
OK
Your Vault Server configuration has been successfully upgraded.
-- END LOG INFO --

Post by **jclausius** » Thu Feb 10, 2005 8:18 am

Anything suspicious in the Vault server's log? The default configuration places this file in %windir%\temp\sgvault\

bahoover · Post by **bahoover** » Thu Feb 10, 2005 8:29 am

Yes, it appears execute permissions for sgvaultuser don't exist for most of the sprocs

-- cut from log file
----2/10/2005 7:26:03 AM --65.102.79.33(65.102.79.33)--SSL Disabled EXECUTE permission denied on object 'spgetserialnums', database 'sgvault', owner 'dbo'.
----2/10/2005 7:26:03 AM --65.102.79.33(65.102.79.33)--SSL Disabled Error in the application.
----2/10/2005 7:26:04 AM admin--65.102.79.33(65.102.79.33)--SSL Disabled EXECUTE permission denied on object 'spgetlogininfo', database 'sgvault', owner 'dbo'.
----2/10/2005 7:26:04 AM admin--65.102.79.33(65.102.79.33)--SSL Disabled Login failed: FailNotValidLogin
-- end log file

Post by **jclausius** » Thu Feb 10, 2005 8:34 am

It appears as if the database connection is not configured correctly. You mentioned an error related to sgvaultuser, do you know what it was? Having this information can help trouble shoot what went wrong.

bahoover · Post by **bahoover** » Thu Feb 10, 2005 8:36 am

I don't have the exact error message, but similar to

sgvaultuser already exists errorcode -1280

Post by **jclausius** » Thu Feb 10, 2005 8:40 am

Perhaps the easiest way to go about this is to reset the user within SQL Server / sgvault, and re try the installation.

Click the email button below, send me a message. In the meantime, I'll start working on instructions.

Post by **jclausius** » Thu Feb 10, 2005 8:50 am

Problem was solved. The installer grants db_owner and public role membership to the Vault server database login.

One of these roles was missing from sgvaultuser. Upon granting db_owner, the problem has been solved.