> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/general-operation/pdfs-as-external-items-in-a-pr.md).

# Issues with PDFs as External Items in a Project File

How to fix PDFs inserted as External Items misbehaving by adjusting Adobe Reader and default PDF settings.

## I have some PDFs inserted as External Items in my ENERCALC Project Files. Why are these now misbehaving?

It probably has to do with a setting in Adobe Acrobat Reader DC. Fortunately the fix is easy. In Adobe Acrobat Reader DC, go to Edit > Preferences. In the Security (Enhanced) category, deselect the option to "Enable Protected Mode at startup". This should resolve the issue, and PDFs as External Items should now behave as expected.

## I can't view PDFs in my project file, regardless of whether they are linked or embedded. What now?

Check to see which program your system is set to use as the default for PDF files. If it is Bluebeam, try setting the default to Adobe Acrobat Reader DC.

To install Adobe Acrobat Reader DC: [https://helpx.adobe.com/acrobat/kb/install-reader-dc-windows.html](https://helpx.adobe.com/acrobat/kb/install-reader-dc-windows.html,)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/sel-faq/using-the-software/general-operation/pdfs-as-external-items-in-a-pr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
