CMsample Site Does Not Work with Visio Documents (245094)
The information in this article applies to:
- Microsoft Site Server 3.0
This article was previously published under Q245094 SYMPTOMS
When a Visio document is uploaded to the Microsoft Site Server Content Management CMSample site, the file is moved into the correct directory but is not visible.
CAUSE
The problem is that Site Server Content Management correctly sets the Visio's document properties; however the Index server does not have a word breaker that can read the properties.
Content Management follows this logic: - If the document is an OLEDOC file, insert properties into the file property stream in the docfile.
- ELSE if the document is an HTML file, insert properties into the HTML through tags.
- ELSE file must be nonOLE and nonHTML, so make a STUB
RESOLUTION
To make sure that OLE document files that do not have word breakers get stub files created, you need to modify the SaveOLEProps function in the LibCM.asp found in the <Microsoft Site Server>\SiteServer\Publishing folder.
If the SaveOLEProps function fails, a stub file will automatically be created. A Visio Document file has a VSD extension. By adding the following line of code to the top of the SaveOLEProps function, you create stub files for VSD files:
if (InStrRev(strFilename,"vsd",-1,1)) Then Exit Function
A separate line can be added for each type of OLE document file that needs a stub file by simply substituting the extension inside the quotation marks.
STATUSMicrosoft has confirmed that this is a problem in Site Server 3 SP3.
| Modification Type: | Major | Last Reviewed: | 10/22/2002 |
|---|
| Keywords: | kbbug KB245094 |
|---|
|