PSIcapture Launch Error: Failed to save configuration, the configuration database is locked


PSIcapture cannot launch and displays the following error:


Error Reference when Loading Modules screen is in process: PSIGEN.Capture.Modules.Configuraton.ConfigurationModule:
PSIGEN.Capture.Modules.Configuraton.ConfigurationModule, Capture.Core,PublicKeyToken=a37817f97b64ad34
Exception has been thrown by the target of an invocaton

Capture Log contains similar errors:

[2/20/2015 12:25:35 PM - Error - v5.0.2.14]
Failed to save configuration, the configuration database is locked by CORP\smartsearch : SFSMARTSEARCH.  Configuration changes cancelled.
Server stack trace: 
   at PSIGEN.Capture.Modules.Configuration.ConfigurationService.Lock(CaptureUser user)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   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 PSIGEN.Capture.Modules.Configuration.IConfigurationService.Lock(CaptureUser user)
   at PSIGEN.Capture.Modules.CaptureServer.CaptureServerModule.LockConfiguration(SettingsLocation location, Boolean system)
   at PSIGEN.Capture.Modules.Configuration.ConfigurationModule.ConvertOldConfiguration()
   at PSIGEN.Capture.Modules.Configuration.ConfigurationModule..ctor()

Within the Configuration.mdf database there is a table called Configuration. Within the table the value for Owner has been locked to a specific value. The value must be changed in owner to a database value of NULL. Ensure it is not the physical value "NULL" but that it is a true database value for empty value NULL*.

  1. Find the Configuration.mdf file that is being used for production on the Capture Server.
  2. Stop the Capture Services within Services.msc.
  3. Attach Database to SSMS and expand Configuration database
  4. Right Click on the Configuration.dbo within SSMS and click edit top 200 rows
  5. Under the top row within the column owner ensure that it has the NULL* value present instead of a value. 
  6. Detach the Database and now the Configuration DB should be accessible.

In order to edit the configuration.mdf you will have to attach it to SQL Server Management Studio or Linqpad.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.