[fluidimagery]

We've recently gone a bit green and consolidated 3 of our Windows Server 2003 servers onto a single SBS2003 box.

Preiously... Server 1 - DC / File, Server 2 - Exchange, Server 3 - BES Express

So we followed all the steps to transfer the foles, change the global catalogs etc. Everything seems to be functioning however there are still a few errors that are occuring. We setup BES Express last night and it's working, we were able to get our blackberries activated wirelessly and they seem to be working just fine with the bes server. However, if I look in the Application log I see a bunch of warning messages that recur every 5 minutes or so...

Event Type: Warning
Event Source: BlackBerry Synchronization Service
Event Category: None
Event ID: 20000
Date: 4/5/2008
Time: 11:52:04 AM
User: N/A
Computer: FIC-SERVER
Description:
BIPPeClient::Connect: Error calling host "FIC-SERVER" [192.168.1.5] (10061)


Event Type: Warning
Event Source: ExchangeConnector
Event Category: None
Event ID: 20000
Date: 4/5/2008
Time: 11:52:56 AM
User: N/A
Computer: FIC-SERVER
Description:
BIPPeClient::Connect: Error calling host "FIC-SERVER" [192.168.1.5] (10061)


Event Type: Warning
Event Source: BlackBerry Policy Service
Event Category: None
Event ID: 20000
Date: 4/5/2008
Time: 11:53:02 AM
User: N/A
Computer: FIC-SERVER
Description:
BIPPeClient::Connect: Error calling host "localhost" [127.0.0.1] (10061)


I read around a bit and saw a few posts about the cdo.dll and mapi32.dll being different versions between BES and Exch but it doesn't seem to be the case

From the MAGT Log in BES:
[30000] (04/05 00:00:02.875):{0x1900} [ENV] MAPI32.DLL: C:\WINDOWS\system32\MAPI32.dll, Version: 6.5.7226.0
[30000] (04/05 00:00:02.875):{0x1900} [ENV] CDO.DLL: C:\Program Files\Exchsrvr\bin\cdo.dll, Version: 6.5.7226.0

One thing I did notice is that in other posts... both those file locations in bes were looking at c:\windows\system32 dir... my log is pointing to the exchange file instead... no idea.

Thanks!

[Keyscan]

For starters, I highly recommend you patch your cdo with the dst. It would need to be 6.5.7651.61 as per Microsoft KB926666.

Is your Synchronization service running? If you check in the CTRL log, do you see any errors stating that it is attempting to restart the Sync service?

Also, is the FIC-SERVER NetBIOS name the BES box, or your exchange box?

[marley1]

Here is the update for the CDO Download details: Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 2 (KB 926666)

[fluidimagery]

Updates are installed, I fixed a few others windows errors in hopes that it would also fix the BES warnings.

Warnings in Applications Errors:

Event Type: Warning
Event Source: BlackBerry Dispatcher FIC-SERVER
Event Category: None
Event ID: 45058
Date: 4/5/2008
Time: 11:01:37 PM
User: N/A
Computer: FIC-SERVER
Description:
{StartNotifyThreadServer}: DBNS component not installed.


Event Type: Warning
Event Source: BlackBerry Dispatcher FIC-SERVER
Event Category: None
Event ID: 20608
Date: 4/5/2008
Time: 11:01:42 PM
User: N/A
Computer: FIC-SERVER
Description:
[BIPPe] WARNING: Using default BIPP shared secret


Event Type: Warning
Event Source: BlackBerry Synchronization Service
Event Category: None
Event ID: 20000
Date: 4/5/2008
Time: 11:01:42 PM
User: N/A
Computer: FIC-SERVER
Description:
[BIPPe] WARNING: Using default BIPP shared secret


