matt40k Posted June 9, 2009 Posted June 9, 2009 From SupportNet: Dear Colleagues We have decided to delay the SIMS 2009 Main Release for between 5 and 10 working days. We are doing this in order to investigate and resolve an upgrade issue that some customers are reporting when applying patches to their SIMS system. Our initial investigations have shown that this problem could also affect upgrades to the June Main Release and therefore we need to address this problem now. The revised release date will be published on Supportnet as soon as possible. We apologise for the inconvenience that this may cause. Regards, Jonathan Wood SIMS Product Manager (Technical and Releases)
sarah09 Posted June 9, 2009 Posted June 9, 2009 I'm glad they are trying to fix this before the release!!
Sivadam Posted June 9, 2009 Posted June 9, 2009 Me too. The application of patch and upgrades issues arose as a by product of the new SIMS Homepage in March. Staff not logging off SIMS 'legally' are still logged in as ghosts the following day. I think the fact that their panels were still trying to address the database when their account was 'closed' has something to do with the problem. I don't want to keep having to convert to single user mode just to apply a patch and then have to convert back again to multi-user after applying the patch or upgrade! Graham, I hope you get it sorted quickly!
sarah09 Posted June 9, 2009 Posted June 9, 2009 If you disable tcpip in the sql configuration that works too instead of locking to single user
EduTech Posted June 9, 2009 Posted June 9, 2009 If you disable tcpip in the sql configuration that works too instead of locking to single user yeah thats what i did to get round it, our SMIS team gave us this little app that disabled all of the users except our admin login. problem was it then did not give us the option to enable this. i think it was down to us not using the sa account. but hey I just disabled the network card when i did the update! as then no bugger could connect hehe. --- another option might be to stop the services for SQL, but i dont know weather the update requires these services. James.
EduTech Posted June 9, 2009 Posted June 9, 2009 What was the problem? If you mean the problem users are getting when installing new patch's etc. Basically when applying any new updates/patches it attempts to lock the database, but if you have users still logged into sims this fails. (you used to be able to just end any sessions, but that dont do anything anymore as the sql account is still active) So the only way of stopping this error from happening is doing any of options above. so you can then successfully update sims. james -- So the error you were recieving latley when updating about the database being locked, ^^ that is why.
kmount Posted June 10, 2009 Posted June 10, 2009 Could be wrong but the last I heard removing the network cable during the upgrade wasn't supported because the server wasn't in it's normal environment. (Something about the network needing to be present and the S:\ mapped etc on the server even after solus had downloaded the packages). Not sure whether this was just best practice or enforced for some other reason. I used to struggle getting staff of of the system so we opted for 7am upgrades rather than fight for access.
rh91uk Posted June 10, 2009 Posted June 10, 2009 I am SO glad that they are sorting out the applying patches issue! I usually do it at 5pm and send a global email round saying the update will be done at that time, please be off SIMS. My back is covered, then!
apeo Posted June 10, 2009 Posted June 10, 2009 Yeah applying patch problem was annoying. SMIS told me how to get round it by locking it down to 1 admin user i.e. -m switch for MS SQL 2005 service.
matt40k Posted June 10, 2009 Author Posted June 10, 2009 Could be wrong but the last I heard removing the network cable during the upgrade wasn't supported because the server wasn't in it's normal environment. (Something about the network needing to be present and the S:\ mapped etc on the server even after solus had downloaded the packages). The "S drive" shouldn't be a network drive on the server, it should be a physical path so you have the correct access etc. I believe mr Edwards (Capita) recommend disabling TCP\IP which would kick off all the remote users, as EduTech etc said, Matt Griffin (SMIS) creating a tool that disables all the SIMS SQL accounts appart from the one user your applying the update as. I believe the issue is Capita uses the standard Microsoft command to lock the database into single user mode, ofcourse this doesn't appear to work (thanks Microsoft), so the new dbupgrade will disable all the users minus the current user. I think it's down to not being able to run SOLUS as the SA user. I tend to find download only via SOLUS then manually upgrade via dbupgrade with the SA works. Still looooads more hassle. Bit strange as you can use the SA user for FMS but not SIMS?! Go figure!!
matt40k Posted June 10, 2009 Author Posted June 10, 2009 Matt, I posted the KB for this on SupportNet. What? :confussed:
wesleyw Posted June 10, 2009 Posted June 10, 2009 @EduTech: You'll need the SQL Server Instance running otherwise it won't be able to apply to changes to the database that runs inside the instance. A few years back removing the network cable actually stopped the upgrade from performing (Strangely you could plug it into a switch that wasn't conencted to anything else so the network would look like it's there but without anyone being able to access it!) Wes
Sivadam Posted June 10, 2009 Posted June 10, 2009 Sorry Matt - it's me that's confused! I actually gave the KB to our Technical Staff. I didn't post it on SupportNet. I just explained the issue above. It's senility setting in!
EduTech Posted June 10, 2009 Posted June 10, 2009 @EduTech: You'll need the SQL Server Instance running otherwise it won't be able to apply to changes to the database that runs inside the instance. A few years back removing the network cable actually stopped the upgrade from performing (Strangely you could plug it into a switch that wasn't conencted to anything else so the network would look like it's there but without anyone being able to access it!) Wes With regards to the SQL Instance, I gathered that would not work but someone else said that would also get round the issue. i know not to take that kind of advice again ;-) (mentioning no names) As for Removing the Network Cable, i was unaware this would stop the upgrade thankfully the little app i was provided with by our SMIS team did the trick so i did not find this out. so thanks for clearing that up. At least it will be fixed in the next release. Cheers Wes James.
skunk Posted June 11, 2009 Posted June 11, 2009 I have to say that I backup SQL and then restart the SQL instance before I apply any patches or upgrades. This removes all of the users attached to the DB nicely and allows for a nice clean upgrade.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now