shadow copy:0x80042319

Current situation.
SBS 2003 STD, SP1
3 Hard Disk (C:\,D:\,E:\), CD-Rom (F:\) ,External Backup Disk( G:\ [USB \
E-Sata])

Scheduled Back-Ups fail permanently, however manual Back-Ups Complete
successfully.
By manual I mean going to the SBS SRV Management Console and clicking on the
"Backup Now" button.
So all settings and ect .. are the same as the scheduled backups.

Anyone had this before ? Any successful fixes ?

Any help would be greatly appreciated as this is driving me up the wall.

Thanks
Nox

----------------------

Current Backup Settings:
Schedule: At 10:00 PM every Mon, Tue, Wed, Thu, Fri, Sat, Sun of every week,
starting 2008/02/04
Backup Location: G:\Backup Files

=====================<BEGIN NTBACKUP LOG FILE>=====================
Backup Status
Operation: Backup
Active backup destination: File
Media name: "Small Business Server Backup (01).bkf created 2008/02/06 at
10:00 PM"

Volume shadow copy creation: Attempt 1.
Timeout before function completed

Error returned while creating the volume shadow copy:0x80042319.

Error returned while creating the volume shadow copy:80042319
Aborting Backup.

----------------------

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12305
Date: 2008/02/06
Time: 10:25:34 PM
User: N/A
Computer: ONT-SBS2003S
Description:
Volume Shadow Copy Service error: Volume/disk not connected or not found.
Error context:

CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy131,0xc0000000,0x00000003,...).

For more

information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 20 43 6f 64 65 3a 20 - Code:
0008: 49 4e 43 49 43 48 4c 48 INCICHLH
0010: 30 30 30 30 30 32 32 30 00000220
0018: 2d 20 43 61 6c 6c 3a 20 - Call:
0020: 53 50 52 51 53 4e 50 43 SPRQSNPC
0028: 30 30 30 30 30 31 32 33 00000123
0030: 2d 20 50 49 44 3a 20 20 - PID:
0038: 30 30 30 30 36 30 32 30 00006020
0040: 2d 20 54 49 44 3a 20 20 - TID:
0048: 30 30 30 30 37 33 35 36 00007356
0050: 2d 20 43 4d 44 3a 20 20 - CMD:
0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
0060: 57 53 5c 53 79 73 74 65 WS\Syste
0068: 6d 33 32 5c 73 76 63 68 m32\svch
0070: 6f 73 74 2e 65 78 65 20 ost.exe
0078: 2d 6b 20 73 77 70 72 76 -k swprv
0080: 2d 20 55 73 65 72 3a 20 - User:
0088: 4e 54 20 41 55 54 48 4f NT AUTHO
0090: 52 49 54 59 5c 53 59 53 RITY\SYS
0098: 54 45 4d 20 20 20 20 20 TEM
00a0: 2d 20 53 69 64 3a 20 20 - Sid:
00a8: 53 2d 31 2d 35 2d 31 38 S-1-5-18

----------------------

Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 2008/02/06
Time: 10:11:29 PM
User: N/A
Computer: ONT-SBS2003S
Description:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0).
Process=3336. Thread=7908. Client.

Instance=SQLEXPRESS. VD=Global\{B7689FAA-A677-438D-80AC-A6411C379218}5.

For more information, see Help and

Support Center at http://go.microsoft.com/fwlink/events.asp.

----------------------

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6013
Date: 2008/02/06
Time: 10:07:08 PM
User: N/A
Computer: ONT-SBS2003S
Description:
Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr
= 0x80004005. SQLSTATE: 08S01,

Native Error: 11
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message:

[DBNETLIB][ConnectionWrite (WrapperWrite()).]General network error. Check
your network documentation.


For

more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 20 43 6f 64 65 3a 20 - Code:
0008: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0010: 30 30 30 30 30 34 39 31 00000491
0018: 2d 20 43 61 6c 6c 3a 20 - Call:
0020: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0028: 30 30 30 30 30 33 39 37 00000397
0030: 2d 20 50 49 44 3a 20 20 - PID:
0038: 30 30 30 30 35 30 36 38 00005068
0040: 2d 20 54 49 44 3a 20 20 - TID:
0048: 30 30 30 30 34 34 39 32 00004492
0050: 2d 20 43 4d 44 3a 20 20 - CMD:
0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
0060: 57 53 5c 53 79 73 74 65 WS\Syste
0068: 6d 33 32 5c 76 73 73 76 m32\vssv
0070: 63 2e 65 78 65 20 20 20 c.exe
0078: 2d 20 55 73 65 72 3a 20 - User:
0080: 4e 54 20 41 55 54 48 4f NT AUTHO
0088: 52 49 54 59 5c 53 59 53 RITY\SYS
0090: 54 45 4d 20 20 20 20 20 TEM
0098: 2d 20 53 69 64 3a 20 20 - Sid:
00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18

All the references I see are:

SP level must be at least SP1
Try Excluding System State for a test. Some find they have to do SS
separately
Check that VSS is running

Re Register your VSS dlls
According to Microsoft Premier Support this is the correct procedure to
follow when re-registering the Volume Shadow Copy service DLL's.
CD to Windows\System32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

Reboot your server.

After reboot, open a command prompt and run:
vssadmin list writers

Ensure that all your writers are displayed w/o errors.

If you are backing up to tape, MS CSS usual suggestions are:

Try the job to a local or external hard drive
Check the HCL for the tape drive compatibility with Windows Server 2003.

[mousumi]

If I execute the followings commands

CD to Windows\System32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

is there any chance to corrupt my server's database or any data?

No, registering dlls will not corrupt any data or databases.

See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive...A/default.aspx

[mousumi]

Hi Jim,
Thanks a lot for your reply.

This did it for me evem though the msxml.dll did not load.

"unknown" wrote:

>