Free Support Forum -

Rendering excel formats


when we try to render an Excel document into an image, we get a blank Image with 1px size. We use the latest version available for Java (3.2.2)

DocumentInfoContainer docInfo = imageHandler.getDocumentInfo(parameters.getPath());

new Gson().toJson(docInfo): {“fq”:“Mappe1.xlsx”,“fW”:“xlsx”,“fr”:11437,“ft”:{“a”:[“d”,“D”,“f”,“F”,“g”,“G”,“m”,“M”,“o”,“O”,“r”,“R”,“s”,“t”,“T”,“u”,“U”,“y”,“Y”],“R”:636104953158870000,“erX”:“de_AT”},“fY”:“Cells”,“fZ”:“Xlsx”,“gb”:{“ff”:“Sep 26, 2016 2:01:55 PM”,“fi”:1,“fj”:[{“fy”:1,“fq”:“Sheet1”,“fz”:0,“dh”:1,“dj”:1,“fA”:[],“fC”:true}],“fl”:1,“fm”:1}}

Hi Josef,

We were able to reproduce this issue at our end as well. We would like to tell you that this issue is already logged in our internal issue tracking system (excel file is not properly rendering to html or images) and the fix will be available in upcoming release of the API.
But, at the moment we cannot share any ETA about the upcoming release. As we get any update from the concerned team we will notify you.

Please stay tuned.
Many Thanks

The issues you have found earlier (filed as VIEWERJAVA-1206) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by groupdocs.notifier.

Any updates?


if i try to render an Excel file, i get attached exception while getting the document Information:

DocumentInfoContainer docInfo = null;



docInfo = imageHandler.getDocumentInfo(parameters.getPath(),new DocumentInfoOptions());

} catch (GroupDocsViewerException e) {

logger.addError(“viewDocumentImage”, e.getMessage());


[MESSAGE] Index: 0, Size: 0

[com.groupdocs.viewer.converter.a.g.bKo(Unknown Source),

com.groupdocs.viewer.helper.c.c(Unknown Source),

com.groupdocs.viewer.helper.c.b(Unknown Source),

com.groupdocs.viewer.handler.ViewerHandler.d(Unknown Source),

com.groupdocs.viewer.handler.ViewerHandler.a(Unknown Source),

com.groupdocs.viewer.handler.ViewerHandler.getDocumentInfo(Unknown Source),


we use Java-viewer 3.7

Hi There,

We are glad to inform you that this issue has been resolved in the upcoming release of the API. And the release is expected in 3rd or 4th week of this month.
Please stay tuned.

Many Thanks

Hi Josef,

Thanks for sharing your experience and the code snippet.
We are not able to reproduce this issue at our end, please see the attached screenshot. Can you please share the problematic file, we’ll investigate the issue using that file?

Best Wishes