View Full Version : WSDL file cannot be loaded
WSDL file cannot be loaded from [http://api.productserve.com/v1/ProductServeService?wsdl]
The above sentence is what I get when I access my site. http://dolphindeal.com Can somebody help me setting up ShopWindow Please? I am new to all this and am lost. :confused:
Hi,
Try refer to this thread http://www.shopwindowforum.com/showthread.php?t=33 or use php 5 instead.
hope this helps.
Hi Karsin,
Thanks for the link. I have contacted the server support people and I had the reply below.
Thank you for contacting us.
I will need to ask the technicians regarding the WSDL file. As for the PHP 5
it is not installed on our servers, since we use the versions included with
RedHat Enterprise Linux (RHEL) - this means that it is running on a stable
code base with security patches backported into it. We will be upgrading PHP
when RHEL does.
Once I have an update from the technicians, I will email you with the
details.
Should the program work under the "RHEL"?
Any other views on this?
Thanks
Put the site on another server.
It saves messing about and waiting...
Put the site on another server.
It saves messing about and waiting...
How easy is to change server? Do I have to pay to be transfered on another server? Which one to go for?
Suggestions would be appreciated, please!
This is my current host's reply (easyspace.com) but I am a newbie and don't understand the process involved.
".... You will be able to specify mime type using
h.taccess if the problem is serving files with the .wsdl extension. Please
note that our servers do not support PHP 5 at the moment.
Should you have any further problems, please feel free to contact us."
Can anybody help on this?
Hi Franc,
We have used 1and1 Internet (http://order.1and1.co.uk/xml/order/Home;jsessionid=AEE745C626F34DEB3BF9E2CBBC596B87.T C33b?__reuse=1177007810118) for testing and this seems fine.
In order to move your site over you would have to purchase hosting from them.
I hope this helps, but any problems feel free to give me a call :)
Amo
Amarath Singh Sokhi
ShopWindow Integration Manager
Digital Window Ltd
amarath.sokhi@digitalwindow.com
Tel: 020 8269 4853
www.digitalwindow.com
Hi Franc,
I am using godaddy, but i would suggest you go for 1&1 uk as the best.
karsin
Hi Amo,
I have received an a reply from my server's tech. people and this is what they are saying:
"Hi Franco,
Thank you for contacting us.
The technicians have checked your site and I was informed that the error: [http://api.productserve.com/v1/ProductServeService?wsdl]
This means that your site was not able to load the software. Due to security reasons, we do not allow fopen for http://.. or ftp through PHP. This is most likely the problem.
Please consult with the software provider regarding this issue to see if there is anyway around our server policy.
Should you have any further problems, please feel free to contact us.
Best Regards,
Songwut Limcharoen
Technical Support Engineer"
I am disappointed to learn this now. It has taken one week for them to realize this! :eek:... ...:mad:
I hope this will at least be useful to other frustrated affiliates with the same problem.
Is anyway around this or will I need to change to 1and1?
Thanks,
Franco
Hi Franco,
Thank you for relaying that information back to all on this forum.
Im afraid there is no way around this as this problem only occurs for a small percentage of affiliates.
I reccommend changing over to 1and1 who do not restrict your use of PHP.
Thanks
Amo
Already done so! :)
Hope to have ShopWindow working (hard) soon.
Thank you for suggesting 1and1. The domain name is cheaper there too.
Franco
Thank you for replying Karsin!
Franco
Now that your with 1&1 remember to make use of 'webspace explorer' it makes uploading and organising files a breeze.
Jake
I actually use SmartFTP Client and I find it easy to use but I will have a look at "webspace explorer".
Thanks for the suggestion. :)
Could somebody please have a look down Freeola's PHP rules here. http://freeola.com/support/webspace_php.php
I too have been having WSDL problems (same problem as reported in this thread) and I'm wondering if it's down to the permissions settings at the bottom of the page?
Dave