• State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 3151 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Quest Rapid Recovery host for MongoDB Service is not getting started afte upgrading from 6.0 to 6.2

jitendra.sharma
over 6 years ago

today i have upgraded the RR from 6.0 to 6.2 , after the upgradation Mongo DB service is not getting started. Can anyone help here

Parents
  • 0 over 6 years ago
    I had this issue a couple of times today. The issue is WMI related (the error message says something along the lines that a select * WMI statement is unable to identify the RapidRecoveryMongod service.
    you can doublecheck by running:
    get-wmiobject -namespace root/cimv2 -class win32_service -Filter "Name='RapidRecoveryMongod'"
    If you get an error it is surely WMI.
    The first thing to do is to attempt restarting WMI and see if the Mongod service starts. (You may need to restart the core service as well to clear some notifications if it does).
    If the issue is not resolved, save the WMI repository to be at peace and at a command prompt run:

    c:\ > cd C:\Windows\System32\wbem\AutoRecover
    C:\Windows\System32\wbem\AutoRecover\> for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

    to recompile most of the WMI objects.
Reply
  • 0 over 6 years ago
    I had this issue a couple of times today. The issue is WMI related (the error message says something along the lines that a select * WMI statement is unable to identify the RapidRecoveryMongod service.
    you can doublecheck by running:
    get-wmiobject -namespace root/cimv2 -class win32_service -Filter "Name='RapidRecoveryMongod'"
    If you get an error it is surely WMI.
    The first thing to do is to attempt restarting WMI and see if the Mongod service starts. (You may need to restart the core service as well to clear some notifications if it does).
    If the issue is not resolved, save the WMI repository to be at peace and at a command prompt run:

    c:\ > cd C:\Windows\System32\wbem\AutoRecover
    C:\Windows\System32\wbem\AutoRecover\> for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

    to recompile most of the WMI objects.
Children
No Data