Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...
.NET Forum / ASP.NET / Web Services / May 2005

Tip: Looking for answers? Try searching our database.

Trouble after applying SP3

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mike - 26 Apr 2005 16:39 GMT
I am stumped. We were running WSE 2.0(SP2) on a Windows 2003 server without
a problem. I applied SP3 and now get this error:

General Information
*********************************************
Additional Info:
ExceptionManager.MachineName: ADDVMFM10
ExceptionManager.TimeStamp: 4/26/2005 11:33:14 AM
ExceptionManager.FullName: Microsoft.ApplicationBlocks.ExceptionManagement,
Version=1.0.1718.23183, Culture=neutral, PublicKeyToken=null
ExceptionManager.AppDomainName: /LM/W3SVC/1/Root/Leave-1-127590175775312500
ExceptionManager.ThreadIdentity:
ExceptionManager.WindowsIdentity: ADDVMFM10\D04M1s

1) Exception Information
*********************************************
Exception Type: System.Web.Services.Protocols.SoapHeaderException
Actor: http://10.13.0.134/DOAWebServices/Users.asmx
Code:
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d:InvalidSecurity
Detail: NULL
Message: An error was discovered processing the <Security> header
TargetSite: System.Object[]
ReadResponse(System.Web.Services.Protocols.SoapClientMessage,
System.Net.WebResponse, System.IO.Stream, Boolean)
HelpLink: NULL
Source: System.Web.Services

StackTrace Information
*********************************************
  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 leave.UsersWS.UsersWse.VerifyUser(String userID, String password) in
F:\WWWRoot\Leave\Web References\UsersWS\Reference.vb:line 280
  at leave.LogonBody.btnLogon_Click(Object sender, EventArgs e) in
F:\WWWRoot\Leave\LogonBody.ascx.vb:line 70.

Can anyone give me a starting point to track this down???

Thanks
Mike
Reply to this Message
Dilip Krishnan - 26 Apr 2005 18:42 GMT
Could you post the soap message thats causing this to fail on the server
side?

> I am stumped. We were running WSE 2.0(SP2) on a Windows 2003 server without
> a problem. I applied SP3 and now get this error:
[quoted text clipped - 40 lines]
> Thanks
> Mike

Signature

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dilip.krishnan AT apdiya DOT com

Reply to this Message
Mike - 26 Apr 2005 18:56 GMT
I'm kinda new to this so I'm not sure where to find the soap message.
Our web server calls the web service - each are on separate boxes. I have
checked the logs from the server that runs our web services and there are no
error messages there. I'm wondering if the call is even getting to that
server from the web front end. Is there a way to check that - and where do I
find the soap message?

> Could you post the soap message thats causing this to fail on the server
> side?
[quoted text clipped - 45 lines]
>> Thanks
>> Mike
Reply to this Message
Mike - 27 Apr 2005 18:43 GMT
Dilip,

I can post what I think are the SOAP messages. I set up an input and output
trace - is that the SOAP you are referring to?
Question about it, I have been looking through it and there are calls to
"localhost" as well as to the IP address of the web services server. Are
they suppose to be there?

Thanks
MIke

> Could you post the soap message thats causing this to fail on the server
> side?
[quoted text clipped - 45 lines]
>> Thanks
>> Mike
Reply to this Message
Mike - 27 Apr 2005 20:53 GMT
Dilip,

Here is the SOAP fault info I am getting on the Web Services server...

 <soap:Envelope
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Header>
     <wsa:Action>http://schemas.xmlsoap.org/ws/2004/03/addressing/fault</wsa:Action>
     <wsa:MessageID>uuid:257e6f7a-74dc-4bcd-b9b0-be3fadbcd9d7</wsa:MessageID>
     <wsa:RelatesTo>uuid:edcce820-183e-4b92-8f44-e475b9e92e7b</wsa:RelatesTo>
     <wsa:To>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:To>
     <wsse:Security>
       <wsu:Timestamp
wsu:Id="Timestamp-25b95b3b-3624-4248-b5d4-d853167e2ff2">
         <wsu:Created>2005-04-27T19:12:06Z</wsu:Created>
         <wsu:Expires>2005-04-27T19:17:06Z</wsu:Expires>
       </wsu:Timestamp>
     </wsse:Security>
   </soap:Header>
   <soap:Body>
     <soap:Fault>
       <faultcode
xmlns:code="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d">code:InvalidSecurity</faultcode>
       <faultstring>Microsoft.Web.Services2.Security.SecurityFault: An
error was discovered processing the &lt;Security&gt; header ---&gt;
System.Exception: Creation time in the timestamp can not be in the future.
  --- End of inner exception stack trace ---
  at Microsoft.Web.Services2.Security.Utility.Timestamp.CheckValid()
  at Microsoft.Web.Services2.Security.Utility.Timestamp.LoadXml(XmlElement
element)
  at Microsoft.Web.Services2.Security.Utility.Timestamp..ctor(XmlElement
element)
  at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element)
  at
Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope
envelope)
  at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope
envelope)
  at
Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapServerMessage
message)</faultstring>
       <faultactor>http://10.13.0.134/DOAWebServices/Users.asmx</faultactor>
     </soap:Fault>
   </soap:Body>
 </soap:Envelope>

Thanks for any help you can send my way!!
Mike

>> I am stumped. We were running WSE 2.0(SP2) on a Windows 2003 server
>> without a problem. I applied SP3 and now get this error:
[quoted text clipped - 42 lines]
>> Thanks
>> Mike
Reply to this Message
ep - 27 Apr 2005 21:27 GMT
are your clocks synced up?

