> For the complete documentation index, see [llms.txt](https://shoppa.gitbook.io/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shoppa.gitbook.io/knowledge-hub/vanliga-fragor-eng/troubleshooting/printer-could-not-be-accessed.md).

# Printer could not be accessed

This error usually occurs when the the computer can't access the printer due to changes in the printer driver or network. The error can also be caused by a corrupt picture in the template.

Start by creating a new printer binding, you can see how [here](https://kb.shoppa.com/knowledge-base/connect-your-printer-to-shoppa/)

If you can print other templates or products the error might be caused by a corrupt picture. Perform the following steps:

1. Exit Shoppa
2. Open the Windows start menu and type *%appdata%* and press Enter
3. Open the “Shoppa” folder within %appdata%
4. Find the folder with the name “cache”
5. Delete the cache folder
6. Start Shoppa

This process should result in Shoppa downloading a new picture when printing which should resolve the issue.


---

# 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://shoppa.gitbook.io/knowledge-hub/vanliga-fragor-eng/troubleshooting/printer-could-not-be-accessed.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.