Tools

Error: "Server already has its own UID. Creation of another Server Identity is not possible." in Serv-U

This article shows how to troubleshoot an issue where Serv-U is showing the error: "Server already has its own UID. Creation of another Server Identity is not possible." after changing the NETWORK SERVICE account to another service account and/or after upgrading Serv-U from an older version to the latest 15.5.0.

First published date

12/19/2022 6:45 PM

Last published date

4/9/2025 9:06 PM

Overview

Serv-U is a file server that allows end users to transfer files via FTP, FTPS, SFTP, web browsers, and mobile devices. Serv-U runs on both Windows and Linux and supports IPv4 and IPv6 networks. In addition, it runs natively on both 32-bit and 64-bit versions of Windows and Linux, taking advantage of performance benefits inherent in 64-bit computing. 

By default, Serv-U runs as a System Service.

On Windows, Serv-U Service can run under any account. By default, on versions before 15.3.2 the Serv-U Service account was Local System a.k.a SYSTEM. Running Serv-U under SYSTEM was determined to be a source of vulnerabilities because it is a built-in account with unlimited access to the OS and User resources.
Therefore, starting from 15.3.2, the default account is NETWORK SERVICE (not to be confused with NETWORK account). NETWORK SERVICE is also a built-in account. that has well-balanced privileges and does not allow the modification of vital OS resources and access to the data residing in user-protected areas (e.g., to a user's documents).

On Linux, the root is the only account under which Serv-U Service can run.

When the service account is changed from NETWORK SERVICE to another service account after the 15.3.2 upgrade, it will cause Serv-U to not have permission to the Serv-U.Archive file and the Server Identity and will throw the error below:

Note: There are also other causes why the error is showing in Serv-U, not just because of changing the NETWORK SERVICE service account.
  
Server already has it's own UID. Creation of another Server Identity is not possible.

Product section

Serv-U Managed File Transfer & Serv-U FTP Server

Cause

  • Server Identity was already created before and was unable to export it. 
  • You change the Serv-U Log On type in the services.msc.
  • Open Serv-U.Archive file in notepad and there's already an encrypted keys here:
  • image.png

Resolution

Scenario 1: A backup of the Server Identity file is available

Launch the Serv-U Management Console
1. Go to Global > Server Details > Server Identity tab
2. Click Import, and navigate to where the exported server identity is saved

If the Import button is not available, follow the steps below.
1. Stop the Serv-U service through services.msc
2. Create a backup copy of the Serv-U.Archive file found inside C:\ProgramData\RhinoSoft\Serv-U (Folder is Hidden in Windows by default)
3. Rename the Serv-U.Archive.Backup file inside C:\ProgramData\RhinoSoft\Serv-U
4. Edit the Serv-U.Archive file found inside C:\ProgramData\RhinoSoft\Serv-U
5. Remove the Server Identity information starting from the colon until the bracket then Save. 

 image.png

6. Start the Serv-U service
7. Then the Import button should be available to import the backup Server Identity file.
 

Scenario 2: Serv-U.Archive file has server identity but is not detected

In this situation, the Serv-U server service is not running the default 'Network Service', but when checked, the Serv-U.Archive file has a server identity stated in Scenario 1, item 5, and then the import button is not available.

Follow these steps to resolve the issue.
1. Stop the Serv-U service through Windows Services or run services.msc.
2. Create a backup copy of the Serv-U.Archive file found inside C:\ProgramData\RhinoSoft\Serv-U (Folder is Hidden in Windows by default).
3. Rename the Serv-U.Archive.Backup file inside 'C:\ProgramData\RhinoSoft\Serv-U'
4. Edit the Serv-U.Archive file found inside 'C:\ProgramData\RhinoSoft\Serv-U'
5. Remove the Server Identity information starting from the colon.

image.png

6. Start the Serv-U service.
7. Go to the Server identity page in the Serv-U console, click the Create button, and Export it.
  

Scenario 3: There is no backup of the Server Identity

1. Stop the Serv-U service through Windows Services or run services.msc.
2. Create a backup copy of the Serv-U.Archive file found inside C:\ProgramData\RhinoSoft\Serv-U (Folder is Hidden in Windows by default).
3. Rename the Serv-U.Archive.Backup file inside 'C:\ProgramData\RhinoSoft\Serv-U'
4. Edit the Serv-U.Archive file found inside 'C:\ProgramData\RhinoSoft\Serv-U'
5. Remove the Server Identity information starting from the colon.

image.png

6. Start the Serv-U service.
7. Go to the Server identity page in the Serv-U console, click the Create button, and Export it.