Problem 1
Unable to connect to AOS with application builder
Answer 1
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
#######################################
Problem 2
Callpilot Application Builder.
'The system could not load the application from the server' seen when trying to open an application.
Answer 2
On Callpilot Application Builder, 'The system could not load the application from the server' is seen when trying to open an application. This happens because when an application is loaded in Application builder 2 files are copied into the C:\Nortel\Callpilot\Appbuilder\Uprog (or C:\Avaya\CallPilot\AppBuilder\uprog) folder. If the user does not have the right to write files into this folder then the error message will be seen. This is commonly seen where the user does not have Admin rights on the PC.
There are a number of ways around this problem;
1. Give the user the rights to write to C:\Nortel\Callpilot\Appbuilder\Uprog. This must be done within the Windows File system by right clicking on the Uprog folder and selecting Properties and Security tab. This should be left to the customer to arrange.
2. Install Appbuilder to a folder that the user has Write rights to. This is a customisable option when doing the Appbuilder install so it will be necessary to uninstall then re-install Appbuilder.
3. Change HKLM\software\Nortel\Callpilot\Appbuilder\progdir to a folder that the user has Write rights to (although this would be a non-standard installation so is not to be recommended
Firebird Scrambler
Nortel and Avaya Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Very advance high level knowledge on Linux BCM with keycode support
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.