Jump to content

Recommended Posts

Posted

Well i thought id ask on here rather than ringing capita its self to see if you could give me a quick reply.

 

Ive downloaded the updates through solus 3 but when deploying them it fails saying an error occured with the deployment plan. Here is the log

 

2011-07-19 11:11:47.0602|CanExecutePlan()|Info|DS|Verifying deployment plan ffe548cf-5bdb-46f7-ac61-783d2b26e177.

2011-07-19 11:11:47.9196|Execute()|Info|DS|Calling proxy for package status check

2011-07-19 11:12:29.3878|Execute()|Error|DS|A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 213.129.90.213:80

2011-07-19 11:12:29.4034|Execute()|Error|DS|A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 213.129.90.213:80

 

From loking at that its like it cant connect to the ipaddress. The proxy part is blank in the settings as we use embc proxy and when i put that in it flags it red.

 

Any help would be welcomed.

Posted

If you need a proxy, but haven't put it in, then that's where the problem lies. I'm sure there was a similar issue not long ago, regarding proxy. Have you got the latest version of Solus3?

@matt40k is the resident expert who will know more...

Posted
It will check with Capita's webserver (http://213.129.90.213) to check the Patch\release is still avalible - ie no one has withdrawn it before it tries to install. Assuming it's v3.4, the proxy settings must be correct as you've registered the site. So it must be an issue between the server and Capita server. Try again later would be the best thing to try, unless you've changed them. Can you access the webserver from IE?
Posted

Its version 3.3 which this school paid capita to install. I know there are issues with this release so is it a case that 3.4 needs to go on to get this working?

 

Ended up downloading the update through solus2. Will try solus 3 at another school today and see how that goes.

Posted

Someone just posted on SupportNet:

"The reason for this issue is that during deployment the SOLUS 3 DS checks with our web-servers to confirm the package has not been withdrawn since the file has been downloaded. At this stage the account used to try and contact our web-server is the local system account (as this is what the SOLUS 3 DS runs under). To resolve this please ensure the local system account can bypass the schools proxy."

 

Run proxycfg -U

Posted
Well I just, and I do me just, done a clean install and it's worked fine, so it could be a proxy issue or something, log a call with them and let them figure it out. They will then remote in check the settings etc and then check the web traffic rather then us wonder around in the dark. I know they did have a problem but that appears to have been sorted.
Posted

Sorted it now matt. Capita did a remote and after about an hour he put a proxy exception in and it started working.

 

Now got another problem about tolerance not met on package.

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