Normal
Sorry to hear you're still having trouble. This is usually not a problem. The fact that you're trying to use an existing database can be a bit of a complication if you're not familiar with the database configuration. BSODs can be triggered by any program like MediaPortal, but the underlying cause is badly behaved drivers, operating system issues, or system instability. Nothing we can do about this. Yes, this will happen until you enter DB credentials that TV Server can use. I thought phpmyadmin has its own users and passwords, but it has been quite some time since I've used it.So lets get a few things really clear. This instance of MySQL is running on the local machine, correct?In that case, use the IP address of the machine. Dependency is the name of the database service. By default that is MySQL5 for MySQL 5... however if you installed as part of LAMP or XAMP or something then you should check the service name in the Windows service management console. As above, the schema name doesn't matter. The user and password are obviously really important. When the DB is installed by MP, the MP installer configures the settings as necessary and assigns the root user a default password, however since you're trying to use an existing database I have no idea what kind of state your DB is in.The key requirements are:You know the username and password for a user that has permission to create new schemas.That user has permission to connect/log in via TCP/IP (ie. named pipes is not sufficient) from the machines you're going to use with MediaPortal. MP won't accept localhost because localhost is ambiguous or incorrect in some valid MP configurations. Consider the situation where you have the database and TV Server on one machine (ie. server-only or standalone install) and are trying to use TV via MediaPortal installed on another PC or laptop (ie. a client-only install). MediaPortal on the client receives the DB connection details from the server. If you've configured the DB connection with "localhost" then that works fine on the server because the database is running on the same machine (ie. definition of localhost is "on this machine"). However, it won't work for the client because when the client attempts to connect to the DB with "localhost" it will be looking for the DB on that local client PC... which is of course wrong. Hence we block configuration using localhost. Does that make sense? I agree. If you want my help to sort this I'd be happy to do that. Just set up remote access using TeamViewer and flick me a PM with the details.http://www.teamviewer.com/en/download/windows.aspx TeamViewer is really easy to use. No installation or configuration required. Just download and run it. Usually this stuff is managed using MySQL Workbench (or historically MySQL GUI Tools). As I say, I'm happy to assist with sorting stuff out but it is too time consuming for both of us to explain in forum posts. Better if you can just set up remote access and I'll walk through it with you.
Sorry to hear you're still having trouble. This is usually not a problem. The fact that you're trying to use an existing database can be a bit of a complication if you're not familiar with the database configuration.
BSODs can be triggered by any program like MediaPortal, but the underlying cause is badly behaved drivers, operating system issues, or system instability. Nothing we can do about this.
Yes, this will happen until you enter DB credentials that TV Server can use.
I thought phpmyadmin has its own users and passwords, but it has been quite some time since I've used it.
So lets get a few things really clear.
This instance of MySQL is running on the local machine, correct?
In that case, use the IP address of the machine.
Dependency is the name of the database service. By default that is MySQL5 for MySQL 5... however if you installed as part of LAMP or XAMP or something then you should check the service name in the Windows service management console.
As above, the schema name doesn't matter.
The user and password are obviously really important. When the DB is installed by MP, the MP installer configures the settings as necessary and assigns the root user a default password, however since you're trying to use an existing database I have no idea what kind of state your DB is in.
The key requirements are:
MP won't accept localhost because localhost is ambiguous or incorrect in some valid MP configurations. Consider the situation where you have the database and TV Server on one machine (ie. server-only or standalone install) and are trying to use TV via MediaPortal installed on another PC or laptop (ie. a client-only install). MediaPortal on the client receives the DB connection details from the server. If you've configured the DB connection with "localhost" then that works fine on the server because the database is running on the same machine (ie. definition of localhost is "on this machine"). However, it won't work for the client because when the client attempts to connect to the DB with "localhost" it will be looking for the DB on that local client PC... which is of course wrong. Hence we block configuration using localhost.
Does that make sense?
I agree. If you want my help to sort this I'd be happy to do that. Just set up remote access using TeamViewer and flick me a PM with the details.
http://www.teamviewer.com/en/download/windows.aspx
TeamViewer is really easy to use. No installation or configuration required. Just download and run it.
Usually this stuff is managed using MySQL Workbench (or historically MySQL GUI Tools). As I say, I'm happy to assist with sorting stuff out but it is too time consuming for both of us to explain in forum posts. Better if you can just set up remote access and I'll walk through it with you.
