Problems after 4.0.2 upgrade

BigBrett · Post by **BigBrett** » Sun Jul 15, 2007 11:50 pm

I have upgraded from Vault 3.5.2 to Vault 4.0.2. I now have the following problems:

1. When trying to access the Users option in the Admin application I just get the message "Error in application" and nothing else. The relevant portion of the log file is as follows:

----7/16/2007 7:40:51 AM dev2--DEV2-PCC(10.10.15.42)--SSL Disabled VaultLib.VaultDbException: Error in the application.
at VaultServiceAPILib.VaultAdminServiceAPI.GetGroupsForRep(Int32 repid, VaultGroupSummary[]& vGroups)
at VaultWebLib.Helpers.GroupSummaries()
at VaultService.Users.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at VaultServiceAPILib.VaultAdminServiceAPI.GetGroupsForRep(Int32 repid, VaultGroupSummary[]& vGroups)
at VaultWebLib.Helpers.GroupSummaries()
at VaultService.Users.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

2. The Vault installation can no longer get information from the DragNet installation on the same computer. This is evidenced by an extract from the server log file:

----7/16/2007 7:40:51 AM dev2--DEV2-PCC(10.10.15.42)--SSL Disabled System.Data.SqlClient.SqlException: Server user 'sgvaultuser' is not a valid user in database 'sgdragnet'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at VaultServiceSQL.VaultAdminSQL.GetGroupsForRepOrProj(VaultSqlConn conn, Int32 nRepID, Boolean bIsRep, VaultGroupSummary[]& vGroups) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at VaultServiceSQL.VaultAdminSQL.GetGroupsForRepOrProj(VaultSqlConn conn, Int32 nRepID, Boolean bIsRep, VaultGroupSummary[]& vGroups)

3. When running the 4.0.2 Vault Client GUI there are no icons on the toolbar buttons nor on the folder tree (just leaves gaps where the icons should be).

Regards,
Brett

lbauer · Post by **lbauer** » Mon Jul 16, 2007 7:50 am

1. When trying to access the Users option in the Admin application I just get the message "Error in application" and nothing else

Do other functions in Vault work properly? Do you only get an error when trying to access the users link?

Are you using SQL Server authentication or Windows authentication for Vault?

We'd like to see the installation log plus your Vault Server log. The installation log is vault_install.log and is in your user's temp directory.
The server log is in %windir%\temp\sgvault.

Email them to support at sourcegear.com ATTN: Linda

BigBrett · Post by **BigBrett** » Mon Jul 16, 2007 8:09 am

Log files as requested have been emailed.

Only admin functions which require user table access are failing (Users under Server Settings, Repository Access under specific repositories), other functions seem to work fine.

We use SQL Server authentication.

Regards,
Brett

lbauer · Post by **lbauer** » Mon Jul 16, 2007 10:50 am

Vault 4.0 no longer supports integration with Dragnet. In addition, installing Vault 4.0 and Dragnet on the same machine is no longer supported.

For users who have both Vault and Dragnet, the upgrade path would be to Fortress, which integrates item tracking and source control in one package.

When you upgraded your Vault server, the installer detected the Dragnet database, and made changes as though it was upgrading to Fortress. I will log a bug so that we provide better information and error messages for users with Dragnet trying to upgrade to Vault 4.0.

The best way to get you back up and running would be for you to restore backups of both your Vault 3.5.2 database, and your Dragnet database, then install Fortress, which will properly upgrade both.

Another option would be to reinstall Dragnet on a different server machine, however, as I stated before Dragnet will no longer integrate with Vault 4.0

If you have gold support for both Vault and Dragnet, then upgrading to Fortress is free. If you don't have gold support for both I will provide you with pricing information for the upgrade.