Cracking the Vault

Invalid object name 'dbo.sysmergesubscriptions'

Trying to Disable Workgroup Replication returned this error in the ADMS Console Log

17/12/2012 9:43:09 AM Connectivity.Application.VaultManager.ServiceException: Invalid object name 'dbo.sysmergesubscriptions'. ---> System.Data.SqlClient.SqlException: Invalid object name 'dbo.sysmergesubscriptions'.
   at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e)
   at Connectivity.Core.Database.SqlAccess.ExecuteNonQueryInternal(SqlCommand cmd)
   at Connectivity.Core.Database.SqlAccess.ExecuteNonQuery(CommandType commandType, String commandText, Int32 commandTimeout, SqlParameter[] commandParameters)
   at Connectivity.Core.BusinessLogic.WorkgroupBL.Database.RemovePublisher(String sqlPublisher)
   at Connectivity.Core.BusinessLogic.WorkgroupBL.DisableReplication()
   at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
   --- End of inner exception stack trace ---
   at Connectivity.Application.VaultManager.KnowledgeMasterService.DisableWorkgroupReplication(String dbUser, String dbPass)
   at Connectivity.Application.VaultManager.ReplicationUtil.DisableWorkgroupReplication_DoWork(Object sender, DoWorkEventArgs e)

Running this SQL Query indicated that even after disabling replication to subscribers, they were marked as being still replicated.

SELECT DISTINCT name, category
     FROM   master.dbo.sysdatabases
     WHERE ((category & 4) = 4)
   and databasepropertyex(name, 'Updateability') = 'READ_WRITE'
        and has_dbaccess(name) = 1

I don't know the circumstances that led to this behaviour, but to Workaround this I ran this Script against all the databases to overcome it. WARNING!!! DO THIS ONLY IF YOU ARE CERTAIN THAT THESE DATABASES SHOULD NOT BE REPLICATED TO ANY SUBSCRIBER.

Use <Vault>
sp_removedbreplication

Vault Server SP1 installation error.

I just had a rather odd Installation error whilst trying to apply "Autodesk Vault 2013 Service Pack 1 (Server).msp" on my laptop.

I neglected to take a screenshot of the error (my bad), however a MSI log file in the %TEMP% folder had the error I got on the screen. It contained simply....

IIS is not running as the default web server
=== Logging stopped: 13/12/2012  21:28:37 ===

The message sent me off in the completely wrong direction trying to check settings in the registry, searching the web for similar issues, none of which helped.

No VP Client could connect.

I started the ADMS Console and saw this error.

 

13/12/2012 21:32:45 *******************************************************************
Error: The connection to the database has been broken. Reattempting operation.
Exception: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)
Stacktrace:    at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e)
   at Connectivity.Core.Database.TransactionContext..ctor(TransactionDatabase database, DatabaseUser databaseUser, Boolean transact)
   at Connectivity.Core.Database.TransactionBase.SetupTransactionContext(TransactionReqs transactionReqs, TransactionDatabase database, Nullable`1 databaseUser)
   at Connectivity.Core.DataAccess.LegacySystems.DetermineKVMName()
   at Connectivity.Core.DataAccess.LegacySystems.LegacyTransaction..ctor(TransactionReqs transactionReqs)
   at Connectivity.Core.DataAccess.SiteCompatibility.GetSiteCompatibilityWithKnowledgeMaster()
   at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

13/12/2012 21:34:49 Unable to check the Autodesk data management server system state.  After closing this message box, you can press F5 to try again. 
If the error condition continues, contact your IT administrator.
__________________________

Operation failed:  System error.  Please contact your system administrator.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)
13/12/2012 21:37:30 Operation failed:  System error.  Please contact your system administrator.
Connectivity.Application.VaultManager.ServiceException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)
   at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e)
   at Connectivity.Core.Database.TransactionContext..ctor(TransactionDatabase database, DatabaseUser databaseUser, Boolean transact)
   at Connectivity.Core.Database.TransactionBase.SetupTransactionContext(TransactionReqs transactionReqs, TransactionDatabase database, Nullable`1 databaseUser)
   at Connectivity.Core.DataAccess.LegacySystems.DetermineKVMName()
   at Connectivity.Core.DataAccess.LegacySystems.LegacyTransaction..ctor(TransactionReqs transactionReqs)
   at Connectivity.Core.DataAccess.SiteCompatibility.GetSiteCompatibilityWithKnowledgeMaster()
   at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
   --- End of inner exception stack trace ---
   at Connectivity.Application.VaultManager.KnowledgeMasterService.GetSiteCompatibilityWithKnowledgeMaster()
   at Connectivity.Application.VaultManager.ConfigUtil.InitializeSystemState()

