Blackberry Server - Email stops sending/receiving

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

what ports need to be opened coming back from WAN->LAN? The server has been working perfectly until a few weeks ago. Also, we're not having any other network connectivity problems as i monitor bandwidth regularly and we are not dropping any packets to our ISP's router.

The only port that needs to be open on your router is the one you have assigned to the Blackberry server on your server. If this port isn't open, then no Blackberry communication will happen at all. By default, this port is 3101, so unless you've changed it, that port would have to already be open on your firewall.

Is there anything in your event logs indicating that a particular service is stopping first, or any related errors that you can see?

Another thing to check - maybe your firewall is blocking an IP address that is needed, or there's a problem with the SRP address that you're using. Take a look at this article in the Blackberry knowledge base:
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB03735&sliceId=1&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=71518745&stateId=0%200%2071520707
If that link doesn't work, go to the Blackberry website, click on the Support link and search for the following article: KB03735

ASKER

srp.us.blackberry.net
located in san diego, so this seems to be correct. Logs just show multiple srp/connected and disconnected events.

ASKER

here is what my results of bbcheck were. Noticed that ESMDB32.dll is not the same as MAPI32.dll or CDO.DLL is this correct?

Platform:             Exchange
Version:             4.1.6 MR4 (Rollup) (Bundle 105)
Install Path:             C:\Program Files\Research In Motion\BlackBerry Enterprise Server\
Network Access Node:       srp.us.blackberry.net
MAPI Profile:            BlackBerryServer

[MAPI_SUBSYSTEM]

MAPI32.DLL:      6.5.7638.1 (c:\windows\system32\mapi32.dll)
EMSMDB32.DLL:      6.5.6944.1 (c:\windows\system32\emsmdb32.dll)
CDO.DLL:      6.5.7651.61 (C:\Program Files\Exchsrvr\bin\cdo.dll)

Hostname:      ENCAUDIO1
DB Name:      BESMgmt
Location:      Local
SQL Version:      Unable to find SQL version!
Location:      Local
MSDE Version:      8.00.761
DB info via TSQL: Desktop Engine (8.00.760 SP3)
MDAC Version:      2.82.3959.0
MSADO15.DLL:      2.82.3959.0 (C:\Program Files\Common Files\System\ado\msado15.dll)

[JAVA]

Version:      1.6
Path:            C:\Program Files\Java\jre1.6.0_02

MDS JVM Path:      C:\Program Files\Java\jre1.6.0_02\bin\client\jvm.dll

[.NET_FRAMEWORK]

Version 1.0:                   MISSING
Version 1.1 (1.1.4322):             INSTALLED
Version 2.0 (2.0.50727):       INSTALLED
Version 3.0 (3.0.0456.30):       INSTALLED

[XML]

XML Parser:      4.20.9870.0 (C:\WINDOWS\system32\msxml4.dll)

[MSMQ]

Microsoft Messaging Queue Version:      Unknown

[NETWORK]

Local IP:            10.0.0.14
TCP/IP Providor:      5.2.3790.0 (C:\WINDOWS\System32\wsock32.dll)
Winsock2 File:            Network Location Awareness (NLA) Namespace 5.2.3790.4318 (C:\WINDOWS\System32\mswsock.dll)

[SRP_CONNECTIVITY]

Host:      srp.us.blackberry.net
IP:      206.51.26.33
Port:      3101

Status:      Connection Successful

[SYSTEM]

Processor:

Processor Identifier:      x86 Family 15 Model 4 Stepping 1
Processor Vendor:      GenuineIntel
Processor Name:            Intel(R) Pentium(R) 4 CPU 2.80GHz
Number of CPUs:            1

Memory:

Memory In Use:            76%
Total Memory:            1,038,376 MB
Memory Available:      245,164 MB
Memory Limit:            2,512,024 MB
Available Commit:      1,547,368 MB
BES Virtual Space:      2,097,024 MB
BES Unused Memory:      2,043,548 MB

Hard Drive:

Total HD Bytes:            1,979,168 MB
Total Free Bytes:      1,143,008 MB

Time Info:

System Up Time:            0 days 0 hours 9 minutes 5 seconds
Local Time Zone:      Pacific Daylight Time (GMT-08:00)

[PROCESSES]

Process                        PID      Threads

