Hi,
We are facing an issue while converting docx to pdf file. The docx file have one page but the result pdf file have two pages. This issue is happening only in one of our servers. The conversion is working well in other machines.
Is there any machine specifications needed for Group docs to perform conversion without this issues?
@jerinthomas
Please share following details and we’ll investigate this scenario:
- API version that you are using (e.g. 20.1, 22.5)
- Sample conversion code or application
- License type
- Do you see an evaluation mark in resultant PDF?
- Do you face this issue for a specific file?
- Problematic Word file and resultant PDF
Hi,
Please find the details
• Nuget Version 22.2.0
• Sample code
using (Converter converter = new Converter(inputFile))
• Developer OEM
• No Evaluation marks
• Yes we are currently facing issue for a single file
inputFile.docx (46.0 KB)
outputFile.pdf (67.3 KB)
@jerinthomas
Please also share the server details where you are facing this issue.
- Server name and version
- List of installed fonts on the server
- Does the output generated on Windows and the output generated on your server has same font?
Server Name :
Windows server 2019 Data Center
Installed Fonts in Server
fonts.png (44.3 KB)
Yes there is font difference in the output generated from server and my local windows machine. Its coming correctly in my local machine but there is a change in the output pdf generated from the server.
ex : the value June 8 changed to June 7.
OutputFromLocalWindowsMachine.pdf (97.2 KB)
@jerinthomas
Please make sure that the source file’s font is available on your server as well (just like it’s available on your local machine). It’s been observed that your Word file has Garamond font. Please install that on your server as well and let us know if issue persists.
Hi @Atir_Tahir,
Installing Garamond font in the server worked. now the pdf file is only one page. But there is a change in date value on the result pdf. June 10 in the docx file changed to June 9 in the result pdf file.
@jerinthomas
We are investigating this scenario. Your investigation ticket ID is CONVERSIONNET-5281. We’ll notify you in case of any update.
Hi @Atir_Tahir,
Any update on CONVERSIONNET-5281 ticket?
@jerinthomas
This issue is still under investigation.
The issues you have found earlier (filed as CONVERSIONNET-5281) have been fixed in this update. This message was posted using Bugs notification tool by Atir_Tahir