I'm baffled by an error I'm getting when I try to drag some JPG image
files into an \image folder in a web:
"An error occurred 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."

This is just the usual local work in FP 2000. A few of the files (all
large JPG's, edited from digicam photos) *do* drag across OK, but the
majority don't.

Did Check & Repair; cleared FP Temp Cache; rebooted Windows XP;
cursed a few times...

What could be going on here please?

--
Terry, West Sussex, UK

OK, just realised that this is because most of the files are greater
than 1 MB. So this is the FP2000 bug Ronx advised me about here in
November. Is there still no proper fix for this crude bug by MS after
all this time - 2000 to 2005?

--
Terry, West Sussex, UK

The only fix is to upgrade.

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.

> -----Original Message-----
> From: Terry Pinnell [private.php?do=newpm&u=]
> Posted At: 8. februar 2005 16:54
> Posted To: microsoft.public.frontpage.client
> Conversation: Cannot drag files into FP
> Subject: Re: Cannot drag files into FP
>
>
> OK, just realised that this is because most of the files are
> greater than 1 MB. So this is the FP2000 bug Ronx advised me
> about here in November. Is there still no proper fix for this
> crude bug by MS after all this time - 2000 to 2005?
>
> --
> Terry, West Sussex, UK
>

For server based webs, the default is set to 1 MB anonymous uploads.
There is a command that you can run on the server that will increase the anonymous upload size for a given web site. The command
(for all ports) is as follows :
owsadm -o setproperty -pn vti_maxuploadcontentlength -pv 3000000
The Owsadm.exe can be found at C:\Program files\common files\Microsoft Shared\Web server extensions\50\bin folder.
The size at the end of the line is in bytes.

If it is a disc based web, copy the large files in Windows Explorer and open FP , Run a Tools Recalculate Hyperlinks for FP to
recognize them

In either case they will be a problem in publishing to an online server (unless you or your host can change the limit per above)
Create a folder (w/ all your large media in it) called say media in your local and remote sites in FP, and convert it to a subweb
- then never open it in FP and FTP the large files up to your server

IMHO
Do some image compression as 1 MB jpgs will be a "thorn" for your users too

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


"Terry Pinnell" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
| OK, just realised that this is because most of the files are greater
| than 1 MB. So this is the FP2000 bug Ronx advised me about here in
| November. Is there still no proper fix for this crude bug by MS after
| all this time - 2000 to 2005?
|
| --
| Terry, West Sussex, UK
|

"Stefan B Rusynko" <(E-Mail Removed)> wrote:

>For server based webs, the default is set to 1 MB anonymous uploads.
>There is a command that you can run on the server that will increase the anonymous upload size for a given web site. The command
>(for all ports) is as follows :
> owsadm -o setproperty -pn vti_maxuploadcontentlength -pv 3000000
>The Owsadm.exe can be found at C:\Program files\common files\Microsoft Shared\Web server extensions\50\bin folder.
> The size at the end of the line is in bytes.
>
>If it is a disc based web, copy the large files in Windows Explorer and open FP , Run a Tools Recalculate Hyperlinks for FP to
>recognize them
>
>In either case they will be a problem in publishing to an online server (unless you or your host can change the limit per above)
>Create a folder (w/ all your large media in it) called say media in your local and remote sites in FP, and convert it to a subweb
>- then never open it in FP and FTP the large files up to your server
>
>IMHO
>Do some image compression as 1 MB jpgs will be a "thorn" for your users too

Thanks very much, Stefan.

I take your point re the large files. In this case they were 'full
size' images (originally digicam photos) optionally accessible from
their 250 x 165 equivalents.

--
Terry, West Sussex, UK