AndyMT

Comments

  • I have seen this multiple times too.. removing and readding the Orion NPMs sometime fixed it and sometimes I had to do a configuration wizard again on the NPM and EOC.. Seems buggy..
  • It appears that a running the database configuration over again solved the problem.. will monitor for a while but it looks fixed..
  • I am also now getting the same error after upgrade.. Unhandled Exception caught in NPM Service Engine startup. Invalid column name 'BusinessLayerPort'. So what is the fix for this? I will try to do a database repair and everyone know if that works out
  • We have a virtualization project underway and this type of monitoring would be very beneficial but I am not as concerned about the traffic between machines as our machines VMotion all over the place this data would be irrelavent but the vCPU and vMemory and other Host/Guest machine specific information would be much more…
  • I too ran into the impersonate issue. I think I had old documentation also. Just make sure it is set to false and everything works fine
  • I just did my install today on v8.5.1 SP3 --> 9.0 SP1. It went pretty smooth but I did also run into a few weird problems. First I was not being able to contact the license server after upgrade but I got around that by just skipping and entering the key manually I then ran into this weird problem.. After rerunning the…
  • In the end nothng seemed to fix it except a complete reinstall. This fixed the seeing the reports and also I can now clear the events. Not only did I reinstall the EOC I reinstalled the Orion NPM.
  • We run two of 4 NPMs in Virtual Machine format on VMWare ESX and you can hardly tell the difference. Best part about the VMWare VMs are that if we want to do patching or upgrade you can snapshot, do the upgrade and if something breaks you can roll back really easily and no harm done (might lose some statistic history but…
  • How do I open a support ticket? I havn't done it before..
  • I had a similar issue but I did not modify my database directly as mentioned by a previous post. It has just been running stock since the upgrade from 1.0 to 1.1. I had to restart each and every service one at a time till things started working. I have no idea what is wrong but it is much less stable since the v1.1 upgrade…
  • I ran into this much earlier on.. from what I can tell Orion links a VM to an ESX host by way of the monitored NIC. So they don't know the linking between the VM and the Orion Node unless you are also monitoring the vNIC inside the VM. Orion is assuming without this link that the node is not monitored and asks you to add…