Jump to content


uniform server as service - not using configured mysql port

mysql non default port

  • Please log in to reply
No replies to this topic

#1 grandy



  • Member
  • Pip
  • 1 posts
  • Main OS: Windows 7

Posted 24 June 2016 - 02:34 AM



I've installed Uniform server successfully and can run the Server as a standalone program. For MySQL I've chosen a non-default port (3386), by changing it using the controller. And it works great - Unless I install the Uniform Server as a Service (using UniService.exe). It appears that MySQL now listens on the default port 3306 and not on the one that I've configured before. (For apache I've chosen a non-default port as well (85) but no problems here) Anyone experienced this behaviour? Your help woul be appreciated.


Versions used:





Windows Server 2008 R2 Standard





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users