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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CALL PILOT
- Thread starter JcBWF
- Start date
There are several different causes for this error. If you have access to Nortel's Knowledge Base and enter that error, it will throw out several solutions. I can tell you one of them off the top of my head:
If you are trying to access AppBuilder by clicking on the link within CallPilot Manager, stop that method. Go to Start, Programs, and access AppBuilder directly from the program you installed on your PC.
Another solution is to check the DCOM settings on your PC. I would have to look for that solution as I don't remember it off the top of my head.
War Eagle!
Lions Baseball '09!
If you are trying to access AppBuilder by clicking on the link within CallPilot Manager, stop that method. Go to Start, Programs, and access AppBuilder directly from the program you installed on your PC.
Another solution is to check the DCOM settings on your PC. I would have to look for that solution as I don't remember it off the top of my head.
War Eagle!
Lions Baseball '09!
Jeffnortel
Vendor
I've had the same problem recently, ended up being a networking issue in the cust network. Callpilot server was in a vlan and a pc on the cust domain received this error.
Firebird Scrambler
Systems Engineer
Problem
Call Pilot - Application Builder (app builder)
fails to connect to Call Pilot server
with a error message: could not connect to aos server
Solution
DCOM turned off on client PC
Full solution details below
Windows 2000
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 required, but if it doesn't work 1st time, try again after a reboot!!
Windows XP
1) Click Start menu, and then click the Run icon.
2) In the small box that Opens, type: Dcomcnfg.exe then click the OK button. Now the Component Services window should open.
3) In the left hand pane "Expand" Component Services.
4) Right-click Computer and select Properties.
5) Select the Default Properties tab.
6) Enable Distributed COM on this Computer box.
7) Click the Apply button to enable DCOM.
8) Click the Default authentication button and select connect.
9) Shutdown and Restart your computer.
All the best
Firebird Scrambler
Meridian Programmer in the UK
If it's working, then leave it alone!.
Call Pilot - Application Builder (app builder)
fails to connect to Call Pilot server
with a error message: could not connect to aos server
Solution
DCOM turned off on client PC
Full solution details below
Windows 2000
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 required, but if it doesn't work 1st time, try again after a reboot!!
Windows XP
1) Click Start menu, and then click the Run icon.
2) In the small box that Opens, type: Dcomcnfg.exe then click the OK button. Now the Component Services window should open.
3) In the left hand pane "Expand" Component Services.
4) Right-click Computer and select Properties.
5) Select the Default Properties tab.
6) Enable Distributed COM on this Computer box.
7) Click the Apply button to enable DCOM.
8) Click the Default authentication button and select connect.
9) Shutdown and Restart your computer.
All the best
Firebird Scrambler
Meridian Programmer in the UK
If it's working, then leave it alone!.
- Status
Similar threads
- Locked
- Question