Re: A request to send data to the computer running IIS has failed. NativeError 28037



(copy&paste from a previous reply about the same issue)

Does the error happen only when synching using GPRS? Can you test with other
remote options, like WiFi, to check if the error only happens with GPRS?

If so, try with a different mobile operator, and if you reach the conclusion
that it only happens synching with GPRS on one particular mobile operator,
contact them to know if they have implemented some changes on their network,
like installing some kind of security or compression tools, and if there is
a way to avoid them.

Here in Portugal, we had a customer who had that problem, that was fixed
using a different username provided by Vodafone to establish the GPRS
connection.

----

About your particular situation, if your are tryng to sync locally, try disabling firewalls, antivirus and other internet security software.

--

Alberto Silva
Mobile Devices MVP @pt
http://msmvps.com/AlbertoSilva

"Brian Williams" <williamsb@xxxxxxxxxxxx> wrote in message news:%23esllJoNHHA.4992@xxxxxxxxxxxxxxxxxxxxxxx
I have installed the the following Microsoft SQL Server 2005 Compact Edition files: (Released 11 Jan 2007)
Microsoft SQL Server 2005 Compact Edition Server Tools.msi
Microsoft SQL Server 2005 Compact Edition Developer Software Development Kit.msi
Microsoft SQL Server 2005 Compact Edition Tools for Visual Studio 2005 Service Pack 1.exe
Microsoft SQL Server 2005 Compact Edition.msi

I have created a publication (SQL Server 2005) and subscription (SQL Server Mobile 2005) via SQL Server Management Studio (SMS). I can connect to my SQL Server Mobile database in SMS and syncronise subscriptions with no problems.

I can at any time run http:// My IP Address/ Virtual Directoy Name /sqlcesa30.dll in my browser and get back:
"SQL Server Mobile Server Agent 3.0"

When I run the CE 5 Project in debug mode against SQL Server and IIS on the same box, I get Native Error 28037.
When I run the CE 5 Project in debug mode against SQL Server and IIS on a diferent Windows 2003 server I get the same Native Error 28037.

This is my code:





.



Relevant Pages

  • Re: [Error 28035] "Header information is either corrupted .." only with GPRS. Internet works. Why ?
    ... Vodafone for a better data handling in GPRS ... The only way to let the RDA work is to contact the operator and force ... I have a SQL Server 2000 SP3 installed on a Windows Server 2003 Small ... USING ActiveSync + Cable connection ...
    (microsoft.public.sqlserver.ce)
  • Re: did I installed CE successfully?
    ... When you find references to SQL Server Mobile 3.0, SQL Server 2005 Mobile Edition, SQL Server Everywhere or SQL Server Compact Edition, all of these refer to the same product, being the 'Compact' edition the latest official designation for the product, since all desktop limitations have been removed. ... apparently I was able to install compact edition successfully. ... when I try to connect from VS2005, and from SQL Server Management Studio it still says sql server mobile, instead of compact edition. ... In SQL Server Management Studio, in Object Explorer, click Connect, and then choose SQL Server Compact Edition. ...
    (microsoft.public.sqlserver.ce)
  • RE: Cannot connect using GPRS and System.Data.SQLClient to remote SQL
    ... While you can theoretically connect to a SQL Server database through GPRS ... If you really want to pursue a direct connection to SQL Server, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Cannot connect using GPRS and System.Data.SQLClient to remote SQL Server
    ... that needs to connect to a remote SQL Server 2000 database via GPRS. ... different connection string when connecting over GPRS than through ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Cannot connect using GPRS and System.Data.SQLClient to remote SQL
    ... When I try connecting to the SQL Server, SQLClient reports it cannot ... > While you can theoretically connect to a SQL Server database through GPRS ... > more detail on the specific connection error you are receiving. ...
    (microsoft.public.dotnet.framework.compactframework)

Loading