Thanks, Todd. You may be referring to me naming the connection "Excel 2007 Connection Manager", which may be a misnomer since I'm using the 2010 drivers.
I took a look at your link and it looks like everyone's having the same issue.
This is my connection string:
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=<filepath>;Extended Properties="Excel 12.0;HDR=YES";
Any manual editing of the string from Excel 12.0 to Excel 14.0 results in Extended Properties=Excel 8.0"Excel 14.0;HDR=YES"; There are ways around this using externalized configurations, expressions, and the like, but at run-time it gives me the same error. I also thought that the Provider portion of the string could use a change to Microsoft.ACE.OLEDB.14.0; but no luck. Basically, SQL doesn't recognize the driver as being installed.
As a side note, this machine doesn't have an Office suite installed, so the existing Excel connections are (ACE 12, Jet 8) are simply what come with SQL Server.
________________________________________Get some SQLey goodness at Dirt McStain's SQL Blog