---
title: "Servicename and Instancename in the Portal and in Lasernet Developer Must Be the Same"
slug: "servicename-instancename-in-portal-and-lasernet-developer"
description: "When the instance name in the portal and the instance name in Lasernet Developer do not match, then this can cause instability, missing log files etc. The article describes how to resolve these issues."
tags: ["Lasernet Developer"]
updated: 2026-03-04T16:00:14Z
published: 2026-03-04T16:00:14Z
canonical: "kb.lasernetgroup.com/servicename-instancename-in-portal-and-lasernet-developer"
---

> ## 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.

# Servicename and Instancename in the Portal and in Lasernet Developer Must Be the Same

**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).

When the instance name in the portal and the instance name in Lasernet Developer do not match, then this can cause instability, missing log files, etc.

To resolve this issue, follow these steps:

1. Check your Service name - in the example, **First**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-TZMLLDUO.png)

1. Check your instance name in Portal.

If different from the Service name, delete the instance from the portal and create it again with the correct name. Pay special attention to the use of underscores, dashes, and spaces.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-FZ3UOJ15.png)

1. Open Lasernet Developer, click **Servers** in the **Tool** menu, and open its **Properties** window.
2. Click the drop-down menu, select the instance name, and click **Ok**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-GH4W25M3.png)

1. Open the **Commit** tab and then **Deploy**.