[ctpuk]

Hi everyone,

I've tried to find answers to this in existing posts, but failed... either I'm not using the correct search terms, or the question hasn't been asked before (apologies if it has).

I'm upgrading from 4.1.6 to 4.1.7 and, in error, I selected the upgrade including MDSS.

The DB is on a shared server - which means the BES account doesn't have SA, it's just got approriate rights on the BESMgmt DB.

So, I've installed the update, updated the DB successfully and all the rest of it.

The problem I have now is I can't cancel the attempt to install MDSS. Every time I run setup (after a restart, etc) I get the "type the MDS integration service datebase name" dialog. If I try and create the DB, it fails, due to my insufficient SQL rights, if I say no to creating it, I get failed to connect to database. Seemingly, there's no way to "reset" the setup.

I've temporarily restored service by starting the services, and users are working ok (the main upgrade having worked), but I want to cancel this MDSS bit and render my server normal again (i.e. ready to receive future upgrades and complete this one successfully).

I'm trawling through process monitor logs to see if there are any obvious reg keys / files that the setup.exe process looks at to get installation progress, but wondered if anyone could advise on this?

I've done the obvious stuff like removing the install folder for the service pack, but this doesn't help... so it's obviously getting it's "installation progress report" from somewhere else.

Getting my SQL rights hiked up will be a nightmare... and not really an option at present.

Please help!

Chris.

[raindownsugar]

We saw this as well. If there is an error on the install on a shared SQL instance/db setup you have to have sa rights so that the setup process can write to the master error db. Get your SQL admin to give you temp sa rights and that setup will write the error codes and finish up. Most likely the errors aren't fatal to the setup but they have to be written.

[r007r]

Dude, It's in the installation guide that you require these rights. You need these permissions in order to update the master database with any new error codes, upgrade the schema of the BESMgmt database and also to create the MDSS and MDSS_DIS databases.

If you are using Windows Authentication then you will need to get the SysAdmins rights added to the BESAdmin service account or you can utilize the SA account.

Suck it up and contact the SQL Admin.