Documentation

Release Notes

Listed below are the release notes for the various PDF Converter versions. If you have identified an issue that is not listed here then please check out the FAQ, Support Area or contact us directly.

Release notes are available for the following public releases:


PDF Converter for SharePoint v7.2
 

Read the announcement to see what is new in this version. Known issues of the 7.2 version are as follows.
 

#2020 - JPEG2000 encoded PDFs cannot be OCRed

The PDF Converter's OCR add-on has the ability to recognise text in scanned PDF files and make these files fully searchable and indexable. Scanned content can be encoded in many different ways, but PDFs that use JPEG2000 encoding cannot be OCRed. As a workaround use the PDF Converter Professional to convert the PDF to an older PDF version that doesn't support JPEG2000 before sending it for OCR processing.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1874 - SharePoint 2013's optional workflow engine is not supported.

SharePoint 2013 comes with two different workflow engines, the one that ships with SharePoint 2007 and 2010, which is the default workflow engine, and an optional new product called Windows Azure Workflow. The SharePoint Designer workflow components that ship with the Muhimbi PDF Converter for SharePoint only work with the Default SharePoint Workflow Engine and not with Windows Azure Workflow. If you wish to use Windows Azure Workflow then you need to use Workflow Interop.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1813 - The Service installer does not run on systems with only .net 4.5 installed

Although the PDF Conversion Service works fine on .NET 4.5 systems, the .NET Framework 3.0 / 3.5 needs to be installed for the installer to be able to run. The various copies of the .net framework can be installed at the same time and run in parallel.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time. For a workaround see this Knowledge Base article.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v7.1
 

Read the announcement to see what is new in this version. Known issues of the 7.1 version are as follows.
 

#2020 - JPEG2000 encoded PDFs cannot be OCRed

The PDF Converter's OCR add-on has the ability to recognise text in scanned PDF files and make these files fully searchable and indexable. Scanned content can be encoded in many different ways, but PDFs that use JPEG2000 encoding cannot be OCRed. As a workaround use the PDF Converter Professional to convert the PDF to an older PDF version that doesn't support JPEG2000 before sending it for OCR processing.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1874 - SharePoint 2013's optional workflow engine is not supported.

SharePoint 2013 comes with two different workflow engines, the one that ships with SharePoint 2007 and 2010, which is the default workflow engine, and an optional new product called Windows Azure Workflow. The SharePoint Designer workflow components that ship with the Muhimbi PDF Converter for SharePoint only work with the Default SharePoint Workflow Engine and not with Windows Azure Workflow. If you wish to use Windows Azure Workflow then you need to use Workflow Interop.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1813 - The Service installer does not run on systems with only .net 4.5 installed

Although the PDF Conversion Service works fine on .NET 4.5 systems, the .NET Framework 3.0 / 3.5 needs to be installed for the installer to be able to run. The various copies of the .net framework can be installed at the same time and run in parallel.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v7.0
 

Read the announcement to see what is new in this version. Known issues of the 7.0 version are as follows.
 

#1889 - The old SharePoint 2010 GUI is not supported in SharePoint 2013

SharePoint 2013 comes with a compatibility mode that displays everything using the old SharePoint 2010 user interface. The PDF Converter for SharePoint does not support this mode, please upgrade your sites to the SharePoint 2013 user interface.
 

#1874 - SharePoint 2013's optional workflow engine is not supported.

SharePoint 2013 comes with two different workflow engines, the one that ships with SharePoint 2007 and 2010, which is the default workflow engine, and an optional new product called Windows Azure Workflow. The SharePoint Designer workflow components that ship with the Muhimbi PDF Converter for SharePoint only work with the Default SharePoint Workflow Engine and not with Windows Azure Workflow. If you wish to use Windows Azure Workflow then you need to use Workflow Interop.
 

#1861 - When FastWebView / Linearization is used PDF Security cannot be applied

As of version 7.0 the PDF Converter Professional add-on license allows a PDF to be optimised for use on the web (FastWebView / Linearization). This option cannot be used in combination with PDF Security and encryption.
 

#1813 - The Service installer does not run on systems with only .net 4.5 installed

Although the PDF Conversion Service works fine on .NET 4.5 systems, the .NET Framework 3.0 / 3.5 needs to be installed for the installer to be able to run. The various copies of the .net framework can be installed at the same time and run in parallel.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 & SP2013 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v6.1
 

