Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   ASP .Net Web Services (http://www.velocityreviews.com/forums/f64-asp-net-web-services.html)
-   -   Consume 2.0 webservice with VS2003 (http://www.velocityreviews.com/forums/t786294-consume-2-0-webservice-with-vs2003.html)

Roel 06-23-2006 09:11 AM

Consume 2.0 webservice with VS2003
 
Hi all,

I'm running a ASP.NET 2.0 webservice and when I consume it with an ASP.NET
2.0 webapp everything works fine.

When I try to access it with an ASP.NET 1.1 webapp I get the folowing error:

<exception>
The XML element named '' from namespace 'http://mynamespace.goes.here/' is
already present in the current scope. Use XML attributes to specify another
XML name or namespace for the element.

Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: The XML element named
'' from namespace 'http://mynamespace.goes.here/' is already present in the
current scope. Use XML attributes to specify another XML name or namespace
for the element.

</exception>

This error does not occur when I access the ASP.NET 2.0 webservice running
on the test-server so it seems like it's a configuration-difference on the
production-server.

Anyone got a clue?

Greetings,
Roel



namewitheldbyrequest@gmail.com 07-05-2006 03:05 PM

Re: Consume 2.0 webservice with VS2003
 
Have you solved this? I have the same problem and I can't figure it
out.

Bill

Roel wrote:
> Hi all,
>
> I'm running a ASP.NET 2.0 webservice and when I consume it with an ASP.NET
> 2.0 webapp everything works fine.
>
> When I try to access it with an ASP.NET 1.1 webapp I get the folowing error:
>
> <exception>
> The XML element named '' from namespace 'http://mynamespace.goes.here/' is
> already present in the current scope. Use XML attributes to specify another
> XML name or namespace for the element.
>
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
>
> Exception Details: System.InvalidOperationException: The XML element named
> '' from namespace 'http://mynamespace.goes.here/' is already present in the
> current scope. Use XML attributes to specify another XML name or namespace
> for the element.
>
> </exception>
>
> This error does not occur when I access the ASP.NET 2.0 webservice running
> on the test-server so it seems like it's a configuration-difference on the
> production-server.
>
> Anyone got a clue?
>
> Greetings,
> Roel



Roel 07-06-2006 06:35 AM

Re: Consume 2.0 webservice with VS2003
 
The problem was the DataTable which was returned by the webservice. When I
altered this to a DataSet object, it works in VS2003 and VS2005.

http://support.microsoft.com/default...b;en-us;306134

Kind regards,
Roel

<namewitheldbyrequest@gmail.com> wrote in message
news:1152111958.745295.222710@j8g2000cwa.googlegro ups.com...
> Have you solved this? I have the same problem and I can't figure it
> out.
>
> Bill
>
> Roel wrote:
>> Hi all,
>>
>> I'm running a ASP.NET 2.0 webservice and when I consume it with an
>> ASP.NET
>> 2.0 webapp everything works fine.
>>
>> When I try to access it with an ASP.NET 1.1 webapp I get the folowing
>> error:
>>
>> <exception>
>> The XML element named '' from namespace 'http://mynamespace.goes.here/'
>> is
>> already present in the current scope. Use XML attributes to specify
>> another
>> XML name or namespace for the element.
>>
>> Description: An unhandled exception occurred during the execution of the
>> current web request. Please review the stack trace for more information
>> about the error and where it originated in the code.
>>
>> Exception Details: System.InvalidOperationException: The XML element
>> named
>> '' from namespace 'http://mynamespace.goes.here/' is already present in
>> the
>> current scope. Use XML attributes to specify another XML name or
>> namespace
>> for the element.
>>
>> </exception>
>>
>> This error does not occur when I access the ASP.NET 2.0 webservice
>> running
>> on the test-server so it seems like it's a configuration-difference on
>> the
>> production-server.
>>
>> Anyone got a clue?
>>
>> Greetings,
>> Roel

>





All times are GMT. The time now is 09:58 PM.

Powered by vBulletin®. Copyright ©2000 - 2013, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.