SOLUS3 Forced Update Check Failing

[Shuriken1]

Morning All,

 

Well, I'm attempting my second proper update via SOLUS3 and feeling like I'm flying completely blind - pretty much just got told you can't use SOLUS2 any more, here's 3, go.

 

I've deployed out the Autumn 2 package and half of the client machines were off, which is fine. First question, is the SOLUS3 Agent intelligent enough to recognise that it missed an update when the client is next switched on and update? It seems they removed this check from the SIMS client loading process which baffles me, but I'm sure there's some over-complicated, backwards reason.

 

The next issue, I turned a client on to test my question above and it didn't do anything after sitting there for a few minutes, so I opened the SOLUS3 agent and clicked "Check for Updates". Almost immediately I received this message:

 

 

Given that it's talking about localhost I checked the firewall settings on the client, it's completely off for Domain (which is our normal setup) so that seems fine. Why it wants to connect back to itself makes me wonder whether I've misunderstood but it's off on the server too.

 

I've opened a call with Capita Support but I wasn't particularly encouraged by the response I got so I thought one of you knowledgeable people may be able to help me!

 

Thanks in advance.

[Bankesy]

Hello

 

Just out of curiosity did you do the SOLUS 3\SQL upgrade yourself or was a Capita engineer involved?

 

I've been using SOLUS 3 for a while and not come across that error message but I do know that my clients pick up an update when they are switched on if it was deployed while they were off. In this scenario my SOLUS 3 console usually tells me the update was partially successful.

 

I know that recently there was an update to SOLUS 3 itself and the SOLUS 3 agents, maybe it would be worth checking this.

 

The initial Autumn 2 update got pulled I believe and re-released so maybe just check that too.

 

Sorry if any of the above sounds like really simple advice.

[Shuriken1]

Hi Bankesy,

 

Thanks for your info. As it turns out Capita got back to me VERY quickly and spent over an hour on this. The Capita engineer wasn't sure what was going on either, albeit he tried hard. End result was/is to reinstall the client. He noticed that the latest status for the affected client on the SOLUS management UI showed it mid-way through installing the 3.8 agent update. I think this bodged update is what has caused my client not to update if they were deployed to whilst off so I think this was the root of both problems. Now currently updating 20 clients as quickly as I can in time for Monday morning!!

 

This was with Autumn 2, yeah.

 

So all resolved by Capita, impressed by their response I have to say. Might skip our county people next time and just go straight to them!

 

Anyway, thanks again for the help.

 

ps. Oh, I did the SOLUS 3 setup with very little info so entirely possible I messed something up.

Edited January 2, 2015 by Shuriken1

[elsiegee40]

Moved to MIS forum

[harriuk]

Hi.

 

This is what happened to us too. The fix was to completely uninstall the agent an reinstall it. I like the idea of Solus 3 and it has got a lot better, but, I have never managed a full deployment without any issues and we have been using it for around 2 possibly 3 years now!