Hello Folks,

I have just installed BES Express 4.1 on my SBS2003 Standard system, and have been working through numerous problems. To make a long story short, my one Blackberry 7105t is working quite well on the system, but since this a test prior to rolling out several similar systems in the near future, I am concerned about several problems.

First, the Application Event Log on the server continues to generate Blackberry Policy Service errors, referring to BIPPeClient Error calling host "localhost" [127.0.0.1]. I am also getting what appear to be related messages on ExchangeConnector and Blackberry Synchronization Service - BIPP Connection Failed. These errors occur several times an hour.

Second, I was unable to successfully perform wireless activation - the Blackberry would hang each time at "Waiting for Services", eventually timing out. I managed to get the handheld activated via a USB cable, and email send/receive and wireless calendar sync is working great now.

Note that I have carefully reviewed and implemented the pages of documentation about setting up the BESAdmin service account and working around the Microsoft Exchange Send As permission problems (lots of special SBS lessons learned there). I worked with Blackberry tech support early on, and really did not receive knowledgeable support from them. I was told that the Application Event log errors were caused by the server being multi-homed. After that, I even reconfigured the server to single-homed, completely removed and reinstalled BES, but the same problems still exist.

Can any gurus with experience installing BES on SBS 2003 provide some pointers to what may be wrong?


Thanks

Andy Williams

BES on Exchange server bad....there's lots of different MAPI errors that could come up from that.

There is a KB at RIM that describes installing BES on SBS 2000, but I couldn't find anything on SBS 2003 (looked the other day for someone else).

Have you ever done a ping to a host and got 1 of 4 replies of "request timed out"? These BIPP messages are similar to that. As long as your server is connected, you should not have to worry about them.

As for the activation, a restart of the BB Sync and policy service's should have resolved that.

Zro

I've not had any MAPI problems on SBS 2003. As mentioned, other than the Application Event Log errors and not being able to complete a wireless activation, everything is working well. I have applied the fix mentioned in the only SBS 2003 article on RIM's KB regarding localhost errors I but it did not help my situation.

I have restarted the sync and policy services, and have restarted the server several times, but still cannot complete wireless activation. I feel sure this is related to the App Log connection errors.

I believe I am having the same problem as described above.

Recieve the following error in the Event log:

Event Type: Warning
Event Source: ExchangeConnector
Event Category: None
Event ID: 20000
Date: 8/4/2006
Time: 9:35:29 AM
User: N/A
Computer: XXXXXXXXX
Description:
[BIPP] Connection failed

Even more interesting data:

[30000] (09:50:51):{0x0F08} [DIAG] EVENT=Register_thread, THREADID=0xF08, THREAD
NAME="BIPPe_ClientReceiver"
[30156] (09:50:51):{0x1F40} [BIPPe] Connection established
[30155] (09:50:51):{0x1F40} [BIPPe] Connection dropped, Error=0
[30000] (09:50:51):{0x0F08} [DIAG] EVENT=Unregister_thread, THREADID=0xF08, THRE
ADNAME="BIPPe_ClientReceiver"
[20000] (09:50:51):{0x1F40} BIPPeClient::Connect: Error calling host "localhost"
[127.0.0.1] (0)
[20000] (09:51:00):{0x1F40} BIPPeClient::Connect: Error calling host "localhost"
[127.0.0.1] (0)
[20000] (09:51:00):{0x1F40} [BIPP] Connection failed

Any help will be greatly apprecitated. Or even how to ignore these errors in the SBS 2003 error logs.

Look in the BES logs (MAGT log file) for the cdo and mapi lines.

[30000] (10/02 07:56:57.537):{0x17AC} [ENV] MAPI32.DLL: C:\WINDOWS\system32\MAPI32.dll, Version: 6.5.7638.1

[30000] (10/02 07:56:57.537):{0x17AC} [ENV] CDO.DLL: C:\WINDOWS\system32\cdo.dll, Version: 6.5.7638.2

Check to make sure those versions match the versions Exchange is using.
(C:\Program Files\Exchsrvr\bin -for me)
If not, get the versions and register them (regsvr32 cdo.dll from the folder with the file).
Restart the BES and see if the messages go away.
Always re-check the log file to make sure it's pulling the correct version of the file from the location you think it should be.
The times I've seen those messages, it was due to version differences between the BES and Exchange files.

Steve

Hello, can you tell me how to find the KB you mentioned?
I am installing on a SBS 2000, or at least testing the install, and could not find the KB you mentioned.

Matt

Steve,

I just setup a BES to work with our exchange server and this was exactly my problem. I figured out that I used the Exchange 2003 CD to install the System Manager software on my BES machine, and did NOT apply SP3 as I did on my exchange server. Thus, the MAPI and CDO DLLs were not in sync. Copying and registering the files from the exchange server onto the BES box fixed my problems thus far. Thanks!