Unexpected WSE 2.0 errors in Event Log -- dotnet xml

Robbert van Geldrop
4/7/2006 1:53:02 AM

Hello,

We run a very stable and well functioning ASP.Net 1.1 webservice using WSE
2.0 sp 3.

Every now and then the following error appears in the system event log:

HTTP/ASMX Message Receive Failure: System.Xml.XmlException: This is an
unexpected token. The expected token is 'EndElement'. Line 1, position 4387.
at System.Xml.XmlTextReader.Read()
at Microsoft.Web.Services2.Xml.XmlSkipDTDReader.Read()
at System.Xml.XmlLoader.LoadCurrentNode()
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean
preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at Microsoft.Web.Services2.SoapEnvelope.Load(Stream stream)
at
Microsoft.Web.Services2.Messaging.SoapPlainFormatter.Microsoft.Web.Services2.Messaging.ISoapFormatter.Deserialize(Stream stream)
at
Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapServerMessage message)

What can I do about this?

--

Robbert van Geldrop
4/25/2006 8:08:02 AM

Hello Luke,

Debugging this will be hard, since so far we did not see an exception
attached to this logging behaviour, since it is not our own application that
logs this but WSE.

Is it possible to stop WSE from logging this error to the event log?

Regards,

--
rvangeldrop

[quoted text, click to view]

lukezhan NO[at]SPAM online.microsoft.com
4/26/2006 12:00:00 AM

WSE only will raise an exception to your web service. The Eventlog part
should be in your web service. You may check if your web service project
have any exception handling part and try block the exception there.

Luke Zhang
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Robbert van Geldrop
6/8/2006 11:26:02 AM

Hello Luke,

We have some more progression on this issue. The problem is caused by the
WebProxy on a client, that is not threadsafe. If the proxy is accessed by two
threads for signing and sending a SOAP Request the WSE interface has trouble
decoding the SOAP:XML on the server side. The WSE dll logs an entry to the
EventLog in that case. The SOAP-request never resolves and this means we were
unable to debug it, since nothing happened in our code.

It means that WSE 2.0 dll logs errors to the EventLog by itself. We do not
log anything at all.

I expect that you look into this to see if the logging of these errors to
the EventLog can be disabled (or redirected to a different log group). Can
you please look to this?

Kind regards,

--
rvangeldrop

[quoted text, click to view]

lukezhan NO[at]SPAM online.microsoft.com
6/9/2006 3:26:27 AM

Hello,

After searching more documents, I found a event og source "Microsoft WSE
2.0" will be created when WSE 2.0 is installed on a server. But I didn't
finda way to disable it. The only way I think is not to grant the
application the permission to write event log.

Regards,

Luke Zhang
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet xml

dotnet xml : Unexpected WSE 2.0 errors in Event Log