Blackberry BIS issues with Exchange 2007
I have a BB (BIS) user who is having to re-validate his email settings (OWA on an Exchange 2007, sbs 08 box) at random times. The error message when validation fails isn't overly helpful. I was on the phone with Blackberry support a few moments ago, and part-way through the conversation the tech said, "Oh, it integrated, now I can validate and you're good." I was simply reviewing event logs to see if I could spot anything. Anyone seen this? Suggestions? Company owner is ready to go back to a pop server because, "We never had any problems then..."
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
There is also a known issue if the BB is using OWA and the SBS is rebooted while the BB is connecting it will loose the credentials and have to be reentered.
If switching to BES, the right way to go as suggested by Simon, it seems to me that BES does not support 64 bit as of yet so you will have to install on a server other than the Exchange 2007.
If switching to BES, the right way to go as suggested by Simon, it seems to me that BES does not support 64 bit as of yet so you will have to install on a server other than the Exchange 2007.
ASKER
Simon - I will check on the updates/patches for Exchange.
Rob - agreed, BIS is lame. Issue with BPS is that you have to upgrade to the corp data plan, often $15.00 more a month. Doesn't sound like alot but it's a show stopper for alot of small businesses I work with.
Rob - agreed, BIS is lame. Issue with BPS is that you have to upgrade to the corp data plan, often $15.00 more a month. Doesn't sound like alot but it's a show stopper for alot of small businesses I work with.
Blackberry is not cheap to run. It is an Enterprise solution. If customers are price sensitive, then buy a Windows Mobile or other ActiveSync enabled device (iPhone, certain nokia solutions etc). I simply say that anyone running around with a Blackberry without BES/BPS is simply using it as a status symbol, nothing else, because it is not integrated with the server.
The ActiveSync solutions that are starting to becomes available make the cost a little easier to bear, but it is still not as cheap as something ActiveSync based.
RIM are basically interested in two segments - Consumers with POP3 type accounts and Enterprises with BES. Small Businesses fall in to a middle ground they are simply not interested in.
Simon.
The ActiveSync solutions that are starting to becomes available make the cost a little easier to bear, but it is still not as cheap as something ActiveSync based.
RIM are basically interested in two segments - Consumers with POP3 type accounts and Enterprises with BES. Small Businesses fall in to a middle ground they are simply not interested in.
Simon.
I agree with Simon.
The only reason business people accept BIS is because they don't understand the features they are missing with BES. I'll bet they all spend $15/month of ring tones or fancy backgrounds :-)
Windows Mobile is an excellent choice and there are no additional licensing or service provider fees. Also the rate plans with Blackberry are usually more than with a Winmobile phone.
The only reason business people accept BIS is because they don't understand the features they are missing with BES. I'll bet they all spend $15/month of ring tones or fancy backgrounds :-)
Windows Mobile is an excellent choice and there are no additional licensing or service provider fees. Also the rate plans with Blackberry are usually more than with a Winmobile phone.
ASKER
Simon - installed the Rollup 9 for Exchange 2007. BIS account needed to be "validated." Validated without a problem and has not come up for re-validation since then (90 minutes ago). I will monitor over the next 24-36 hours. Good info, thank you.
ASKER
Update - looks like a firewall issue. BB sent me some logs that show a 404 error from one server, but things working fine from another. I've no firewalls that would be limiting connection by source IP address.
Suggestions on where to look?
Suggestions on where to look?
ASKER
BTW-here's the logs (search/replace domain name with mydomain.com)
__LOG_SEARCHED__ /var/bis/log/eng/engine.lo
22:17:10.169 12/19 [DBUG] [EngineServlet91238] OWACommonDownlo 0(tim)Checking detector=com.teamon.apps.c
22:17:10.169 12/19 [DBUG] [EngineServlet91238] EWSUrlDetector Unexpected HTTP Response=: 401 [bis-na-ui096]
22:17:10.169 12/19 [INFO] [EngineServlet91238] OWACommonDownlo 0(tim)Detector Timing[1369] source url=https://remote.mydomain.com/EWS/Exchange.asmx, isDetected=false [bis-na-ui096]
__LOG_SEARCHED__ /var/bis/log/eng/engine.lo
22:31:51.672 12/19 [DBUG] [EngineServlet92498] OWACommonDownlo 0(tim)Checking detector=com.teamon.apps.c
22:31:51.675 12/19 [INFO] [EngineServlet92498] OWACommonDownlo 0(tim)Detector Timing[1022] source url=https://remote.mydomain.com/EWS/Exchange.asmx, isDetected=true [bis-na-ui142]
22:31:51.675 12/19 [DBUG] [EngineServlet92498] OWACommonDownlo 0(tim)Detector result=detected=true; protocol=EWS; sourceUrl=https://remote.mydomain.com/EWS/Exchange.asmx; servername=null; nextDetector=null [bis-na-ui142]
22:31:51.675 12/19 [INFO] [EngineServlet92498] OWACommonDownlo 0(tim)OWA detected; detector=com.teamon.apps.c
__LOG_SEARCHED__ /var/bis/log/eng/engine.lo
22:17:10.169 12/19 [DBUG] [EngineServlet91238] OWACommonDownlo 0(tim)Checking detector=com.teamon.apps.c
22:17:10.169 12/19 [DBUG] [EngineServlet91238] EWSUrlDetector Unexpected HTTP Response=: 401 [bis-na-ui096]
22:17:10.169 12/19 [INFO] [EngineServlet91238] OWACommonDownlo 0(tim)Detector Timing[1369] source url=https://remote.mydomain.com/EWS/Exchange.asmx, isDetected=false [bis-na-ui096]
__LOG_SEARCHED__ /var/bis/log/eng/engine.lo
22:31:51.672 12/19 [DBUG] [EngineServlet92498] OWACommonDownlo 0(tim)Checking detector=com.teamon.apps.c
22:31:51.675 12/19 [INFO] [EngineServlet92498] OWACommonDownlo 0(tim)Detector Timing[1022] source url=https://remote.mydomain.com/EWS/Exchange.asmx, isDetected=true [bis-na-ui142]
22:31:51.675 12/19 [DBUG] [EngineServlet92498] OWACommonDownlo 0(tim)Detector result=detected=true; protocol=EWS; sourceUrl=https://remote.mydomain.com/EWS/Exchange.asmx; servername=null; nextDetector=null [bis-na-ui142]
22:31:51.675 12/19 [INFO] [EngineServlet92498] OWACommonDownlo 0(tim)OWA detected; detector=com.teamon.apps.c
ASKER
any other thoughts?
ASKER
to close this out, I followed Simon's suggestion to install the rollup patch for Exchange 2007. I don't think that fixed it. What I did change, which I feel made the biggest difference, was to disable the Windows firewall. Even though the rule-sets didn't appear to be filtering based on source IP address, removing that from the mix resolved the issue.
I'm awarding points to Simon as I appreciated the definitive suggestion to fix what I had instead of moving to BPS or BES.
I'm awarding points to Simon as I appreciated the definitive suggestion to fix what I had instead of moving to BPS or BES.
To nmaxwell-ks. There is NO 13 in the link provided at the very beginning of this series of Q&A's.
ASKER
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB02858&sliceId=1&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=249960628&stateId=1%200%20249966073
While speaking to tech I was connected in from offsite, so I know internet connectivity was good. I made no changes to the IIS or any other config settings.