Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

callpilot 5.0 202i , AppBuilder Login Problem

Status
Not open for further replies.

LittleMaster

Technical User
Sep 16, 2015
182
PK
Hello All.
working on the newly installed Avaya call pilot...202i
Facing Login Problem through Appbuilder application from the client side. done all the setting for DCOM according to the procedure at both server and client side, But still it is giving the LDAP error at login page..

expert opinion please
 
I have these two reports below. I'm not sure if it is the same problem?.

Unable to connect to AOS with application builder

Verify the following TCP and UDP ports are enabled:

TCP port 20 (FTP)
TCP port 21 (FTP)
TCP port 135 (DCOM)
UDP port 135 (DCOM)
TCP port 143 (IMAP)
TCP port 389 (LDAP)
TCP port 636 (LDAP)
TCP port 993 (IMAP)
TCP ports 1024 to 65535 (DCOM)
UDP ports 1024 to 65535 (DCOM)

Not able to connect to AOS server

1. Select start > run > dcomcnfg
2. Select component services > computers > my computer
3. Right-click and select properties
4. Select the General tab and make sure the check box ' *enable DCOM on this computer'* is checked
5. Select the default protocols tab and make sure ' *Connection Oriented TCP/IP*' is selected and is on top of the list.
6. Click Apply and exit out of the dcomcnfg utility.
7. Restart the client pc.


Check the following AOS DCOM permissions are correct:*
1. Open Start->Administrative Tools->Component Service.
2. On the left pane of Component Services go to Component Services->Computers->My Computer->DCOM Config->nmaos.
3. Open Security tab in nmaos properties.
4. Under Launch and Activation Permissions click Customize and then click Edit button.
5. Make sure that ANONYMOUS LOGON group has Local Launch, Local Activation and Remote Activation permissions granted.
6. If not, then add ANONYMOUS LOGON group with Local Launch, Local Activation and Remote Activation permissions granted.
7. If not, correct and reboot.


Check ANONYMOUS LOGON group is permitted*
1. Go to Start -> Programs -> Administrative Tools -> Local Security Policy.
2. On the left pane select Security Settings -> Local Policies -> Security Options.
3. On the right pane find 'DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax' line and double click on it.
4. Click Edit Security. Launch Permission window will appear.
5. Make sure that ANONYMOUS LOGON group is granted with Local Launch and Remote Activation permissions. Grant them if necessary by selecting Add, Advanced, Find Now, and double clicking on ANONYMOUS LOGIN, then save your changes.
6. Reboot is not required.


Check the following to get AOS to start in order to login to CPMGR:
1. Run regedit.
2. Under HKKEY_LOCAL_MACHINE->SOFTWARE->NORTEL-> MPCX->NMLDAPSRV.
3. Set EnableLoginAuth to yes.
4. Set EnableCRAuth to yes.
5. Exit regedit.
6. Reboot CP server

#######################################################

Invalid Credentials when tying to Login to My Callpilot.

Callpilot 5

Invalid Credentials when tying to Login to My Callpilot.

The LDAP Search Base in the Configuration Settings in MyCallpilot did not match the LDAP Search base in Callpilot Manager Configuration Wizard.

#######################################################



Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support
 
bundle of thanks firebird for such a good reply..
these all settings were already checked but the issue was that I was using an old version of applications builder... I just installed the latest version of app builder and everything is working fine ..thanks for your expertise
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top