Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 924394 - Last Review: September 22, 2006 - Revision: 2.0
You may receive an error message when you try to import a management pack by using the Microsoft Operations Manager 2005 Administrator Console
When you try to import a management pack by using the
Microsoft Operations Manager (MOM) 2005 Administrator Console, you may receive
the following error message:
Call to load data using
'Object Name' DAS object on computer 'Server Name'
failed:'0x800706be'
This problem typically occurs when you
try to import the MOM Management Pack and the Active Directory Management Pack. However, this problem may also
occur when you try to import other management packs.
The following events may be logged in the Application event log:
Event ID: 1000
Type: Error
Description: Faulting application dllhost.exe, version 5.2.3790.0, faulting module DasServer.dll, version 5.0.2911.0, fault address 0x002789e5.
Event ID: 4786
Source: COM+
Type: Error
Description: The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID:
Server Application ID: {A3124213-BAC0-48A2-9082-732BB4123C4D}
Server Application Instance ID:
{4B5BEE24-CDBE-499A-AD75-BEA5A8220D78}
Server Application Name: Microsoft Operations Manager Data Access Server
The serious nature of this error has caused the process to terminate.
Exception: C00000FD
Address: 0x00B989E5
Call Stack:
DASSER~1!DllUnregisterServer + 0x1e20be
DASSER~1!DllUnregisterServer + 0x177e96
DASSER~1!DllUnregisterServer + 0x1e761f
DASSER~1!DllUnregisterServer + 0x1bb61e
RPCRT4!NdrServerInitialize + 0x462
RPCRT4!NdrStubCall2 + 0x217
RPCRT4!NdrCStdStubBuffer2_Release + 0xd4
OLEAUT32!VariantTimeToDosDateTime + 0x1827
ole32!WdtpInterfacePointer_UserMarshal + 0x13fa
ole32!WdtpInterfacePointer_UserMarshal + 0x13ad
ole32!ProgIDFromCLSID + 0x1fd3
ole32!ProgIDFromCLSID + 0x1dd1
ole32!WdtpInterfacePointer_UserMarshal + 0x1e5f
ole32!WdtpInterfacePointer_UserMarshal + 0x116c
ole32!WdtpInterfacePointer_UserMarshal + 0x1e6f
RPCRT4!I_RpcGetBuffer + 0x1d8
RPCRT4!I_RpcGetBuffer + 0x159
RPCRT4!I_RpcGetBuffer + 0x7f
RPCRT4!NdrConformantArrayMemorySize + 0x558
RPCRT4!RpcRevertToSelfEx + 0x919
RPCRT4!RpcRevertToSelfEx + 0x6a6
RPCRT4!I_RpcBindingIsClientLocal + 0x68b
RPCRT4!NdrOleFree + 0x3c5
RPCRT4!I_RpcTransGetThreadEvent + 0x188
RPCRT4!I_RpcLogEvent + 0xe92
kernel32!GetModuleFileNameA + 0xeb
For more information, see Help and Support Center at http://support.microsoft.com.
This problem may occur if the LoggingFlags registry entry
is not set to the default value of 0.
To resolve this problem, set the LoggingFlags registry entry
in the following registry subkey to the default value of 0:
HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical
Software\DASServer\LoggingFlags
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
APPLIES TO
- Microsoft Operations Manager (MOM) 2005
| kberrmsg kbtshoot kbprb KB924394 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate