Running Streamserve 5.6.2 on WIndows Server 2025

Hi, I'm currently looking at migrating out Streamserve 5.6.2 installation from Windows Server 2016 to Server 2025. As part of the switch we've moved the server to a protected part of the network because of the risk of running out of date software. Everything appears to be working fine, but there is one warning/error that I can't get rid of:

In the application log I get this:
"Unable to connect to the Management Gateway for initialize management."

In the platform log I am getting these errors:
99 Service {12aab7a0-499a865c-1a5a3775-324c236e} not registered with service controller http://schemas.streamserve.com/uid/manager/repositorymanager/1.0
0216 134036 (0314) 99 Service controller: Failed to get service: {12aab7a0-499a865c-1a5a3775-324c236e}. (0x80000009: not found)
0216 134036 (0414) 4 Service controller: Remote service support not available.
0216 134036 (0368) 4 Service controller: Failed to invoke service: {12aab7a0-499a865c-1a5a3775-324c236e}.

It is not stopping anything working, the only difference it seems to make is that I can't see the runtime properties in the Control Center. I think that the issue is probably network related. Does anyone have any idea of what ports may need to be opened for this to work - it's a bit confusing as we are running everything on the same Server so it shouldn't be accessing an external server.

Find more posts tagged with

Comments

Vyv

Hi Tim, I believe that you have some old IP’s in the security descriptors in your DB.

First look in your DB for your previous (2016) IP numbers and then update them with your replacement (2025).

You may also need to update the tenant with the ss_tentant.exe tool to get this right - but only perform this if your step above does not work.

Keep us posted and let us know how you get on.

Have you thought about upgrading to the latest release? (25.3).

Tim Midwinter

Thanks Vyv, all the DB's have been created from scratch so there shouldn't be any old IP's, would it just be the nodes table in the Enterprise repository? This appears to be correct.

Is there any particular tables I need to check?

Tim Midwinter

Hi, I managed to find a fix for this, it had been previously raised under https://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0465391 .

The issue was that the user that was running the Streamserve applications wasn't an admin on the server. I added the user to the administrators group and I can now access the runtime properties and there are no more warnings in the log.

Thanks for your help.

Vyv

Great! Thanks for the fix.