Forums are not clear on this point since it was initially not support. In TODAY’s world (not 2009) Windows 2008 R2 is supported for the blackberry servers.

See below:

Any of the following operating systems:

* Windows Server® 2003 SP1 or later
* Windows Server 2003 R2
* Windows Server 2003 (64-bit)
* Windows Server 2003 R2 SP2 (64-bit)
* Windows Server® 2008 or later
* Windows Server 2008 (64-bit)

http://docs.blackberry.com/en/admin/deliverables/7314/SR_BES_350426_11.jsp

There are a lot of cool features that this tablet has, glad to see RIM is finally getting on board the tablet bandwagon.  I’m hoping that RIM sends my company a demo of this tablet, as I am really excited about it.  I’ve been thinking of either purchasing an iPad or ‘Droid tablet, but just haven’t made the jump yet.  The playbook might make me take the plunge.

As I write this entry, I am on the phone with RIM technical support.  Let me tell you the story of upgrading my BES server to version 5.0.

*NOTE: The second time for this issue, the issue was DNS related insofar, the entry had gotten changed with the wrong server name through replication.
I have been working with BES for a long time (since version 2) and my current environment is 4.6.  I downloaded the 5.0 upgrade media and kicked off the install.  I was pleased with the progress and the install seemed to be moving right along with no major issues.  Every other time I have upgraded my BES servers, something always went crazy mid install, be it my fault or not.

The first option which I am still regretting is the option to select windows authentication for the Blackberry Administration Service.  I had thought, why would I need another hardset password, my organization would just use the besadmin account anyways!  As you will see, this is a huge mistake.

The install finishes without any noticeable problems and the first thing I realized was that the Blackberry manager snapin no longer works.  I read up on the features that version 5.0 brings, but for some reason, I never knew that it would take it to a webdav.  Regardless, I launch the shortcut and it brings me to a pretty login page where I enter the besadmin creds.  It then provides the error message:

“The username, password, or domain is not correct.  Please correct the entry”

The first thing I do is enter it again, and again, and again.  Next, I check to make sure that the time is correct on the bes server and the LDAP domain controller.  It is.  This rules out TIME KB.  I then verify that my reverse DNS and proper ldap settings are correct.  They are.  This rules out the LDAP kb.

After further reading, I see that the test LDAP settings button may be corrupted.  I did hit the test LDAP button (who wouldn’t????) and thought, HA that MUST be my problem.  I followed the following steps in option 1, and rebooted the BES, but the error still occurred.

Option 1

1. On the server where the BlackBerry Administration Service is installed, navigate to this directory:<drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\bin
2. Run the following command:basUtility “C:\Program Files\Java\jre1.5.0_15″ “C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS” encode “<LDAP Password>” > C:\Output.txt
3. Open the text file created in Step 2.
4. Copy the hashed version of the password to your Microsoft SQL Server.
5. Run the following SQL Query against the BlackBerry Configuration Database:update BASAuthenticationCredentials set password = ‘<contents of output.txt>’ where AuthenticationType LIKE ’1′
6. Restart the BlackBerry Administration Service services.
7. Log in to the BlackBerry Administration Service using Microsoft Active Directory.

Option 2

Install the BlackBerry Administration Service again.
I then went down the path of option 2, but this also did not fix my issue.  At this point, I was at wits end, and decided to give RIM tech support a call.  Applying the latest SPs actually allowed me to login, and I was happy.  This worked until my VM got rebooted, and now today, the problem is still occuring.  Once the BES tech gets back on the phone, (I have been on hold for 40 minutes now, while he “reviews” my case, I will paste the resolve)

So, when you have tried everything else, here is something that you can try.  Ultimately, this resolved the issue that I was having with a excvhange 2007 server.  Good luck and happy reading!

Overview

One way calendar synchronization is not working from the BlackBerry smartphone to Microsoft® Outlook®

The following log lines are displayed:

[30001] (08/14 13:58:46.822):{0x164C} CDOCalendar::Initialize – Code = 80040705, WCode = 0505, Code meaning = IDispatch error #1285,

[30002] (08/14 13:58:46.822):{0x164C} Server = exchange, Mailbox = /o=My Organization/ou=First Administrative Group/cn=Recipients/cn=user Description = The attempt to log on to the Microsoft Exchange Server computer has failed. [Microsoft Exchange Server Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]]

[30180] (08/14 13:58:46.822):{0x164C} {user} CDOCalendar::Initialize – Error in call m_spCalendarFolder = m_spCDOSession->GetDefaultFolder

[40000] (08/14 13:58:51.028):{0x164C} CDO initializing failure in CDO helper 00f31e78 (5)

[40580] (08/14 13:58:52.029):{0x164C} CDO helper 00f31e78 closing after CDO initialize failure

[40000] (08/14 13:58:52.129):{0x164C} CalHelper failed 00f31e78, ErrorCode = -11, Thread activity was Checking CDO object list

The following error message is displayed when you attempt to connect to the affected BlackBerry smartphone user’s Microsoft Outlook mailbox using a profile that does not have cached Exchange mode turned on:

The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.

Cause

This issue has multiple causes.

1. The public folder store is not loaded.
2. The BlackBerry Enterprise Server service account does not have the appropriate permissions.
3. The protocol settings in Microsoft® Active Directory® have been set to deny MAPI connections.

