FP will publish files under 1 MB only

[steve rocke]

Some (but not all) of the webs I manage began getting this
message when publishing:

"An error occurred when accessing your FrontPage web
files. Authors - if authoring against a web server,
please contact the webmaster for this server's site.
WebMasters - please see the server's system log for more
details."

Unfortunately, there are no log file messages anywhere. I
finally determined that only files under 1 Mb are being
published. If a mark all the larger files to exclude them
from publishing, the web will publish w/o errors.

I am running SunOne WebServer 6.1 (formerly iPlanet) on
Windows 2000 Server.

Any ideas what may be causing this? Any suggestions will
be greatly apppreciated.

Thanks.
Steve

 

[Steve Easton]

There is an issue with FP 2000 and files over 1mb in size.
The workaround seems to be to open the remote web and drag the files in.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

 

[Sparky Polastri]

I'd like to add that since the non IIS web server is involved, the publish
probably won't work either.

In October 2003 there was a Critical Security Patch for FrontPage 2000
server extentsions that fixed a buffer over run get control of your server
blah blah blah hole...

The fix permenently breaks the ability for the extensions on that box to
accept files over about 950kb.

Work arounds involve upgrading to the FP2002 extensions, however Microsoft
has not produced versions for all non IIS web servers and "SunOne" may be
one of them.

I'd suggest that now would be a good time to switch to Linux/Apache as a web
server, or go to IIS on Windows. (Though I am not sure if FP2002 extensions
exist for Apache either.)

[You could roll back the security updates maybe, but that has other risks.]

IIS is a dream come true compared to the pile of crap I was using
previously, you may find you end up liking it.

 

[Steve Easton]

There are 2002 extensions for Apache/UNIX.
They are written by Ready To Run software. www.rtr.com


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

I'd like to add that since the non IIS web server is involved, the publish
probably won't work either.

In October 2003 there was a Critical Security Patch for FrontPage 2000
server extentsions that fixed a buffer over run get control of your server
blah blah blah hole...

The fix permenently breaks the ability for the extensions on that box to
accept files over about 950kb.

Work arounds involve upgrading to the FP2002 extensions, however Microsoft
has not produced versions for all non IIS web servers and "SunOne" may be
one of them.

I'd suggest that now would be a good time to switch to Linux/Apache as a web
server, or go to IIS on Windows. (Though I am not sure if FP2002 extensions
exist for Apache either.)

[You could roll back the security updates maybe, but that has other risks.]

IIS is a dream come true compared to the pile of crap I was using
previously, you may find you end up liking it.

There is an issue with FP 2000 and files over 1mb in size.
The workaround seems to be to open the remote web and drag the files in.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
.......................with a computer

 

[steve rocke]

Thanks for the responses, guys. Actually, Microsoft quit
providing server extensions for the Netscape/iPlanet/Sun
web servers back on Netscape 4.6, so I am not using them.
Your explanation about the security fix that breaks the
extensions sounds exactly what I am experiencing, although
w/o extensions. I wish they would provide a fix for the
fix, but I can't find anything on their site. Thanks for
your input.

Steve

-----Original Message-----
There are 2002 extensions for Apache/UNIX.
They are written by Ready To Run software. www.rtr.com


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

"Sparky Polastri" <[email protected]> wrote in

message news:[email protected]...

I'd like to add that since the non IIS web server is involved, the publish
probably won't work either.

In October 2003 there was a Critical Security Patch for FrontPage 2000
server extentsions that fixed a buffer over run get control of your server
blah blah blah hole...

The fix permenently breaks the ability for the extensions on that box to
accept files over about 950kb.

Work arounds involve upgrading to the FP2002 extensions, however Microsoft
has not produced versions for all non IIS web servers and "SunOne" may be
one of them.

I'd suggest that now would be a good time to switch to Linux/Apache as a web
server, or go to IIS on Windows. (Though I am not sure if FP2002 extensions
exist for Apache either.)

[You could roll back the security updates maybe, but that has other risks.]

IIS is a dream come true compared to the pile of crap I was using
previously, you may find you end up liking it.

 

[Sparky Polastri]

Thanks for the responses, guys. Actually, Microsoft quit
providing server extensions for the Netscape/iPlanet/Sun
web servers back on Netscape 4.6, so I am not using them.
Your explanation about the security fix that breaks the
extensions sounds exactly what I am experiencing, although
w/o extensions. I wish they would provide a fix for the
fix, but I can't find anything on their site. Thanks for
your input.

Steve

Steve,

I am a little confused about how you are publishing using FrontPage without
having the FrontPage server extensions on the server.....

This problem could be entirely different then. Are you using FTP?

 

[Guest]

No, I don't use FTP. I have my users map to shares where
they have read, write and delete privs. The development
and production sites are both on the same server (but
wouldn't have to be). The webs look like drive names in
FrontPage ("M:\" for the development site, for example).
They do all of their work in FrontPage, never accessing
their files through Windows. When they publish,
the "Publish Web" location looks like this: "file:///N:"
(the production site). This has been working without a
hitch for over a year, until mid-March. Not all of the
webs have this problem - only about 4 out of 20 - so far.
This is why it's so perplexing.