Unrecognized MS Word version for generating Application Document.
Hello! I have a Pega 8.3 system that I'm accessing via Windows 10 and Office 2013. In the Pega 8.3 system, I go to generate the application document and get the following error.
"Initialization Failed. Unrecognized Microsoft Word version. Only Word 2010, 2007, 2003, 2002, and 2000 are supported."
It generates part of a document and then stops. Any ideas on how to fix this?
Thanks!
***Edited by Moderator: Lochan to tag SR***
Pegasystems Inc.
US
If this is the DCO document (and not Word merge) and this is 8.x, then this generation should be all done on the server and not even care about what Word version you have.
I'll see if I can tag someone from DCO here to confirm my understanding.
Updated: 22 Jan 2020 1:57 EST
Highmark Health
US
This is the DCO document. I get the message, "Document generation completed. Click to save the document locally." I click to download the document and when I do, it opens the document and displays the error about the WORD version. It looks like the document is generated on the server as you stated.
Thanks!
Updated: 22 Jan 2020 1:57 EST
Highmark Health
US
I am getting the same error with the 3 document types - Application Overview, Data model, and Gap analysis.
I've attached the document that was generated.
Pegasystems Inc.
IN
It seems this document was manually saved after generation, so it is opening fine (Data lost). Can you please share the document which is giving error on opening without saving manually.
Updated: 22 Jan 2020 1:57 EST
Highmark Health
US
Here is a document that was generated and I copied it from the ServiceExport folder.
I opened via my FTP program and from my desktop and I still get the same error as when I try to open it via the download.
Thanks!
Pegasystems Inc.
IN
The file which you shared is opening up fine in my windows machine. I am using office 365 to open it. Is it possible for you to try it in a machine which has office 365? If not, let us know.
Pegasystems Inc.
IN
Did you already raise a SR for this issue. If not, please raise one. We would need older windows+ office suite to debug this further.
