We got hit by DEP (Data Execution Prevention) described in here : https://forums.embarcadero.com/thread.jspa?threadID=109752

We got hit by DEP (Data Execution Prevention) described in here : https://forums.embarcadero.com/thread.jspa?threadID=109752

At the end of this thread you can see part of the madExcept error report we got : http://forum.madshi.net/viewtopic.php?f=4&t=27582

We use latest Delphi and seems that they would have fixed this by now in HTTPRIO components, but maybe not.

Someone made patch at D2007 era http://cc.embarcadero.com/item/24535 but it is quite old.

Any ideas how to get around this or should we even see this error on the SOAP call.

We can get around this if customer wiling/able disable DEP on that Windows Server installation (This is Desktop App, and that is only customer that needs to run it on a server platform).

What other ways are around this?
https://forums.embarcadero.com/thread.jspa?threadID=109752

Comments

  1. Tommi Prami Is that the right link? It's to a post about a "random" crash with no known cause. If you know the cause, please make a SSCCE as Jeroen asks, and file a QP report. If you post the number here I'll make sure it's looked at.

    ReplyDelete
  2. OK, there was two incidents on this now. Always it seems to be related to the getting Adapter addresses from DHCP (etc).

    Might have nothing to do with the DEP after all. Some others had had problems with DEP with similar error messages.

    Installed Windows Server 2008 R2 and no issues so far. Might be very hard to find actual cause. Might be madExcept bug , related to some policy etc that it does not get the Adapter addresses etc.

    In anyways, I am all ears if someone have any idea what to check.

    Oh, disabled the ipv4 from the local network of that server virtual machine. and program worked fine.

    ReplyDelete

Post a Comment