For example, if you have a beta version of the PowerPivot download installed and upgrade to the released version of Excel 2010, the PowerPivot addin will not be available in Excel. The solution is to upgrade the beta components to their released versions when they become available. Apr 27, 2013 - 2-Download and install latest ODBC connector. Microsoft SQL Server Migration Assistant (SSMA) for MySQL tool. The download file size may also vary depending on the edition and additional switches you might use. Milestone versions include specific sets of functions and are released as soon as.
Hi Jason, I never did get it working in the definition editor, so I had to create the XML file from scratch. As I mentioned in my previous post, I do not have connection errors anymore but I am having problems with passing parameters to the SELECT statement for MySQL, so I don't actually know for sure whether it works yet.
The code I have attached below uses an MS SQL statement with the @ symbol used for the parameter, so if anyone can help me to translate this into a MySQL statement, it will be much appreciated. BTW, I have commented out a few lines whilst I have been testing, so only a Finder instance exists at the moment - the code can still be uploaded without a Specific Finder instance, but I am just concentrating on a simple example first before I start fleshing out the code Thanks, Phil.
There were actually three changes that I needed to do manually to get the BDC connection working with mySql driver. I used the BDC Definition Editor to create the initial xml file. Then I opened the xml file and made the following changes; 1) change rdbconnectiontrustedconnection to uppercase rdbconnectionTrustedConnection 2) remove double quotes from all select statements (ie Select 'id' from table should read Select id from table) 3) changed where clause to a? (WHERE id = @id should read WHERE id =?
B.6.2.2 Can't connect to local MySQL server A MySQL client on Unix can connect to the server in two different ways: By using a Unix socket file to connect through a file in the file system (default /tmp/mysql.sock), or by using TCP/IP, which connects through a port number. A Unix socket file connection is faster than TCP/IP, but can be used only when connecting to a server on the same computer. A Unix socket file is used if you do not specify a host name or if you specify the special host name localhost. If the MySQL server is running on Windows, you can connect using TCP/IP. If the server is started with the option, you can also connect with named pipes if you run the client on the host where the server is running. The name of the named pipe is MySQL by default. If you do not give a host name when connecting to, a MySQL client first tries to connect to the named pipe.
If that does not work, it connects to the TCP/IP port. You can force the use of named pipes on Windows by using. As the host name. The error (2002) Can't connect to.
Normally means that there is no MySQL server running on the system or that you are using an incorrect Unix socket file name or TCP/IP port number when trying to connect to the server. You should also check that the TCP/IP port you are using has not been blocked by a firewall or port blocking service. The error (2003) Can't connect to MySQL server on ' server' (10061) indicates that the network connection has been refused. You should check that there is a MySQL server running, that it has network connections enabled, and that the network port you specified is the one configured on the server. Start by checking whether there is a process named running on your server host. (Use ps xa grep mysqld on Unix or the Task Manager on Windows.) If there is no such process, you should start the server. If a process is running, you can check it by trying the following commands.
The port number or Unix socket file name might be different in your setup. Hostip represents the IP address of the machine where the server is running. Shell mysqladmin version shell mysqladmin variables shell mysqladmin -h `hostname` version variables shell mysqladmin -h `hostname` -port=3306 version shell mysqladmin -h hostip version shell mysqladmin -protocol=SOCKET -socket=/tmp/mysql.sock version Note the use of backticks rather than forward quotation marks with the hostname command; these cause the output of hostname (that is, the current host name) to be substituted into the command. If you have no hostname command or are running on Windows, you can manually type the host name of your machine (without backticks) following the -h option.
You can also try -h 127.0.0.1 to connect with TCP/IP to the local host. Make sure that the server has not been configured to ignore network connections or (if you are attempting to connect remotely) that it has not been configured to listen only locally on its network interfaces.
If the server was started with, it will not accept TCP/IP connections at all. If the server was started with, it will listen for TCP/IP connections only locally on the loopback interface and will not accept remote connections.
Check to make sure that there is no firewall blocking access to MySQL. Your firewall may be configured on the basis of the application being executed, or the port number used by MySQL for communication (3306 by default). Under Linux or Unix, check your IP tables (or similar) configuration to ensure that the port has not been blocked. Under Windows, applications such as ZoneAlarm or Windows Firewall may need to be configured not to block the MySQL port. Here are some reasons the Can't connect to local MySQL server error might occur. is not running on the local host.
Check your operating system's process list to ensure the process is present. You're running a MySQL server on Windows with many TCP/IP connections to it. If you're experiencing that quite often your clients get that error, you can find a workaround here:. Someone has removed the Unix socket file that uses ( /tmp/mysql.sock by default). For example, you might have a cron job that removes old files from the /tmp directory. You can always run to check whether the Unix socket file that is trying to use really exists.
The fix in this case is to change the cron job to not remove mysql.sock or to place the socket file somewhere else. You have started the server with the option, but forgotten to tell client programs the new name of the socket file. If you change the socket path name for the server, you must also notify the MySQL clients. You can do this by providing the same option when you run client programs. You also need to ensure that clients have permission to access the mysql.sock file. To find out where the socket file is, you can do: shell netstat -ln grep mysql See. You are using Linux and one server thread has died (dumped core).
In this case, you must kill the other threads (for example, with ) before you can restart the MySQL server. The server or client program might not have the proper access privileges for the directory that holds the Unix socket file or the socket file itself. In this case, you must either change the access privileges for the directory or socket file so that the server and clients can access them, or restart with a option that specifies a socket file name in a directory where the server can create it and where client programs can access it. If you get the error message Can't connect to MySQL server on somehost, you can try the following things to find out what the problem is. Check whether the server is running on that host by executing telnet somehost 3306 and pressing the Enter key a couple of times. (3306 is the default MySQL port number.
Change the value if your server is listening to a different port.) If there is a MySQL server running and listening to the port, you should get a response that includes the server's version number. If you get an error such as telnet: Unable to connect to remote host: Connection refused, then there is no server running on the given port. If the server is running on the local host, try using to connect using the Unix socket file.
Verify the TCP/IP port number that the server is configured to listen to (it is the value of the variable.). If you are running under Linux and Security-Enhanced Linux (SELinux) is enabled, make sure you have disabled SELinux protection for the mysqld process. B.6.2.2.1 Connection to MySQL Server Failing on Windows When you're running a MySQL server on Windows with many TCP/IP connections to it, and you're experiencing that quite often your clients get a Can't connect to MySQL server error, the reason might be that Windows does not allow for enough ephemeral (short-lived) ports to serve those connections. The purpose of TIMEWAIT is to keep a connection accepting packets even after the connection has been closed. This is because Internet routing can cause a packet to take a slow route to its destination and it may arrive after both sides have agreed to close. If the port is in use for a new connection, that packet from the old connection could break the protocol or compromise personal information from the original connection.
The TIMEWAIT delay prevents this by ensuring that the port cannot be reused until after some time has been permitted for those delayed packets to arrive. It is safe to reduce TIMEWAIT greatly on LAN connections because there is little chance of packets arriving at very long delays, as they could through the Internet with its comparatively large distances and latencies. Windows permits ephemeral (short-lived) TCP ports to the user. After any port is closed it will remain in a TIMEWAIT status for 120 seconds.
The port will not be available again until this time expires. The default range of port numbers depends on the version of Windows, with a more limited number of ports in older versions. Start Registry Editor ( Regedt32.exe). Locate the following key in the registry: HKEYLOCALMACHINE SYSTEM CurrentControlSet Services Tcpip Parameters. On the Edit menu, click Add Value, and then add the following registry value: Value Name: MaxUserPort Data Type: REGDWORD Value: 65534 This sets the number of ephemeral ports available to any user. The valid range is between 5000 and 65534 (decimal). The default value is 0x1388 (5000 decimal).
On the Edit menu, click Add Value, and then add the following registry value: Value Name: TcpTimedWaitDelay Data Type: REGDWORD Value: 30 This sets the number of seconds to hold a TCP port connection in TIMEWAIT state before closing. The valid range is between 30 and 300 decimal, although you may wish to check with Microsoft for the latest permitted values. The default value is 0x78 (120 decimal). Quit Registry Editor.
Reboot the machine. Note: Undoing the above should be as simple as deleting the registry entries you've created.