Discussion:
The root element is missing
(too old to reply)
NetDeveloper
2009-03-31 16:33:03 UTC
Permalink
Hi I have a dev environment which I havent used in a while. Today to do some
support I went into it and no matter what mappoint object I try, I get the
error "The root element is missing". Why am I getting this error? Is it
authentication problems? Any help ASAP is appreciated.

My Environment: VS 2005
MapPoint URL: http://staging.mappoint.net/standard-30/mappoint.wsdl

The whole error is pasted below for reference:


System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> The root element is missing.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Bandag.MapServices.MapPointServices.FindServiceSoap.FindAddress(FindAddressSpecification
specification) in D:\MapServices\Web
References\MapPointServices\Reference.vb:line 545
NetDeveloper
2009-03-31 19:04:05 UTC
Permalink
UPDATE: The same code base works with Production MapPoint Production Web
Services but doesnt with the staging URL.

Has the staging URL changed? Please let me know if it is different.
Post by NetDeveloper
Hi I have a dev environment which I havent used in a while. Today to do some
support I went into it and no matter what mappoint object I try, I get the
error "The root element is missing". Why am I getting this error? Is it
authentication problems? Any help ASAP is appreciated.
My Environment: VS 2005
MapPoint URL: http://staging.mappoint.net/standard-30/mappoint.wsdl
System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> The root element is missing.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Bandag.MapServices.MapPointServices.FindServiceSoap.FindAddress(FindAddressSpecification
specification) in D:\MapServices\Web
References\MapPointServices\Reference.vb:line 545
Derek Chan
2009-04-01 23:30:11 UTC
Permalink
The staging URL you've posted is correct, I haven't experienced any issues
lately on my end.

Try deleting your web reference and adding it again, it's possible that you
need to regenerate your proxy classes (from using an old version of MWS).

Regards,
--
Infusion Development
http://www.infusion.com
Post by NetDeveloper
UPDATE: The same code base works with Production MapPoint Production Web
Services but doesnt with the staging URL.
Has the staging URL changed? Please let me know if it is different.
Post by NetDeveloper
Hi I have a dev environment which I havent used in a while. Today to do some
support I went into it and no matter what mappoint object I try, I get the
error "The root element is missing". Why am I getting this error? Is it
authentication problems? Any help ASAP is appreciated.
My Environment: VS 2005
MapPoint URL: http://staging.mappoint.net/standard-30/mappoint.wsdl
System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> The root element is missing.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Bandag.MapServices.MapPointServices.FindServiceSoap.FindAddress(FindAddressSpecification
specification) in D:\MapServices\Web
References\MapPointServices\Reference.vb:line 545
NetDeveloper
2009-04-02 19:41:02 UTC
Permalink
I have deleted the service and added it again and still run into the same
problem. What do you mean I have to regenerate the proxy classes? and how do
I do that or what steps do i need to take to achieve that? what do you mean
by the old MWS?

What I dont understand is, the same code base works when I delete the
staging URL and point to the production one.

Thanks for all your help.
Post by Derek Chan
The staging URL you've posted is correct, I haven't experienced any issues
lately on my end.
Try deleting your web reference and adding it again, it's possible that you
need to regenerate your proxy classes (from using an old version of MWS).
Regards,
--
Infusion Development
http://www.infusion.com
Derek Chan
2009-04-07 14:19:01 UTC
Permalink
Try downloading the staging .wsdl locally on your hard drive and then add web
reference from there. There's been known issues with VS 2005 "Add Web
Reference" when it comes to MWS.

Regards,
--
Infusion Development
http://www.infusion.com
Post by NetDeveloper
I have deleted the service and added it again and still run into the same
problem. What do you mean I have to regenerate the proxy classes? and how do
I do that or what steps do i need to take to achieve that? what do you mean
by the old MWS?
What I dont understand is, the same code base works when I delete the
staging URL and point to the production one.
Thanks for all your help.
Post by Derek Chan
The staging URL you've posted is correct, I haven't experienced any issues
lately on my end.
Try deleting your web reference and adding it again, it's possible that you
need to regenerate your proxy classes (from using an old version of MWS).
Regards,
--
Infusion Development
http://www.infusion.com
Loading...