---
title: "Error Message: 'Failed to Pass Job: Cannot Assign Requested Address'"
slug: "error-failed-to-pass-job-cannot-assign-requested-address"
description: "After importing a configuration created in an older version to Lasernet 9, an error log can occur when a job is exchanged between two services/servers."
updated: 2026-03-05T13:20:06Z
published: 2026-03-05T13:20:06Z
canonical: "kb.lasernetgroup.com/error-failed-to-pass-job-cannot-assign-requested-address"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Error Message: 'Failed to Pass Job: Cannot Assign Requested Address'

**Applies to:** Lasernet 9

> [!NOTE]
> Note
> 
> This article describes a software version that is no longer supported. Although the software will no longer receive updates or technical support, existing documentation, such as this article, will be retained for reference purposes but will no longer be updated. If you have any questions, contact [Lasernet Support](https://support.lasernetgroup.com/new-ticket).

After importing a configuration created in an older version of Lasernet to Lasernet 9, an error log can occur when a job is exchanged between two services/servers.

> [!CAUTION]
> Error
> 
> Failed to pass job: Cannot assign requested address

This happens within the configuration, which has two modules connected that appear on different servers/instances in the configuration. Lasernet 9, unfortunately, cannot auto-convert these settings.

This error can also be caused by backslashes in printer profile names.

## Resolution

The server name and port number are no longer supported as a part of the module path and now require the instance name only.

In previous versions, such as Lasernet 7 or 8, the destination syntax was: `servername:portnumber/modulename`

After migration to Lasernet 9, the syntax for a destination must be changed to: `instance:modulename`

> [!NOTE]
> Info
> 
> The syntax for module destinations can be present in **Modules**, **Forms**, and **Scripts**.