no one could log on to the bes admin site
here is how I fixed the problem

I found link that said that bes does not like special characters.. I was able to change the pw in the bes configuration console active directory ( or ldap ) tab
to a pw that only included letters and numbers
I restarted the server..
But I still could not log in to the Bes administration site

I found that I got a security bar” that internet explorer is blocking access to the website “ when I tried to load the blackberry web desktop manager

I added https:// servername to the list of trusted sites.. I then reloaded “ blackberry web desktop manager” without an error

Then when I tried Blackberry administration service and what do ya know … it now works

I have seen no reference to any such internet explorer problem in any bes blog or posting
hope this helps someone

I ran on the BES ipconfig /flushdns
I restarted BlackBerry Administration Service – Native Code Container
I then watched the task manager to show BAS-AS at over 500,00K Memory usage and )-1% on CPU

I then tried again and Viola’ it worked!!

Reinstall and select BES instead of AD. DO NOT INSTALL WITH AD.

On top of that, do not use characters for the password. I have another post on the site that says what characters you can use.

Good luck!

Koopa

thanks.
if it works i post it.

I had about eight or nine hours trying to resolve this yesterday and this is what I finally did to get this working. I am posting this here for others who may have the same issue and hopefully it may help the OP of this thread.

I made a discovery in the Security log of the Event viewer on my Server
that was hosting both BES Express 5.0.1 as well as Exchange 2007. They are both on the same box. The Security log entry made reference to a Kerberos right being denied to the BESADMIN active directory account around the time I tried to login to the BES Admin service website. This was irrespective of whether I wanted to login to the BES Express Admin website as BESADMIN or as another login (Say my domain admin account).

I deduced from this that when the BES Express Admin Web service needs to verify your login it is being denied some sort of Kereberos Ticket and or elevated privilege. Since the Message indicated the problem to be with the BESADMIN Active Directory user that I created for installing BESX and of course used by the BESX background services to execute under, I checked out the properties of this account I had created and made the following changes / settings.

Using Active Directory Users and Computers
I went to the users container and right clicked on the user BESADMIN and selected properties. Under the Account Tab I set the following items in the “Account Options” list at the bottom of that tab.

Use Kerberos DES etc – Checked.
This account Supports Kerberos AES 128bit encryption – checked.
This account supports Kerberos AES 256bit encryption – checked.
Do not require Kerberos preauthentication – UNCHECKED.

I rebooted the server (Not just restarting the background services!) and finally I was able to login to the BESX Administration Service web site under BESADMIN or under my Domain Admin login ID.

Hope that helps anyone else in this predicament. It was an unnecessarily long day yesterday getting this going thanks to that one stupid little problem.