Maybe I should start to tone down a bit, after reading and finding the follwoing in response to a 2 year old query from a Lunarpages.com forum page:
-----------------------------------------------[the Raply today would be today, btw]
 | Re: Extensions are down for 4 Days - Support isn't Helping « Reply #17 on: Today at 08:41:13 PM » |    |
A similar problem is worldwide now (no pun intended in case you are a MyWebHoster customer on their windowsworldwide servers).
The issue is the Server2003 Service Pack1 update (out on November 2005, warnings and problems first appeared in January 6, 2006). A lot of webhosting companies have in the last few weekends updated their Server 2003 machine - both 32 bit and 64 bit - to make way for the a onslaught of the poor Linux Server customers using Frontpage extensions on those Linux servers. Why would there be an onslaught? Because Microsoft as of July 12th, 2006 has End-of-lifed any support for Frontpage Extensions for Linux/Unix and has no plans to make any 2003 Extensions. (this basically means that if you applied any SPs for FPSE modules on a Linux server of any version or not, you are now officially SOL
). But if you are on an actual Windows Server box, then read on. 
The Service Pack 1 as applied to actual Windows machines only running Server2003 32 or 64 bit has been malfunctioning across the world, and there is only one solution. The solution involves only a fix that only your webhoster can make: It is a registry setting permissions change The message may not appear unless the webhoster ALSO has the latest version of FPSE2002 installed (yes, 2002 (two) there are no such things as FPSE2003 and there never will be, they will be called instead SharePoint Services. Period):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Ports\Port 80
http://support.microsoft.com/default.aspx?scid=kb;en-us;264922
The above link is really only helpful to Server2003 engineers.
You may or may not also receive the following error IF you are on an actual Windows machine:
Server error: Error 2 opening registry key Software/microsoft/shared tools/web server extensions/ports/port 80
This error is coming ONLY from a Windows machine running ONLY Server2003 and only AFTER SP1 AND FPSE2002 latest version has been applied SUCCESSFULLY. If there was a failure to apply, then another message would appear on the back end at the webhosting company machine doing the install of the patch.
That is a whole other problem.
This behavior can occur if the Web Server Extensions key and its subkey do not have the correct type of access rights assigned to them.
http://support.microsoft.com/kb/873148
Hey you Linux peeps, sorry to bring the bad news, but there are a LOT of webhosters NOT telling their customers of these issues.
---------------------------------------------
So I gues, MAYBE, I'll start toning down..
-----------------------------------------------
The issue is the Server2003 Service Pack1 update (out on November 2005, warnings and problems first appeared in January 6, 2006). A lot of webhosting companies have in the last few weekends updated their Server 2003 machine - both 32 bit and 64 bit - to make way for the a onslaught of the poor Linux Server customers using Frontpage extensions on those Linux servers. Why would there be an onslaught? Because Microsoft as of July 12th, 2006 has End-of-lifed any support for Frontpage Extensions for Linux/Unix and has no plans to make any 2003 Extensions. (this basically means that if you applied any SPs for FPSE modules on a Linux server of any version or not, you are now officially SOL
). But if you are on an actual Windows Server box, then read on. The Service Pack 1 as applied to actual Windows machines only running Server2003 32 or 64 bit has been malfunctioning across the world, and there is only one solution. The solution involves only a fix that only your webhoster can make: It is a registry setting permissions change The message may not appear unless the webhoster ALSO has the latest version of FPSE2002 installed (yes, 2002 (two) there are no such things as FPSE2003 and there never will be, they will be called instead SharePoint Services. Period):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Ports\Port 80
http://support.microsoft.com/default.aspx?scid=kb;en-us;264922
The above link is really only helpful to Server2003 engineers.
You may or may not also receive the following error IF you are on an actual Windows machine:
Server error: Error 2 opening registry key Software/microsoft/shared tools/web server extensions/ports/port 80
This error is coming ONLY from a Windows machine running ONLY Server2003 and only AFTER SP1 AND FPSE2002 latest version has been applied SUCCESSFULLY. If there was a failure to apply, then another message would appear on the back end at the webhosting company machine doing the install of the patch.
That is a whole other problem.
This behavior can occur if the Web Server Extensions key and its subkey do not have the correct type of access rights assigned to them.
http://support.microsoft.com/kb/873148
Hey you Linux peeps, sorry to bring the bad news, but there are a LOT of webhosters NOT telling their customers of these issues.
---------------------------------------------
So I gues, MAYBE, I'll start toning down..
-----------------------------------------------
No comments:
Post a Comment