home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Can't use TV or repair database
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="doveman" data-source="post: 971548" data-attributes="member: 67412"><p>I created a new Server Instance on localhost port 3307. It couldn't connect on localhost, 127.0.0.1 or 192.168.1.64 but it said it might be because the server wasn't running so I continued through to the end of the creation. It defaulted to use my.ini but that's set to use port 3306 so I copied it to my2.ini and changed the port in it to 3307. I also changed the data folder to data2 so that it didn't use the same one as the first instance.</p><p> </p><p>So then I have two instances in the SQL Development column, the original one on port 3306 and the new one on port 3307. Comodo Firewall doesn't show anything listening on either port but netstat -an shows 3306 open, so probably Comodo just doesn't show local/internal connections. If I try to connect to the second instance on 3307 via "Open connection to start querying" or "Manage Connections" - Test Connection it says Can't Connect. Maybe I need to restart mysql before the second instance will work. However now I can connect to the original instance on 3306 via either method so I don't know why that's suddenly started working. It still just closes the window when I enter MediaPortal as the password in the Start Menu commandline shortcut though, which is weird.</p><p> </p><p>Anyway, now I can connect I'll try doing what jameson_uk suggested.</p></blockquote><p></p>
[QUOTE="doveman, post: 971548, member: 67412"] I created a new Server Instance on localhost port 3307. It couldn't connect on localhost, 127.0.0.1 or 192.168.1.64 but it said it might be because the server wasn't running so I continued through to the end of the creation. It defaulted to use my.ini but that's set to use port 3306 so I copied it to my2.ini and changed the port in it to 3307. I also changed the data folder to data2 so that it didn't use the same one as the first instance. So then I have two instances in the SQL Development column, the original one on port 3306 and the new one on port 3307. Comodo Firewall doesn't show anything listening on either port but netstat -an shows 3306 open, so probably Comodo just doesn't show local/internal connections. If I try to connect to the second instance on 3307 via "Open connection to start querying" or "Manage Connections" - Test Connection it says Can't Connect. Maybe I need to restart mysql before the second instance will work. However now I can connect to the original instance on 3306 via either method so I don't know why that's suddenly started working. It still just closes the window when I enter MediaPortal as the password in the Start Menu commandline shortcut though, which is weird. Anyway, now I can connect I'll try doing what jameson_uk suggested. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Can't use TV or repair database
Contact us
RSS
Top
Bottom