+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 17
MIS Systems Thread, incompatible database summer update in Technical; Just a heads up people, ran the summer update today same old "incompatible database" error, que techs manually do the ...
  1. #1
    RichB's Avatar
    Join Date
    Oct 2008
    Location
    A Nice School
    Posts
    399
    Thank Post
    142
    Thanked 51 Times in 38 Posts
    Rep Power
    70

    incompatible database summer update

    Just a heads up people, ran the summer update today same old "incompatible database" error, que techs manually do the update!!!

    Waste of time and effort are sims, they know the issue but dont solve it!

    Not got time to rant, 600 Pc's to sort!

    For those not knowing the fix you run the SimsApplicationSetup.exe in the simsroot folder.

  2. #2

    Steve21's Avatar
    Join Date
    Feb 2011
    Location
    Swindon
    Posts
    2,696
    Thank Post
    335
    Thanked 515 Times in 483 Posts
    Rep Power
    179
    That's just when the versions of server to client are different isn't it? aka somethings not deploying properly.

    Steve

  3. #3
    RichB's Avatar
    Join Date
    Oct 2008
    Location
    A Nice School
    Posts
    399
    Thank Post
    142
    Thanked 51 Times in 38 Posts
    Rep Power
    70
    Ours are the same, still got the issue had it 3 times now. Ever since they tried pushing solous 3 on me...

  4. #4

    Join Date
    Oct 2007
    Location
    Northamptonshire
    Posts
    311
    Thank Post
    20
    Thanked 82 Times in 69 Posts
    Rep Power
    44
    You could try running SimsApplicationSetup.exe from a GPO startup script to save doing it manually. Try the following (may need to adjust the SIMSDirectory bit):

    simsapplicationsetup.exe /S {QuietMode} {NoServerApps} [SIMSDirectory]="S:\SIMS"

  5. Thanks to Ashm from:

    RichB (25th July 2013)

  6. #5
    Cache's Avatar
    Join Date
    Apr 2008
    Location
    Cumbria
    Posts
    1,214
    Thank Post
    454
    Thanked 176 Times in 173 Posts
    Blog Entries
    3
    Rep Power
    64
    Quote Originally Posted by RichB View Post
    Ours are the same, still got the issue had it 3 times now. Ever since they tried pushing solous 3 on me...
    That might explain your problem.

    Are you using Solus 3 to deploy the updates or have you got Solus 3 installed on your clients and your doing the updates through Solus 2?

    If you have the Solus3 agent installed on a pc and are using Solus2 to deploy the updates on your server, then the Solus3 aspect of it disables SimsLoad.exe from checking the server for updates (hence having to manually update it) - this is the only way I can see of your solution of manually updating using SimsApplicationSetup working as that file no longer gets updated when you start using Solus3.

    If not, how was Solus3 pushed on you and how does it currently sit in your network?
    Last edited by Cache; 25th July 2013 at 11:25 AM.

  7. #6
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 490 Times in 375 Posts
    Rep Power
    0
    Quote Originally Posted by RichB View Post
    Ours are the same, still got the issue had it 3 times now. Ever since they tried pushing solous 3 on me...
    Bingo. There's your problem right there.

    @Ashm - No good once SOLUS3 is in place. The setups folder becomes obsolete and is not updated.

    Check to make sure ALL of your SIMS clients are defined within the SOLUS3 SIMS Client channel, otherwise they won't get SIMS upgrades. Also make sure they show as 'Online' in the UI. Keep aneye out for any communication error messages. Also, are you on the latest SOLUS3 release?

    Quote Originally Posted by RichB View Post
    For those not knowing the fix you run the SimsApplicationSetup.exe in the simsroot folder.
    I know when SOLUS3 gets put in a school, its a monster to get working, god knows I've spent many an hour pulling my hair out and cursing Capita over getting SOLUS3 working. However, running the SIMSApplicationSetup.exe from the Setups folder when your on SOLUS3 is a bit of a 'dirty' fix. The setups folder won't be around forever and I'm supposed that if you have SOLUS3 in school, you still get the upgrade via SOLUS2 too. It's upgrades like this that highlight issues with your setup, the environment, or SOLUS3 itself. Will running the SIMSApplicationSetup.exe get you up and running quickly? Yes. Will it help long term in making SOLUS3 more reliable for future upgrades? No. If you make changes to your environment, you'll only have to wait to the next upgrade to see if the changes have had any impact in deployment success.

    I've come to terms with the fact that no matter how much I wish for it, Capita will not be binning SOLUS3 and everyone will at some point have to get it in place no matter what. Take these opportunities to learn and correct your environment to ensure the next upgrade does not hurt as much.
    Last edited by Rawns; 25th July 2013 at 11:43 AM.

  8. #7
    MrMat's Avatar
    Join Date
    Jul 2013
    Location
    Solihull
    Posts
    157
    Thank Post
    17
    Thanked 34 Times in 26 Posts
    Rep Power
    27
    We've just had to deal with an abundance on Incompatible database errors after upgrading about 60 schools via Solus 3. As mentioned above this error is purely done to the workstation being 'out of date' in comparison to the server.

    To resolve these errors we first tried to redeploy to see if that picked up any that were missed.

    We then asked each school to create a list of badge numbers for those workstations that still werent working (there were two of us doing this and we split our upgrades so we had a maximum of 10 going per night over 6 days to soften the blow). We then checked these badge numbers to see if they were listed in our deployment service.

    If they werent listed in the DS we simply added them to SOLUS. The agent downloads and the upgrade goes through.

    If they were listed but still werent working it was usually because users either didn't see the warning upgrade message or just decided to ignore it completely and leave SIMS open. If SIMS is left open when the upgrade is due to go through the SIMS.net folder cannot be accessed and the upgrade will fail (obvious comment is obvious).

    To resolve these - First find these comps in the Deployment Service and check the version number (view agent details). Important note, more often than not these workstations will still display 'Update was successfully installed' even though they have in fact failed (good old Capita eh). Get the user to get out of SIMS and then redeploy. Alternatively, get the user out of SIMS, open network path in explorer, locate the SIMS.Net folder and either delete it or rename it to 'SIMS.net old' or something similar, then connect to that workstations Services and restart the SOLUS3 agent service. The agent will then realise there's no SIMS.net folder and will download and install the correct version.

    For us at least (besides a few abnormalities) SOLUS3 worked exactly as it should have and the vast majority of problems were down to user error or outdated information.
    Last edited by MrMat; 25th July 2013 at 01:30 PM.

  9. #8
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 490 Times in 375 Posts
    Rep Power
    0
    Quote Originally Posted by MrMat View Post
    If they were listed but still werent working it was usually because users either didn't see the warning upgrade message or just decided to ignore it completely and leave SIMS open. If SIMS is left open when the upgrade is due to go through the SIMS.net folder cannot be accessed and the upgrade will fail (obvious comment is obvious).

    To resolve these - First find these comps in the Deployment Service and check the version number (view agent details). Important note, more often than not these workstations will still display 'Update was successfully installed' even though they have in fact failed (good old Capita eh). Get the user to get out of SIMS and then redeploy. Alternatively, get the user out of SIMS, open network path in explorer, locate the SIMS.Net folder and either delete it or rename it to 'SIMS.net old' or something similar, then connect to that workstations Services and restart the SOLUS3 agent service. The agent will then realise there's no SIMS.net folder and will download and install the correct version.
    You may be interested to know that if a user does have/leave SIMS .net open when the upgrade goes though on the workstation, the upgrade will actually complete successfully after a reboot, hence SOLUS3 returning the result of "Update successfully installed". It's a bit of a grey area because like you said, if you look at the agent info for a device and look at the version of SIMS .net, it will still show the version that has been left open, rather then the version that will be applied after the user reboots their device. But if you do see this, tell the user to reboot their workstation and when they try SIMS again, it will be working.
    Last edited by Rawns; 25th July 2013 at 01:41 PM.

  10. Thanks to Rawns from:

    Cache (25th July 2013)

  11. #9
    MrMat's Avatar
    Join Date
    Jul 2013
    Location
    Solihull
    Posts
    157
    Thank Post
    17
    Thanked 34 Times in 26 Posts
    Rep Power
    27
    Quote Originally Posted by Rawns View Post
    You may be interested to know that if a user does have/leave SIMS .net open when the upgrade goes though on the workstation, the upgrade will actually complete successfully after a reboot, hence SOLUS3 returning the result of "Update successfully installed". It's a bit of a grey area because like you said, if you look at the agent info for a device and look at the version of SIMS .net, it will still show the version that has been left open, rather then the version that will be applied after the user reboots their device. But if you do see this, tell the user to reboot their workstation and when they try SIMS again, it will be working.
    Aha. I did not know that although actually now you've mentioned it it's obvious really as it's essentially doing the same thing i.e. restarting the agent.

  12. #10
    RichB's Avatar
    Join Date
    Oct 2008
    Location
    A Nice School
    Posts
    399
    Thank Post
    142
    Thanked 51 Times in 38 Posts
    Rep Power
    70
    Quote Originally Posted by RichB View Post
    Ours are the same, still got the issue had it 3 times now. Ever since they tried pushing solous 3 on me...

    We have solus 3 but we dont use it, it has one PC attached. We use 2 and its always worked perfectly until they pushed 3 on us. Coincidence?

  13. #11

    matt40k's Avatar
    Join Date
    Jun 2008
    Location
    Ipswich
    Posts
    4,408
    Thank Post
    368
    Thanked 639 Times in 521 Posts
    Rep Power
    158
    So you upgrade via SOLUS2? Check a machine that doesn't upgrade. Open notepad then open SIMS.ini - check the SIMS Setups Directory is correct (ie the UNC path to the setups directory - such as \\server\capita$\setups). Next, check if the SOLUS3 agent is installed, if it is, remove it. I reckon someone been naughty and installed it on all your machines then removed from the UI, but not actually uninstalled it from all the clients.

  14. #12
    RichB's Avatar
    Join Date
    Oct 2008
    Location
    A Nice School
    Posts
    399
    Thank Post
    142
    Thanked 51 Times in 38 Posts
    Rep Power
    70
    I just use AB tutor log onto all machines as admin, and run the SimsSetupApplication.exe using a macro 30 minute job, then reboot them all. The fix is simple its capita that you go around in circles with beacuse they know the fault and do nothing about it.

    This video always sums it up...

    Hitler Apply's The Sim's Spring Upgrade - YouTube

  15. #13

    matt40k's Avatar
    Join Date
    Jun 2008
    Location
    Ipswich
    Posts
    4,408
    Thank Post
    368
    Thanked 639 Times in 521 Posts
    Rep Power
    158
    Just look... personally I'd rather not have to do loads of boring repetitive work. If it does have the S3 agent installed, removing it will fix it. Assuming the sims.ini hasn't been mangled.

    Yer saw the video, kinda funny, but rather sad at the same time - I mean IT folk standing in the way of progress?? Bah, give me the new stuff any day, especially when it comes with nice new hardware as well lol

  16. #14
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 490 Times in 375 Posts
    Rep Power
    0
    Quote Originally Posted by matt40k View Post
    I mean IT folk standing in the way of progress??
    If SOLUS3 is progress, then I want no part in IT.

    If you want me, I'll be living as a hermit on a small island off Scotland and you can contact me with smoke signals....

  17. #15

    matt40k's Avatar
    Join Date
    Jun 2008
    Location
    Ipswich
    Posts
    4,408
    Thank Post
    368
    Thanked 639 Times in 521 Posts
    Rep Power
    158
    I think you're forgetting how bad SOLUS2 is...

    It's like when WinXP came out and people said how awesome Win98 was.

    (Sorry, I've been told I'm not allowed to start a fire on the car park roof in attempt to transmit this message via smoke signals)

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Solus 3 incompatible database
    By Sammidge in forum MIS Systems
    Replies: 13
    Last Post: 6th July 2013, 12:20 PM
  2. [SIMS] Anybody use Intouch? Server getting hammered since Summer update
    By Eric_Bisto in forum MIS Systems
    Replies: 7
    Last Post: 24th September 2012, 03:11 PM
  3. Replies: 5
    Last Post: 18th January 2012, 02:40 PM
  4. [SIMS] FMS Incompatible Database
    By jlucas in forum MIS Systems
    Replies: 6
    Last Post: 1st October 2011, 01:07 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •