SIMS Patch through Solus 3 Tolerance not met for target

[rrrrr]

Trying to run "Patch To resolve the issue in cover where the remaining entries are not removed when the absence period is shortened" through solus 3

Getting an error "Tolerance not met for target Sims Database, Deployment stopping"

 

I have tried;

restarting server

re-entering SA username and password

made sure everyone was logged out

 

Couple of things I noticed in log file;

target id Sims-server reported target version number 3.62.232.0, expected target version is 0.0.0.0.|WaitForAgentResponse()

Why is it expecting version 0.0.0.0?

 

*** Checking tolerance for SIMS Database (32Bit) targets

We are running a 64bit server

 

Any ideas?

[Ghostgame]

Try downloading the patch again.

Its not an issue with your server.

 

Is this an old patch?

 

If it is you might need to ask your LA to authorise it to you again.

Some patches need to be upgraded so that they work with the latest SIMS release.

[rrrrr]

Try downloading the patch again.

Its not an issue with your server.

 

Is this an old patch?

 

If it is you might need to ask your LA to authorise it to you again.

Some patches need to be upgraded so that they work with the latest SIMS release.

 

No this patch is only been sent out for about 1 week.

LA have told me to try through dbattach, which I will try next week.

Just wanted to get to the bottom of the issue

[Ghostgame]

Check the server and database settings in SOLUS3 for SIMS targets.

If they are slightly out, you get the intolerance message.

[rrrrr]

Check the server and database settings in SOLUS3 for SIMS targets.

If they are slightly out, you get the intolerance message.

 

Environment>Targets>sims-server = version 7.164.21.1

Version of update is 1.8.221.1

 

is this where you mean?

[Ghostgame]

Yes, but don't look at the version.

Go through the Target definitions and make sure they are all correct.

 

Also make sure the SOLUS3 agent on the server is started in Services.msc

[rrrrr]

Yes, but don't look at the version.

Go through the Target definitions and make sure they are all correct.

 

Also make sure the SOLUS3 agent on the server is started in Services.msc

 

Sims database version looks correct : 3.62.232.0, but the patch seems to be looking for 0.0.0.0

Solus agent had not crashed and service was still running

our LA cleared out the C:\ProgramData\Capita\Solus3\Deployments\Packages folder and told me to retry

will retry next week

[Cazale]

Did you get anywhere with this? I'm seeing exactly the same issue at one school!

[CyberDrac]

The 0.0.0.0 error was where it couldn't determine the version due to not being able to talk to the server/software.

I don't know the exact fix, but my external SIMS support team worked through it and presented it back to me in a working state.

[Cazale]

I have seen that before, I think this is different though? As the person above, this says it expects version 0.0.0.0 (not that it finds 0.0.0.0). I think that is different to what you mean? (or is it?).

[CyberDrac]

I have seen that before, I think this is different though? As the person above, this says it expects version 0.0.0.0 (not that it finds 0.0.0.0). I think that is different to what you mean? (or is it?).

 

I think you're right, apologies for muddying the waters

[superfletch]

Sims-server reported target version number 3.62.232.0, expected target version is 0.0.0.0.|WaitForAgentResponse()

Why is it expecting version 0.0.0.0?

 

This - it's just dreadful wording, I can't get my head around it either.

 

 

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

 

 

As Ghostgame stated it could be that the patch is written for a specific version(s) of SIMS and that your SIMS database isn't on a matching version although I think that would raise a slightly different error.

 

More likely - this is down to one or more entries in the SOLUS 3 database where SIMS database version information is stored being either incorrect or unreadable by the SOLUS agent. If you log a support case with your SIMS Team, like for CyberDrac they should be able to dial in and edit the entry in the SOLUS 3 table to sort it out.