Multiple user accounts on windows with Omnis listening on a hard-coded port

Bastiaan Olij Bastiaan.Olij at
Thu Feb 28 16:43:02 EST 2019

Hey Reg,

Ran into that years ago too using Omnis remote tasks to allow some automation into the library, never found a solution and gave up on the idea.
Much may have changed since then but Rudolfs suggestion is on point in theory. If you can't bind on the port because it is in use, bind on the next one until you find a free one or run out of a range. What got me stuck was that you needed to restart Omnis before it would try to bind on the new port. But that was Studio 4 days so it may work today.

Kindest Regards,

Bastiaan Olij
Head of development - Instinct Systems: The JobBag People
Ground Floor, 48 Chandos Street
St Leonards NSW 2065

Phone +61 2 8115 8000
Mobile +61 4 321 44833
bastiaan.olij at

 From:   Reg Paling <reg.paling at> 
 To:   OmnisDev List - English <omnisdev-en at> 
 Sent:   2/28/2019 7:00 PM 
 Subject:   Multiple user accounts on windows with Omnis listening on a hard-coded port 

Hi all,

One of my clients has just got a new IT support provider, and they have 
set up so that everyone who walks up to a workstation is supposed to log 
on with their own name and password.

I have got the local AppData working the the multiple users, but I have 
a potential problem where if the previous user hasn't quit from my 
application and hasn't logged out, then there will be a "ghost" 
omnis.exe still running (visible in Task Manager). The problem is that 
this Omnis is listening on a particular port and it wont let go of the 
port so when the next user comes along and opens another instance of  
Omnis, it cannot get access to the port.

Has anyone else worked though this issue?


Manage your list subscriptions at
Start a new message -> mailto:omnisdev-en at 

More information about the omnisdev-en mailing list