SIMS Upgrades Failures

[moggy]

I've just tried to do the December upgrade and it's failed.

 

As far back as I can recall (at least 2 years) only one upgrade has worked. We always finish up copying files around in the setup/temp and setup folder; running various .exes individually and on a number of occasions SIMS support has had to remote access in to fix the problem.

 

Does anyone else suffer the same?

 

I've raised it with SIMS, but no-one seems to want to try to find out what is wrong with our system to give us such trouble.

 

Thanks.

[sharkster]

we had the same trouble at my school, but it was simple, might not be the same for your's when updating. "the user must have local admin rights" i don't know if this will help but before i did this it looked as if it was updating fine then stopped half way when copying a pdf file.

[mrbenn]

we have the same problem when sims upgardes are run, although the December release wasnt as bad as some. It never runs properly on some machines and we end up doing it manually. It effects random machines each time, we have just put this down to sims being sims ...

[apeo]

@moggy: Cant say i've had your problem. Yes i've had failed upgrades before but its mostly been problems relating to logged on users that werent logged on. Quick question, is there a reason you 'need' the december upgrade. I only ask cause the Main Feb one is due.

 

@sharkster: In the client setup you will either need to run simsperm or assign users to Power User at most (unless you run FMS or something).

Edited February 6, 2008 by apeo

[PhilNeal]

Moggy - I can't trace your school. If you would like to let me know where you are I will follow this up.

[moggy]

Thanks for your responses. Does the December update have to be run before the Feb one, or can you simply run the Feb one and forget Dec?

[PhilNeal]

You can forget Dec!

[monty]

I always do my upgrades on the server and the only time it fails is when a user logs in during the upgrade. I now make a big issue of getting everyone out of sims, email to all staff, get office staff to ring all relevant people. Then check on SQL manager to see who is still in and VNC or use shutdown command to switch their computer off, they soon realise what is going on.