[freakency]

Wirelessly posted

Hi !

I've been working on this one since friday. I'll try to make it short :

- we've been experiencing cpu overload on a BES on vmware esxi. So we backed up the vm because it could have been hardware related issue. We moved the BES to a new VM on another server but we were not able to recover the server, some files was missing within the backup.

We started from scratch and we installed 5.0.1 MR1 without a glitch.

Now we could no longer log to the web interface.

We uninstalled and reinstalled maybe 5 times and the same problem keep going.

We have consulted and checked every KB that we could find. We already know about the hash no being passed trought and my network admin have checked this many times.

We checked our DNS, our DC, added the GC to the DC that is connecting,

And now, the log file for BAS-AS stopped telling me errors codes but we're still not able to log.

Before that, the last error in bas-as was user besadmin unknow !!???!!!!

I opened a ticket to rim today, but I would like to know if someone else have been trought this and what wa the solution

[GrandsireTriples]

If you are using a DC with Server 2008 there is a KB to cover this from RIM.

There are 2 logons to the BAS BAS and AD (Unless you are on Domino then there are 3)

If you can use the BAS logon then the problem is with AD commuication. You may not have installed a BAS admin when you installed the BES 5.0.1 the default changed from BES 5.0.0.