shadow copy / back-up problems...

Steven,

Wow. Thanks so much for your assistance - I really appreciate it. I will
proceed with your suggestions around noon California time, and respond to all
of your questions. I've got to find a time that I can break everyone off the
network to do the maintanence. Back to you soon - thanks again!
--
Thanks,
MarkW


"Steven Zhu [MSFT]" wrote:

> Hi Mark,
>
> Thanks for posting here.
>
> From your post, my understanding on this issue is: the server unexpectedly
> shutdown and you find the hard-disk and the VolSnap error message in Event
> Viewer. If I am off base, please feel free to let me know.
>
> First of all, 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 again.
>
> From your description about the error message, I find the issue is exactly
> related with the bad block on HD. The problem could be caused by the hard
> disk failure.
>
> Could you let me know how you run the CHKDSK command to check the disk?
> Anyway, I suggest we use Chkdsk with proper parameters to check the bad
> sector again to see if the bad block still exists. Please use the following
> command:
>
> CHKDSK C: /v /f
> CHKDSK D: /v /f
>
> Is there any new error found?
>
> Please let me know the result above so that I can provide the further
> assistance on this issue. I am looking forward to your reply.
>
> Have a nice day.
>
> Best Regards,
>
> Steven Zhu
> MCSE
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ======================================================
> PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
> updated on February 14, 2006.? Please complete a re-registration process
> by entering the secure code mmpng06 when prompted. Once you have
> entered the secure code mmpng06, you will be able to update your profile
> and access the partner newsgroups.
> ======================================================
> 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.
> ======================================================
>
>
>
>
>
>
>
>
 >> Stay informed about: shadow copy / back-up problems... 

Hi Steven - I'm back!

I followed your suggestions to a T, and will try to reply as simply as
possible. First, I did the clean boot. It did give me a warning that I
needed Administrator rights to change a service, but it seemed to reboot fine.

Upon reboot, it brings up a Service Control Manager warning message telling
me that at least one service or driver failed during system startup.

From here, I went to the Event Viewer to try and see what's going on. Under
the application logs, I get an #50070 error that states that Unableto connect
to the database STS_Config on Server\Sharepoint. I also get a warning that a
provider, PERFPROV has been registered in the WMI namespace, but did not
specify a HostingModel property.

Under the application logs, I get a few strange things as well. I have a
fatal error that occurred while trying to access the SSL server credential
private key. This is followed up with a warning that no suitable default
credential exists on the system. I also get a warning that the DHCP service
has detected it is running on a DC and has no credentials configured for use
with Dynamic DNS registrations. Lastly, I get a Service Control Manager
error that there was a timeout waiting for the Distributed Transaction
Coordinator Service to connect, and a follow-up error stating that the Dist.
Trans Coordinator service failed to start.

The good news... once I found all of these errors, I went to perform the
chkdsk utility as you described. Previously, I had been getting this started
from the drive property screen, and going into "Error Checking". Of course,
it wouldn't run the program, but prompts to schedule upon reboot. Per your
instructions, I got out to a cmd prmpt, and when I tried to run chkdsk, it
informed me that I could not run the program because the volume was in use by
another process. It asked if I wanted to schedule it next reboot > yes > and
it seemed to run fine with no reported errors. Pretty much the same happened
when I ran the chkdsk on D.

So, maybe it is possible that my bad sector problems have been fixed? I'm
not certain though, because I have not tried to run back-up. I think the
shadow copy/VolSnap errors stemmed from a back-up request? Anyway, the disks
seem to pass the chkdsk utility just fine.

Steven, I know this is getting more and more complicated. I don't want to
waste a bunch of your time, but any thoughts or direction you could give me
would be really appreciated. Maybe if I fix this crazy credential problem,
my troubles will be solved?!?!

Have a great day!
--
Thanks,
MarkW


"Steven Zhu [MSFT]" wrote:

> Hi Mark,
>
> Thanks for posting here.
>
> From your post, my understanding on this issue is: the server unexpectedly
> shutdown and you find the hard-disk and the VolSnap error message in Event
> Viewer. If I am off base, please feel free to let me know.
>
> First of all, 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 again.
>
> From your description about the error message, I find the issue is exactly
> related with the bad block on HD. The problem could be caused by the hard
> disk failure.
>
> Could you let me know how you run the CHKDSK command to check the disk?
> Anyway, I suggest we use Chkdsk with proper parameters to check the bad
> sector again to see if the bad block still exists. Please use the following
> command:
>
> CHKDSK C: /v /f
> CHKDSK D: /v /f
>
> Is there any new error found?
>
> Please let me know the result above so that I can provide the further
> assistance on this issue. I am looking forward to your reply.
>
> Have a nice day.
>
> Best Regards,
>
> Steven Zhu
> MCSE
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ======================================================
> PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
> updated on February 14, 2006.? Please complete a re-registration process
> by entering the secure code mmpng06 when prompted. Once you have
> entered the secure code mmpng06, you will be able to update your profile
> and access the partner newsgroups.
> ======================================================
> 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.
> ======================================================
>
>
>
>
>
>
>
>
 >> Stay informed about: shadow copy / back-up problems... 

Hi Mark,

Thanks for your update.

Since the Chkdsk still could not give out the error of the hard disk, I
think we need to run a defragement of HD and see if it will help. After
defragging the server, please check the report to see if there is any error
and try to backup your server again.
In additional, I understand that you find the #50070 error message in Event
Viewer. Based on my research, this problem could be caused because the
SharePoint Timer Service failed to contact the SharePoint database while
the SBS is rebooting. In SBS 2003, the SharePoint Timer Services is used to
send notifications and performs scheduled tasks of WSS. It needs to access
the SharePoint database when starting. Since several backup exec related
services have started during the reboot, these services could cause the
SharePoint database from being mounted in a timely manner, thus, causing
the problem to occur.

I reproduced this problem in my test machine. After the MSSQL$SHAREPOINT
service has stopped, this error message will be logged in the application
log. You may now try to manually start this service to see if the problem
will still occur.

1. Start-->Run-->Type ''services.msc'' (without the quotation marks) and
press Enter.

2. In the Services console, stop the ''SharePoint Timer Services''. Check
the status of the ''MSSQL$SHAREPOINT'' service, make sure it has been
started and then restart the ''SharePoint Timer Services''. The problem
should be resolved.

If there is no problem with the manually service startup, we can set a
service dependent of the SharePoint Timer Service. Please try the following
steps:

1. Start-->Run-->Type ''Regedit'' (without the quotation marks) and press
Enter.

2. In the registry editor, navigate to the following registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer

3. Right-click the blank area in the right panel, click
''New''-->''Multi-String Value''.

4. Input the value name ''DependOnService'' (without the quotation marks)
and then double-click the newly created value. In the value data area, type
''MSSQL$SHAREPOINT'' and click ''OK''.

5. Close the registry editor and reboot the server box.

I hope the above information helps.

Have a good day.

Best Regards,

Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile
and access the partner newsgroups.
======================================================
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.
======================================================
 >> Stay informed about: shadow copy / back-up problems... 

Hi everybody,