SOLUTION

For some reason the AUTODESKVAULT SQL Service had not started since bootup!

Nothing to do with IIS or the web service. After starting SQL in the Services (and losing 10 minutes of my life that I will never get back again), Vault 2013 Update 1 was applied successfully.

 

 

Error 155 Illegal Null Parameter during Assign Item in Vault Pro 2013

In Vault Pro 2012 we also had the issue with the error 155 during assign item and the solution was mentioned in this article Error 155 When Trying To Assign Item on Vault Pro 2012.

However if you have this error "Error 155 Illegal Null Parameter" in Vault Pro 2013 the solution mentioned here (checkout file, rebuild all in Inventor, check back in) usually doesn´t help.

You will need to reinstall the Vault Server 2013.

Before this you should be sure that you have a valid backup of your Vault.

Steps to reinstall the Vault Server:

1. Go to Control Panel

2. Go to Programs and Features

3. Go to Autodesk Vault Professional 2013 (Server) and choose "Uninstall/Change"

4. On the Setup Pick "Repair or Reinstall"

5. Select Reinstall and start the operation

If this was successful the issue with error 155 should be resolved.

Update 28th February: the reinstall option will only recreate and re register the dlls in the Vault Server program folder and won´t do anything with the database!

As consequence you would have to perform this operation on all sites when using Workgroup replication.

The database principal owns a database role and cannot be dropped

Trying to attach a Vault database to the ADMS Console returned this error.

27/11/2012 09:15:51 Connectivity.Application.VaultManager.ServiceException: The database principal owns a database role and cannot be dropped. ---> System.Data.SqlClient.SqlException: The database principal owns a database role and cannot be dropped. at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e) at Connectivity.Core.Database.SqlAccess.ExecuteNonQueryInternal(SqlCommand cmd) at Connectivity.Core.Database.SqlAccess.ExecuteNonQuery(CommandType commandType, String commandText, Int32 commandTimeout, SqlParameter[] commandParameters) at Connectivity.Core.DataAccess.DatabaseSecurity.ClearDatabaseUsers(String dbName) at Connectivity.Core.DataAccess.KnowledgeMasters.AttachDatabase(String dbName, String datafile, String logfile) at Connectivity.Core.Operations.Attach.Execute(Boolean markForMigration) at Connectivity.Core.Services.KnowledgeVaultService.AttachKnowledgeVault(String name, String datafile, String logfile, String filestore, Boolean markForMigration) at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) --- End of inner exception stack trace --- at Connectivity.Application.VaultManager.ProgressCommand.Execute() at Connectivity.Application.VaultManager.AttachVaultCommand.OnExecute(ExplorerCommandContext context)

This happened because the Database Roles had been edited by the DBA which was not supported by Autodesk.

The solution was to attach the mdf and ldf in SQL Server Management Studio.

In the properties of the Database, expand Security>Roles>Database Roles. Right click on ADMS-VacuumRestriction>Properties. On the General page, change the Owner to "dbo".

