Jump to content

Recommended Posts

Posted

Good Morning,

 

I've been a tech in a school since october and everytime we have a SIMS update we have waves of machines coming in reporting "incompatible Database" the fix for this is extremely easy, Copy and Paste files across from a working machine over to a broken machine, but this takes a lot of time and resources away from other aspects of the network.

 

Instead of limping through every update and patching the leaks, i'm looking to fix Solus3 and its sims deployment.

 

I'm not completely ignorant as I have been through hours of material at home this weekend looking for a fix or even a suggestion and found nothing,

 

Any idea's?

 

I have a helpdesk call logged with the Sims Team over at county council offices.

 

Cheers,

Sam

Posted

Incompatible database shows when the client is a different version to the server.

 

E.g. Server gets updated client doesn't.

 

Are you sure you're deploying the updates to all clients, not just the server?

 

Steve

Posted
I think incompatible database usually relates to the connect.ini file not having the correct information in it. Compare a working machine ini file against a non working one as a first point of call. (At least thats what causes it here).
Posted

steve21 is correct

 

incompatible database is displayed when the client has not been ugraded

 

solus 3 is not working if this happens

 

goto your sims drive

 

find the setups folder

 

and rerun simsinst

 

this will reinstall sims with the correct version

 

100% sure solus is not working for you.

 

i had an issue where solus was pushing out the summer 2012 update instead of the latest just wondering if this is happening for you.

Posted

First thing to check is solus itself.

 

Do the clients have the solus clients installed. Is solus trying to push anything out to them? Are they even in the deployment group for SIMS clients?

Are the solus clients up to date, what does the deployment log tell you in the Solus 3 deployment console?

  • Thanks 2
Posted (edited)

Make sure that the server has an agent installed on it and is designated as a SIMS workstation in S3 (S3 needs to know which workstations have SIMS or FMS).

Check the firewall on the workstations to check that it is not blocking the upgrades.

 

Had a similar issue on this post.

Edited by Ghostgame
Posted

Incompatible database is an out of date client.

 

Everything that @synaesthesia said.

 

The most common problem we find is that users expect SIMS to be upgraded but find it's not been added into the SIMS Workstation Channel so gets missed.

 

Also, if the workstations are in the SOLUS3 UI, are they listed as "online" and on the correct agent version? If the agent is not running for whatever reason, again, the workstation will fail.

 

Also, SOLUS3 will only deploy to workstations if the upgrade against the server components has been successful. If it fails, workstations won't upgrade (and in theory, the database should not be updated either) but if you accidentally use SOLUS2, that could upgrade the database and cause the incompatable database issues.

 

It does sounds more though like your environment is not set up quite correctly though...

  • 4 weeks later...
Posted

SOLUS3 should also display the various version of SIMS that is available.

Ensure you are selecting the most recent version.

Incompatible DB is a result of the client not being up-to-date with the DB, not the other way around.

Posted

does SOLUS3 force the update to run though?

 

I know we have to make sure to go through Start-Programs-Sims-Sims to get it to run right, if you use a shortcut from your start bar, or desktop you'll get incompatible database.

 

I won't get SOLUS3 upgrade till next spring so I don't know how it handles the updates

Posted
does SOLUS3 force the update to run though?

 

I know we have to make sure to go through Start-Programs-Sims-Sims to get it to run right, if you use a shortcut from your start bar, or desktop you'll get incompatible database.

 

I won't get SOLUS3 upgrade till next spring so I don't know how it handles the updates

 

It pops up with a warning message, but yes it'll force the upgrade.

 

Doesn't need the user to do anything like Solus 2 does.

 

Steve

  • Thanks 1

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...