Environment
Novell Identity Manager 3.0
Nsure Identity Manager 2.x
Novell NetWare 6.5
Nsure Identity Manager 2.x
Novell NetWare 6.5
Situation
Unable to start IDM driver after running DSRepair
After running DSRepair, the IDM driver will not start and the error '670 ERR_INVALID_CONTEXT' is seen in the trace
After running DSRepair, the IDM driver will not start and the error '670 ERR_INVALID_CONTEXT' is seen in the trace
Resolution
To work around the problem, unload DIRXML.NLM followed by JCLNTR.NLM before running DSRepair. If you are running iManager on the box you may need to stop tomcat as well before you can unload JCLNTR.NLM.
This issue is addressed in the eDirectory 8.7.3.10 build.
This issue is addressed in the eDirectory 8.7.3.10 build.
Additional Information
This appears to be a JClient defect. JClient tries to keep track of when DS unloads so it can consider any existing contexts to be invalid. The method that it is using to detect when DS unloads is flawed because it only looks up the module handle for DS when it is first initialized and the module handle can get reused by a different module and then trigger JClient to think that DS unloaded again. As such the problem is very random. It is only a problem for JClient on NetWare, but it appears to be in every version of JClient ever shipped on that platform. On NetWare, JClient ships as a part of eDirectory.
It has also been confirmed that stopping and starting DIRXML.NLM after running DSRepair works around the issue.
Formerly known as TID# 10100237
It has also been confirmed that stopping and starting DIRXML.NLM after running DSRepair works around the issue.
Formerly known as TID# 10100237