Unable to start managers on tcp port 4999

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
Search

Post Reply
4 posts • Page 1 of 1
daniel.ponader
Posts: 34
Joined: Tue Jan 10, 2012 1:40 pm

Unable to start managers on tcp port 4999

Post by daniel.ponader »

Dear all,

I like to use WINCC OA on a Windows PC with installed HiPath telephone system dialer Simplyphone this uses the same TCP Port 4999 as PVSS00pmon.exe. Is there a possibility to change the used TCP Port of WinCC OA? Simplyphone doesn't allow this.

Thanks an greetings

Daniel

User avatar
mweber
Posts: 42
Joined: Mon Aug 02, 2010 11:23 am

Re: Unable to start managers on tcp port 4999

Post by mweber »

Hi,

of course you could change the ports WinCC OA uses for communication.
(the port 4999 is the default port for the pmon - our process monitor)
simply add those line to your config file (into the [general] section):

pmonPort = 6000

you could as well change the ports of other managers that act as a communication master:
eventPort =
dataPort =
distPort =
reduPort =

Be sure that you always delimit the last line in the config file with an !

btw: the Pmon port can also be changed at the project administration panel when opening the project properties.


have fun

Markus
P.S.: we will meet each other in KW6 for the basic training...

User avatar
aorange
Posts: 147
Joined: Thu Nov 04, 2010 10:07 am

Re: Unable to start managers on tcp port 4999

Post by aorange »

Of course this is also useful to know to run multiple WinCC-OA projects on the same platform..

User avatar
leoknipp
Posts: 2926
Joined: Tue Aug 24, 2010 7:28 pm

Re: Unable to start managers on tcp port 4999

Post by leoknipp »

Hello,

please notice that running several projects at the same time on one machine is only allowed for the project-engineering.
In real runtime systems you have to start only one project at one machine.

Best Regards
Leopold Knipp
Senior Support Specialist

Post Reply
4 posts • Page 1 of 1