Not able to connect to AOS server

[dhananjayak]

We have a 11C Rls 4.5 with Call Pilot 201i Rls 4. We configured the Application builder CP404S03G02A, and loaded the latest patches in Call pilot. While trying to open application builder it says unable to connect to aos server.We done the reinstallation of call pilot. Still we are getting the same issue.

1) Checked the dcomcnfg
2) loaded the latest patches
NM010709G093C,
CP40404SU02S,S02G04C,2G09S,2G10S,2G11S,2G19S,2G20S,2G211S,2G26S,2G26S,EC004S.

 

[unkalary]

You cannot run Application Builder from the CallPilot server. You must install the App Builder on a seperate PC in order to access any applications or build any applications. YOU CANNOT run app builder that is on the Callpilot Manager home screen. You have to treat it like any other piece of software on a PC and insall it as an application.

 

[dhananjayak]

Dear I loaded the app builder in a client system on the same LAN (I missed to mention), I tried to open it on the system and I connected a laptop though Cross cable connected to call pilot. I am unable to open.

Thanks...

 

[MagnaRGP]

connected a laptop though Cross cable connected to call pilot."

Install App builder on the laptop. Click on the link to app builder when you are logged into the CP manager. That will cause app builder ON THE LAPTOP to launch.

 

[dhananjayak]

Dear We already tried by connecting the laptop through cross over cable.

 

[RS528]

Try this:
There is missing DCOM information in the CallPilot Server registry HKEY_LOCAL_MACHINE\Software\Microsoft\OLE.




Problem Resolution

Fix:
Apply Primus solution NORT047842 - Unable to connect to server with AppBuilder, MyCallPilot or CallPilot Manager: (Refer to solution: NORT047842-Unable to connect to server with AppBuilder, MyCallPilot or CallPilot Manager. )

1. Download EnableDCOM.reg from the Enterprise Solutions PEP Library (ESPL) at

http://www.nortel.com/espl.

Go to Multimedia PEP Tools > Product: CallPilot / Plarform:Server / Release: 03.03.06 and select 'EnableDCOM'

2. Double-click on the file to add the registry entry that was removed by pcAnywhere.

Note: The same error may occur because DCOM was denied on the Application Builder PC. Apply Primus Solution NORT059140 (Refer to solution: NORT059140-Cannot connect to AOS server.).

 

[RS528]

Maybe your DCOM on the client PC is turned of.

Turn on DCOM as per the following steps (ON CLIENT PC):

1) Bring up command line window: Start -> Run ->CMD

2) Type in "dcomcnfg" without quote.
The "Distributed COM Configuration Properties" window will appear.

3) Click on TAB "Default Properties".

4) Check "Enable Distributed COM on this computer".

5) Click APPLY
No reboot needed.

 

[dhananjayak]

Dear,

We checked the following, all the configurations was the same in client and Call Pilot 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.

*2.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.

*3.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.

*4.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.

In the document we found the TCP,UDP ports 20,5000 for FTP should be opened. While checking the ports details enabled in call Pilot we found these ports are not enabled.

Please confirm.

 

[thattekguy]

I am having the same problem and been thru all the same exact steps. Is your elan going thru any type of new ethernet switching equipment?I think my problem is my new nortel 470-24 poe switch,I think it is blocking port 135.I will let you know what's up when I get it fixed.

 

[dhananjayak]

Dear,

After enabling the anonymous login it's working fine. I followed this procedures for the same. Now issue was close. Thanks....


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. Attempted access to Application Builder-successful. Requested Tom attempt to access-successful. Tom approved closure as NNA as having to readd Anon Logon acct manually.