Answered by:
WSUS SQL install physical file name error

Question
-
Hi there,
I'm trying to reinstall WSUS on my SCCM server (2012 R2) as a SQL db instead of WID. I inherited it this way. No matter what I try, the post-install tasks bomb out with this error:
2018-08-08 12:08:16 Postinstall started 2018-08-08 12:08:16 Detected role services: Api, Database, UI, Services 2018-08-08 12:08:16 Start: LoadSettingsFromParameters 2018-08-08 12:08:16 Content local is: True 2018-08-08 12:08:16 Content directory is: D:\Windows Server Update Service 2018-08-08 12:08:16 SQL instname is: GAMBIT 2018-08-08 12:08:16 End: LoadSettingsFromParameters 2018-08-08 12:08:16 Start: Run 2018-08-08 12:08:16 Fetching WsusAdministratorsSid from registry store 2018-08-08 12:08:16 Value is S-1-5-21-1355483703-2602408213-1168805140-1004 2018-08-08 12:08:16 Fetching WsusReportersSid from registry store 2018-08-08 12:08:16 Value is S-1-5-21-1355483703-2602408213-1168805140-1005 2018-08-08 12:09:15 Configuring content directory... 2018-08-08 12:09:15 Configuring groups... 2018-08-08 12:09:15 Starting group configuration for WSUS Administrators... 2018-08-08 12:09:15 Found group in regsitry, attempting to use it... 2018-08-08 12:09:18 Writing group to registry... 2018-08-08 12:09:18 Finished group creation 2018-08-08 12:09:18 Starting group configuration for WSUS Reporters... 2018-08-08 12:09:18 Found group in regsitry, attempting to use it... 2018-08-08 12:09:18 Writing group to registry... 2018-08-08 12:09:18 Finished group creation 2018-08-08 12:09:18 Configuring permissions... 2018-08-08 12:09:18 Fetching content directory... 2018-08-08 12:09:18 Fetching ContentDir from registry store 2018-08-08 12:09:18 Value is D:\Windows Server Update Service 2018-08-08 12:09:18 Fetching group SIDs... 2018-08-08 12:09:18 Fetching WsusAdministratorsSid from registry store 2018-08-08 12:09:18 Value is S-1-5-21-1355483703-2602408213-1168805140-1004 2018-08-08 12:09:18 Fetching WsusReportersSid from registry store 2018-08-08 12:09:18 Value is S-1-5-21-1355483703-2602408213-1168805140-1005 2018-08-08 12:09:18 Creating group principals... 2018-08-08 12:09:18 Granting directory permissions... 2018-08-08 12:09:18 Granting permissions on content directory... 2018-08-08 12:09:18 Granting registry permissions... 2018-08-08 12:09:18 Granting registry permissions... 2018-08-08 12:09:18 Granting registry permissions... 2018-08-08 12:09:18 Configuring shares... 2018-08-08 12:09:18 Configuring network shares... 2018-08-08 12:09:18 Fetching content directory... 2018-08-08 12:09:18 Fetching ContentDir from registry store 2018-08-08 12:09:18 Value is D:\Windows Server Update Service 2018-08-08 12:09:18 Fetching WSUS admin SID... 2018-08-08 12:09:18 Fetching WsusAdministratorsSid from registry store 2018-08-08 12:09:18 Value is S-1-5-21-1355483703-2602408213-1168805140-1004 2018-08-08 12:09:18 Content directory is local, creating content shares... 2018-08-08 12:09:18 Creating share "UpdateServicesPackages" with path "D:\Windows Server Update Service\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system." 2018-08-08 12:09:18 Creating share... 2018-08-08 12:09:18 Share successfully created 2018-08-08 12:09:18 Creating share "WsusContent" with path "D:\Windows Server Update Service\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system." 2018-08-08 12:09:18 Creating share... 2018-08-08 12:09:18 Share successfully created 2018-08-08 12:09:19 Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance." 2018-08-08 12:09:19 Creating share... 2018-08-08 12:09:19 Share successfully created 2018-08-08 12:09:19 Finished creating content shares 2018-08-08 12:09:19 Stopping service WSUSService 2018-08-08 12:09:19 Stopping service W3SVC 2018-08-08 12:10:49 Configuring database... 2018-08-08 12:10:49 Configuring the database... 2018-08-08 12:10:49 Establishing DB connection... 2018-08-08 12:10:49 Checking to see if database exists... 2018-08-08 12:10:49 Database does not exist 2018-08-08 12:10:49 Loading install type query... 2018-08-08 12:10:49 DECLARE @currentDBVersion int DECLARE @scriptMajorVersion int = (9600) DECLARE @scriptMinorVersion int = (18694) DECLARE @databaseMajorVersion int DECLARE @databaseMinorVersion int DECLARE @databaseBuildNumber nvarchar(10) IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB') BEGIN SELECT 1 END ELSE BEGIN SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB') SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB') DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber) IF (@delimiterPosition = 0) BEGIN RAISERROR('Invalid schema version number', 16, 1) with nowait return END SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1) SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition)) IF @currentDBVersion < 926 BEGIN SELECT 3 END ELSE BEGIN IF (@scriptMajorVersion > @databaseMajorVersion OR (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion)) BEGIN SELECT 2 END ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion = @databaseMinorVersion) BEGIN SELECT 0 END ELSE BEGIN SELECT 4 END END END 2018-08-08 12:10:49 Install type is: Fresh 2018-08-08 12:10:49 Creating database... 2018-08-08 12:10:50 Msg 5105, Level 16, State 2, Server GAMBIT, Line 2 A file activation error occurred. The physical file name 'D\:Database\SUSDB.mdf' may be incorrect. Diagnose and correct additional errors, and retry the operation.Msg 1802, Level 16, State 1, Server GAMBIT, Line 2 CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 2018-08-08 12:10:50 Re-Establishing Connection to execute Multi User Query ... 2018-08-08 12:10:50 Ensuring SUSDB is set to Multi-User Mode ... 2018-08-08 12:10:50 Microsoft.UpdateServices.Administration.CommandException: Database creation failed at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDatabase() at Microsoft.UpdateServices.Administration.ConfigureDB.Configure() at Microsoft.UpdateServices.Administration.ConfigureDB.Run(String instanceName, Action`1 logWriter, Boolean contentLocal) at Microsoft.UpdateServices.Administration.PostInstall.Run() at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
I've uninstalled WSUS (including WID), made sure the WSUScontent folder and SUSDB/SUSDB.log are detached and gone, deleted the IIS site. Pretty much everything at these two Answers:
https://social.technet.microsoft.com/Forums/ie/en-US/c7a6f2d6-2e4d-437b-a104-03328c146d4a/wsus-post-deployment-tasks-configuration-failed?forum=winserverwsus
https://social.technet.microsoft.com/Forums/office/en-US/74c48550-52f6-4160-b8a6-67fc4e6eab79/wsus-post-install-fails-quotfatal-error-the-system-cannot-find-the-path-specifiedquot?forum=winserverwsus
This is my first time configuring WSUS/SCCM. Help?
Wednesday, August 8, 2018 7:20 PM
Answers
-
Got it to work!
Rolled back to a earlier checkpoint, migrated the database from WID to SQL, then ran the post install tasks via Powershell. Then it finally completed successfully.
- Marked as answer by SLGoff Thursday, August 9, 2018 11:07 PM
Thursday, August 9, 2018 11:07 PM
All replies
-
Hello SarahGoff,
Glad to help.
"A file activation error occurred. The physical file name 'D\:Database\SUSDB.mdf' may be incorrect."
There is an input error in your path, change "D\:" to "D:\"
Hope my answer could help you and look forward to your feedback.
Best Regards,
Ray Jia
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thursday, August 9, 2018 1:04 AM -
Hi Ray!
I noticed that filepath error, I just can't find where it needs to be changed. Going through the setup wizard, there's nowhere that filepath is entered. I have no idea where it's getting pulled from.
Any advice?
Thursday, August 9, 2018 4:55 PM -
Got it to work!
Rolled back to a earlier checkpoint, migrated the database from WID to SQL, then ran the post install tasks via Powershell. Then it finally completed successfully.
- Marked as answer by SLGoff Thursday, August 9, 2018 11:07 PM
Thursday, August 9, 2018 11:07 PM