Vault server 3.1.8 install fails creating stored procs

mitch.wheat · Post by **mitch.wheat** » Wed Apr 12, 2006 2:31 am

Hi

This is what I did in the end (as suggested):

Installed on the offending server (as network service option) and pointed the DB install to my local server.

Backed up and restored the local DB to production.

Recreated the sgvaultuser and ran sp_change_users_login to sync user.

Hopefully, all is well...

Mitch

Post by **jclausius** » Wed Apr 12, 2006 5:28 am

That is very strange.

I have no idea why the install in your scenario would be declaring this is the case. The script does not have @dbname declared twice. Perhaps it is something related to the production server.

I did find this article from Microsoft. Perhaps the @dbname error is related to the problem described here - PRB: Creating New Database Objects Fails in a SQL Server Database

mitch.wheat · Post by **mitch.wheat** » Thu Apr 20, 2006 8:43 pm

Thanks for your help guys.

Post by **jclausius** » Fri Apr 21, 2006 8:10 am

Mitch:

Did you try the suggestion in the MS article? Did that work?