Component Errors-A FrontPage Image Map component has a parameter..

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am receiving the following type of errors when I run a report:

(1) A FrontPage Image Map component has a parameter "Original Source Image
(U-OriginalSrc)" with the value "dir/file.gif", but a file cannot be found at
this location.

(1) A FrontPage Image Map component has a parameter "Overlay Source Image
(U-OverlaySrc)" with the value "_overlay/dir.htm_txt_file.gif", but a file
cannot be found at this location.

I also receive a long list under Unlinked Files, although they are linked
and work fine. My guess is this happened when I was using FP to rename files
and reorganize the directory structure (again, using FP, not Explorer). In
the process of renaming a directory, I received the following, and then the
rename process stopped.

An error occurred accessing you 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.

Is there an equivalent of a "repair & detect" for FP files? I don't want to
manually delete the "U-OriginalSrc" content in the files, and Recalculate
Hyperlinks hasn't removed this obselete Src information. I deleted all the
VTI directories, which FP recreated the next session. The logfile doesn't
appear to have any answers either.

I'm using FP 2002 SP3.
Thanks!
Andy
 
1. When you started FP, did you use File Menu | Open Web / Site before working on the content of
your site? If not then you need to.

2. You must always import all external content (images) into the current open web / site before
using them, etc.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
Back
Top