This post is more than 5 years old

2 Intern

 • 

63 Posts

3804

August 26th, 2009 04:00

WSUS problem in VSS saveset

Hi all,

We have a Windows 2008 server (x64) with WSUS installed.
On this server, a NetWorker 7.4.4 client is installed.

During the backup, I recieve the following error:
F:\WSUS\
F:\WSUS\UpdateServicesDbFiles\
Windows Internal Database - Get file attributes returned error 123 for VSS file \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\WSUS\\UpdateServicesDbFiles
Windows Internal Database - Error saving file path F:\WSUS\\UpdateServicesDbFiles that is associated with Shadow Copy path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\WSUS\\UpdateServicesDbFiles. The filename, directory name, or volume label syntax is incorrect.

Windows Internal Database - Warning: Failed to save connecting dir \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\WSUS\\UpdateServicesDbFiles
Windows Internal Database - Get file attributes returned error 123 for VSS file \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\WSUS\\UpdateServicesDbFiles\SUSDB.mdf
Windows Internal Database - Error saving file path F:\WSUS\\UpdateServicesDbFiles\SUSDB.mdf that is associated with Shadow Copy path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\WSUS\\UpdateServicesDbFiles\SUSDB.mdf. The filename, directory name, or volume label syntax is incorrect.

Windows Internal Database - ERROR: Failed to save FileGroup files, writer = SqlServerWriter
Windows Internal Database - Error saving writer Windows Internal Database
Windows Internal Database - ERROR: Aborting backup of saveset VSS SYSTEM SERVICES: because of the error with writer Windows Internal Database.
Windows Internal Database - Error saving
7162:(pid 984): save of VSS SYSTEM SERVICES:\ to bvault01 failed


The WSUS DB is installed on the F-drive, so this should be OK.
I've already tried to add the "VSS:sqlsystemwriter=off" and "VSS:*=off" as save operations, but because it's a W2K8 server this is not possible:

43705:(pid 984): Save Operations value is ignored on this OS platform.

32 Posts

March 29th, 2012 07:00

Microsoft has confirmed that this is a problem in the Microsoft products that are listed below.

  • You are running Windows Server 2008 R2.
  • You use one or more of the following Windows components:
    • Windows SharePoint Services
    • Windows Server Update Services
    • Active Directory Rights Management Services
    • Windows System Resource Manager and UDDI Services.
  • The above components use a special edition of SQL Server called Windows Internal Database (WYukon) for storing data.

Please refer MSKB http://support.microsoft.com/kb/2015904 for additional information.

2 Intern

 • 

63 Posts

August 26th, 2009 04:00

That's correct, it's a server which holds all the OS'es and patches so they can be applied to other servers in the network

2 Intern

 • 

63 Posts

August 27th, 2009 00:00

Yeah, that was one of the first things I let the sysadmins do.
All returned stable and no error.

2 Intern

 • 

1.1K Posts

August 26th, 2009 04:00

It looks from the messages that it is not getting the hostname in the UNC path...?

2 Intern

 • 

1.1K Posts

August 26th, 2009 04:00

I did a search - Windows Update Service Server, right?

2 Intern

 • 

1.1K Posts

August 26th, 2009 04:00

Sorry to sound ignorant but what is WSUS? I assume it is Windows S*** U*** Server or something like that?

36 Posts

August 26th, 2009 05:00

Do you get any errors when checking the VSS writers with command 'vssadmin list writers' ?

4 Operator

 • 

14.4K Posts

September 4th, 2009 05:00

The problem you have is related to "\\" thingy. To fix it using sqlcmd deattach db, set new paths to mdf and ldf file and attach it back.

Top