Jump to content

Recommended Posts

Posted

solus error.JPG anyone seen this before ,

 

its the first time running solus 3 on this server we have up till now always used solus 2

 

any ideas whilst I wait for the helpdesk to get back to me?

Posted

Had a similar error with trying to upgrade to 3.9 - it refused to believe that 3.something was on for it to upgrade from.

 

In the end I think i installed solus 3.9 manually on the server, overwriting what was there, then carried on.

 

Petrr

Posted
Had that today. Funnily enough, since the update to 3.9 Solus had forgotten the SA password. Corrected it and problem was solved (also after "Get Target Version" or whatever it was on the database target.
  • Thanks 1
Posted
the agent on the server and all clients is 3.9.0.18 and that can talk on and has managed to upgrade itself from 3.8.53. its just that neither sims or fms will upgrade , ive checked the sa passwords ther all present an correct anything else to look at ? our support unit is being very slow today ;)
Posted
support remoted in and changed some permissiions on a few tables in sql and now its working fantastic im happy again

 

They like to keep a few tricks up their sleeve to justify the support contract...

Posted
We had that with the first big update following our SQL2008 to SQL2012 update, is was the sa user password as someone else mentioned, it returns a 0.0.0.0 version when it cannot get another response from the database.
Posted
Had that today. Funnily enough, since the update to 3.9 Solus had forgotten the SA password. Corrected it and problem was solved (also after "Get Target Version" or whatever it was on the database target.

 

^^

This is usually the answer to this issue.

 

It usually occurs if the SA password is changed and SOLUS 3 not updated to reflect that change.

 

Otherwise if the SA password is correct within SOLUS 3, then just doing the "Get Target Version" under "Environment | Agents | Targets" for the SIMS/FMS Database entry will normally resolve it.

 

IIRC - The permissions on the SQL table issue mentioned by @woodham is a hangover from a bad SOLUS 3.6 > 3.7 upgrade which Capita patched once SOLUS 3.7 was out, I'm guessing you never got the patch.

  • 4 weeks later...

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...