Can't access APP Builde in CP 1

[acewarlock]

I've asked this question before, but nerer got an answer that fixed the problem.

On my OTM PC connected to the company LAN I can connect to Call Pilot and then APP Builder. I used to be able to access APP Builder from my Laptop, Desktop and my Boss's desktop, Now we only access it from the OTM. I though maybe It was a LAN thing so I plugged my Laptop inthe the port the OTM was plugged into, no change, I still can't access it. I get a NOT CONNECTED TO SERVER message. Is there a setting somewhere that only alows a certen IP/MAC address to access to APP Builder? I can ping the Call Pilot from any PC.

 

[acewarlock]

Option 11C with Call Pilot 2.1 in Cab 0.

 

[janeenaj]

make sure you have the latest version of appbuilder installed. the current release of appbuilder is 4.04.04...

Its a lot more stable then the older release, don't worry about it being 4.x, its backward compatitable.

just make sure you uninstall the previous release before you install the newer one

 

[acewarlock]

But why did the old version stop working on the other PC's???????

 

[ineedtoknow]

Check out thread 798-1350603........it could be your answer

 

[yyrkroon]

on the PC where AppBuilder is installed, go to the
x:\Nortel\CallPilot\AppBuilder\uprog (where x is the drive letter on your pc where appbuilder is installed)

There should only be 2 files in the upgro folder. AppBuilderlog.txt and NMABDlauncherlog.txt. Anything else residing in this folder needs to be deleted.

All connection related issue will be in the NM...txt folder and all session related items are in the AppBui...txt folder.

See what is failing in yours.

 

[acewarlock]

I was part of that thread and it didn't help. they couldn't access it at all, I can access it but only from the PC that has OTM on it, which has nothing to do with Call Pilot, it's just that this PC works to get to the APP Builder and the other PC's don't work anymore.

 

[yyrkroon]

Open up the NMABDLauncherlog.txt file on the PC that isn't working anymore and see what it say. The log in this files will tell you at what point the failure is occuring.

 

[acewarlock]

This is what it say's on this PC.

> 05/04/07 09:25:08 Starting Application Builder in integrated mode...

 

[yyrkroon]

Integrated mode means AppBuilder was launched from the link from CPMGR instead of running the AppBuilder.exe on the PC.

If you do a mixture of both method, after a while, AppBuilder kinda gets confuse/corrupted. Only fix I know of is to uninstall, remove registry key, delete AppBuilder foler and reinstall.

AppBuilder should never be launch from the CPMGR link.

A normal sessin should look like this:

> 05/08/07 11:55:48 Starting Application Builder login...
> 05/08/07 11:55:48 NMAppBuilderLogin
> 05/08/07 11:56:00 Creating LDAP Bean object
> 05/08/07 11:56:00 Created LDAP Bean object
> 05/08/07 11:56:00 CServerConnection::Login
> 05/08/07 11:56:00 CServerConnection::GetLDAPSuffix
> 05/08/07 11:56:08 CServerConnection::GetAppBuilderVersion
> 05/08/07 11:56:08 CServerConnection::GetAppBuilderVersion. Successfully got AppBuilder version.
> 05/08/07 11:56:08 CServerConnection::GetClientIP
> 05/08/07 11:56:08 CServerConnection::GetClientIP. Successfully got client IP address.
> 05/08/07 11:56:08 Start anonymous login.
> 05/08/07 11:56:08 Start actual login.
> 05/08/07 11:56:09 Successful login for user.
> 05/08/07 11:56:09 Retrieved context ID.
> 05/08/07 11:56:10 Password successfully encoded!
> 05/08/07 11:56:10 AppBuilder launched successfully

 

[acewarlock]

This is the APPbuilder.log

Start Logging -> Log Level:3 LogInterval:0
COM libraries initialized.
COM security initialized.
WinSock Initialized
SSL Settings: Port=636, Level=0.
NMAppBuilderApp::initAppBuilder, CustID=1, ServerIP=10.1.6.9, UserID=000000, ContextID=412650296.
CLDAP::Init, ContextID: 412650296
Module: CAOS::GetLdapSuffix Code: Cannnot create AOS broker object on CallPilot server , Text:Cannnot create AOS broker object on CallPilot server
CAOS::GetLdapSuffix - config wiz client failed to connect to 10.1.6.9, hr=80004005
CLDAP::Init to retrieve LDAP suffix from AOS
NMAppBuilderApp::initAppBuilder, Failed init of LDAP server, hr=80004005.