[condor]

PROBLEMS:
BES 4.1.4 not connecting to GW 7.0.3 BES Address book will not sync with GroupWise System Address book. Cannot find GW user in BES Manager.


SOLUTION:
I tried so many things. I continued getting those " Err=Directory Services Data missing " errors. (See Error Symptoms below)

While I was installing win 2003 on another machine to create a whole new BES srv from scratch, I tried 1 last thing. I created a new GW Trusted App and put the new KEY into BES. But this time, I ran the Key Generation program from my XP machine instead of running it right on the BES server. I noticed that the APP NAME in the BES Config Server (on the GroupWise Settings Tab where the Key is located) did not match with the Name for my new GW Trusted App (as seen in ConsoleOne). So I changed it in BES to match what was in GroupWise. WHAM/BAM-- BES started talking to GW instantly!

CONCLUSION:
I believe it was the NAME that caused all my problems. I don't believe that generating a trusted Key from my xp machine instead of a win 2003 srv would make a diff. I don't think it was a new Key that did the trick, I had tried a new key once before.

My efforts to reproduce the problem by simply changing the App NAME in BES server Config have failed so far; HOld on... its confirmed I broke it again! The BES logs did not start reporting errors until I had completely rebooted the server. The POA logs did show the errors right after I changed the NAME. That's weird. All 3 log files now show the original errors again (see below) I reset the NAME in BES Config back again so it matches GW. It works AGAIN!




ENVIRONMENT:
BES server has GW 7.03 client installed
Novell GW server is 7.03
In GW Server, the trusted Application Name = RIM BES (default name from the Generation program)
BES server config = App name = BES




ERROR SYMPTOMS:
BES's ADMIN_GWCO log file:
[34157] (07/16 19:18:11):{0x1E60} {GWCO} {GWConnector} Novell GroupWiseObject Library: C:\Novell\GroupWise\\gwcma1.dll, Version: 7.0.3
[34493] (07/16 19:18:11):{0x1E60} {GWCO} {GWConnector} GWConnector Version: 4.1.4.15
[34481] (07/16 19:18:11):{0x1E60} {GWCO} {GWConnector} GW API Mode=GW_SOAP
[34154] (07/16 19:18:11):{0x1E60} {GWCO} {GWConnector} Mailstore test start, test level=1
[34116] (07/16 19:18:12):{0x1E60} {GWCO} {srv-bes} Login: Start
[14123] (07/16 19:18:12):{0x1E60} {GWCO} {} MultiLogin failed, error=System.Runtime.InteropServices.COMException (0x80004005): Login unsuccessful
at System.RuntimeType.ForwardCallToInvokeMember(Strin g memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at GroupwareTypeLibrary.DIGWSession4.MultiLogin(Strin g vUserID, Object vCommandLine, Object vPassword, Object vWhenToPrompt, Object vReserved)
at ConnectorLibrary.ICEWrapper.AccountLogin(String& sUserID, String& sDomain, String& sPOA, String& sFID3)
[14047] (07/16 19:18:12):{0x1E60} {GWCO} {srv-bes} Login Failed, Username=srv-bes
[34045] (07/16 19:18:12):{0x1E60} {GWCO} {srv-bes} Logout admin user
[14095] (07/16 19:18:12):{0x1E60} {GWCO} {GWConnector} Mailstore test failed


BES's ADMIN_GWSC log file:
[34480] (07/16 19:18:11):{0x1EA0} {GWSC} {GWSoapConnector} GW API Mode=GW_SOAP
[34480] (07/16 19:18:11):{0x1EA0} {GWSC} {GWSoapConnector} SSL=OPTIONAL
[34483] (07/16 19:18:11):{0x183C} {BESMgmt} {GWSoapConnector} Begin BESMgmt Thread
[34154] (07/16 19:18:11):{0x1EA0} {GWSC} {GWSoapConnector} Mailstore test start, test level=1
[34116] (07/16 19:18:11):{0x1EA0} {GWSC} {srv-bes} Login: Start
[14047] (07/16 19:18:15):{0x1EA0} {GWSC} {srv-bes} Login Failed: Err=Directory Services Data missing, UserName=srv-bes
[34045] (07/16 19:18:15):{0x1EA0} {GWSC} {srv-bes} Logout admin user
[14095] (07/16 19:18:15):{0x1EA0} {GWSC} {GWSoapConnector} Mailstore test failed

GroupWise's POA log file (verbose mode)
19:18:11 343 C/S Login Windows ::GW Id=srv-bes :: 10.0.1.4 Trusted App=BES
19:18:12 343 Error: Directory Services Data missing [D105] User:srv-bes App( BES )

[vonkleist]

Hi.

Same problem over here. I re-created the trusted application key, on a XP machine, with no luck.

I see you are using a srv-bes account. So, is your blackberry-groupwise configured using that account, and not the admin one? How did you got access to the wpdomain.db directory?

[svandamme]

It does not matter where you run the trusted key generator

it does matter what the application name is

The key and app name are set in the GW DB
you should check the actual value in C1

that's the combination you need to configure your BES with

[vonkleist]

Well... I've tried several dozens of ways, with no luck.

Whenever I run some of the BES utilies, I get always the same error:
"MultiLogin failed, error=System.Runtime.InteropServices.COMException (0x80004005): Login unsuccessful
at System.RuntimeType.ForwardCallToInvokeMember(Strin g memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at GroupwareTypeLibrary.DIGWSession4.MultiLogin(Strin g vUserID, Object vCommandLine, Object vPassword, Object vWhenToPrompt, Object vReserved)
at ConnectorLibrary.ICEWrapper.AccountLogin(String& sUserID, String& sDomain, String& sPOA, String& sFID3)"

I've created several trusted app keys, and used the corresponding App Name and key. No luck.

My scenario is:
- Groupwise 7 on SLES10
- Generated the keys on W2003 and XP
- Verified app names and keys
- Accounts used for the admin user in BES config already in PO
- Logging in to the SLES10 server through SLES samba, logged in also using Novell Client.

Any idea?

[vonkleist]

By the way, I'm not using OES... Just in case it's important...

[knoogle]

I seem to remember having that same issue when I first installed BES. If I recall, you have to log into the admin user through Groupwise at least once. On a workstation, just exit notify and Groupwise, then start the Client with a /u-? it should prompt you with login credentials. Login as your Admin user and then reboot the BES, it should work.

Hope that helps....