G
Guest
For 3 or 4 years I have had a 9 gigabyte webspace account with Infinology,
with 5 websites occupying around 3 gigs. It recently started giving me a
problem. My ISP support staff tells me that the problem is that the size of
the website(s) are simply too big for FrontPage 2003 to use with.
My large site is around 2.5 gigs. There are no subwebs, though if it will
fix the problem I can split off the photos section and that would probably
segregate over 1.5 gigs. This is an archival website devoted to target
archery in the U.S., hence the large number of photos.
THE ERROR happens when FP 2003 tries to open the remote website. It gives
me this message:
Unable to Open 'http://www.usaarcheryrecords.org'.
Server error: Server error: Error 2 opening registry key
"SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Ports\Port 80".
Possible causes:
1. The web server may not have the FrontPag Server Extensions installed.
2. The web server may be temporarly out of service.
3. If you are connecting through a proxy server, the proxy settings may be
incorrect.
4. An error may have ocurred in the web server.
if this server does not support the FrontPage Server Extensions, FrontPage
may still be able to publish to the server via FTP or WebdAV. Please select
one of these options and try again.
The irritating thing is that this broken website is not the "big" one - it
is only a month old, less than 3 megs in size. I've used the control panel
provided by the ISP to delete the FP extensions and repair them, no joy.
This has happened several times, and each time the ISP tech support people
have somehow fixed the problem after I have dogged them for days, though they
will not tell me how/what was truly wrong. So I don't think it is anything
on my PC. My account space was originally on a Windows server (at my
request), but at one point they chose to move it to a unix server and I can't
help but wonder whether that is a contributor to this PITA.
The big site, http://www.texasarchery.org, is working just fine - people can
surf it and I can publish to it with FP .
It is only a couple of the smaller sites that are giving me this problem
with publishing. I've searched the knowledgebase. I've deleted the .web
files and the dui file on my development laptop where I do all the work on
these sites. No Joy.
Is there a point beyond which too many files in a website causes the front
page extensions on the server to become corrupt, and is a unix server more
unstable than a windows server would be? Would splitting the photos
subdirectory on the website into a subweb relieve this problem? If this size
issue is indeed a cause for the error 2, then how come the small sites are
what gets hosed?
at this point,
one site lets me surf it but not publish to it, but the critical problem is
that http://www.usaarcheryrecords.org will not let me publish NOR CAN ANYONE
SURF TO IT - if you try to surf it you get: Directory Listing Denied
This Virtual Directory does not allow contents to be listed.
The really big site, http://www.texasarchery.org , lets me surf and lets me
publish. VERY frustrating and confusing.
Any suggestions on this problem would be very, very, gratefully received.
Will gladly give instructions in archery as exchange
with 5 websites occupying around 3 gigs. It recently started giving me a
problem. My ISP support staff tells me that the problem is that the size of
the website(s) are simply too big for FrontPage 2003 to use with.
My large site is around 2.5 gigs. There are no subwebs, though if it will
fix the problem I can split off the photos section and that would probably
segregate over 1.5 gigs. This is an archival website devoted to target
archery in the U.S., hence the large number of photos.
THE ERROR happens when FP 2003 tries to open the remote website. It gives
me this message:
Unable to Open 'http://www.usaarcheryrecords.org'.
Server error: Server error: Error 2 opening registry key
"SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Ports\Port 80".
Possible causes:
1. The web server may not have the FrontPag Server Extensions installed.
2. The web server may be temporarly out of service.
3. If you are connecting through a proxy server, the proxy settings may be
incorrect.
4. An error may have ocurred in the web server.
if this server does not support the FrontPage Server Extensions, FrontPage
may still be able to publish to the server via FTP or WebdAV. Please select
one of these options and try again.
The irritating thing is that this broken website is not the "big" one - it
is only a month old, less than 3 megs in size. I've used the control panel
provided by the ISP to delete the FP extensions and repair them, no joy.
This has happened several times, and each time the ISP tech support people
have somehow fixed the problem after I have dogged them for days, though they
will not tell me how/what was truly wrong. So I don't think it is anything
on my PC. My account space was originally on a Windows server (at my
request), but at one point they chose to move it to a unix server and I can't
help but wonder whether that is a contributor to this PITA.
The big site, http://www.texasarchery.org, is working just fine - people can
surf it and I can publish to it with FP .
It is only a couple of the smaller sites that are giving me this problem
with publishing. I've searched the knowledgebase. I've deleted the .web
files and the dui file on my development laptop where I do all the work on
these sites. No Joy.
Is there a point beyond which too many files in a website causes the front
page extensions on the server to become corrupt, and is a unix server more
unstable than a windows server would be? Would splitting the photos
subdirectory on the website into a subweb relieve this problem? If this size
issue is indeed a cause for the error 2, then how come the small sites are
what gets hosed?
at this point,
one site lets me surf it but not publish to it, but the critical problem is
that http://www.usaarcheryrecords.org will not let me publish NOR CAN ANYONE
SURF TO IT - if you try to surf it you get: Directory Listing Denied
This Virtual Directory does not allow contents to be listed.
The really big site, http://www.texasarchery.org , lets me surf and lets me
publish. VERY frustrating and confusing.
Any suggestions on this problem would be very, very, gratefully received.
Will gladly give instructions in archery as exchange