Detach the database from SQL Server Managment Studio then, re-attach via the ADMS Console.. (and don't do it again.....)

 

Error 1405 Item Version Identified Incorrectly in the Item Master

If you select items in the item master in Vault Professional you may get this error message:

"Error 1405: Item version identified incorrectly. Please refresh and try again."

On the client try to delete/rename the file WorkingFolders.xml on your workstation.

You usually find this file under:

C:\Users\[YourUserID] \AppData\Roaming\Autodesk\VaultCommon\Servers\Services_Security_6_29_2011\localhost\Vaults\<YourVault>\Objects

"The filestore identity does not match the Vault"

When trying to enable a Vault database, I received this error message.

"The filestore identity does not match the Vault"

In the ADMS Console log

11/13/2012 4:53:15 PM The filestore identity does not match the Vault.
11/13/2012 4:53:15 PM Connectivity.Application.VaultManager.ServiceException: FileStoreMismatch [212]  ---> Connectivity.Core.Exceptions.CoreException: FileStoreMismatch [212]

Server stack trace:
   at Connectivity.Core.DataAccess.KnowledgeVaults.EnableKnowledgeVault(String server, Guid vaultguid, String fspath)
   at Connectivity.Core.BusinessLogic.SiteBL.ActivateVaultOnSite(Guid vaultguid, String rootpath, Boolean logMissingFiles)
   at Connectivity.Core.Services.KnowledgeVaultService.EnableVault(Guid vaultGuid, String rootPath, ICollection`1 initialSchedule)
   at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Connectivity.Core.Services.KnowledgeVaultService.EnableVault(Guid vaultGuid, String rootPath, ICollection`1 initialSchedule)
   at Connectivity.Application.VaultManager.KnowledgeVaultService.EnableVault(Guid vaultGuid, String rootpath, ReplicationScheduleObject initialSchedule)
   --- End of inner exception stack trace ---
   at Connectivity.Application.VaultManager.KnowledgeVaultService.EnableVault(Guid vaultGuid, String rootpath, ReplicationScheduleObject initialSchedule)
   at Connectivity.Application.VaultManager.EnableAndDisableVaultCommand.EnableVaultAtNewLocation(String site, String vaultName, String rootPath, Guid vaultGuid)
   at Connectivity.Application.VaultManager.EnableAndDisableVaultCommand.OnExecute(ExplorerCommandContext context)

This happened, because there was a previous Vault database enabled with the same name but different identitiy (GUID) in the same location. Navigating to the location chosen for the filestore, and either renaming the folder or deleting the exisiting folder, allowed me to repeat the process successfully.

Unable to clean up replication database

Trying to disable replication from the Publisher ADMS Console on a Standard Content Center Library, showed this error in the ADMSConsole log file.

11/13/2012 2:22:52 PM Unable to clean up replication database 'AI2013_Inventor ISO' on subscribing database server 'RR-W2K8R2-SUB\AUTODESKVAULT'.
11/13/2012 2:22:52 PM Connectivity.Application.VaultManager.ServiceException: SubscriberCleanupError [4415] (RR-W2K8R2-SUB\AUTODESKVAULT, AI2013_Inventor ISO) ---> Connectivity.Core.Exceptions.EncodableException: SubscriberCleanupError [4415] (RR-W2K8R2-SUB\AUTODESKVAULT, AI2013_Inventor ISO) ---> System.Data.SqlClient.SqlException: Changes to the state or options of database 'AI2013_Inventor ISO' cannot be made at this time. The database is in single-user mode, and a user is currently connected to it.
ALTER DATABASE statement failed.
   at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e)
   at Connectivity.Core.Database.SqlAccess.ExecuteNonQueryInternal(SqlCommand cmd)
   at Connectivity.Core.Database.SqlAccess.ExecuteNonQuery(CommandType commandType, String commandText, Int32 commandTimeout, SqlParameter[] commandParameters)
   at Connectivity.Core.DataAccess.KnowledgeMasters.SetDatabaseOptions(String databaseName, String[] options)
   at Connectivity.Core.DataAccess.KnowledgeMasters.DropDatabase(String databaseName)
   at Connectivity.Core.BusinessLogic.WorkgroupBL.Database.CleanupRemoteSubscription(Workgroup publisher, String publicationName, String databaseName)
   at Connectivity.Core.BusinessLogic.WorkgroupBL.Database.Unsubscribe(Workgroup currentwg, Workgroup targetwg, String databaseName, Boolean ignoreSubscriberErrors)
   --- End of inner exception stack trace ---

