Backup fails on 0x800423f4 (VSS/System State)
Rick
First scheduled backup failed with:
**********************************
5/21/2007 11:00 PM
-------------------------------
Date: 5/21/2007
Time: 11:00 PM
User: SYSTEM
-------------------------------
Backup Runner started.
NTMS session started successfully.
EnumerateNtmsObject(NTMS_LIBRARY) succeeded.
Will enumerate on 4 media libraries found.
GetNtmsObjectInformation(NtmsLibraryInfo) succeeded.
GetNtmsObjectInformation(NtmsLibraryInfo) succeeded.
Found an enabled library.
InventoryNtmsLibrary(NtmsInventoryOmid) succeeded.
Identify Media completed
EnumerateNtmsObject(NTMS_PHYSICAL_MEDIA) succeeded.
Will enumerate on 0 media types found.
GetNtmsObjectInformation(NtmsLibraryInfo) succeeded.
Found an enabled library.
InventoryNtmsLibrary(NtmsInventoryOmid) succeeded.
Identify Media completed
EnumerateNtmsObject(NTMS_PHYSICAL_MEDIA) succeeded.
Will enumerate on 1 media types found.
GetNtmsObjectInformation(NtmsPhysicalMediaInfo) succeeded.
GetNtmsObjectInformation(NtmsMediaTypeInfo) succeeded.
Found a tape media type in the library (DLT).
Launching NTBackup: ntbackup.exe backup "@C:\Program Files\Microsoft Windows
Small Business Server\Backup\Small Business Backup Script.bks" /d "SBS
Backup created on 5/21/2007 at 11:00 PM" /v:yes /r:no /rs:no /hc:on /m
normal /j "Small Business Server Backup Job" /l:s /p "DLT" /UM
NTBACKUP LOG FILE: C:\Documents and Settings\SBS Backup User\Local
Settings\Application Data\Microsoft\Windows NT\NTBackup\data\backup03.log
=====================<BEGIN NTBACKUP LOG FILE>=====================
Backup Status
Operation: Backup
Active backup destination: DLT
Media name: "Media created 5/21/2007 at 11:00 PM"
Volume shadow copy creation: Attempt 1.
"MSDEWriter" has reported an error 0x800423f4. This is part of System State.
The backup cannot continue.
Error returned while creating the volume shadow copy:800423f4
Aborting Backup.
*********************************************
This is possibly due to SQL DB not in SIMPLE mode?
How do I look at the state of the MDB files? SQL Enterprise Manager is not
installed.
Thanks for your assistance.
Rick
Jacky Luo [MSFT]
Thank you for your post here.
I understand that you encounter error 800423f4 when trying to backup SBS
Server. If I have misunderstood your issue, please do let me know.
I suggest that we first perform following generate troubleshoot steps to
see how it goes. If the issue persists, please help me to gather more
information for further research.
1. Please refer to the following article
http://blogs.msdn.com/adioltean/archive/2005/08/31/458907.aspx
Downloaded BETEST.EXE. from VSS SDK
http://www.microsoft.com/downloads/details.aspx?FamilyID=0b4f56e4-0ccc-4626-
826a-ed2c4c95c871&DisplayLang=en
Reloaded the VSS writers using BETEST utility
Opened C:\Program Files\Microsoft\VSSSDK72\TestApps\betest\obj\i386> in
Command prompt.
ran betest.exe without parameters, so that it does a backup and restore all
the writers.
Then you can backup again to see if it helps to resolve your issue.
2. MSDEwriter is one of VSS writer installed by MSDE. I suggest that you
read through following KB articles and apply the steps if you meet the
exact same symptom.
912414 Error message when you use the Volume Shadow Copy Service (VSS) to
back up SQL Server 2000 database files or SQL Server 2000 Desktop Engine
(MSDE) database files: "'MSDEWriter' has reported an error 0x800423f4"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;912414
828481 Error 800423f4 appears in the backup log file when you back up a
volume by using the Volume Shadow Copy service in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;828481
3. Since the error refers to the MSDEWriter, this issue may be related
with Microsoft SQL Server 2000 Desktop Engine (MSDE) database files. As
0x800423f4 is translated to VSS_E_WRITERERROR_NONRETRYABLE, I suggest that
we have a check the service account issue of the MSDE instance.
1). Run Services.msc to bring up the Service console.
2). Double click MSSQL$SHAREPOINT to open the properties page.
3). In the logon tab, please make sure this service is running under Local
System Account instead of a specific account.
4). Please check the same settings with MSSQL$SBSMONITORING service.
5). Restart the server and test your issue again.
4. Please install following hotfix to see how it goes:
For SBS 2003 SP0:
A Volume Shadow Copy Service (VSS) update package is available
http://support.microsoft.com/?id=833167
A Volume Shadow Copy Service (VSS) update-2 package is available
http://support.microsoft.com/default.aspx?scid=kb;en-us;887827
For SBS 2003 SP1:
Update is available that fixes various Volume Shadow Copy Service issues in
Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;891957
913648 A new Volume Shadow Copy Service update is now available that fixes
various Volume Shadow Copy Service problems in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;913648
============================
There are two options to get this hotfix, contacting CSS at your
convenience and they will deliver it to you with no charge
5. this problem might be caused if VSS related DLL files are not registered
properly. Please follow the step below to re-register:
Net stop vss
Net stop swprv
regsvr32.exe /i eventcls.dll
regsvr32 stdprov.dll
regsvr32.exe /i swprv.dll
regsvr32.exe vssui.dll
regsvr32.exe vss_ps.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml2.dll
regsvr32.exe msxml3.dll
regsvr32.exe msxml4.dll
regsvr32.exe ole32.dll
regsvr32.exe oleaut32.dll
regsvr32.exe es.dll
vssvc /register
Net stop vss
Net stop swprv
6. Also, please note that when the VSS service and the SQLWriter service
are installed, the service startup account is configured as Local System
[NT AUTHORITY\SYSTEM]. When the writer tries to establish a connection to
instances of SQL Server, the writer uses the credentials of the Local
System [NT AUTHORITY\SYSTEM] startup account. You must make sure that the
instances of SQL Server have granted access to this Windows account either
explicitly or through group membership of BUILTIN\Administrators. Please
follow the step below to try to solve the problem:
a. Open the SQL Server, Expand "Security", right-mouse click on
"Logins", select "New Login", type in the "Name" field "NT
AUTHORITY\SYSTEM" without the quotation marks and press enter
b. In the right pane right-mouse-click on "NT AUTHORITY\SYSTEM", select
"Properties", click "Server Roles" tab, select the "System Administrators"
check-box and click OK
If the problem persists, please help me to gather following information for
further research: collect an MPS Report and send it to
v-j...@microsoft.com.
1. What is your backup tape exact brand and model? Please check if it's
listed in HCL list. If not, it may cause some problems.
Products Designed for Microsoft Windows - Windows Catalog and HCL
http://www.microsoft.com/whdc/hcl/default.mspx
2. Do you have standard SQL server installed on the SBS 2k3 server? If
yes, go to the Service Console and double click the MSSQLServer service, on
the Log on tab, what is the account the service is running as? Please make
sure that SQL SERVER Service is using Domain Administrator account.
3. Can you manually run the ntbackup to local hard disk? To do so:
a. Click Start, click Run, type ntbackup, and then press Enter. The
Backup or Restore Wizard launches.
b. On the Welcome to the Backup or Restore Wizard page, click Advanced
Mode.
c. Click the Backup tab. From the Job menu, choose Load Selections.
d. In the File Name box type %sbsprogramdir%\backup.
e. Click Small Business Backup Script.bks to select, and click Open.
f. Please choose your local hard disk as backup destination.
g. On the Backup tab, click Start Backup.
h. Can the problem be reproduced?
4. Please help me to gather the Backup logs:
a. The Backupxx.log files in the folder 'C:\Documents and Settings\SBS
Backup User\Local Settings\Application Data\Microsoft\Windows
NT\NTBackup\data'.
b. The Sbsbackuplog0x.log files which can be located under the folder
'%sbsprogramdir%\Support\Backup Logs'.
5. Please help me to collect MPS Report:
a. Download MPSrepot_setupperf from
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_SETUPPERF.EXE
b. Run MPSRPT_SETUPPERF.exe on the server box.
c. The tool will automatically collect the information. This procedure will
take 10~15 minutes.
d. Open Windows Explorer, navigate to the folder:
%SystemRoot%\MPSReports\SETUP\Reports\Cab\
e. Please send the .cab file to me at v-j...@microsoft.com.
Have a nice day!
Best regards,
Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================
Rick
back how it went.
.. Rick
Jacky Luo [MSFT]
Thank you for posting back.
If you have any updates or need any further assistance on this issue,please
feel free to let me know.I am glad to be of assistance. :-)
Rick
writers screwed up and I could no longer get at any SQL (monitoring,
sharepoint, wsus) databases (could not connect). This approach left me worse
off than when I started. MSFT did not do anything with all the documentation
he requested at the end of the procedure - rather, suggested I call (pay)
CSS.
Jacky Luo [MSFT]
Thank you for posting back.
I am not sure if you have called CSS,if so,Please Post back if you have any
update regarding solution of your issue. I am still performing researching
on your issue.
I give the suggestion because it resolve the similar issue that other
people have experienced. I am sorry for it doesn't meet your case. Thanks
for your understanding.
Rick
It was much easier for me to do a clean install of SBS2003 R2 , key anew the
Users and Computers, then recover Exchange and User Data Folders. Took the
system offline Friday evening and we were back up-and-running Saturday
afternoon. So I can't give you any fresh information other than to have you
reconsider advising people to recreate their VSS writers. Even MS calls the
code 'BETA'.
I shudda known better.
Rick