iManager 2.7, IDM 3.5.1 - Driver's Unknown State

Celso G. Lima wrote:

> I upgraded an IDM Server from 3.5 to 3.5.1 and also the iManager 2.6
> running on the same server to version 2.7. My tree has 2 servers and
> they both had IDM 3.5 installed on them. I first updated the
> metadirectory on both servers, then I removed iManager 2.6 and
> installed version 2.7 from scratch on server 1 (master). Only after
> that I installed the IDM 3.5.1 plug-ins. I restarted nds after I had
> installed metadirectory and restarted tomcat after I installed the
> IDM 3.5.1 plug-ins. When I logged into iManager after I installed the
> plug-ins, iManager showed all my driver in unknown state. I
> uninstalled iManager and reinstalled it a couple of times on the same
> server and got the same result. I then decided to use another
> instance of iManager 2.7 I had on another server/tree to connect to
> this tree I was having problems, and the drivers showed up as they
> were expected (stopped/running). No unknown state issue. I didn't
> know if it was something wrong with the tree, so I removed IDM from
> the second server (I had not configured it yet), and installed
> iManager on the second server (replica). I was able to get a fully
> working install of iManager 2.7 on the second server.
>
> Does anybody know what could have gone wrong with iManager on the
> master replica? Did I miss something, during the upgrades?

Unfortunately sometimes it just happens that the iManager plugins can't
determine what state the driver is in. What I do in those cases is
change the drivers from auto start to manual start, restart the DS and
start the manually. Not always possible though as certain customers
can't take their servers down.

--
Cheers,
Edward