After extensive usage of the plugin by a significant number of clients, we have observed several frequent errors or blockages where users get stuck and believe it to be a plugin bug, when in reality it is a client machine configuration issue.
...
- Ensure that Microsoft Office is properly installed on your machine. If not, please install it.
- Check that your Office does not have any restrictions on running its services in the background.
- Create a "Desktop" folder in C:/Windows/(system32 or SysWOW64)/config/systemprofile.
- Schedule a task to run every minute. This task eliminates report windows indicating that a previous conversion failed. The scheduled task should execute a .bat file containing these two lines:
Info icon false title MS bat script for looking those windows and close them over Windows' task scheduler. - taskkill /F /FI "WindowTitle eq Microsoft Word*"
- taskkill /F /FI "WindowTitle eq Microsoft Office*"
Schedule a task (similar to step 4) but this time the task should be executed one time per day at a time when the plugin is not in use (for example, at 2 am) because running this task prevents PDF generation. The purpose of this task is to eliminate zombies created by multiple instances of MS Word and scripts in the task manager. This .bat file should contain these two lines:
Info icon false title MS bat script to kill them by script over Windows' task scheduler. - taskkill /f /t /im wscript.exe
- taskkill /f /t /im winword.exe
- Ensure that the service account has the necessary read and write permissions on the Atlassian Jira execution directory. Even if the service account is part of the local administrators group, it may not have the required permissions due to UAC (User Account Control) restrictions.
- To fully understand points 3, 4, and 5, please refer to this documentation, especially the section Running documents4j application as Windows service, where everything is detailed.
...
| Info | ||
|---|---|---|
| ||
|
Refer to the last part of the section Running documents4j application as Windows service in this documentation.
If you are experiencing difficulties, have questions, or need our assistance, please do not hesitate to contact us. We are available to help you at any time.
Permissions
- Service Account Write Permissions Issue
In some cases, the service account used to run Jira may not have the necessary write permissions on the Atlassian Jira execution folder.
Even if the account is part of the local administrators group, UAC restrictions can prevent access.
Granting the service account direct write permissions on the folder resolves this issue.
- Missing "Desktop" Folder and Permissions in System Profile
It is crucial to create a "Desktop" folder in both C:/Windows/system32/config/systemprofile and C:/Windows/SysWOW64/config/systemprofile.
Additionally, it is important to ensure that the "Desktop" folder and the "config" folder at the root of both C:/Windows/system32/config and C:/Windows/SysWOW64/config have administrator-level permissions.
These permissions are necessary to allow the service account to perform operations without restrictions, which helps prevent issues with PDF generation.