Well, I first thought too that a '500 - Server Error' meant that
something must be wrong with the server, so I reinstalled it. No
change. Then I tried it in Netscape, and it worked perfectly. So it
isn't the server, it's MSIE. It has suddenly stopped recognizing
127.0.0.1 as a valid IP address, and it's MSIE reporting the server
error, NOT the server itself.
Regards,
Karl Simanonok
Original message:
-----------------
Date: Thu, 14 Sep 2000 16:12:09 -0700
From: "Mark Warrick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: RE: 500 - Server Error
Message-ID: <[EMAIL PROTECTED]>
Well, a server response 500 means there's something wrong with the =
server. So it's quite possible that some of the files for your web =
server or ColdFusion server have somehow become corrupt. I would =
recommend uninstalling and reinstalling both servers.
---mark
--------------------------------------------------------------
Mark Warrick
Phone: (714) 547-5386
Efax.com Fax: (801) 730-7289
Personal Email: [EMAIL PROTECTED]
Personal URL: http://www.warrick.net=20
Business Email: [EMAIL PROTECTED]
Business URL: http://www.fusioneers.com
ICQ: 346566
--------------------------------------------------------------
> -----Original Message-----
> From: Karl Simanonok [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 14, 2000 1:55 PM
> To: [EMAIL PROTECTED]
> Subject: 500 - Server Error
>=20
>=20
> While developing offline I have been using CF 4.5.1 with MSIE 5.0 and
> O'Reilly's Website version 1.1. I don't use Studio, but instead
> TextPad. No problems for a very long time. Suddenly two days ago (no
> new software, hardware, or configuration changes) MSIE consistently
> returns a "500 - Server Error" and refused to load any sites locally
> using 127.0.0.1. Trying an old Netscape browser, it worked fine, so
> there can't be any problem with O'Reilly's or CF (I think). I tried
> reinstalling MSIE, that didn't help, so I upgraded to the latest MSIE
> 5.5 high-security beta, and still no good. I've run
> troubleshooting/repair on the hard drive and defragmented it, neither
> made any difference. MSIE will work however if I use the local server
> name ('betsy') in place of 127.0.0.1, so it isn't any kind of
> life-or-death issue by any means, but I'd like to know why it suddenly
> stopped recognizing 127.0.0.1. Has anybody seen this happen before?
>=20
> Regards,
>=20
> Karl Simanonok
>=20
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