Read the announcement to see what is new in this version. Known issues of the 6.1 version are as follows.
 

#1801 - File names with multiple periods are truncated during conversion

When a file name contains multiple periods ('.') then the name may be truncated after the first period. We are working on a fix, as a temporary workaround replace periods with dashes ('-').
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v6.0
 

Read the announcement to see what is new in this version. Known issues of the 6.0 version are as follows.
 

#1384 - AuthorizedType is not deleted from web.config when uninstalling solution

When uninstalling the PDF Converter's front-end WSP SharePoint's deployment mechanism does not retract all changes to the web.config file. This may lead to problems creating new SharePoint Designer workflows if a new version of the PDF Converter is not installed after the uninstallation. To solve this problem remove all references to 'Muhimbi.SharePoint.DocumentConverter.PDF' from the 'authorizedTypes' section in the affected web.config files.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v5.2
 

Read the announcement to see what is new in this version. Known issues of the 5.2 version are as follows.
 

#1572 / 1670 - Site and List workflows are not supported

All SharePoint Designer and Nintex Workflow activities shipped with the PDF Converter for SharePoint are primarely aimed at workflows associated with Document Libraries. Regular List and Site Level workflows are currently not officially supported.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

Some converters are not able to to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v5.1
 

Read the announcement to see what is new in this version. Known issues of the 5.1 version are as follows.
 

#1508 - Nintex File Merge activity fails when used inside a 'For each' iterator

Using the PDF Merge activity in a Nintex workflow crashes the workflow when this activity is used inside an iterator loop. As a workaround maintain a list of files to merge in a string and carry out the merging outside of the loop.
 

#1495 - Externally referenced images don't always finish loading before conversion in InfoPath

When an InfoPath form contains a number of externally referenced large images then the PDF Conversion may be carried out before these images finish loading. As a workaround use smaller images or embed the images inside the InfoPath form.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v5.0
 

Read the announcement to see what is new in this version. Known issues of the 5.0 version are as follows.
 

#1399 - Uploading a file in SP2010 using Windows Explorer does not trigger insert Watermark

When using the new automatic watermarking functionality to apply watermarks when new files are uploaded, then this process is not triggered when using SharePoint 2010 AND uploading the file using the Windows Explorer. As a workaround either apply watermarks using workflows or upload files using the regular SharePoint upload facilities.
 

#1395 - Filtering in SP2010 doesn't take the regional settings of the current site into account

When using the new automatic watermarking functionality to only apply watermarks under certain conditions using filters, then - when using SP2010 - the filters do not take the current site's regional settings into account. It appears to use the Web Application service account's regional settings. This is not a problem in most cases as all accounts are likely to use the same settings. As a workaround either use workflows to apply filters or change the regional settings for the Web Application service's account. This is not a problem in SharePoint 2007.
 

#1016 - User facing translations for new functionality are in English only.

The new watermarking screens and merging facility are always in English. All languages will be refreshed as part of the upcoming 5.1 release.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v4.1
 

Read the announcement to see what is new in this version.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v4.0
 

Read the announcement to see what is new in this version.
 

#1150 - Office DRM protected documents are not supported

Documents that have been encrypted and secured via Microsoft's DRM solution are not supported at this moment in time.
 

#1151 - Converting SharePoint pages to PDF sometimes results in a bitmap based PDFs

Under normal circumstances Muhimbi's HTML to PDF Conversion module generates 'vector based' output when converting HTML files. This has the advantage that it looks very well and all text contained in the HTML file is maintained and can be edited using normal text editing tools. However, certain SharePoint pages are converted to a single bitmap. We are looking into a solution.
 

#1149 - InfoPath 2010 Prioritises views selected in the Print Multiple Views dialog

InfoPath ships with a dialog box that allows the user to select which views (multiple) are printed when a form is sent to the printer. In InfoPath 2007 this functionality is ignored when generating PDF files, however in InfoPath 2010 these views are given priority over Muhimbi's own dynamic view selection functionality. If you wish to use Muhimbi's dynamic view selection features in combination with InfoPath 2010 then please make sure no views are selected in InfoPath's Print Multiple Views dialog. We hope to find a more permanent workaround for a next software release.
 

