I'm getting this error on one of the ASP pages of our site.
msxml3.dll error '80072efe'
The connection with the server was terminated abnormally
The error refers to this line in the ASP, which essentially is just posting some info back into a page after the user selects an option from the dropdown:
xmlHTTP.Send strFormData
I searched for a solution to the error and saw several responses which I didn't really understand. Some suggested adding SNAT to the server, some talked about using Server.Transfer and others talked about it being a Firewall issue. [I tried reconfiguring the Firewall to allow all incoming TCP connections to all ports. Didn't solve the issue]
I'm sort of inexperienced when it comes to server issues so I don't wanna make any changes in server configs or production DB unless there's a clear answer/solution to this. I'm running MS SQL Server Management Studio Express 2005.
Any help on this will be highly appreciated. Let me know if you need any other information.
Thanks.
Related
This will probably be an environmental issue but I'm stumped as where to start.
I'm attempting to call a a webservice on an external server in an asp.net web app while debugging in VS2008. The exact same code/project works on one machine calling the server but on another machine (my new one) it fails with the 400 Bad request (data is invalid) error.
Both machines are running Windows 7. What should I be looking for as differences in the two machines that could be contributing to this problem?
Edit Deleting the webreference in the project and re-creating the webreference had no effect
Update
I went to use Fidler2 to inpect the request and response which resulted in the error going away. Things are beginning to point to an internet proxy issue.
It's an Internet Proxy issue. The suspect machine had be configured to manually use a proxy server. Turning this off: Control Panel -> Internet Options -> Connections Tab -> Lan Settings Button, and enabling "Automatically detect settings" has fixed the problem.
All of a sudden on a working Windows 2003 server - ASP just up and quit serving pages?
I have a simple hello.asp script that reads:
http://www.icontrolwebstudio.com/hello.asp
And when I run it - I get:
msxml3.dll error '80072efe'
The connection with the server was terminated abnormally
/LM/W3SVC/7/Root/global.asa, line 63*
I also have a test.asp page that just has text in it:
Test - Page is running.
And I am getting the same error?
Not sure what the deal is, any help would be greatly appreciated?
Chris
The most common problem is your antivirus or firewall interfering with the connection or it can also be caused by a name resolution issue like when the host name resolves to 127.0.0.1 (via local) and the web server is bound to the public IP address only.
Last night my server admin upgraded us to SQL Server 2008, this morning I made the updates to our code to reflect the new server location in both my DBML as well as my webconfig. Running locally everything looked good, I migrated to my development server and once there our very first web service call started to fail with a '500 Internal Server Error'. The message returned when looking in firebug is simply:
"{"Message":"There was an error processing the request.","StackTrace":"","ExceptionType":""}"
Also when I attempt to just navigate to my web service directly in my browser it is giving me a 403 error. No firewall settings on my web-sever have changed to my knowledge the only known change is the SQL server upgrade.
I can't really come up with any reason why this would happen after a sql server change. Anybody have any ideas?
You might try checking the port you are connecting to.
I had this problem a few weeks ago where my admin upgraded and changed the port from the default 1433 to a different one.
Just a thought, hope this helps.
Before doing anything else: Connect to the new server using Management Studio on your machine (not from the sql server itself).
If this works, then look at your connection strings on your dev server to ensure they are correct.
If it doesn't work, go sit at the DBA's desk and kindly ask them to finish the server configuration. Namely: enabling TCP.
I just got IIS7 set up on a Windows Server 2008 R2 machine in VirtualBox. After doing so, I could not connect from any other client, though http://localhost worked. For that matter, I was unable to even ping the server.
After doing some research, I found that enabling File and Print Sharing on the server solved the problem, but surely there has to be a better way, and I would much prefer to learn to use the best method, rather than the easiest one.
What, specifically, should I do to enable both pinging of the server as well as access to the web server running on it?
Isn't it that the inbound web HTTP port is blocked by default? I'm not a server guru but can remember going to the firewall to allow it through. Should already be there.
Out of the box on Windows Server 2008/2008R2 firewall is installed and users cannot access resources or services on the server unless you configure exceptions to the firewall. There is one exception to this are services/resources on this server that you make available through the GUI tools (Initial Configuration Tasks Wizard, Server manager) - these automatically create firewall required exceptions for you.
So in your case either upon File and Print Sharing installation or upon using File and Print Sharing config wizard/Shared resource provision wizard (most likely the later) required firewall exception was created for you. The rule in question is: File and Printer Sharing (Echo Request – ICMPv4-In) - actually allows ping, but I guess Windows also uses it for network resources discovery and other things implied by the role you installed.
Nothing prevents you from not enabling File and Print Sharing and just enabling mentioned firewall exception manually.
I'm experiencing some really odd timeout issues when running a ASP.NET 2.0 project on Cassini on localhost, and I don't have enough data to get a clue of what's going on.
Is there a way to monitor localhost traffic to Cassini, either using some specific development tool or a general-purpose monitoring app such as fiddler?
Just to pre-empt some answers I'm already aware of:
Normally I can use the well-known dot-hack for using fiddler to monitor localhost traffic, but with Cassini I get the following error message in the browser:
[Fiddler] Connection to localhost. failed. Exception Text: No connection could be made because the target machine actively refused it ::1:3213
Fiddler also listens to localhost on http://ipv4.fiddler:port, and I can intercept the traffic. But when I do this the timeout issues don't occur!
Any other tools or fiddler workarounds welcome! Thanks!
Edit: Oops. This question had already been asked... Twice.. Didn't come up on search or suggestions. The solution found in the second thread is to use the dot-hack with ip-address (http://127.0.0.1.:port/ instead of "localhost". This question may be closed.
While fiddler ignores requests to localhost, it listens to 127.0.0.1. (note the trailing dot):
So this won't work:
http://localhost:1234/
But this will:
http://127.0.0.1.:1234/
You're generally better off using http://ipv4.fiddler as it makes it more explicit what you're trying to do.
CassiniDev is an open source project that was developed to fill in all the blanks left by WebDev.WebServer/Cassini.
You will find this issue handled as well as many others.
It works well as a stand-alone server, as an in-process server suitable for testing and embedding and, most notably, as a direct replacement for the Visual Studio 2008/2010 dev servers.
alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=cassinidev&DownloadId=123367
alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=cassinidev&DownloadId=123366