Event Type: Warning
Event Source: BlackBerry Synchronization Service
Event Category: None
Event ID: 45058
Date: 4/5/2008
Time: 11:01:42 PM
User: N/A
Computer: FIC-SERVER
Description:
The description for Event ID ( 45058 ) in Source ( BlackBerry Synchronization Service ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: {StartNotifyThreadServer}: DBNS component not installed..


Event Type: Warning
Event Source: BlackBerry Policy Service
Event Category: None
Event ID: 20608
Date: 4/5/2008
Time: 11:01:43 PM
User: N/A
Computer: FIC-SERVER
Description:
[BIPPe] WARNING: Using default BIPP shared secret


Event Type: Warning
Event Source: BlackBerry Policy Service
Event Category: None
Event ID: 45058
Date: 4/5/2008
Time: 11:01:43 PM
User: N/A
Computer: FIC-SERVER
Description:
{StartNotifyThreadServer}: DBNS component not installed.


Event Type: Warning
Event Source: DevMgmtConnector
Event Category: None
Event ID: 45058
Date: 4/5/2008
Time: 11:01:43 PM
User: N/A
Computer: FIC-SERVER
Description:
The description for Event ID ( 45058 ) in Source ( DevMgmtConnector ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: {StartNotifyThreadServer}: DBNS component not installed..


From MAGT log:
[30000] (04/05 22:14:31.721):{0x1028} [ENV] MAPI32.DLL: C:\WINDOWS\system32\MAPI32.dll, Version: 6.5.7638.1
[30000] (04/05 22:14:31.721):{0x1028} [ENV] CDO.DLL: C:\Program Files\Exchsrvr\bin\cdo.dll, Version: 6.5.7651.61



You get the idea... there are about 10 others in the application log but the same gist. Any ideas?

I tried uninstalling and re-installing bes. I'm able to send and receive on the blackberry still.

[Keyscan]

It appears your environment requires the Database Notification System (DBNS). Are you running MSDE or SQL Server 2000/2005?

If you want instructions on how to install DBNS, refer to page 32 of the BES 4.1.4 installation guide PDF.

http://na.blackberry.com/eng/deliver...idexxx91;1].pdf

[fluidimagery]

msde with a seperate instance for the blackberry db MSSQL$BLACKBERRY

[fluidimagery]

how do you go about installing that on MSDE? The instructions seem geared for SQL Server and I'm not experienced with either.

[fluidimagery]

As another note... everytime I restart the server I lose the BESAdmin account in AD under each individual user. The account shows as "Account Unknown..." I need to remove that and re-ad the "BESADmin" account with the send as permission enabled. After that I'll be able to send mail out.

[marley1]

Originally Posted by fluidimagery

As another note... everytime I restart the server I lose the BESAdmin account in AD under each individual user. The account shows as "Account Unknown..." I need to remove that and re-ad the "BESADmin" account with the send as permission enabled. After that I'll be able to send mail out.

I had to use this fix the last time i had that issue during the DST updates.

To correct the "Send As" issue I have outlined the steps I use to quickly resolve this issue:

1. Stop the Blackberry Router service.

2. Open Active Directory and from the View menu select "Advanced Features". Then go to each user that will be added to the BES and open their properties, go to the security tab and add the user BESadmin and add the security permission "Send As".

3. Run the following script logged on as Administrator
Note: Only use this step if you have BlackBerry users that are members of Admin groups. Using best practice methods it is recomended that mobile user accounts aren't members of any administration groups.

dsacls "cn=adminsdholder,cn=system,dc=domainname,dc=c om " /G "DOMAINNAME\BESadmin:CA;Send As"

Example 1: dsacls "cn=adminsdholder,cn=system,dc=experts-exchange,dc=com " /G "EXPERTS_EXCHANGE\BESadmin:CA;Send As"

Example 2: dsacls "cn=adminsdholder,cn=system,dc=blackberryforum s,dc =com,dc=au " /G "BLACKBERRYFORUMS\BESadmin:CA;Send As"

Example 3: dsacls "cn=adminsdholder,cn=system,dc=mobilenetwork,d c=lo cal" /G "MOBILENETWORK\BESadmin:CA;Send As"

NOTE: dsacls can be found in the Windows Server 2003 SP1 Support Tools pack: Download details: Windows Server 2003 Service Pack 1 32-bit Support Tools

4. Wait 20 minutes and then restart the BlackBerry Router service.

5. Restart the BES server.