Specific error messages:
When the export fails with a stack trace chances are the error is still in the project content and not in the template itself.
The error could be caused by something like a space in the label of your node, a missing document property, or a problem with the format of a hyperlink. If the stack trace doesn't pinpoint the source of the issue, try Validating your project to check for common issues like node labels, missing Issue fields, missing document properties, and more.
Below are more details and troubleshooting tips for the most common export error messages. This is not an exhaustive list of all of the possible error messages and solutions. If you can't find a solution to your problem here, please contact the support team and send us a copy of the stack trace!
The error: undefined method `replace' for nil:NilClass indicates a problem with your document properties. Start by checking your report template to make sure that the values of your custom properties aren't flagging Word's internal spellcheck.
If all looks good there, validating your project to check for a mismatch between your project contents and what your template is looking for.
Next, use the export log to see which document property is causing problems. On the
/pro/export page, the onscreen log will display something like this:
[11:22:33] Populating custom properties. [11:22:33] dradis.project: Vulnerability Assessment Report [11:22:33] dradis.client: ACME Inc [11:22:33] dradis.version: <V> [11:22:34] There was an error while generating the report: undefined method `replace' for nil:NilClass
Each document property that is being replaced will be listed in the export log in the format
property.name: Property Value. Check the document property listed right above
There was an error while generating the report: undefined method `replace' for nil:NilClass. That's the one causing problems!
The error: There was an error generating the report: can't dup NilClass indicates a problem with one of the links in your project. Open the content that appears in the log directly above this error and check for errors. For example, if the error appears after Issue#1234, open up that Issue by navigating to
/pro/issues/1234 on your instance and check the links. Is the :href nill (e.g.
"foo":) or are you dealing with any special characters in the link? In the case of special characters (including single quotes), encasing the link in a code block should do the trick. If you think you've stumbled on a bug, please contact our support team and let us know!
The Invalid predicate error also indicates a problem with one of the links in your project. The most common cause of this problem is that there is a single quote in your link. For troubleshooting ease, the problem link is included in the error message.
You will see an error message like this in your onscreen log:
[16:14:17] Post-processing hyperlinks.
[16:14:17] There was an error while generating the report: Invalid predicate: //r:Relationship[@Target='http://staging.sample.com/example.json?search=a'++--+&page=1']
The link listed inside
@Target='' is the link that is triggering the error. Search your project for this link. In most cases, wrapping this link in a code block will allow the report to export without an error.
For example, in your project change:
The No such file or directory @ dir_initialize error indicates a problem with one of the screenshots/images in your project. The most common cause of this problem is that your Project Template contains screenshot links.
When you export your report, you will see an error message like this in your onscreen log:
[19:57:14] There was an error while generating the report: No such file or directory @ dir_initialize - /opt/dradispro/dradispro/releases/20160629160951/attachments/1502
To resolve this error, Search your project for the ID referenced in the onscreen log (
1502 in the example above). This will show you where the link appears in your project. Edit or delete the screenshot and confirm that it is displaying correctly within Dradis before exporting your report again.
The function not found error also indicates a problem with one of the links in your project. The most common cause of this problem is that there are multiple single quotes in your link. The word enclosed by these single quotes will appear in the error message as the function name.
For example, if you see an error message like the following in your onscreen log:
[15:12:18] There was an error while generating the report: xmlXPathCompOpEval: function alert not found
Search your project for the function name ("alert" in this example) and look for an instance in a hyperlink like
To resolve this error, either edit the hyperlink or enclose it in a code block to allow the report to export without an error.
If you have found a bug with the report engine, please let us know about it through one of these channels:
Make sure to include the stack trace of your report generation so we know where to start looking for problems!
Next help article: Word error: ambiguous cell mapping →