4 Replies Latest reply on May 28, 2014 9:46 AM by simonp73

    NPM License Details page shows "Could not connect to Orion Server on "server_name," even though the polling engine is running


      Running an NPM instance at version 10.3, with three polling engines (one primary and two secondary) running Orion Core Version 2012.1.0. For whatever reason, on the "License Details" page of the primary engine, the primary polling engine shows that one of the secondary engines can not be connected to, and thus, can not retrieve licensing information:



      However, the secondary polling engine is, in fact, up and running and shows up just fine on the "Polling Engines" page of the same primary engine page:



      Any NPM users out there ever come across this sort of behavior before? I look forward to any and all feedback on the matter--thank you and good afternoon.