Quantcast
Channel: ProjectWise Design Integration Wiki
Viewing all articles
Browse latest Browse all 1890

Opening chm files with Explorer error: Unable to link to webpage

$
0
0
Current Revision posted to Content Management - Wiki by Elisa Pry on 8/16/2013 5:50:12 PM

  
 Applies To 
  
 Product(s):ProjectWise V8i
 Version(s):08.11.xx.xx
 Environment: N/A
 Area: Explorer
 Subarea: N/A
 Original Author:Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

Problem Description

When trying to open .chm files through PW Explorer, User receives error: Unable to link to webpage.

Solution

This error may be experienced after installing Security update 896358, 840315, or Server 2003 SP1. Attachment Manager may treat a downloaded .chm file as an untrusted file. Therefore, you may not be able to open it.
  Use UNC file paths and file shares to link to .chm files If your intranet Web page uses the HTTP URL scheme to link to .chm files, security update 896358 may prevent users from seeing topics in the .chm file. Replacing an HTTP file path with a UNC file path can make it possible again to open .chm files from the Web page.

To use a UNC file path instead of an HTTP URL, follow these steps:
Put the .chm files on a file share server that can be addressed by using a UNC file path.

A UNC file path looks similar to the following path:

\\productmanuals\helpfiles

Use the ItssRestrictions\UrlAllowList value to enable the systems in your intranet to access the .chm files from that file share.

  Also, you may "Save" the File locally, instead of "Opening" the file directly

See Also

Product TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" sectioXn. THANK YOU!

 


Viewing all articles
Browse latest Browse all 1890

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>