#1139 - Dynamic lookup values in SP2010 workflows may behave unexpectedly

Due to a bug in SharePoint 2010, workflows that contain a lookup value as part of a text field (e.g. [%Shared Documents:Modified By%]) may have a side effect on any other text that is stored in the same text field. You will find that until this bug has been fixed by Microsoft, one level of back slashes is stripped out. A simple workaround is to replace any backslashes in your text with double backslashes (\\). SharePoint 2007 does not suffer from this problem.
 

#1140 - HTML to PDF Conversion of SP2010 screens is not working correctly.

Due to the large amount of JavaScript and Dynamic HTML that the SharePoint 2010 user interface relies on, some pages may not convert correctly when using the Convert Page to PDF option from the user's Personal Actions menu. SharePoint 2007 does not suffer from this problem.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v3.5
 

Read the announcement to see what is new in this version.
 

#880 - Transparency settings in watermarks depend on PDF Reader.

The PDF Converter allows transparency settings to be specified for entire watermarks as well as individual watermark elements. Some PDF Readers do not always interpret transparency of elements correctly. You may need to move your transparency settings from the watermark container to the individual elements.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v3.4
 

Read the announcement to see what is new in this version.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts, separate Print Views or switching the server to InfoPath 2010, which is much improved.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround switch to using Office 2010 on the server or save the presentation using the PPTX, ODP or XML format.
 


PDF Converter for SharePoint v3.2.0.20 - 3.2.1.22
 

Read the announcement to see what is new in this version.
 

#781 - Files containing macros fail to convert when using Visio 2010.

When using the beta version of Visio 2010 to convert Visio files that contain macros, the file will fail to convert. As a workaround remove the macro or use Visio 2007 to convert these kind of files.
 

#782 - The 64 bit version of Office 2010 is not supported.

Regardless of the OS used (32 bit / 64 bit), always use the 32 bit version of Office 2010 on the document conversion server.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v3.0.0.11
 

Read the announcement to see what is new in this version.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v3.1.1.17 - 3.1.2.18
 

Read the announcement to see what is new in this version.
 

#734 - MS-Word Documents containing the ASK field code do not convert.

MS-Word documents that contain this rare field code cause the converter to time out. To quickly check if a document contains such a field code, press CTRL-A to select all text and then press F9 to refresh all field codes. If a dialog box shows up asking for text to be entered then your document contains an ASK field code. Please remove it before conversion.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered. Please consider using our Workflow Power Pack in these situations as outlined in this article.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v3.0.0.11
 

Read the announcement to see what is new in this version.
 

#700 - Workflows started for files written via WEBDAV may not work correctly under load

When copying a large number of files to a Document Library using WEBDAV (e.g. using Windows File Explorer), workflows may trigger before the file has been fully copied into SharePoint, causing the conversion to fail. As a workaround, copy large number of files using SharePoint's 'Upload multiple files' facility.
 

#686 - Central Administration screen only available in English

Although the user facing screens are available in multiple languages, the Central Administration configuration screen is only available in English.
 

#687 - Not all converters generate PDF Bookmarks

The MS-Word converter is the only converter with the ability to automatically generate PDF Bookmarks.
 

#668 - InfoPath Character spacing is not optimal

Although in general the converted InfoPath files look good, character spacing may be less than optimal. As a work around try to use different fonts or a separate Print View.
 

#678 - Empty Excel sheets cannot be converted

Excel sheets that contain no data cannot be converted to PDF format.
 

#689 - Password protected documents cannot be converted from SharePoint

Although our conversion engine has the ability to convert password protected documents via the Web Services interface, none of the SharePoint related user interfaces allow passwords to be entered.
 

#701 - Smart art objects are not converted for PPT files

PowerPoint files that contain 'smart art' objects and are saved in the 'Pre Office 2007' PPT format are converted correctly with the exception of the Smart Art. As a workaround save the presentation using the PPTX, ODP or XML format.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 


PDF Converter for SharePoint v1.4.0.0 - v1.4.0.2
 

Read the announcement to see what is new in this version.
 

#628 - DocProperties containing spaces and quotes are not supported

