SOLUS update failed

[wesleyw]

Trying to update sims via solus fails the error I get is attached any thoughts?

 

 

Wes

[kmount]

I assume you've followed the instructions and "tried again later" ?

[bossman]

It Looks like your LA support team haven't authorised the download as yet have you spoken to them or do you deal with Capita direct?

[Mcshammer_dj]

can you see the solus site manually??

[wesleyw]

I have tried again later

 

We do have single site status but have support from SMIS in Sandwell.

 

And I can see the SOLUS site manually (if that's the one that you can download the SOLUS setup file).

 

 

Wes

[dhicks]

Trying to update sims via solus fails the error I get is attached any thoughts?

 

Try again even later. The update server has probably simply got overloaded, with lots of people doing updates after the break and is waiting for someone to reboot it.

 

--

David Hicks

[matt40k]

Check you can access SOLUS Home - Capita Education Services. Check that SOLUS has the correct proxy settings.

 

Basically it can't connect Capita (central DB), it does this even before connecting to the mirror site (the place with the files). Might be worth asking Capita if your support license has been payed

[ninjabeaver]

Hey Wes,

 

We are getting the same problem here. Any news on how you fixed it?

[wesleyw]

Haven't as yet, downloaded off our support teams website.

 

 

Wes

[matt40k]

Check your proxy settings, check you address the address above, check you school details in SIMS\FMS, should be lea 3 digit code then 4 digit school code. If you contact Capita and get them to check you have a valid license as well.

[ninjabeaver]

@Wesleyw

 

Just found this. Norfolk LEA is behind a Squid Proxy I think.

 

Hi this post is as much informational as anything else.

Having recent problems with Solus2 not being able to contact schools manager to check for updates(Solus.log mentions http 417 error), Capita could only point me in the general direction of "we've no idea, we're all ok at this end, must be your end", well it was our Linux proxy server that had just been upgraded. Here's part of a transcript of the case log with Capita :-

"After a long hard look at various Proxy server logs, the problem turns out to be due to a system update that has occured in the last month. The version of Linux SQUID proxy server software we are using has been upgraded from 2.5 to 2.7 which now supports http 1.1, BUT needs an extra change in the squid configuration file, adding

ignore_expect_100 on

this works around the error allowing SOLUS2 updates to work.

for further info please see (Nabble - Squid - Users - Understanding Expect 100 default setting)

 

The other oddity is the way the proxy settings work in SOLUS2, if you set it to use NO PROXY, it infact uses the default proxy settings in Internet Explorer, this was somewhat misleading when we where trying to work out which settings it was using (the SOLUS.log clearly stated the settings it was using!)"

 

Hope this helps anyone in a similar situation,

 

Dave.