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.
Related
I'm setting up website. IIS hosting my site (ASP.NET) is located on server server1. when I connect to my website http://server1.com/site/ eveything work fine.
We decided to use DNS alias - supersite, which means, when I connect to my website using http://supersite.com/site/, this should be equal to first request.
Command line ping command shows the same server - this is for sure.
This doesn't happen. When I'm connecting with raw URL http://server1.com/site/, server responds correctly, when I connect using DNS alias http://supersite.com/site/, server returns:
The page cannot be displayed because an internal server error has occurred.
I tried configure more detailed information, I set up Error Pages -> 500 -> Detailed Error, I enabled Send errors to browser in ASP menu. Nothing helps.
I think, that server doesn't connect to my website when I'm using DNS alias and all my attempts enabling detailed errors means nothing.
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.
I use cyberduck for SFTP my website files to the server. Dreamhost is the server.
In setting up a new bookmark in cyberduck I received this error "Connection failed - EOF while reading packet." [end of file]
The website is up and working fine, http://ce-t.org
Initially I thought this error had to do with the connection opening with cyberduck. So I setup a different bookmark to test and was able to do without a problem.
I have also deleted my first attempt to setup and reset up. This did not alter anything.
Now after doing more reading, may be in one of the website files?
As you can see i am a novice.
Help appreciated.
Usually when I run into this issue, its because my pw has expired.
Try SSHing into the server and change/update your pw. After I change it, I can FTP in.
This is 3 years too late for the OP. But I had this error when trying to make an SFTP connection to hosting on a Plesk server and the solution was to:
Enable the 'Access to the server over SSH' setting for the ftp user via the Plesk Control panel.
Of course you might need to contact your hosting service to get this done if you are not managing your own server.
In my case the same error occurred due to a syntax error in the .bashrc file on the remote server.
Also note that the default account setting for an FTP user at Dreamhost might specify an FTP connection. If so, trying to use Cyberduck to connect via SFTP will generate this error message. You can use the Dreamhost control panel to edit the user's record to specify SFTP.
In my case I have used dropbear ssh server.
I replace this server with openssh server, and now i can open the sftp connection without any issues.
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.
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.