Problem:

Error when starting a Fileshare Server: "FS077-S A Fileshare Server of the same name has already been defined"

Resolution:

The end-user was trying to start more than one Fileshare Server having the same name, though on different machines.  They were running ccitcp2 processes on each machine, and were not setting the CCITCP2 environment variable on any machine.  This conflicts with the design intention of Fileshare and CCITCP2.  The ccitcp2 process is a registration process, similar to a nameserver, and the intention is that just one machine in the network will run the registration process and act as the nameserver, while on all other machines, the environment variable CCITCP2 will be set to the name of the machine where the ccitcp2 process is running, so all machines will use one registration process.

When the CCITCP2 environment variable is not set, the assumption is that the ccitcp2 process running on the local machine is the intended registration process for the whole network.  By starting a ccitcp2 process on multiple machines, the end-user was establishing multiple and potentially conflicting registration processes on the network.

Under prior versions of Server Express, when the ccitcp2 process was named exactly "ccitcp2", this approach worked, and they could have multiple Fileshare servers of the same name on the network, but in recent versions of Server Express, the mfds32 process takes the role of the ccitcp2 process, and mfds is smart enough to look across the network and see occasions when a user tries to start a fileshare server having the same name as a fileshare server already started.

The solution in modern versions of Server Express, when using mfds as the ccitcp2 process, is to use unique names for all Fileshare Servers.