RE: backup fail

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi,

Thanks for using the SBS newsgroup.

>From your description, I understand that the backup task failed with ESE
478 error event. If I am off base, please don't hesitate to let me know.

Error -613 translates to JET_errSLVReadVerifyFailure (checksum error in SLV
file during backup, where "SLV" stands for "streaming" or ".stm" file).

Based on my research, this issue could be caused by the following three
causes:

=================
1. Some third party software such as eXclaimer and Sybari Antigen. To avoid
any affect from third party software, please perform a clean boot, and then
check if there is any change.

To perform a clean boot, follow the steps below:

A. Click Start, click Run, type "msconfig" (without the quotation marks)
and click OK.
B. Select "Selective Startup" and remove the check box for "Load Startup
Items".
C. On the "Services" tab, click Enable All.
D. Check "Hide all Microsoft Services", click Disable All and clear "Hide
all Microsoft Services".
E. Click the OK button and then Click Yes to restart your computer.
F. Try to backup again, how about the result?

=================
2. This issue may also be caused by the error with hard disk or with the
hard disk controller. To troubleshoot hardware problems
A. View the System log to determine whether disk I/O errors are listed.
B. Obtain available firmware updates or driver updates for your hard disk
drive controllers.
C. Run the Chkdsk utility to determine whether a problem exists with the
hard disk drives.

=================
3. The issue can happen if the information store database is damaged or
corrupted either. If the above test did not help you find the cause, you
may defragment and repair the information store database referring to the
KB810333.

You may receive the "ESE event ID 215 the backup has been stopped because
it was halted by the client" error message in Exchange 2000 Server
http://support.microsoft.com/?id=810333

For your information:

How to defragment Exchange databases
http://support.microsoft.com/?id=328804

What is more, I would like to suggest you apply the SBS 2003 SP1 (including
Exchange 2003 SP1) to the server box to resolve the problem. There are some
known issues if there is only Windows 2003 SP1 installed on the server box.

It is recommended you apply SBS sp1 follow installation guide provided by
Microsoft and you will not encounter many issues.

You can refer to the following link to apply SBS SP1:
http://www.smallbizserver.net/Default.aspx?PageContentID=62&tabid=236

In the following website you can find many useful resources related to SBS
SP1:
http://www.smallbizserver.net/Default.aspx?PageContentID=53&tabid=236

The website includes: What is SP1 for SBS 2003 and what you need to know |
Standard install step-by-step | Premium install step-by-step | Things to do
after the upgrade | Errors that can occur after the upgrade

Hope above information helps. I am happy to be of assistance to you and
look forward to your reply.

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: backup fail
>thread-index: AcYUvgcRUwaa/DbbT06NRz5O7GbeRQ==
>X-WBNR-Posting-Host: 66.28.244.181
>From: =?Utf-8?B?a2hhbGVkIGF6emF6?= <khaledazzaz@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: backup fail
>Date: Sun, 8 Jan 2006 17:43:02 -0800
>Lines: 31
>Message-ID: <7D097156-673C-44E8-BC16-F5A6942BD74D@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:234991
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi
>I recently restore SBS2003 to a new hard drive. It has been working for a
>week with no issues. The backup was working during this week. Sudenly i
have
>this error in the applictaion log, and the backup failed.
>
>Windows 2003 SP1 Was applied by one of the guys who works in the copany.
but
>not the rest of the SP1 of SBS2003. That was done 9 months ago. We kept
like
>that because we do not want to change that much on the server.
>
>Event Type: Error
>Event Source: ESE
>Event Category: Logging/Recovery
>Event ID: 478
>Date: 1/8/2006
>Time: 8:28:34 PM
>User: N/A
>Computer: AIRPDC2
>Description:
>Information Store (6648) The streaming page read from the file "C:\Program
>Files\Exchsrvr\mdbdata\priv1.stm" at offset 184520704 (0x000000000aff9000)
>for 4096 (0x00001000) bytes failed verification due to a page checksum
>mismatch. The expected checksum was 3383479753 (0xc9abcdc9) and the
actual
>checksum was 4225161683 (0xfbd6d9d3). The read operation will fail with
>error -613 (0xfffffd9b). If this condition persists then please restore
the
>database from a previous backup.
>
>For more information, click http://www.microsoft.com/contentredirect.asp.
>
>Please help
>Thank you
>
>

.

Quantcast