[ThomasB]

I just upgraded Domain and Exchange from SBS2000 to SBS2003 with swing migration and forklifted the exchange database.

Had BES 4.0 running on Win2000. Had previously been 3.6 with other applications and decided to do a fresh install. Saved the database and fdisk the server, win2000, SP3. Added ESM 2003 and SP1. Registered cdo.dll 6.5.7226 both in \program files\exchsrvr\bin and \winnt\system32.

Installed MSDE 2000 and MDAC 2.8.

Set BESADMN for local admin, log on locally and log on as service
On domain/exchange: domain users, view only administrator, administer information store, send as, receive as.
Using BESADMIN installed BES 4.0 , SP1 and SP2.

All tests are ok (SQL connection, IEMSTest, Validate SRP, Test network connection, MAPI edit)
All Blackberry services start and the logs seem to show no problems.

EXCEPT when I try to start Blackberry manager

"Unable to retrieve the server's distinguished name of allocate a MAPI buffer for this server"

Then:

"Unable to connect to the database"

Manager then opens with no information.

Tsupport is a bit slow in getting back to me and the users are getting desperate.

Any fresh ideas? The case is going cold!

Tom

[conwawj]

Just a thought... I'm running BES on Domino not exchange but I'm assuming the SQL connection is the same. Check to see if you have the following regkeys set up. I had a similar problem after upgrading to BES 4.0sp2 where the key was removed.

HKEY_CURRENT_USER\Software\Research In Motion\BlackBerry Enterprise Server\Management\Database\

DatabaseName = BESMGMT
DatabaseServerMachineName = <name of sql server>

[ThomasB]

Thanks for the quick response.

These were not there.

I added string values for DatabaseName and DatabaseServerMachineName under the Database key with no difference.

I am guessing it is something in the registry. I thought I started with a clean install but something must ahve gone awry.

[conwawj]

Are you running the Manager from the server or from your workstation? If you haven't done so already I would attempt to install the BES Manager client on your workstation and see if you can get it to work there first.

[ThomasB]

Great idea!

However would Outlook not cause a problem?

I take it that ESM 2003 would be the only prerequisite?

Tom

[jibi]

On the BES, itself, Outlook would be a problem. However, you're simply installing the BlackBerry Manager portion of it on a remote machine, so no.

From the installation guide (which is still a great resource):
Microsoft Exchange 5.5. Administrator or
Microsoft Exchange 2000 System Manager (not supported on Windows Server 2003 or Windows
XP) or
Microsoft Exchange 2003 System Manager or
Microsoft Outlook 2000 (Corporate or Workgroup installation)
Microsoft Outlook 2003 (Corporate or Workgroup installation)
Microsoft Outlook XP (Corporate or Workgroup installation)

[yckernel]

Have you tried to stop the SQL service and Start again

[ThomasB]

Have reset the machine countless times.

Have installed manager on a 2000 workstation and, although I do not get the first error, I am not able to connect ot database.

Tried Data Sources (ODBC) on the remote machine and Test Data Source works in connecting with BESmgmt.

Still lost...

[T-Roy]

You attached a 3.6 database and performed a fresh install of 4.0? ...and pointed it to the 3.6 database? that should not work unless you use the createdb.exe to migrate the database schema

[ThomasB]

Sorry T-Roy...

I upgraded to 4.0 in the spring. Just recently upgraded SBS from 2000 to 2003. Tsupport showed me the secret SMBDeviceEnabled which got rid of most errors. Now I am left with the Manager error. Tsupport now suggests a complete reinstall, which I thought I did. I have the database copied out so may be ok.

Wondering if the issue is that we also have a SQL database on the SBS?

See if I can get this fixed before going on vacation!!!

Tom

[ThomasB]

Tsupport suggested a complete uninstall and creation of a new Bes administrator user.

That worked!

Stopped MSDE, copied the database I saved and everything came back on line.

During the migration to 2003 the BESadmin must have got corrupted.

Thanks for the suggestions - I do think they lead in the right direction.

Tom

[BBTechGuy]

Based on the first error being a MAPI error I wouldn't have spent too much time on the SQL aspect. The first thing I would have done would be to delete the BlackBerry Profiles out of the Windows Messaging Subsytem in the Registry and then recreate them.

conwawj had a good suggestion as well.