Resolution

Complete the appropriate resolution for the cause of the issue.

Cause 1

The public folder store is not loaded.

Resolution

Load the public folder store.

The BlackBerry Enterprise Server service account does not have the appropriate permissions.

Resolution

Verify that the BlackBerry Enterprise Server service account has the same permissions as the mailbox store.

The protocolSettings in Active Directory have been set to deny MAPI connections.

Resolution

Microsoft Exchange 2003 SP2 and Microsoft Exchange 2007 SP1

Complete the following steps:

1. Install the Windows 2003 Support Tools if they are not currently installed.
2. Open adsiedit.msc.
3. Expand Domain [servername.domain.com] then the respective container holding the user object that you want to check the protocolSettings of.
4. Right-click a user and select Properties on the context menu.
5. Select protocolSettings from the list of properties and click Edit.
6. If you see a value of MAPI§0§0§§§§§§ or MAPI§1§1§§§§§§ then MAPI access has been turned off for this user. Remove the value.Note: It can take anywhere from 15 minutes to 2 hours for this change to take effect.

   Note: By default the Multi-valued string is blank which means that no value is defined and MAPI access is allowed.

HMC 4.0 and later

If the MPS was used to create the user accounts and mailboxes in a hosted environment then the configuration settings of the front-end application that was used to create the accounts must be changed. The change to the configuration settings makes the required changes to all user accounts that were created using MPS.

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB14075

To migrate the BlackBerry Enterprise Server from Microsoft Exchange Server 2000 or 2003 to Microsoft Exchange Server 2007, complete the following steps

1. Stop all BlackBerry Enterprise Server services.Important: Restarting certain BlackBerry Enterprise Server services will delay email message delivery to BlackBerry smartphones. For more information, see KB04789.
2. Move the BlackBerry Enterprise Server service account mailbox. The default name for this account is BESAdmin.
3. After migrating Microsoft Exchange Server 2000 or 2003, verify the Microsoft Exchange Server 2007 permissions for the BlackBerry Enterprise Server.
4. Set the required permissions for the BlackBerry Enterprise Server in Microsoft Exchange 2007. For more information, see KB12483.
5. Remove Microsoft Exchange System Manager 2000 or 2003. (Exchange installation cd will be required to complete this step)
6. Perform a search for MAPI32.dll and cdo.dll.
7. Rename any cdo.dll and MAPI32.dll files from the system32 folder and the program files\exchsrvr\bin folder to a .bak file extension.
8. Download and install the latest Messaging Application Programming Interface (MAPI) and Collaboration Data Object (CDO) clients. For more information, see KB12697.
9. Resolve the MAPI profile for the BESAdmin mailbox on the Microsoft Exchange Server 2007 by going to Start > Programs > BlackBerry Enterprise Server > Edit MAPI Profile.
10. Restart the BlackBerry Enterprise Server.Important: Restarting the BlackBerry Enterprise Server will delay email message delivery to BlackBerry smartphones. For more information, see KB04789.

View the reference link for further details:

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB14502

Ok – first, I need to figure out why localhost is blocking port 10054 and this should clear up the issue.  The strange thing though when I put this error message in google is here is one of the hits.

broadsword calling danny boy wav naked lesbian teenager cheap calling cards india srpclient error calling host …

Really?  REALLY?  I got a porn hit on a blackberry issue.  What is the world coming to today?!?!?!  If I figure out why I’m getting this error, I’ll be sure to post it..

Navigate to the following:

Options
Advanced Options
Enterprise Activation

In Enterprise activation, perform the following:
Press and HOLD ALT and type “CNFG”
This will provide the configuration for the enterprise activation. Scroll down to Wireless Sync and select no.
Repeat the steps and change it back to yes. The soft enterprise activation will now perform.

I stumbled upon this when researching another issue on my BES.  I tried it out and works like a charm!

There is nothing that pisses me off in the BES World like error messages that does not mean much to me!  This is one of them…

Event Type:      Warning
Event Source:      BlackBerry Policy Service
Event Category:      None
Event ID:      20000
Date:            7/03/2008
Time:            4:24:11 PM
User:            N/A
Computer:     BES
Description:
{email@email.com, PIN=XXXXXXX, UserId=12}RequestHandler::HandleSERVICE_BOOKDataCommand - IncompleteACK data for SERVICE_BOOK request

This error occured after I added a new person and the contacts did not port over.  For giggles, I did the following:

On the blackberry go to options, advanced options, host routing table, then click the button on the blackberry and choose register with network.  Sometimes if the blackberry does not register right the first time it corrupts the service book.

I then resent the service books from the BES server and waited.  After about 20 minutes, the guy’s contacts started to sync!

The latest and greatest project is to get our blackberry devices to work with this website that my development team is creating.  Since I am the blackberry admin, it has fallen into my lap to get the blackberries to conform to standards.  One of the things that RIM has suggested is to turn on internet explorer emulation.

Open the browser on the BlackBerry device.

Click on the menu button and go to options Select Browser Configuration For Emulation Mode, select Microsoft IE.

Save and close.

This did not resolve the issue, but it was worth a shot!

Open BlackBerry manager.

Click on the mds-cs connection and select edit properties.

On the Logs tab, set both the HTTP Logging Enabled and the Verbose HTTP Logging Enabled drop-down lists to True.

Click Apply, then click OK.