November Update

[Simcfc73]

Joy of joys, its ******** up Sims for a change.

 

Timed out connection, no one can log in and the upgrade won't complete because of a unhandled error message.

 

Can't wait till they open at 9 so I can talk to someone who will take my number and then forget about me.

[tech_guy]

Well, after all the hoo-hah over us having to be getting ready in time for the "all-singing, all-dancin' biggy-wiggy stupendous November update" we've heard nothing from the LEA support team and it's all gone strangely very quiet........

[localzuk]

Well, after all the hoo-hah over us having to be getting ready in time for the "all-singing, all-dancin' biggy-wiggy stupendous November update" we've heard nothing from the LEA support team and it's all gone strangely very quiet........

 

Same down here...

[Bromcom_John]

Well it was only released late yesterday, give your LEA guys a chance.

[Simcfc73]

Managed to catch most of the workstation before they updated the clients.

 

Wish Sims would only push the updated clients on after the SQL has been successfully updated to avoid this stuff.

 

Now I'll have to track down the staff who were in too early for me to stop their computers updating.

[PhilNeal]

SIMS has to upgrade the workstation that you are on. It then updates the database - if that is successful it will then upgrade the remaining workstations.

 

By the sound of it the database thought it had upgraded.

[TechMonkey]

We've been told that it was held off until the 22nd. After the previous 3 delays.

[PhilNeal]

.. and that is true but we completed the additional work earlier that we thought possible.

[tech_guy]

Well it was only released late yesterday, give your LEA guys a chance.

 

How much time do they need fcs?

 

Only jokin' ;-)

[petectid]

Another upgrade, Yawn!!! Could Capita please develop a component in SIMS that will tell me who is connected to SIMS and that can stop users connecting during the upgrade process.

[Jawloms]

If you are using a 'Redirect' connect.ini on each workstation then simply rename the connect.ini on your S:\SIMS (or wherever) to something else and then no-one will be able to log in. Obviously this doesn't help you get people out in the first place and it's not a 'solution', but it may help!!

 

Stuart

[localzuk]

Well it was only released late yesterday, give your LEA guys a chance.

 

Well this is news to me - as we were not given any information about what was happening with the database update or the impending november update since the big panic 'you must do X Y AND Z' messages a while back.

[Oops_my_bad]

Only reasonable way of doing it is checking shares in use in computer management (but even then I dont think it shows "everything".

 

Because of this nonsense I have to do SIMS upgrades during the evening from home, because that's the only way you know for sure..

[moggy]

I plan to do the upgrade tomorrow. Has anyone been successful yet?

[cookie_monster]

No we have just done the update and it's messed up all of the stations, Capita suggest we rename the sims folder on each station and then run simsinst (all 100 of them). Great.

[Guest richard]

Haven't heard anything from our LEA................yet. But I know I'm not looking forward to this one as we had a whole load of problems with the September upgrade. Anyway all being this will be my last SIMS nightmare that I will have to deal with.

[Simcfc73]

No we have just done the update and it's messed up all of the stations, Capita suggest we rename the sims folder on each station and then run simsinst (all 100 of them). Great.

 

Only had to do it on 5 of mine. My initial error is now in the hands of the developers but sims is okay for the moment. There has been an issue with changing passwords in System Manager which throws up a Sims_Parent error which I think is related.

 

Created 20/11/2007

Last Updated 21/11/2007

 

--------------------------------------------------------------------------------

Affected Products SIMS .net Installation & Upgrade

--------------------------------------------------------------------------------

 

Notes When running the November 2007 upgrade you receive the following error:

 

Cannot drop the user sims_sims_slgadmin because it does not exist or you do not have permission

 

OR

 

Cannot drop the user sims_sims_PARENT because it does not exist or you do not have permission

[bossman]

We did the migration from SQL2000 to SQL2005 enterprise after wiping the server and installing windows 2003 R2 then updated all the msi packages and deployed all in one day and they all work fine just waiting to get my hands on the November update.

 

As PhilNeal says once the server has upgraded its database then the workstations will follow suit unless as in previous posts you change the connect.ini file oh BTW it's an RM CC3 network.

[ngregory_simsconsultant]

You can just rename the setups folder, if you want them to not upgrade to the next version.

[forcryingoutloud]

Just completed ours, went a treat, my SIMS Support Manager says .

[tech_guy]

Has anybody actually done THE famous November update yet? Our LEA has gone all quiet on us after all the kerfuffle over getting ready for it.

[Sylv3r]

The LEA has released it for us. I am planning on doing it at the weekend. I'll let you know how it goes.

[meastaugh1]

November went fine for me, along with the other five recommended patches (and five consecutive backups).

 

Also, did the FMS 6.91 migration at long last, which also went smoothly, but involved a lot of waiting around either for our finance people to run reconciliation reports, or for Capita to release an upgrade patch.