System                        4      84
smss.exe                  300      3
csrss.exe                  348      13
winlogon.exe                  372      25
services.exe                  420      18
lsass.exe                  432      43
svchost.exe                  620      7
svchost.exe                  692      12
svchost.exe                  760      11
svchost.exe                  804      14
svchost.exe                  820      65
spoolsv.exe                  992      13
msdtc.exe                  1016      19
BBAttachServer.exe            1152      113
BBConvert.exe                  1208      2
bmds.exe                  1224      88
BBConvert.exe                  1236      2
BESAlert.exe                  1260      6
DWRCS.EXE                  1288      12
BBConvert.exe                  1300      2
BBConvert.exe                  1348      2
svchost.exe                  1380      2
inetinfo.exe                  1716      9
FrameworkService.exe            1912      10
Mcshield.exe                  2012      24
naPrdMgr.exe                  2068      5
VsTskMgr.exe                  2100      11
sqlservr.exe                  2320      32
svchost.exe                  2348      2
svchost.exe                  2412      3
wmserver.exe                  2908      16
beremote.exe                  2948      12
BlackBerryController.exe      3024      7
BlackBerryDispatcher.exe      3052      52
ITAdminServer.exe            3068      21
BlackberryRouter.exe            3100      8
BlackBerrySyncServer.exe      3268      87
exmgmt.exe                  3304      7
svchost.exe                  3384      16
BlackBerryAgent.exe            2704      52
wmiprvse.exe                  3888      7
svchost.exe                  4364      23
alg.exe                        4660      6
DWRCST.EXE                  5348      4
explorer.exe                  5448      15
svchost.exe                  5580      17
shstat.exe                  5588      7
UpdaterUI.exe                  5628      5
TBMon.exe                  5644      2
hkcmd.exe                  5688      1
smax4pnp.exe                  5712      3
jusched.exe                  5720      1
ctfmon.exe                  5740      1
DesktopMgr.exe                  5880      9
sqlmangr.exe                  5928      2
bbmgrw32.exe                  6028      23
wmiprvse.exe                  6092      7
CalHelper.exe                  2624      8
RIMDeviceManager.exe            4080      12
BbDevMgr.exe                  4184      7
BBCheck.exe                  6004      7
[END_13:44:24]
[START_16:16:25]

Generated by BBCheck Version 1.0.0.2

jdera

Emsmdb.dll file has to be the same version or greater than the other 2 files.

Check out the below for your solution:

http://www.blackberryforums.com/bes-admin-corner/120979-cdo-dll-mapi32-dll.html

I would check your firewall to see if it is dropping packets. All you need to do is ensure you have port 3101 TCP open outbound ONLY and ensure your firewall isn't dropping out of state packets. Apart from restarting the service did you do a full server restart?

Another known issue is that another application is using port 4101 (Port 4101 is the default port used by the BlackBerry Router for the serial bypass functionality). To check this run the following command below and then open the output file and search for 4101.

netstat -ab >c:\ports.txt

It is also common for select Symantec AV,firewall and security products to cause this issue on the BES.

ASKER

jdera:

I have checked versions of EMSMDB32.DLL on exchange and blackberry server. There is a conflict of versions. the article says that i need to upgrade blackberry software? I am on current version. Will i be able to update this DLL and place in under system32 folder on my BES? The version on my Exchange server is 6.5.7638.2. (version on BES of ESMDB32.DLL is 6.5.6944.1)

ASKER

garycutri:

Here are the results (ports.txt) Looks to me like everything is in line here.

As you can see by your ports.txt output only "BlackberryRouter.exe" is using port 4101 which is good.

If you have Exchange System Manager 2003 installed on the BES you don't want to manually register anything under c:\windows\system32 (you never need to manually register files if you do updates correctly). First install Exchange SP2 over Exchange System Manager on the BES and then apply any DST updates or hotfixes if required. Once the ESM updates are applied you will have the correct files version, the only issue is that someone has manually registered other file versions on your BES. Just manually unregister the files below from c:\windows\system32 and you will find the correct and freshly updated versions in C:\Program Files\Exchsrvr\bin (you will have to re-register these). Once you have corrected the registered files in future all you need to do is install an Exchange update on the mail server, and then remember to install it on the BES and they will stay consistent.

MAPI32.DLL: 6.5.7638.1 (c:\windows\system32\mapi32.dll)
EMSMDB32.DLL: 6.5.6944.1 (c:\windows\system32\emsmdb32.dll)
CDO.DLL: 6.5.7651.61 (C:\Program Files\Exchsrvr\bin\cdo.dll)

ASKER

I have decided that i am going to setup another BES in parallel. Will i be able to do this? I need to know what steps to follow to build a bes from scratch. Install ESM on newly build machine, then install sp2 over top? Please give me steps and i will build out monday and assign points. Do i need to apply DST patch to mail server and bes? Not completely sure and i need to make sure all bases are covered so this goes smoothly.

Thanks!

You cannot run two BES's in parallel unless you have two licenses. Your SRP and license keys cannot be active on two servers at the same time.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Also here is a guide on how to install Exchange System Manager:

http://www.good.com/faq/17133.html

ASKER

sounds good. Can i setup the database on another server? we currently have a dedicated server running SQL2005 and wanted to know if i can just create the database within instead of using the default msde/express version that comes with the server.

ASKER

last question. How can i tell if the daylight savings patch has been installed/which one installed on exchange? under assumption that i need to install patches on both exchange and bes, correct?

In my guide above explains how to move the msde database and this will also work on the SQL 2005 server. So just run the same script and restore the database over the top. To make sure all the updates are applied just run Windows update and if you havent done so upgrade it to Microsoft update (this will show Exchange patches.)