View Full Version : WSDL file cannot be reached
I've had great success with ShopWindow V1 and now V2. All went well until Friday, August 21, when I got this message:
"This account's Shop Window quota has less than 10% of it's api calls remaining."
Contacting support the quota was refreshed. But coincidentally, or consequently, (I don't know which) I immediately started to get an error on my ShopWindow page.
"WSDL accessible: NO ( The WSDL file cannot be reached at http://api.productserve.com/v2/ProductServeService?wsdl )"
(I still have V1 running in a separate directory and it, too, has now come up with a similar error message: "WSDL file cannot be loaded from [http://api.productserve.com/v1/ProductServeService?wsdl]"
My server provider says there have been no changes to my server or the php.
At the suggestion of ShopWindow support I downloaded a fresh copy of the client software, but this has not helped.
I have now been stuck for two weeks with a non-working Shop Window website and don't have enough techical knowledge to adjudicate between Shop Window support and UK2.net support as to where the problem lies.
Can anyone out there help as Shop Window support are blaming the server and the server support people are saying nothing has changed at their end? I appear to be caught in stalemate with neither party willing to provide support and my site remaining non-functional.
Thanks
Scotia
Jaded Studio
14-09-08, 18:27
I have had the same problem as described in your post. First off I had the Quota problem repeated over the page, then it simply started saying "WSDL accessible: NO ( The WSDL file cannot be reached at http://api.productserve.com/v2/ProductServeService?wsdl )". I am hosted with Heart Internet and don't believe it to be anything to do with the server. I think it is some kind of limitation within the Client software.
That certainly increases my suspicions that it was not coincidental that my ShopWindow pages went haywire following the quota reset. Did you manage to get things sorted?
I'm still caught with ShopWindow denying any problem with the system and my server supplier also saying nothing has changed at their end.
Hello guys,
OK this seems really strange and is certainly not anything that I have come across before.
Are you saying that since you both had quota increases that your sites have ceased to work since the increase stating the WSDL error?
Have either of you edited your sites in anyway during the quota increase period that could have caused this?
Have you raised support tickets? If so can you PM me the ticket numbers.
Can you PM me your affiliate ID's.
Can you PM me links to the relevant sites.
Without the above information then I am limited as to what I can actually investigate.
Regards
Just had the same thing happen to my site (failed WSDL check although not quota related).
When I contacted my host (who are usually excellent) I had this response:
The 3rd party software is using the remote execution URL script
which tries to changes directory, permissions and many more server side settings remotely.
and that is why it has been denied by security rules implemented on our server .
You will not be able to use this software in shared/reseller environment.
You will need to go for a semi-dedicated or VPS hosting for the same.
This is very concerning, not just for me but for all SW users.
Do we really need semi-dedicated/VPS for SW?
I know my host has been making some security changes recently (and presumably just caught up with my server) so I can see this being the case.
OK - I'm still using version 1.0 but I certainly don't want to put in all the effort to upgrade (it is planned!) just to find the same problem.
Any ideas/thoughts?
Bud
Hi Bud,
Thanks for your input here and also for your email... Ive passed on your comments to Ollie in our Dev team who will be responding to the points raised shortly.
Kind Regards,
Adrian
Hi George
I can confirm that ShopWindow worked perfectly until the quota was reset. I did no editing on the site after the quota reset and my server provider assures me nothing was changed at their end.
Immediately after the quota reset, the WSDL error started and the site has not worked since.
I have, as requested, supplied my Affiliate number and site URL by private message.
Regards
Ken
Hi guys.
Thank you for bringing this to our attention. I would like to clarify a few things and suggest a work around for the moment.
Firstly, the WSDL is fine. It would appear that there are no problems with the client itself accessing the WSDL on our servers. The problem seems to exist within the 'status.php' file.
To work around your issue for the moment please comment out the following lines from your status.php file:
# WSDL access
$sEcho.= '<li>WSDL accessible: ';
$aUrlParts = parse_url(API_WSDL);
$sRequest = "HEAD ".$aUrlParts['path'].'?'.$aUrlParts['query']." HTTP/1.1\r\n";
$sRequest .= "Host: ".$aUrlParts['host']."\r\n";
$sRequest .= "Connection: Close\r\n\r\n";
$rSocket = @fsockopen($aUrlParts['host'], 80);
@fwrite($rSocket, $sRequest);
// get first line and check HTTP response
if ( is_resource($rSocket) && strpos(trim(@fgets($rSocket)), '200 OK') !== false ) {
$sEcho.= '<span style="color:green; font-weight:bold;">YES</span>';
}
else {
$bError= true;
$sEcho.= '<span style="color:red; font-weight:bold;">NO</span>';
$sEcho.= '<span style="color:grey; font:10px;"> ( The WSDL file cannot be reached at '.API_WSDL.' ) </span>';
}
@fclose($rSocket);
$sEcho.= '</li>';
You can commet this out by adding /* and */ around the code as follows:
/*
# WSDL access
$sEcho.= '<li>WSDL accessible: ';
$aUrlParts = parse_url(API_WSDL);
$sRequest = "HEAD ".$aUrlParts['path'].'?'.$aUrlParts['query']." HTTP/1.1\r\n";
$sRequest .= "Host: ".$aUrlParts['host']."\r\n";
$sRequest .= "Connection: Close\r\n\r\n";
$rSocket = @fsockopen($aUrlParts['host'], 80);
@fwrite($rSocket, $sRequest);
// get first line and check HTTP response
if ( is_resource($rSocket) && strpos(trim(@fgets($rSocket)), '200 OK') !== false ) {
$sEcho.= '<span style="color:green; font-weight:bold;">YES</span>';
}
else {
$bError= true;
$sEcho.= '<span style="color:red; font-weight:bold;">NO</span>';
$sEcho.= '<span style="color:grey; font:10px;"> ( The WSDL file cannot be reached at '.API_WSDL.' ) </span>';
}
@fclose($rSocket);
$sEcho.= '</li>';
*/
We are currently working on a fix for the status.php file and will release this with the next update of the ShopWindow Client Software.
Apologies for the confusion caused.
Ollie
Hi Ollie
Thanks for the update, I accessed the status.php file as you suggest and altered the code with the /* and */.
It has cleared the WSDL error, but the page no longer seems to load. I have cleared the cache and tried two different browsers.
(I note that Shop Windows V1 says WSDL file cannot be loaded from [http://api.productserve.com/v1/ProductServeService?wsdl])
Any suggestions?
Ken