I`ve done everything that u suggested, but still there is a problem :

Code:

Backup Status Operation: Backup Active backup destination: File Media name: "sysstate.bkf created 1/17/2008 at 5:17 PM" Volume shadow copy creation: Attempt 1. Backup (via shadow copy) of "System State" Backup set #1 on media #1 Backup description: "Set created 1/17/2008 at 5:17 PM" Media name: "sysstate.bkf created 1/17/2008 at 5:17 PM" Backup Type: Copy Backup started on 1/17/2008 at 5:18 PM. WARNING: Portions of "\Boot Files\C:\WINDOWS\system32\comsvcs.dll" cannot be read.  The backed up data is corrupt or incomplete. This file will not restore correctly. Warning: Unable to open "C:\WINDOWS\system32\comuid.dll" - skipped. Reason: The system cannot find the file specified. WARNING: Portions of "\Boot Files\C:\WINDOWS\system32\confmsp.dll" cannot be read.  The backed up data is corrupt or incomplete. This file will not restore correctly. Warning: Unable to open "C:\WINDOWS\system32\conime.exe" - skipped. Reason: The system cannot find the file specified. WARNING: Portions of "\Boot Files\C:\WINDOWS\system32\console.dll" cannot be read.  The backed up data is corrupt or incomplete. This file will not restore correctly. Warning: Unable to open "C:\WINDOWS\system32\control.exe" - skipped. Reason: The system cannot find the file specified. Warning: Unable to open "C:\WINDOWS\system32\convert.exe" - skipped. Reason: The system cannot find the file specified. Warning: Unable to open "C:\WINDOWS\system32\convmsg.dll" - skipped. Reason: The system cannot find the file specified. WARNING: Portions of "\Boot Files\C:\WINDOWS\system32\corpol.dll" cannot be read.  The backed up data is corrupt or incomplete. This file will not restore correctly. Warning: Unable to open "C:\WINDOWS\system32\country.sys" - skipped. Reason: The system cannot find the file specified. WARNING: Portions of "\Boot Files\C:\WINDOWS\system32\cprofile.exe" cannot be read.  The backed up data is corrupt or incomplete. This file will not restore correctly. WARNING: Portions of "\Boot Files\C:\WINDOWS\system32\credui.dll" cannot be read.  The backed up data is corrupt or incomplete. This file will not restore correctly. Warning: Unable to open "C:\WINDOWS\system32\crtdll.dll" - skipped. Reason: The system cannot find the file specified. ...... (a lot of strings/files) ...... Warning: Unable to open "C:\WINDOWS\system32\d3dpmesh.dll" - skipped. Reason: The specified network resource or device is no longer available. Warning: Unable to open "C:\WINDOWS\system32\d3dramp.dll" - skipped. Reason: The specified network resource or device is no longer available. Warning: Unable to open "C:\WINDOWS\system32\d3drm.dll" - skipped. Reason: The specified network resource or device is no longer available. Error: Could not access portions of directory System State\COM+ Class Registration Database. You may not have permission to open the file, or the directory may be missing or damaged. Please contact the owner or administrator. Error: Could not access portions of directory System State\Registry. You may not have permission to open the file, or the directory may be missing or damaged. Please contact the owner or administrator. Backup completed on 1/17/2008 at 5:19 PM. Directories: 273 Files: 653 Corrupt: 12 Bytes: 169,348,774 Time:  31 seconds

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

and th event log:

Code:

Event Type:   Error Event Source:   NTBackup Event Category:   None Event ID:   8001 Date:      1/17/2008 Time:      5:19:11 PM User:      N/A Computer:   SQDC Description: End Backup of 'System State' 'Warnings or errors were encountered.'     Verify:  Off     Mode:  Append     Type:  Copy   Consult the backup report for more details. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I`ve done:
1. Install SP2 for Win 2003 Server (i`ve just normal Server, not SBS)
2. All steps with msconfig, given below
3. chkdsk c: /v/f (and in addition Right Click->Tools->Error Checking)
4.have done

Code:

Cd c:\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

and i can see writers at vssadmin list writers

Want i must do in addition, plz help me ...

Thanks before ...

Steven Zhu [MSFT] wrote:

Hi Mark, Thanks for posting here. From your post, my understanding on this issue is: the server unexpectedly shutdown and you find the hard-disk and the VolSnap error message in Event Viewer. If I am off base, please feel free to let me know. First of all, 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 again. From your description about the error message, I find the issue is exactly related with the bad block on HD. The problem could be caused by the hard disk failure. Could you let me know how you run the CHKDSK command to check the disk? Anyway, I suggest we use Chkdsk with proper parameters to check the bad sector again to see if the bad block still exists. Please use the following command: CHKDSK C: /v /f CHKDSK D: /v /f Is there any new error found? Please let me know the result above so that I can provide the further assistance on this issue. I am looking forward to your reply. Have a nice day. Best Regards, Steven Zhu MCSE Microsoft Online Partner Support Get Secure! - http://www.microsoft.com/security

 >> Stay informed about: shadow copy / back-up problems...