Re: NPM failed few times, with error mesasge

I experienced this problem after updating SAM--from 6.1 to 6.1.1--and after 2.5 days, I was able to isolate, reproduce, fix, reproduce, fix, etc. These are a few of my lessons-learned, if you will. (NOTE: This is running in a virtualized environment and the operating system is Win2012 R2.):

• Ensure that UAC is disabled. (NOTE: This step is critical!)
• Reboot machine--on ORION, not the supporting machines--such as, NTA dB, Orion supporting dB, other Linux VMs, etc.
• Start Orion Service Manager on the Orion server.
  • Click "Shutdown Everything."
  • Ensure every "Service" reports "Stopped."
• Delete (or rename) the .sdf files under:
  • ..\ProgramData\SolarWinds\JobEngine\Data\
  • ..\ProgramData\SolarWinds\JobEngine.v2\Data\
• Copy the blank .sdf files and rename each file to
  • "JobEngine35.sdf" within each respective directory
    • ..\ProgramData\SolarWinds\JobEngine\Data\
    • ..\ProgramData\SolarWinds\JobEngine.v2\Data\
• Ensure that each .sdf file's property is set to "Read-only" (right-click each .sdf file and select Properties and 'tick' the "Read-only" property--if the "Read-only" Property (checkbox) is 'ticked' (checked/selected). (Ultimately, you want the "Read-only" checkbox 'un-ticked'.)
• Start Orion Configuration Wizard.
  • 'Tick' (select) each option: "Website", "Database", "Services."
  • Run through the Wizard and accept the default selections already made available to you.
  • NOTE: The Wizard takes some time to run; it is okay.
• Return to (or re-start, if you previously closed) Orion Service Manager.
  • Ensure every "Service" reports "Running."
• Note: It may take 18 hours for the service to continuously run successfully--in that, the Orion Web Console runs as expected. (NOTE: You may see the "SolarWinds Orion Module Engine" automatically switch from "Running" to "Stopped" and then automatically restart the "Service" and it switches to "Running." As this process occurs, the Orion Web Console will appear intermittent; at least in my case, this was normal for 15 hours.
• I was able to re-create the problem; fix it; intentionally break it; and fix it again; so-on and so-forth. I do not know why it required 15 hours to finally stay in the "Running" state, but I wonder if it is due to the SAM dB, Orion dB, etc.--in that, these services must run and doing so, corrects the configuration information, etc., but this is merely a guess out of left field--way out in left field. I hope others know better than me.

Good luck everyone!