I've got a bit of a problem. Since yesterday we are unable to consume a WCF service from our production environment.
We have an Oracle database, which consumes a c# asmx webservice we built ourselves. That webservice itself consumes a .NET wcf service.
One of the input fields to the WCF service is an XS:datetime field. That field now gives us errors.
When we invoke our own webservice from our test oracle environment, everything works fine, but when we invoke the same webservice from our production environment (which worked fine also before yesterday) we get an error from the WCF service stating that the format of the ScheduledDate parameter is wrong "5-Nov-2013 12:39".
I've used wireshark to determine what the call is to our own webservice and both are identical (from test and production). Unfortunately since the WCF is ssl encrypted with a certificate, I cannot read the request to that service.
In the service reference, the field is listed as a DateTime and in the xsd, it's a xs:datetime.
I'm kinda lost right now, does anyone have a clue where I might find the answer.
In a nutshell the soap request from the database appears to be the same, our own webservice is the same in both cases (no distinction between test and production), yet the resulting call to the WCF service seems to be different.
Anyone that could shed some ligth on this will be greatly appreciated.