[ctpuk]

Hi.

I'm upgrading from BES 4.0.7 to 4.1.6 - an in place upgrade on the same server. I've gone a bit wrong...

SQL is hosted remotely on a SQL 2005 server.

Tried launching the upgrade on the BES and got as far as SQL backup (successful) only to then be informed that the process couldn't upgrade the DB.

BES service account has got dbowner rights on the BESMgmt DB. My admin account has the same.

Question - is the DB now stuffed and does it need to be restored?? Is there a way I can tell this?

going forward...

What's the best method...

1) get rights upped to sysadmin and run upgrade again?

2) upgrade the DB first, using "createdb besmgmt.cfg". does this also need sysadmin?


please help!

Thanks,

Chris.

[gibson_hg]

You can make the BESAdmin a server admin and try again. That is what you need for the upgrade.

Once completed you can take the serveradmin role away.

[knottyrope]

Hope you did not do the upgrade with your admin account.

It has to be done with the besadmin account.

[ashleyneiltaylor]

Doesn't the BES computer account need to have system administrator priviledges on the BESMgmt DB?

[gibson_hg]

The BESAdmin account needs serveradmin role in SQL in order to upgrade the DB. Other than that DBOwner is all the accounts needs for day-to-day use.

Systemadmin is needed only if you use MDSS, not to be confused with MDS-CS

[ctpuk]

Thanks to everyone for the responses.

gibson_hg - you're a legend, as always!

knottyrope - I was doing the upgrade with the bes service account.

Going to be retrying the upgrade again tomorrow with a DBA on standby to make permissions changes.

With regards role based administration on bes 4.1 - do you need permanent SA rights for that?

Thanks again,

Chris.

[gibson_hg]

In order for role based administration to work you will need to have the BESAdmin account added to the systemadmin role in SQL, which is not a full SA but is high up there.

Hope that answers your question.