Do you have ISA 2004 and Shadowprotect installed on your SBS2003 server? Seen these types of errors in the logs?
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013 Error state: 1, Severity: 16 Source: Microsoft OLE DB Provider for SQL Server Error message: BACKUP DATABASE is terminating abnormally.
SQLVDI: Loc=SVDS::Open. Desc=Open(control). ErrorCode=(2)The system cannot find the file specified. . Process=1908. Thread=8372. Server. Instance=MSFW.
It would appear that the MSDE database used by ISA2004 for logging (as demonstrated by Instance=MSFW) isn’t very VSS compliant! Worse still given the right set of circumstances the ISA Services would fail and the whole server would be brought to grinding halt.
The best solution seems to change the logging in ISA2004 from MSDE to text file. To do this:
- 1. In the Microsoft ISA Server Management console click ‘Monitoring’ -> ‘Logging’ tab in the centre pane.
- 2. In the right pane, click the ‘Tasks’ tab, and then click the appropriate task:
- To log the Firewall service data to a file, click ‘Configure Firewall Logging’.
- To log the Web Proxy service data to a file, click ‘Configure Web Proxy Logging’.
- To log the SMTP message screener service to a file, click ‘Configure SMTP Message Screener Logging’.
- 3. On the ‘Log’ tab, click ‘File’.
- 4. In the ‘Format:’ field, ensure that ‘W3c Extended log file format’ is selected.
- 5. Click ‘Options’ to confirm or to modify the following parameters: (This step is optional.)
- ‘Store the log files in’
- ‘Log file storage limits’
- ‘Maintain log storage limits by’
- ‘Delete log files older than’
- ‘Compress log files’
Hopefully that way when Shadowprotect runs, since nothing is being logged to the MSDE database, hang ups won’t occur. The general result I found on the Net is that logging of ISA 2004 should be set to text file only as it is more stable.