> Dilip,
>
> Here is the SOAP fault info I am getting on the Web Services server...
>
>   <soap:Envelope
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
ty-secext-1.0.xsd"

xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
y-utility-1.0.xsd"
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
>     <soap:Header>

<wsa:Action>http://schemas.xmlsoap.org/ws/2004/03/addressing/fault</wsa:Acti
on>

<wsa:MessageID>uuid:257e6f7a-74dc-4bcd-b9b0-be3fadbcd9d7</wsa:MessageID>

<wsa:RelatesTo>uuid:edcce820-183e-4b92-8f44-e475b9e92e7b</wsa:RelatesTo>

<wsa:To>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa
:To>
>       <wsse:Security>
[quoted text clipped - 8 lines]
>       <soap:Fault>
>         <faultcode

xmlns:code="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
ty-secext-1.0.xsd">code:InvalidSecurity</faultcode>
>         <faultstring>Microsoft.Web.Services2.Security.SecurityFault: An
> error was discovered processing the &lt;Security&gt; header ---&gt;
> System.Exception: Creation time in the timestamp can not be in the future.
>    --- End of inner exception stack trace ---
>    at Microsoft.Web.Services2.Security.Utility.Timestamp.CheckValid()
>    at
Microsoft.Web.Services2.Security.Utility.Timestamp.LoadXml(XmlElement
> element)
>    at Microsoft.Web.Services2.Security.Utility.Timestamp..ctor(XmlElement
> element)
>    at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element)
>    at

Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnve
lope
> envelope)
>    at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope
> envelope)
>    at

Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapSer
verMessage
> message)</faultstring>

<faultactor>http://10.13.0.134/DOAWebServices/Users.asmx</faultactor>
>       </soap:Fault>
>     </soap:Body>
[quoted text clipped - 24 lines]
> >> Actor: http://10.13.0.134/DOAWebServices/Users.asmx
> >> Code:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d:InvalidSecurity
> >> Detail: NULL
> >> Message: An error was discovered processing the <Security> header
[quoted text clipped - 7 lines]
> >> *********************************************
> >>    at

System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
Message
> >> message, WebResponse response, Stream responseStream, Boolean asyncCall)
> >>    at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> >> methodName, Object[] parameters)
> >>    at leave.UsersWS.UsersWse.VerifyUser(String userID, String password)
[quoted text clipped - 6 lines]
> >> Thanks
> >> Mike
Reply to this Message
Mike - 27 Apr 2005 23:24 GMT
Our web server sits in a different segment from te application server that
runs our web services. Our "trusted" segment is in our domain and the web
server is not. Chances are they are not exactly the same.
What kind of problem are we talking about here?

> are your clocks synced up?
>
[quoted text clipped - 123 lines]
>> >> Thanks
>> >> Mike
Reply to this Message
Mike - 28 Apr 2005 12:35 GMT
Brilliant! The web server was 2 minutes ahead of the application server.

> are your clocks synced up?
>
[quoted text clipped - 123 lines]
>> >> Thanks
>> >> Mike
Reply to this Message
SA - 04 May 2005 00:18 GMT
Mike:

To avoid this, you can probably still get Windows to sync your clocks, even
if you web server is not in the domain. You will need to open up the SNTP
port on the firewall between both networks

On the web server:

net time /setsntp:<domain controller IP>

Signature

Sven.

> Brilliant! The web server was 2 minutes ahead of the application server.
>
[quoted text clipped - 6 lines]
> >>   <soap:Envelope
> >> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
> > ty-secext-1.0.xsd"

xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
> > y-utility-1.0.xsd"
> >> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> >>     <soap:Header>

<wsa:Action>http://schemas.xmlsoap.org/ws/2004/03/addressing/fault</wsa:Acti
> > on>
> >>
> > <wsa:MessageID>uuid:257e6f7a-74dc-4bcd-b9b0-be3fadbcd9d7</wsa:MessageID>
> >>
> > <wsa:RelatesTo>uuid:edcce820-183e-4b92-8f44-e475b9e92e7b</wsa:RelatesTo>

<wsa:To>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa
> > :To>
> >>       <wsse:Security>
[quoted text clipped - 8 lines]
> >>       <soap:Fault>
> >>         <faultcode

xmlns:code="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
> > ty-secext-1.0.xsd">code:InvalidSecurity</faultcode>
> >>         <faultstring>Microsoft.Web.Services2.Security.SecurityFault: An
[quoted text clipped - 7 lines]
> >> element)
> >>    at
Microsoft.Web.Services2.Security.Utility.Timestamp..ctor(XmlElement
> >> element)
> >>    at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement
> > element)
> >>    at

Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnve
> > lope
> >> envelope)
> >>    at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope
> >> envelope)
> >>    at

Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapSer
> > verMessage
> >> message)</faultstring>
[quoted text clipped - 29 lines]
> >> >> Actor: http://10.13.0.134/DOAWebServices/Users.asmx
> >> >> Code:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d:InvalidSecurity
> >> >> Detail: NULL
> >> >> Message: An error was discovered processing the <Security> header
[quoted text clipped - 7 lines]
> >> >> *********************************************
> >> >>    at

System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
> > Message
> >> >> message, WebResponse response, Stream responseStream, Boolean
[quoted text clipped - 12 lines]
> >> >> Thanks
> >> >> Mike
Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.