Topic
  • 3 replies
  • Latest Post - ‏2012-11-28T17:11:29Z by SystemAdmin
SystemAdmin
SystemAdmin
6772 Posts

Pinned topic Error: Unable to retrieve http://www.w3.org/2001/xml.xsd

‏2012-11-28T15:30:50Z |
We just upgraded our XI52 appliances to version 5 (5.0.0.3) firmware from 4.0.2.8. Though all the services came up and all seemed OK, we started getting errors on our Web Service Proxies. On some of our WSDL's, we are getting errors like:

There was an error while reading WSDL 'local:///WSDLs/XDS/XDS.b_DocumentRepository.wsdl'.
Error: Unable to retrieve http://www.w3.org/2001/xml.xsd.


In all broken cases, the problem is
Error: Unable to retrieve http://www.w3.org/2001/xml.xsd.
We only did the firmware upgrade, and haven't changed anything else. Any ideas on how to fix this?
Updated on 2014-03-25T02:45:33Z at 2014-03-25T02:45:33Z by iron-man
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Error: Unable to retrieve http://www.w3.org/2001/xml.xsd

    ‏2012-11-28T16:19:48Z  
    • Update ***

    With 2 identically configured appliances, the same exact firmware, the same exact WSDL files, one is reporting this error and the other is not.

    In an interesting twist, on another WSDL, both appliances report the problem.

    This is strange to say the least.
  • msiebler
    msiebler
    140 Posts

    Re: Error: Unable to retrieve http://www.w3.org/2001/xml.xsd

    ‏2012-11-28T16:48:06Z  
    • Update ***

    With 2 identically configured appliances, the same exact firmware, the same exact WSDL files, one is reporting this error and the other is not.

    In an interesting twist, on another WSDL, both appliances report the problem.

    This is strange to say the least.
    most likely its a routing issue ; do you have multiple default routes ? if so a reload can change the ordering. can both routes hit the internet ?
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Error: Unable to retrieve http://www.w3.org/2001/xml.xsd

    ‏2012-11-28T17:11:29Z  
    • msiebler
    • ‏2012-11-28T16:48:06Z
    most likely its a routing issue ; do you have multiple default routes ? if so a reload can change the ordering. can both routes hit the internet ?
    Actually, it seems to be related to some kind of read timeout during the reboot following the upgrade. I restarted the domain for all affected appliances and now they're just fine.