> 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/9.3-data-integration/data-integration-issues/troubleshoot-pentaho-data-service-issues.md).

# Troubleshoot Pentaho data service issues

You can list the services running on the Pentaho Server or Carte server using the `listService` command, as shown in the following example URL:

* `http://localhost:8080/pentaho/kettle/listServices`

If the data service appears in the list, the Pentaho Server is set up correctly. Check your network and client setup.

If it does not appear in the list, try the following tasks:

* If you stored the transformation in the Pentaho Repository, check the status using this command: `http://localhost:8080/pentaho/kettle/status`. Make sure the repository name appears in the configuration details section. If the repository name is missing or an error appears, check the configuration of the **slave-server-config** and accessibility of the `repositories.xml` file.
* If you did not store the transformation in the Pentaho Repository, but instead stored it on the local file system, make sure the service name is listed and accessible from the user account that runs the Pentaho Server in: `<users home>/.pentaho/metastore/pentaho/Kettle Data Service`

If the service name (the table to query) is still missing, reopen the service transformation and check the data service in the transformation settings.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/data-integration-issues/troubleshoot-pentaho-data-service-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.