[Elf]

Hi Guys,

I am having a wee bit of a nightmare. We have had to change domains. So today the Bes was moved across. However the Bes didn't like that much. It is saying that it can't connect to the SQL due to a login error. I originally thought it could be because the SQL server is still on the old domain but it is due to be moved across later tonight. However I am now thinking that it could be because the BESAdmin account was an account on the old domain that ain't getting moved across as it was the domain admin account. Ahhhh I know sorry it wasn't me that set it up. I would have made a nice BESadmin account and only use it for the BES. Is there a way that I can change the service admin account? Doing a search I have found how to do it in Exchange but not in Domino.

All the services have been changed so that they are using the new domain account and that account has got rights to the SQL database there must be something else that needs changed.

Help!

I am running Bes 4.1.6, Domino 6.5.5 FP3 on Windows Server 2003

Thanks,
Elf

[DarthBBerry]

You have to grant the BES itself permission to the SQL Server / Instance / database.
I think the syntax is $BES or something like that. I've got a SQL admin to do my bidding...

[Elf]

Yeah I caught that one too. I have a user created on the SQL server in the format domain\besservername$ he has public, DB_owner and Rim_Bes_server rights.

Which is what the old domain had.

I must be missing something else too.

[knottyrope]

This might help out

View Document

[Elf]

Thanks Knottyrope

I didn't have the windows account with Server administrator rights in the SQL DB

However I am still getting the "Unable to open BESMgmt database: Login failed for user '(null)' . Reason: Not associated with a trusted SQL server connection.0x80004005 NativeError=18452 Error Initialising BES. Terminating"

I wish I had a SQL Admin but ours ran away to Oz

Is it possible to recreate the SQL DB and whack all the back in? Or take the current one off line and then create a new one and then delete it and then readd the old one? Or is that just me grasping at straws?

[Elf]

I've also tried this.....View Document

Which wasn't set in my registry but it hasn't fixed my problem.

[noname]

You should have verify the access on the BES on these items:-

(1) Can you telnet <sqlsevername> 1433 on the BES?
(2) Move your OSQL.EXE to the BES and perform a "OSQL -E -S <sqlservername>" to see if you are able to connect?
(3) If your SQL Server is 2000 and installed on Windows 2003, make sure to patch it up to SP4. There is a known issue for SQL2000 on Windows2003.

That error you have is because Domino server is running on LocalSystemAccount and it is using this credential to talk to your SQL server. Make sure those listed in your BES local administrators have been granted access to the SQL server (including BESMgmt db).

Your issue is not complicated, just a Windows permission issue. Good luck.

[Elf]

Woo you might be on the money there.

I have changed the domino service to run using my windows service account instead and that has started the bes service! However the messages are just queueing up and not going out to the handhelds.

Any ideas?

[Elf]

It's ok as my mum would say "Patience is a virtue" and I am never patient enough.

They are all flying through now.

Only thing is Domino console ain't showing on the server when I am logged in as me. I am using domino admin to see it. That might cause some concern with the on call team.

But I am soooooo happy that it is back up now.

Thanks to all those that helped.