Question
Not able to preview attachment using snowbound virtual viewer
Hi,
We are facing the issue to preview the attachment using snowbound virtual viewer.
Below are the steps we completed to implement snowbound virtualviewer.
- Deployed VirtualViewer.war file to tomcat9/webapps directory
- Copied the SnowboundLicence.jar file into virtualviewer/WEB-INF/lib directory.
- Added the VirtualViewer component to the list of Enabled components in application definition rule.
- Restarted the server
- Updated dynamic system setting(VirtualViewerURL) rule by giving the value.please find the attachment for the screen shot
But when I tried to open the attachment, getting error.PFA for error Message
Please let me know if any one knows the solution for it.
Thank you
Regards,
Srinivas
Hi
Thanks for the reply.
I have updated dynamic system setting value as http://<ServerURL>/virtualviewer/? format.
When I tried to open attachment Virtual viewer screen is opening but attachment content is not displaying.
Getting below message:
"Document result without document content returned for {documentId}"
Please suggest how to resolve this issue.
Regards,
Srinivas
Just double checking with you, hope you have just added the "/?" to the original url on https as attached in the first document of the issue, so that it reaches the Pega application to retrieve the document.
1) Please try with other type of files like png and let us know if that works. If that works fine, in that case the issue might be the specific docx file you are trying to preview in your previous comment.
2) In case png file is also giving same error. Please make sure that the 2 servers (Virtual viewer server and Pega Server) can communicate with each other. You can try pinging one server from another.
3) In case you are still not able to preview any attachment. It is best to check the logs as per the log location mentioned in https://community.pega.com/knowledgebase/articles/implementing-snowbound-virtualviewer-pega-platform something like ../logs/pegaLogs/virtualviewerlog.log as well as catalina logs on virtual viewer side.
Let us know your findings.
Hi,
Thanks for response.
I have tried with PNG and PDF file also still getting same error.
pega PRPC and virtual viewer war files placed on same tomcat application server.so they both should communicate each other right?.
I have noticed that there is one exception on virtual viewer log file.Please find the attachment for the exception details.
"2018-11-20 05:21:21 ERROR PegaContentHandler:getDocumentContent:821 -
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated".
please let me know if you need any other information.
Thank you.
Regards,
Srinivas
Hi Srinivas,
As per the first document uploaded by you, I see that the Pega is running on http but for Virtual viewer you have mentioned https. Just change the VirtualViewerURL DSS to using http and see if error is resolved.
Also what is the Java version you are using?
Hi,
I have already updated to http, after that only snowbound virtual viewer screen is opening when click on the attachment.
But getting the below error.
"Document result without document content returned for {documentId}"
java version:1.8
Regards,
Srinivas
So in your case currently both Pega and Virtual viewer are using http.
Please try following
1. Use https in the virtual viewer url dss and see what happens
2. Use https in pega url (your browser prweb url) and see what happens
3. Use https in both places (Pega and Virtual viewer) and see what happens.
Issue might still persist. If yes, There might be some SSL certificate on the server.
If there is still some issue, we would need a SR to debug further.
Please make sure that the VirtualViewerURL ends with "/?"
so correct url will be in format
http://<serverurl>/virtualviewer/?
If the issue still persists then try to hit http://<serverurl>/virtualviewer/? (Replace the server url )in the standalone browser window and see if you are able to see a virtual viewer frame. if yes, Let us know so that we can debug further. If not, Please check the virtual viewer server logs once and see if you see any error in server startup.