Server stack trace:
   at Connectivity.Core.BusinessLogic.WorkgroupBL.Database.Unsubscribe(Workgroup currentwg, Workgroup targetwg, String databaseName, Boolean ignoreSubscriberErrors)
   at Connectivity.Core.BusinessLogic.WorkgroupBL.KnowledgeDB.DeleteReplica(String sqlServer, KnowledgeDatabase database, Boolean ignoreSubscriberErrors)
   at Connectivity.Core.Services.KnowledgeLibraryService.DeleteLibraryReplica(String sqlServer, Guid libraryGuid, String partionID, Boolean ignoreSubscriberErrors)
   at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Connectivity.Core.Services.KnowledgeLibraryService.DeleteLibraryReplica(String sqlServer, Guid libraryGuid, String partionID, Boolean ignoreSubscriberErrors)
   at Connectivity.Application.VaultManager.KnowledgeLibraryService.DeleteLibraryReplica(String sqlServer, Guid libraryGuid, String partitionID, Boolean ignoreSubscriberErrors)
   --- End of inner exception stack trace ---
   at Connectivity.Application.VaultManager.KnowledgeLibraryService.DeleteLibraryReplica(String sqlServer, Guid libraryGuid, String partitionID, Boolean ignoreSubscriberErrors)
   at Connectivity.Application.VaultManager.ReplicationUtil.DeleteLibraryReplica(String remoteServerName, String workgroupDisplayName, Guid libraryGuid, String libraryPartition, Boolean ignoreSubscriberErrors, String dbUser, String dbPassword, ICommonProgressReporter progressReporter)
   at Connectivity.Application.VaultManager.KnowledgeLibraryObject.DeleteReplica(String remoteServerName, String workgroupDisplayName, ICommonProgressReporter progressReporter)
   at Connectivity.Application.VaultManager.ManageReplicationCommand.ApplyChange(ICommonProgressReporter progressReporter, Form threadSafeForm, ReplicationUpdate currentUpdate)
   at Connectivity.Application.VaultManager.ManageReplicationCommand.WorkgroupReplication_DoWork(Object sender, DoWorkEventArgs e)

 

I am not able to reproduce how this happened in the first place.

Logging into SQL Server Management Studio (SSMS) on the subscriber showed that the database had been put into Single User mode. To workaround this, I detached the database from the subscriber SSMS restarted the following services

Net stop "Autodesk Data Management Job Dispatch"
Net stop "SQLAgent$AUTODESKVAULT"
Net stop "MSSQL$AUTODESKVAULT"
Net stop "W3SVC"
Net start "Autodesk Data Management Job Dispatch"
Net start "MSSQL$AUTODESKVAULT"
Net start "SQLAgent$AUTODESKVAULT"
Net start "W3SVC"

...and then went back to the Publisher ADMS Console and tried again. The second time it was successful.

Error 29001. Install Error

Installing Vault Server encountered this error.

Error 29001. Vault Management error: Could not load file or assembly ‘Microsoft.Web.Administration, Version 7.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

This was resolved by checking the components installed for IIS. Specifically, ensuring that the "IIS Management Console" option was ticked. A reboot of the machine is then required.

Error 1053 During the Start of Autodesk Data Management Job Dispatch Service

We get more and more reports about an issue that after a Server reboot or new Installation of Vault it is not possible to login the Vault Clients and the ADMS console anymore.

The issue is caused by the failed start of the "Autodesk Data Management Job Dispatch" service.

If you want to run the Service "Autodesk Data Management Job Disptach" manually (inside the control panel - administrative tools - Services) it is not possible and you get this error message:

"Could not start the Autodesk Data Management Job Dispatch service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."

The issue is directly linked to this issue Error 1920. Error during Vault Server installation (same cause).

You can use the same methods to resolve the issue.
The quickest method would be to unplug the network cable, start the service and plug it back after the Service is running.

Enabling Sharepoint Logging and How to Analyse Them.

To enable logging in Sharepoint 2010

1. Login to "Share 2010 Central Administration"
2. Click "Monitoring"
3. Click "Configure diagnostic logging"
4. Under "Select a Category" tick either "All Categories" or at a minimum "Business Connectivity Services" to capture any errors coming from the Autodesk Vault Sharepoint Integration.
5. Under "Least critical event to report to the event log" select "Verbose"
6. Under "Least critical event to report to the trace log" select "Verbose". (By Default the log files are located here = %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\14\LOGS
7. Leave the other options as they are.
8. Click OK

To help analyse the log files, Microsoftt provides a free utility called ULS Viewer that allows filtering by a specific product.

• Click the Filter icon,
• Field = "Product"
• Operation = "Contains"
• Value = "Autodesk Vault BCS Connector"

If there is a Sharepoint "Correlation ID", you can filter on that as well.

 

After you have solved the issue that you are troubleshooting, you may want to turn off verbose logging. :-)