> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/data-integration-issues/cannot-run-a-job-in-a-repository-on-a-carte-instance-from-another-job.md).

# Cannot run a job in a repository on a Carte instance from another job

If you run a Job on a Carte instance and the repository information does not seem available, and further jobs and transformations cannot be loaded after the job runs a child job, then you may see an error similar to the following message:

```
RepositoriesMeta - Reading repositories XML file: <HOME>/.kettle/repositories.xml
General - I couldn't find the repository with name 'singleDiServerInstance'
(...)
Secondary - Could not execute job specified in a repository since we're not connected to one
(...)
```

Perform the steps below to run jobs in a repository on a Carte instance from another job:

1. Using an editor, open the `<HOME>/.kettle/repositories.xml` file on the server where the Carte instance is located.
2. Add a new `<repository>` element to it or append the current content with the name `singleDiServerInstance`, as shown in the following code block:

   ```xml
   <repository>
       <id>PentahoEnterpriseRepository</id>
       <name>singleDiServerInstance</name>
       <description/>
       <is_default>false</is_default>
       <repository_location_url>http://localhost:8080/pentaho</repository_location_url>
       <version_comment_mandatory>N</version_comment_mandatory>
   </repository>
   ```
3. Save and close the file.

You can now run jobs in a repository on a Carte instance from another job.


---

# 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://docs.pentaho.com/pdia-data-integration/10.2-data-integration/data-integration-issues/cannot-run-a-job-in-a-repository-on-a-carte-instance-from-another-job.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.
