Re: WCF SOAP WSDL... Parsing Schema: element error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5 January 2011 13:11, etangle <shahid.mehmud@gmail.com> wrote:
>
> Dear Richard,
> Try to tracert gadm01wsrv01 to 04, I tested, and if entries in hosts file
> are true, it resolves to corresponding IP and traces route...
> Also, you can also check if endpoints are accessible by putting url in
> browser:
> http://84.235.63.38/MTReceiver/TSLMTRECEIVER.svc?xsd=xsd0
> http://84.235.63.38/MTReceiver/TSLMTRECEIVER.svc?xsd=xsd1
> http://84.235.63.38/MTReceiver/TSLMTRECEIVER.svc?xsd=xsd2
> Do you think if we use hostname gadm01wsrv01 to 04, they access different
> endpoints, as terminating url parameters xsd=xsd2 are same for gadm01wsrv02
> and gadm01wsrv03 (hosts are different)..

It's a windows issue. If you are using DNS Client, then the hosts file
isn't even read. I can confirm this using FILEMON.

tracert and ping both fail (when reading hosts or not). As I've said,
it is the fact that the names are just server names and not fully
qualified. Our network things "something" is really
"something.localdomain.local).

The end points all worked fine. So it looks like the same server can
be used for all of the xsds.

If the WSDL file (and xsd0) all used the IP address, I could probably
move forward.

-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY

-- 
PHP Soap Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[Index of Archives]     [PHP Home]     [PHP Users]     [Kernel Newbies]     [PHP Database]     [Yosemite]

  Powered by Linux