Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Stuck SQL Server Replication Creation

38 views
Skip to first unread message

Robert

unread,
Nov 28, 2009, 11:38:01 AM11/28/09
to
Hi,

I'm using DPM 2007 Sp1, latest hotfix package from october installed. I
have one protected server (windows 2008 r2 with sql server 2008), where most
of the databases are backing up okay but I have problems with the replica
creation and any consistency check getting "stuck" for both the C:, F: and G:
drives on the server and 5 databases ONLY. The other drive H: and the other
databases (about 10) create the replica and appear to backup up fine.

What happens is that it appears that the replica creation transfers a small
amount of data, 1-25MB and then just hangs for hours and never completes.

To troubleshoot I actually completely rebuilt the windows 2008 r2 server
that is being protected from scratch but it didnt help.

Additionally I have tried protecting the server on two different DPM servers
and both encounter this issue.

I just recreated the protection for one database to try to troubleshoot. On
the protected server event log I see a SQL Server entry indicating a backup
was performed successfully for the database. There are no further log
entires on either the Protected Server or DPM Server.

On the protected server, here are the entries from the dpm agent log that
appear to be related to this job.

|TaskID=955CDE56-5623-49B0-9BBF-2DB407CB3A5E FindFirstVolumeMountPoint
failed for [\\?\Volume{285691ce-dbae-11de-9674-806e6f6e6963}\] hr [0x80070012]
0B90 12EC 11/28 16:27:48.304 67 mountpointutil.cpp(126) |TaskID=955CDE56-5623-49B0-9BBF-2DB407CB3A5E FindFirstVolumeMountPoint
failed for [\\?\Volume{285691cf-dbae-11de-9674-806e6f6e6963}\] hr [0x80070012]
0B90 12EC 11/28 16:27:48.304 67 mountpointutil.cpp(126) |TaskID=955CDE56-5623-49B0-9BBF-2DB407CB3A5E FindFirstVolumeMountPoint
failed for [\\?\Volume{285691d0-dbae-11de-9674-806e6f6e6963}\] hr [0x80070012]
0B90 12EC 11/28 16:27:48.304 67 mountpointutil.cpp(126) |TaskID=955CDE56-5623-49B0-9BBF-2DB407CB3A5E FindFirstVolumeMountPoint
failed for [\\?\Volume{285691d1-dbae-11de-9674-806e6f6e6963}\] hr [0x80070012]
0B90 12EC 11/28 16:27:49.141 67 mountpointutil.cpp(126) |TaskID=955CDE56-5623-49B0-9BBF-2DB407CB3A5E FindFirstVolumeMountPoint
failed for [\\?\Volume{285691ce-dbae-11de-9674-806e6f6e6963}\] hr [0x80070012]
0B90 12EC 11/28 16:27:49.147 67 mountpointutil.cpp(126) |TaskID=955CDE56-5623-49B0-9BBF-2DB407CB3A5E FindFirstVolumeMountPoint
failed for [\\?\Volume{285691ce-dbae-11de-9674-806e6f6e6963}\] hr [0x80070012]
0B90 12EC 11/28 16:27:49.789 26 agentutils.cpp(1766) |TaskID=955CDE56-5623-49B0-9BBF-2DB407CB3A5E Failed:
Could not get the value of registry key name CopyBackupEnabled under
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection
Manager\Agent\2.0 , hr = 80070002: 0x80070002
0B90 10D4 11/28 16:27:50.903 22 fsutils.cpp(3624) |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 Failed: G: lVal : HRESULT_FROM_WIN32(dwError): 0x80070002
0B90 10D4 11/28 16:27:50.903 22 fsutils.cpp(2111) |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 Failed:
Invalid filespec:Datasources\PSExchangeDatasourceConfig.xml: 0x80990a52
0B90 10D4 11/28 16:27:50.903 26 agentutils.cpp(1676) |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 Failed:
Could not get the value of registry key name
SharePointSearchEnumerationEnabled under
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection
Manager\Agent\2.0 , hr = 80070002: 0x80070002
0B90 10D4 11/28 16:27:50.996 26 wmiqueryhelper.cpp(105) [000000000369E7 |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 Failed:
unable to connect to the wmi namespace:
root\Microsoft\SqlServer\ComputerManagement: 0x8004100e
0B90 10D4 11/28 16:27:51.080 22 fsutils.cpp(3624) |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 Failed: G: lVal : HRESULT_FROM_WIN32(dwError): 0x80070002
0B90 10D4 11/28 16:27:51.080 22 fsutils.cpp(2111) |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 Failed:
Invalid filespec:Datasources\PSExchangeDatasourceConfig.xml: 0x80990a52
0B90 10EC 11/28 16:27:51.533 24 cc_extcalls.cpp(517) [0000000008B155 |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 DM: TempErr: err=0x4d4 read=1 write=0
0B90 10EC 11/28 16:27:51.535 24 cc_extcalls.cpp(517) [0000000008B155 |TaskID=410F7264-CDA5-4806-AEF1-1F1CF9BF1F39 DM: TempErr: err=0x3e3 re

Hitesh Sharma[MSFT]

unread,
Nov 30, 2009, 2:37:37 AM11/30/09
to
Hi,

From the error logs that you have pasted one of the issues could be corrupt
WMI.

Can you please run a quick check? Start 'wbemtest' from command prompt.
Click 'Connect' and type the following -
'root\Microsoft\SqlServer\ComputerManagement'. In query type - 'Select *
from serversettings'. Does this work? If not the WMI registry needs repair.


Thanks,
Hitesh Sharma [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights.

Use of included script samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm
"Robert" <rob...@noemail.nospam> wrote in message
news:0B1D8CC4-37EA-4CE3...@microsoft.com...

Robert

unread,
Dec 1, 2009, 12:15:01 AM12/1/09
to
I tried the below and receive an error "invalid namespace" when I enter:

root\Microsoft\SqlServer\ComputerManagement

If I enter just the below, I am able to at least connect

root\Microsoft\SqlServer

But "ComputerManagement" appears to not exist.

"Hitesh Sharma[MSFT]" wrote:

> .
>

Robert

unread,
Dec 1, 2009, 12:17:01 AM12/1/09
to
Just did a search and found the below:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=352098

Apparently the correct namespace for SQL Svr 2008 is "ComputerManagement10".

Tried that and it works, can connect.

Robert

unread,
Dec 1, 2009, 1:33:01 PM12/1/09
to
For other people's reference, I was able to resolve this issue it appears by
turning on throttling on all agents and setting it for 85 mbps.

Apparently the network connection on the dpm server and/or protected server
was saturated thereby preventing dpm agent control messages to flow timely.

This resulted in the errors.

Once I turned on throttling, all of the jobs for the server in question
worked successfully.

0 new messages