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.