Alter Database Failed Because a Lock Could Not Be Placed on Database dbname Try Again Later

• Remove From My Forums

Additional WSUS and SUP

• Question

•  I accept a WSUS /SUP on Server A and database hosted on SQL Server (SUSDB), I am program to install WSUS/SUP on Server B for failover scenarios  , I came to know from few blogs that we can share the SUSDB for an additional WSUS and SUPs in a single chief site.

  1. Practice nosotros demand specify SQL Instance while installing WSUS.

  2. WSUS Content share permissions on Server A

  Could you please guide how to Install Additional WSUS/SUP

All replies

• During post configuration steps, I got below error,is in that location whatsoever permission required at database level

  Fatal Error: ALTER DATABASE failed because a lock could not exist placed on database 'SUSDB'. Try over again later.
  ALTER DATABASE argument failed.

  Log:

  2017-02-06 12:xxx:08  Establishing DB connectedness...
  2017-02-06 12:thirty:08  Checking to encounter if database exists...
  2017-02-06 12:30:08  Database exists
  2017-02-06 12:30:08  Switching database to single user mode...
  2017-02-06 12:xxx:14  System.Data.SqlClient.SqlException (0x80131904): Modify DATABASE failed considering a lock could not be placed on database 'SUSDB'. Endeavor once again after.
  ALTER DATABASE argument failed.
  at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
  at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
  at Microsoft.UpdateServices.Administration.ConfigureDB.ConnectToDB()
  at Microsoft.UpdateServices.Assistants.ConfigureDB.Configure()
  at Microsoft.UpdateServices.Assistants.PostInstall.Run()
  at Microsoft.UpdateServices.Administration.PostInstall.Execute(Cord[] arguments)
  ClientConnectionId:61fc8953-6192-4eef-80f0-e0c546e366f6

• The computer accounts of the servers must take admission (db owner) to SUSDB. The outset server should have such access past virtue of the initial setup. Add the computer account of the second server.
  

• Assign server B read/write/modify permissions to this folder so it has proper access to it. Also, when you installed A, you lot must have configured this UNC path and non a local drive.
  

• Hi,

  When configuring additional WSUS, a shared WSUS content directory that yous already created using either a standard network share or distributed file system. All the WSUS reckoner accounts must have change permissions for the share.

      Only check in current situations, Please feel free to let us know if you need further aid.

  Best Regards,

  Ray

  ---

  Delight remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Back up, contact tnmff@microsoft.com.

• Thanks Ray, Delight let me know which directory that I tin can employ, beneath are the directories which are bachelor while installing WSUS Server A ( i.e 1st WSUS)

  \\<Computername\SoftwareUpdates\WsusContent - It was created during  1st WSUS installation on Server A

  it is a standard network share I accept added read/write/modify permissions to this folder

  ane# During mail service configuration steps, I got beneath error. I gave DBO permission for Server B

  Fatal Error: Modify DATABASE failed considering a lock could not exist placed on database 'SUSDB'. Try again after.
  ALTER DATABASE statement failed.

  #2 farther I got below error afterwards #1 troubleshooting.

  The schema version of the database is from a newer version of WSUS
  than currently installed.  You must either patch your WSUS server to at least
  that version or driblet the database

  Could you please guide on this.

• I have installed KB3095113 on server B and Post Installation went well.

  I have another query about content directory.

  On Server A, I have post-obit directory

  \\<Computername\SoftwareUpdates\WsusContent - It was crated during WSUS installtion

  Which directory is a content directory ?

• Go over the links that I posted higher up again. Cheque the ContentDir value in HKLM\Software\Microsoft\Update Services\Server\Setup.

• how to motion WSUS Contender  to different bulldoze or other share

• I got beneath fault , Can you lot delight help on this.

  C:\Plan Files\Update Services\Tools>wsusutil.exe movecontent \\SCCMWSUS\WSUSContent D:\wsusmove.log

  Fatal Error: You must specify an existing local directory on an NTFS sectionalisation equally an absolute path or specify an existing UNC path for the new content file location.

  C:\Program Files\Update Services\Tools>

• Does the UNC path you specified already exist and the servers accept proper permissions on it?
  

• Yes, I  accept added read/write/alter permissions for Server A(SUP1) and Server B (SUP2) & primary server as well for shared path due east.g   \\SCCMWSUS\WSUSContent

  • Marked equally reply by Tuesday, March vii, 2017 vii:36 PM
  • Unmarked as answer by TaarunRaj Tuesday, March 7, 2017 7:36 PM

• I was trying to move WSUS Content Binder to DFS share . Is it possible ?

• I am getting below error when I was tried to motion WsusContent Directory to DFS share

  C:\Programme Files\Update Services\Tools>wsusutil.exe movecontent \\SCCMWSUS\WSUSContent <LogFile>

  Fatal Error: You must specify an existing local directory on an NTFS partition every bit an accented path or specify an existing UNC path for the new content file location.

  C:\Program Files\Update Services\Tools>

• DFS shares piece of work fine. Verify again that the path actually exists and you can browse to it. Validate again that you take assigned proper permissions to the computer account objects of A & B to that share, check both NTFS permissions and Share permissions.
  

• Both the computer acconts accept both NTFS and share permissions. nevertheless getting aforementioned error

  Fatal Error: You must specify an existing local directory on an NTFS sectionalization as an
  absolute path or specify an existing UNC path for the new content file location.

powellhishonce.blogspot.com

Source: https://social.technet.microsoft.com/Forums/lync/en-US/2cbd07fc-4f4a-484f-a254-b1338529489b/additional-wsus-and-sup

Share this post