While Upgrading from NEC AD-120 2.3 to 2.4 software I recieved 4 seperate errors. All 4 had the following error content w/ seperate headers:<br> The procedure entry point NdiDuplicateNRB could not be located in the dynamic link library NDI.DLL.<br> The 4 headers read:<br>1) Tapisrv.exe entry point not found<br>2) LFDriver.exe entry point not found<br>3) LFmon.exe entry point not found<br>4) MCI command handling window: winlogon.exe entry point not found<br><br>Please advise.<br><br>
The NDI.DLL file is one of Dialogic's system files, though I'm not entirely sure what function it serves.
You can try uninstalling and reinstalling just the Dialogic component (either through our setup or straight through their setup off CD #2 of the set), but if that doesn't work you've got some DLL or another (it may not actually be the NDI.DLL iteself) that's not in a happy state and isn't getting oveverwritten/uninstalled by the Dialogic setup.
The best I can suggest if that doesn't work is to wipe the box clean and reinstall, install on another box or try and get Dialogic involved (good luck on that one).
I have an Export/Import tool in use at a couple sites that can help capture all your users/handlers etc... so you don't have to reconfigure the box from the ground up if you want to try it here (assuming you end up having to wipe the slate clean).
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...