HRESULT 0x80072EE4, Native error 28037 - A request to send data to the computer running IIS has failed.


  • hello,

    i have seen this error on several occasions, and until now have been able to resolve it.

    i can connect to https://server/vdir/sqlcesa35.dll?diag from the device but can not connect to ?stats.
    ?diag returns:

    SQL Server Compact Modules Test
    sqlcerp35.dll SUCCESS 0x0 3.5.5692.0
    sqlcesa35.dll SUCCESS 0x0 3.5.5692.0

    Reconciler Test
    10.0 Database Reconciler FAILURE 0x80040154 <- we use sql 2005 so i guess that error is of no concern
    9.0 Database Reconciler SUCCESS 0x0

    also, vdir contains these files:


    the first two of these files have last modification flag set to the very specific moment at which the sync stopped syncing.
    i have also checked ssl certificate, which is fine. disabled it so sync can run over simple http, and still i was getting that error.

    this is happening on our very-soon-to-be-needed-online production environment, so the issue is critical to us. environment:

    1. web sync box:

    windows server 2008 x86 standard sp1 eng
    iis 7
    merge replication server tools x86 3.5.5692.0

    2. sql box:

    windows server 2008 x86 standard sp1 eng
    sql server 2005 sp3 cu2 (9.0.4211)

    3. separate box for AD


    Thursday, April 02, 2009 8:39 AM

All replies

  • Hi,

        SQL Server Compact replication is not supported using IIS7. One should install IIS6 backward compatibility components, if one wants to use IIS7 for sync. As you said, the error about 10.0 reconciler is not of concern, if you are using SQL 2005 publisher. But, only the stats page failing, is something unknown to me. I think you should try to re-install all Compact components, and also re-setup the virtual directory. Also, make sure all permissions on the required folders (IIS vdir folder and snapshot folder) are present for sync user to access.

        Please let us know, if this does not solve the problem for you.


    • Proposed as answer by UdayaBG Monday, April 06, 2009 8:20 AM
    • Unproposed as answer by kamil nowicki Monday, April 06, 2009 2:01 PM
    Sunday, April 05, 2009 8:54 AM
  • hi,

    iis6 compatibility components are installed, and the sync was working for a few weeks before that issue occurred.

    the problem was present last thursday, i took a day off on friday and today it's working again without touching anything.

    now ?stats load ok, sync from device is working. i didn't have the chance to follow your suggestion about reconfiguring with web sync wizard. 


    looks scary.




    Monday, April 06, 2009 1:24 PM
  • Hi,

        Ok. Just in case, you encounter this error, you can better troubleshoot using server agent logging on the IIS machine. When you get the sync failed and/or stats page not loading fine, please use the logging options to get more information. I think it is some setup issue, if not a network issue denying some requests and allowing others. I have never come across only stats not displaying and diag page showing up. Anyway, the link for server agent logging is at,

    • Marked as answer by kamil nowicki Monday, April 06, 2009 1:59 PM
    • Unmarked as answer by kamil nowicki Monday, April 06, 2009 2:00 PM
    • Marked as answer by kamil nowicki Monday, April 06, 2009 2:00 PM
    • Unmarked as answer by kamil nowicki Monday, April 06, 2009 2:01 PM
    • Marked as answer by kamil nowicki Monday, April 06, 2009 2:01 PM
    • Unmarked as answer by kamil nowicki Wednesday, June 24, 2009 10:54 AM
    Monday, April 06, 2009 1:32 PM
  • hi,

    the issue has returned only this time it was during application training for mobile users. i need to fix this ASAP.
    when the problem occurs extended logging for server tools shows:

    2009/06/24 10:13:02 Hr=00000000 Compression Level set to  6
    2009/06/24 10:15:30 Hr=00000000 Compression Level set to  6
    2009/06/24 10:15:41 Hr=00000000 Compression Level set to  6

    so it looks like just after starting a new sync session it is being dropped.
    according to google 0x80072EE4 is IIS error (?) ERROR_INTERNET_INTERNAL_ERROR.
    iis site log looks ok, firewall was off.

    when the issue occurs sqlcesa35.dll?stats page does not load and no one can sync.
    i can "fix it" by restarting entire server (site/iis restart doesn't cut it).

    Wednesday, June 24, 2009 10:54 AM
  • Hi,

        Not sure, but, if IIS is dropping some requests time to time, you can try increasing the connection retry options, as detailed here:

        But, if that does not solve, I suggest you file an issue with Support people, to make sure they can troubleshoot/fix the issue.

    Wednesday, June 24, 2009 7:29 PM
  • hi,

    thank you for answering again. once the problem starts no one can sync and every mobile device logs this exception, so it looks more like a server issue.
    rebooting just the web sync box is sufficient for the problem to go away for a few hours.


    • Edited by kamil nowicki Monday, June 29, 2009 7:42 AM i meant resetting the web sync box, not the publisher. doh.
    Thursday, June 25, 2009 7:06 AM
  • hello,

    i have noticed that the moment the sync stops working http.sys error log starts logging:

    2009-06-24 08:44:13 HTTP/1.1 POST /sync/sqlcesa35.dll - 2 Connection_Dropped DefaultAppPool
    2009-06-24 08:45:13 HTTP/1.1 POST /sync/sqlcesa35.dll - 2 Connection_Dropped DefaultAppPool

    following that trail i have found:

    "It is very unlikely that a default installation of IIS would close a connection to a client before the complete response message is sent. However, a custom ISAPI application that does not handle response messages correctly may cause a "Connection_Dropped" event message to be logged in the Httperr.log file."

    i have opened a support ticket and will update this thread with other info i will find.

    Thursday, June 25, 2009 9:25 AM
  • when i have turned off all offloading features on the nic, the problem started occurring more frequently but could be fixed by just recycling the server agent application pool in iis. it seems that outdated nic drivers were causing this.

    i have currently moved the iis from a separate box to the publisher which has those newer drivers and have never seen that error since.
    will post an update when i will have a chance to test once again on the same box with newer drivers.

    Monday, August 17, 2009 6:50 AM