Default superserver port on installation

Question

Question

Trevor Strong · Jan 25, 2018

Does anyone know where the default port comes from when installing a new instance on Windows Server 2012 R2?

It constantly picks up the wrong default which is already running on the server (probably swapped over after installation) and the install fails and rolls back.

I installed again and this time without rollback but still allocated the wrong port so at least was able to manually update the cpf and then start the instance.

Would like a simpler solution to the issue and assume they are traversing some windows registry entry that may need updating.

Discussion (3)1

Log in or sign up to continue

John Murray · Jan 26, 2018

There's some documentation here.

In your case it sounds like a Cache instance was moved onto the server but not added to the registry that Cache's ccontrol command uses. On Windows I think Cache uses the Windows Registry. On other platforms it uses a file, and offers commands ccontrol create, ccontrol update and ccontrol delete to maintain entries in this registry.

1 0

John Murray · Jan 29, 2018

The superserver port is recorded in the cache.cpf file, and I think it can be changed there by simply editing the file and then restarting Cache.

I'm guessing that the Cache installer uses the registry to discover the locations of the CPF files it needs to check when picking a "free" port to offer as the superserver port for a new instance. So if one of your instances wasn't properly registered at the time you installed another instance then the installer may have defaulted to a port that was actually already taken.

1 0

score 0 · Answer 1 · 2018-01-26T18:35:26-05:00

Sure. So the entries in the registry are maintained correctly if you use the management portal to edit.

My situation was a copied cpf on the server that had created the problem and subsequently the issue occurred. I manually started the two instances one at a time and updated the ports using SMP and everything is in sync.