Trinkor Sales Department Posted May 28 Report Share Posted May 28 Hi, We are evaluating using Nitro PDF Pro as our Default PDF program with our move to Worksite 10 and have purchased a license in order to test this. Our Current Configuration is as follows: - iManage Work Server is version 10.4.8 - iManage Work Desktop is version 10.9.3. - Windows Server 2019 NITRO has been installed following your deployment guide (https://www.gonitro.com/user-guide/pro/integrations/deploying-imanage-work-10) with an update to the new pathway with the latest release of Work 10 (C:\Program Files\iManage\Work10\109.3.43) We are able to open PDFs using the iManage work browser, make changes to the document and Sync and Save with no issues. The documents show "checked out" when opening them in Nitro and check back in correctly when we close them. If we try to save over the top of a checked out document Nitro shows the "Document is checked out" error correctly. The issue is when we try to save a NEW Document or Save a New Version into iManage we receive the following Error in Nitro (image taken from another forum post): "Sorry, the iManage Work Server failed to understand Nitro PDF Pro's Request." We have checked the Registry and the Path is correct. We have done a fresh install and still experience the same issue. Do you have any guidance or troubleshooting steps for us to see if we can fix this error before we look into an alternative PDF solution? Looking forward to your advice. - Steve. Link to comment Share on other sites More sharing options...
Official Nitronaut Joseph Capiral Posted June 4 Official Nitronaut Report Share Posted June 4 Hi @Trinkor Sales Department Thank you for reaching out to us through our Community Forums. We noticed that there is an active support case for the issue. To get a faster response, we recommend communicating through the support ticket case. Thank you. Link to comment Share on other sites More sharing options...
Steven Laurence Posted June 10 Report Share Posted June 10 Hi @Trinkor Sales Department, did you ever get a solution to this issue? If so, could you post an update here along with the solution fix? Thank you! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now