> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-windows-cli-guide/commands/startrasobj.md).

# startrasobj

![Parallels](https://www.parallels.com/static/pl/fileadmin/res/img/navigation/pl-logo-dk.png)

## AppserverClient Command Line Interface

### startrasobj

starts a published object from a RAS connection.

**Category: RAS-Connections**

```
AppServerClientCLI startrasobj -id ras:61:34 [-waitforid [20]] [-dismisserrortime 5] [returnpath] [-window 12345]  
```

### Arguments

* **`id (mandatory)`** Specify the published item ID to use.
* **`waitforid (optional)`** Wait for sessionid then return it. See notes for further information. Has no effect on local applications.
* **`dismisserrortime (optional)`** Time in seconds before the error message is automatically dismissed. A value of -1 will not show the error. Has no effect on local applications.
* **`returnpath (optional)`** When set, the command will return the arguments required to start the application instead of starting it.
* **`window (optional)`** Specify the window handle that will be used as the parent to any UI required.

### Return codes:

ok - Command was successful\
NotAvailable - Communication with the client backend failed, ensure that the client is running\
InvalidId - Invalid connection, object or session ID\
InvalidArgs - Some arguments are missing or invalid\
Exception - System problem

### Examples:

AppServerClientCLI startrasobj -id ras:61:34\
AppServerClientCLI startrasobj -id ras:61:34 -waitforid\
AppServerClientCLI startrasobj -id ras:61:34 -waitforid 20

### Notes:

If you use waitforid, the CLI will wait until the session is started and its ID is returned. waitforid can take the time in seconds after which the command would timeout as an argument.

### See also:

[logonras](/landing/ras-windows-cli-guide/commands/logonras.md)\
[logoffras](/landing/ras-windows-cli-guide/commands/logoffras.md)\
[logoffallras](/landing/ras-windows-cli-guide/commands/logoffallras.md)\
[logoffrassession](/landing/ras-windows-cli-guide/commands/logoffrassession.md)\
[savefavorites](/landing/ras-windows-cli-guide/commands/savefavorites.md)\
[disconnectras](/landing/ras-windows-cli-guide/commands/disconnectras.md)\
[disconnectallras](/landing/ras-windows-cli-guide/commands/disconnectallras.md)\
[getloggedrasinfo](/landing/ras-windows-cli-guide/commands/getloggedrasinfo.md)\
[getraspolicyinfo](/landing/ras-windows-cli-guide/commands/getraspolicyinfo.md)\
[getpublicipinfo](/landing/ras-windows-cli-guide/commands/getpublicipinfo.md)\
[clearpublicipinfo](/landing/ras-windows-cli-guide/commands/clearpublicipinfo.md)


---

# 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.parallels.com/landing/ras-windows-cli-guide/commands/startrasobj.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.