Peculiar error after migrating SIMS to SQLE2005

[Oops_my_bad]

Last night i did the sql changeover - all prereq's were fine, several dozen backups taken, process carried out smoothly. Everyone's happy And I can still login.

So this morning I run SOLUS for the September update. However part way through running it just bottoms out. After it finishes restoring i get the attached error

When running solus I am using a SQL login (my personal login which has sysman rights and always has). The database is running in mixed authentication mode as per Capita's guidelines

I can still use SIMS as normal using my login. It's just this damn september update that is failing

[PhilNeal]

I don't recognise this problem so please log a call.

[Oops_my_bad]

OK will do.. just thought I'd try here first

[Quatermass]

I just got that exact error too! SIMS fine, SQL fine, but September update procedure takes a successful backup, then crashes out and gives that screen. I've logged with LEA too but incredibly annoying! Argh!!!

[steve]

By any chance were you performing the update via remote desktop?

Had a similar error when using remote desktop, worked fine with VNC though.

[DMcCoy]

And actually on the server itself?

[steve]

DMcCoy is right, you must upgrade now only on the server:

IMPORTANT NOTES: The SIMS 2007 August Main Release should only be applied to existing installations by running SOLUS on the SIMS SQL Server. The changes to the Security Model for August mean that some database changes have to be registered on the server before dbUpgrade can be run. This can only be done by running the upgrade on the SIMS SQL Server. If users try to apply the upgrade by running SOLUS on a SIMS client, the upgrade will fail and the database will be rolled back to the previous version..

[Quatermass]

This wasn't via Remote Desktop or even VNC. It was on the server, direct. Yes, thanks, I did see the Capita caveat... it's in the September release notes too

[DMcCoy]

I know thats for august, but I'd run the september one on the server too

[Oops_my_bad]

I *always* do updates on the server. This was via dameware - which is just the same as being sat in front of the server so it's not like a TS session or anything. Ran it this morning too physically sat in front of the server and same issue.

[DMcCoy]

Something else broken then :|

I had 10 cases in 14 days this month. Something is always broken

[Quatermass]

Hi guys

I've just had a reply from my LEA about this. They tested our data and got similar problems, so sent it to Capita. Capita's final reply is that there is an "issue" in the current version of DBUpgrade - they are testing a fix which they hope to include in the November release (out 5/11/07). Sigh...

[Oops_my_bad]

November release (out 5/11/07)

Hmm.. I hope it's only a coincidence that it's out on guy fawkes :bom:

[Oops_my_bad]

Got this sorted

For anyone else having this error i removed the read only attribute of all files in the setups and setups\<random number> folder. Then i ran SOLUS and the database upgrade went ahead without problems and am now running the september update.

i would only do this AFTER you have tried out the things in KB73455 but for now I'm happy.. FMS migration next