Issue:
Documents from a SAP system should be displayed. But some problems occur.
A) The document should be displayed in SAP own ECL Viewer.
Although documents from Connect To SAP is passed as .dwtiff and as MIME type image/tiff, the download of the document is performed either without a suffix or with false suffix (eg .mdb).
B) The document should be displayed in the Internet browser, however, the documents are called on the client without a file extension when displaying documents from SAP and therefore not automatically open in the appropriate viewer. The file is often just "run".
Solution:
Before all these solutions-steps are applied, please make sure that the latest hotfix Pack is installed:
- DocuWare Version 6.8 Hotfix 04
- DocuWare Version 6.7 Hotfix 40
- DocuWare Version 6.6 Hotfix 58
To obtain these hotfixes, please go to http://go.docuware.com/HFPacks
Solution A.1) On DocuWare side check the file DWSAPHTTPServer.exe.config if the file extension is available (in your case maybe .dwtiff?). The values dwtiff=image/tiff or pdf=application/pdf by the SAPMimeTypes option. Otherwise, please add.
Sample:
<add key="SAPMimeTypes" value="bin=application/octet-stream|doc=application/msword|pdf=application/pdf|ps=application/postscript|rtf=application/rtf|xls=application/vnd.ms-excel|mpp=application/vnd.ms- project|ppt=application/vnd.ms-powerpoint|msg=application/vnd.ms-outlook|alf=application/x-alf|otf=application/x-otf|raw=application/x-raw|reo=application/x-reo|scr=application/x-scr|bmp=image/bmp|gif=image/gif|jpg=image/jpeg|pcx=image/pcx|tif=image/tiff|dwtiff=image/tiff|html=text/html|txt=text/plain|note=application/x-note|descr=application/x-alf-descr"/>
Solution A.2) Check the following settings of the 'Display Settings' on the SAP server. The settings in the OAG4 and OAA3 stand in a causal relationship.
- Also try out the option, the 'Data Provider Cache Disable '.
- Also try out the option, 'Call Internet Browser '. (The browser of the computer is to take place to open the document).
Transaction OAG4:
Transaction OAA3:
The version should be 0045.
On this place the protocol is used only for the Content Repository 'FI'.
Within that protocol the file types will be assigned. Each of the three functions are adjusted('Display Stored Document', 'Providing Frontend', ' Display Lokal File').
For 'Display Stored Document "is the document type' TIF 'assigned to the communication type' ARCHIVELNK '.
For 'Providing Frontend' is the document type 'TIF' assigned to the communication type 'HTTP'.
For 'Display Local File' is the document type 'TIF' assigned to the communication type 'ARCHIVELNK'.
Solution B.1) For that file type, run a reassignment of the file extension to the standard Windows program.
http://windows.microsoft.com/de-de/windows/change-default-programs#1TC=windows-7
Solution B.2) In some cases, all you need to do is to update the installed version of Microsoft Internet Explorer to the latest version and then reset the security level for the security zone in question to "default".
Solution B.3 )If there is a client on which the document can be viewed from SAP successfully, open the Windows registry* on this computer (Start > Run > "regedit") and enter the "HKEY_CLASSES_ROOT\MIME\Database\Content Type" key.
All MIME types in this branch are allocated to an associated application.
Export the key affected by the faulty MIME type (e.g. "image/tiff") from this computer and import this key onto all clients on which the display is not working.
Only import the registry key onto computers with the same operating system version as the computer from which the key was exported.
The document should now be displayed correctly. Internet Explorer and the SAPGUI may have to be restarted after these changes have been made.
* Note: Changes to the Windows registry can upset the stability and function of Microsoft Windows or installed programs and components. Changes should only be made with extreme care and by experienced persons. DocuWare AG accepts no guarantee or liability for errors caused by changes to the registry in connection with this Knowledge Base article or any other instructions. If you have any questions regarding changes to the Windows registry, please contact Microsoft.