As of version 1.4.0.0 DocProperties embedded in an MS-Word document are automatically refreshed using the values in any associated SharePoint Columns. However, this fails if the DocProperty field name contains either a space or a double quote ("). We are working on a solution, which will be released shortly.
 

#620 - Custom Formatting in DocProperties is not supported

When a DocProperty contains additional formatting information then this is not automatically applied. For example {DOCPROPERTY DateField \@ "yyyy/MM/dd"}.
 

#579 - Doc Properties inserted using MS-Word 2007 'Quick Parts' are not supported

Currently the PDF Converter only supports DocProperties that have been inserted using the 'pre MS-Word 2007' insert field -> DocProperty functionality. Please do not use MS-Word 2007's Insert -> Quick Parts -> Document Property. 
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with fully automated and friendly command line based batch scripts to deploy the solution.
 

#521 - PDF Engine - Converting Arabic documents is not supported

Documents authored in Arabic use the RTL (Right To Left) text direction, which is currently not supported.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.3.0.2
 

Read the announcement to see what is new in this version.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with fully automated and friendly command line based batch scripts to deploy the solution.
 

#521 - PDF Engine - Converting Arabic documents is not supported

Documents authored in Arabic use the RTL (Right To Left) text direction, which is currently not supported.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.2.3.41734
 

Read the announcement to see what is new in this version.
 

#482 - SETUP - Resources may need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The SharePoint Administrator may need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with fully automated and friendly command line based batch scripts to deploy the solution.
 

#521 - PDF Engine - Converting Arabic documents is not supported

Documents authored in Arabic use the RTL (Right To Left) text direction, which is currently not supported.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.1.1.41734
 

Read the announcement to see what is new in this version.
 

#482 - SETUP - Resources need to be manually deployed on farms where the Timer service account is not a local Administrator.

High security SharePoint environments, in which the Timer service account is not in the local Administrators group, do not support the automatic deployment of SharePoint Resource files. This is not specific to the PDF Converter. The customer will need to manually run the following command on each SharePoint server: "stsadm -o copyappbincontent"
 

#331 - SETUP - No GUI installer

The Windows installer, which was available in the Beta version, has been dropped as it didn't fully work in some of our customers' environments. The product ships with command based batch scripts to deploy the SharePoint solution file.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 


PDF Converter for SharePoint v1.0.1.6 - BETA
 

#342 - Web applications that use Forms Based Authentication are not supported?

When users are authenticating using FBA then documents cannot be converted to PDF. It is expected that this issue will be resolved in the official release.
 

#341 - PDF Engine - Converting large 'plain text' files is slow

Converting a plain text file of 1MB, an unrealistic scenario, takes an unexpected amount of time to convert to PDF. This is due to a bug in the PDF Engine, which has been reported to the relevant team.
 

#337 - PDF Engine - Images outside of the margins are cropped for MS-Word 2003 files

Images that are located outside of the page's margins are cropped when the document has been saved in MS-Word 2003 format. This only happens on certain OS Versions and is due to a bug in the PDF Engine, which has been reported to the relevant team. It is expected that this issue will be resolved in the official release.
 

#335 - PDF Engine - Some 'double byte' character sets are not supported

Even though our user interface fully supports Japanese, the PDF Engine currently doesn't support some double byte character sets such as those used by the Japanese language. This is due to a bug in the PDF Engine, which has been reported to the relevant team.
 

#270 - PDF Engine - Text wrapping around floating elements not supported

Currently we only support the following Text Wrapping options: Inline with Text, Above Text and Below Text. This is a known limitation of the PDF Engine. All other wrapping will be supported in a future release.
 

#243 - PDF Engine - MS-Word 2007 WordML schema not supported

Although MS-Word 2007 (docx) as well as MS-Word 2003 WordML files are fully supported, files saved as WordML2007 are not. This is a known limitation of the PDF Engine.
 

#234 - PDF Engine - ODT (Open Office) documents experimental support

Support for Open Office Writer files (ODT) is currently experimental. If you are interested in using this file format then please download the trial version and test if it works with your particular documents.
 

#346 - PDF Engine - TOC always rendered as blue hyperlinks

Although this may be considered a 'feature', the Table Of Contents are always rendered in 'blue hyperlink format'. This is a known issue in the PDF Engine, which has been reported to the relevant team.
 

#230 - PDF Engine - Footnotes are not supported

Footnotes embedded in the documents are currently ignored. This is a known issue in the PDF Engine, which has been reported to the relevant team.