sp_DatabaseRestore -- Operating system error 123(The filename, directory name, or volume label syntax is incorrect.)

[SLDave-MDA]

Version of the script
8.25

What is the current behavior?
When specifying a network path for FULL backup location - it produces below error.
Operating system error 123(The filename, directory name, or volume label syntax is incorrect.)
Return value -6

Example path location: '\SERVERNAME\Z$\BAK'

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Native SQL restore with the above path works fine. Also works in Quest's LiteSpeed

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
OS: Windows Server 2019 Datacenter (10.0.17763) - SQL 2019 (SQL Server 15.9.4430.1)

[SLDave-MDA]

I do have \ before SERVERNAME. ' \SERVERNAME\Z$\BAK'

[SLDave-MDA]

Do have two \ befire server name in the path.

[BrentOzar]

First, UNC paths require two backslashes, as in \\SERVERNAME\Z$\BAK. Try that.

Second, the restore would rely on the SQL Server engine account's permission to access that particular share drive. You'll want to verify that the engine service account (not Agent, not your account, not LiteSpeed's account) has read access to that share.

Also, use the @debug parameter to find out what the exact T-SQL commands it's trying to run, and test those in SSMS. That may help track down where the issue is.

[SLDave-MDA]

Brent, it does have two backslashes. Thanks

[BrentOzar]

Sure, check the rest of the notes. Thanks!

[SLDave-MDA]

For the SQL Server and agent we use gMSA service account -- Creating a native SQL restore job and running works fine with Z$ in the path. Next -- Running with @debug parameter

[SLDave-MDA]

Output with @debug = 1

Fixing @MoveDataDrive to add a ""
Fixing @MoveLogDrive to add a ""
Setting default data drive for @MoveFilestreamDrive
Setting default data drive for @MoveFullTextCatalogDrive
INSERT INTO #FileListParameters WITH (TABLOCK)
(LogicalName, PhysicalName, Type, FileGroupName, Size, MaxSize, FileID, CreateLSN, DropLSN
,UniqueID, ReadOnlyLSN, ReadWriteLSN, BackupSizeInBytes, SourceBlockSize, FileGroupID, LogGroupGUID
,DifferentialBaseLSN, DifferentialBaseGUID, IsReadOnly, IsPresent, TDEThumbprint, SnapshotUrl)
EXEC ('RESTORE FILELISTONLY FROM DISK=''\servername\z$\BAK''')
Msg 3201, Level 16, State 2, Line 3
Cannot open backup device '\servername\z$\BAK'. Operating system error 123(The filename, directory name, or volume label syntax is incorrect.).
Msg 3013, Level 16, State 1, Line 3
RESTORE FILELIST is terminating abnormally.
INSERT INTO #Headers WITH (TABLOCK)
(BackupName, BackupDescription, BackupType, ExpirationDate, Compressed, Position, DeviceType, UserName, ServerName
,DatabaseName, DatabaseVersion, DatabaseCreationDate, BackupSize, FirstLSN, LastLSN, CheckpointLSN, DatabaseBackupLSN
,BackupStartDate, BackupFinishDate, SortOrder, CodePage, UnicodeLocaleId, UnicodeComparisonStyle, CompatibilityLevel
,SoftwareVendorId, SoftwareVersionMajor, SoftwareVersionMinor, SoftwareVersionBuild, MachineName, Flags, BindingID
,RecoveryForkID, Collation, FamilyGUID, HasBulkLoggedData, IsSnapshot, IsReadOnly, IsSingleUser, HasBackupChecksums
,IsDamaged, BeginsLogChain, HasIncompleteMetaData, IsForceOffline, IsCopyOnly, FirstRecoveryForkID, ForkPointLSN
,RecoveryModel, DifferentialBaseLSN, DifferentialBaseGUID, BackupTypeDescription, BackupSetGUID, CompressedBackupSize
, Containment, KeyAlgorithm, EncryptorThumbprint, EncryptorType)
EXEC ('RESTORE HEADERONLY FROM DISK=''\servername\z$\BAK''')
Msg 3201, Level 16, State 2, Line 3
Cannot open backup device '\servername\z$\BAK'. Operating system error 123(The filename, directory name, or volume label syntax is incorrect.).
Msg 3013, Level 16, State 1, Line 3
RESTORE HEADERONLY is terminating abnormally.
Msg 50000, Level 16, State 1, Procedure dbo.sp_DatabaseRestore, Line 761 [Batch Start Line 2]
Backupfile "" does not match @database parameter "DBName"

(1 row affected)

(1 row affected)

Completion time: 2025-08-11T13:15:35.0155182-05:00

[BrentOzar]

Dave - I get the feeling you kinda wanna lob this issue over at me and go, "Brent, figure it out," but this isn't something I can reproduce on my end. You'll want to work through the commands it's trying to run, how it's building the variables, where it's failing on your end, etc., and then make the necessary changes to the proc (or your environment) to get it to work for you.

I do wish I could help more, but I'm out in Alaska on vacation with my family, and this isn't something I'll have bandwidth to dig more deeply on.

If you have specific questions for me, feel free to ask, but unfortunately open source doesn't mean unlimited free support. I hope that's fair, and I know that's kind of a bummer to hear.

[SLDave-MDA]

No worries at all. I'm simply thrilled to get a response from you. I'll let you know if and when I can fix the issue. Best - Sanjeev

…

________________________________ From: Brent Ozar ***@***.***> Sent: Monday, August 11, 2025 1:26 PM To: BrentOzarULTD/SQL-Server-First-Responder-Kit ***@***.***> Cc: Dave,Sanjivkumar L ***@***.***>; Assign ***@***.***> Subject: [EXTERNAL] Re: [BrentOzarULTD/SQL-Server-First-Responder-Kit] sp_DatabaseRestore -- Operating system error 123(The filename, directory name, or volume label syntax is incorrect.) (Issue #3684) SLOW DOWN! - EXTERNAL SENDER: ***@***.*** Be suspicious of tone, urgency, and formatting. Do not click/open links or attachments on a mobile device. Wait until you are at a computer to confirm you are absolutely certain it is a trusted source. If you are at all uncertain use the Report Phish button and our Cybersecurity team will investigate. [https://avatars.githubusercontent.com/u/245462?s=20&v=4]BrentOzar left a comment (BrentOzarULTD/SQL-Server-First-Responder-Kit#3684)<https://urldefense.com/v3/__https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/3684*issuecomment-3176284267__;Iw!!PfbeBCCAmug!kkGKXLtJVIa17QDXolr27yxt9_6HF1cjn1UcIW360l4UJBnjIsBhrrxuQkQuoDIXomc8-S6oSeTGq0OrAYrfPq91uA$> Dave - I get the feeling you kinda wanna lob this issue over at me and go, "Brent, figure it out," but this isn't something I can reproduce on my end. You'll want to work through the commands it's trying to run, how it's building the variables, where it's failing on your end, etc., and then make the necessary changes to the proc (or your environment) to get it to work for you. I do wish I could help more, but I'm out in Alaska on vacation with my family, and this isn't something I'll have bandwidth to dig more deeply on. If you have specific questions for me, feel free to ask, but unfortunately open source doesn't mean unlimited free support. I hope that's fair, and I know that's kind of a bummer to hear. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/3684*issuecomment-3176284267__;Iw!!PfbeBCCAmug!kkGKXLtJVIa17QDXolr27yxt9_6HF1cjn1UcIW360l4UJBnjIsBhrrxuQkQuoDIXomc8-S6oSeTGq0OrAYrfPq91uA$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BV3XX74P57QSCOABGYS5D4L3NDN3VAVCNFSM6AAAAACDUDVRS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZWGI4DIMRWG4__;!!PfbeBCCAmug!kkGKXLtJVIa17QDXolr27yxt9_6HF1cjn1UcIW360l4UJBnjIsBhrrxuQkQuoDIXomc8-S6oSeTGq0OrAYoA6uBMBw$>. You are receiving this because you were assigned.Message ID: ***@***.***> The information contained in this e-mail message may be privileged, confidential, and/or protected from disclosure. This e-mail message may contain protected health information (PHI); dissemination of PHI should comply with applicable federal and state laws. If you are not the intended recipient, or an authorized representative of the intended recipient, any further review, disclosure, use, dissemination, distribution, or copying of this message or any attachment (or the information contained therein) is strictly prohibited. If you think that you have received this e-mail message in error, please notify the sender by return e-mail and delete all references to it and its contents from your systems.