4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

This situation is by design. Internally, Microsoft uses @@servername (i.e., vsql\instance) for
verification, while Enterprise Manager uses the registered server name (i.e., vsql,port#). Because
the values do not match, the attempt to create the distributor fails.
To work around this limitation, it is necessary to connect to HP PolyServe Software for Microsoft SQL
Server via <servername>\<instancename>. This type of connection is not guaranteed from the
remote Enterprise Manager because of name resolution and the custom TCP port used for HP PolyServe
Software for Microsoft SQL Server. Instead, we recommend that you launch Enterprise Manager either
locally on the active node or within the local subnet. You can then create the distributor.
When you create the distributor, a Replicator Monitor should also be created for you.
Configuring publication database(s) and selecting qualified subscriber(s) is similar to configuring a
stand-alone server, as shown below.
HP PolyServe Software for Microsoft SQL Server administration guide 123