I'm facing a trouble with Windows 8.
I've an application in VB6 using SQL Server 2008 through the net with SQLNCLI10 provider, which I always install with sqlncli10.msi, but when I tried to install in a PC with Windows 8, I can't... said something it's no more supported.
I use ADO for connection, and the string connection is:
Provider=SQLNCLI10;Server=SERVER\SQLEXPRESS;Database=MyDataBase;
Any ideas?
Are you installing on a 64-bit machine? If you are, you may need to create a reference directly to the C:\Windows\SysWow64\sqlncli.dll.
Related
sqldeveloper 4.1.1 new connection "Access" tab missing. I have windows 8.1 64bit. I tried 32bit 64bit office. I tried Windows 64-bit with JDK 8 included, Windows 32-bit/64-bit.
Oracle sqldeveloper starting version 4.1 require java 8 which remove jdbc-odbc bridge necessary for the program to connect Microsoft access database. sqldeveloper 4.0 with java 7 works.
reference:
https://community.oracle.com/thread/3758769
https://community.oracle.com/thread/3726855
From access to link to a server database you use the external data tab, and from that tab choose ODBC database.
So there never was some “new” connection button or tab, but only that of using the ODBC connection manager.
An application developed with VS 2010 and .NET 4, originally and successfully deployed on Vista, after installing on Windows 8.1 has exhibited the following problem (after installing the official MySQL data provider version 5.0.9):
A call to DbProviderFactories.GetFactoryClasses returns all the other providers (ODBC, SQL Server, etc.), but not the MySQL provider.
What could be wrong? Is the version not compatible with 8.1? Does the installer not register it so that DbProviderFactories.GetFactoryClasses can find it? Could there be a 64 vs 32 bit issue?
I need to install SQLCMD utility on a windows 2003 Standard Edition SP 2 server. I tried to install download it from http://www.microsoft.com/en-in/download/details.aspx?id=36433. When I try to install, it asks for ODBC driver 11 for SQL Server. This driver is available at http://www.microsoft.com/en-in/download/details.aspx?id=36434. However this is not supported for Windows 2003 OS. I tried to look for the older version of SQLCMD utility that might use an older driver compatible with Windows 2003 server, but could not find it.
Can you pls. suggest any alternative or give any other suggestion?
Faced the same problem, solution that worked for me on my server 2003:
First installation of sqlncli.msi from https://www.microsoft.com/en-us/download/confirmation.aspx?id=16978 (you have to expand the Install instructions)
Then installation of SqlCmdLnUtils.msi (different from MsSqlCmdLnUtils.msi which failed) from the same page https://www.microsoft.com/en-us/download/confirmation.aspx?id=16978
I was running VSExpress 2010 C# and SQLExpress 2008 on 32b XP. Due to a failure I am now on Win7 64bit. I have reinstalled VSExpress C# (64b). I installed SQLExpress (64b) however my application uses the Microsoft.ACE.OLEDB.12.0 driver to connect to a Office 2007 (32b) database. I could not get the Microsoft.ACE.OLEDB.12.0 to load on SQLExpress (64b).
What do I need to do to get Microsoft.ACE.OLEDB.12.0 working again in SQLExpress? Do I need to run the 32bit version? (I have downloaded it but am having problems getting it to install so I am asking while I uninstall all of my SQLExpress)
Thanks for the help. (I saw a lot of similar issues addressed but could not find a solution for my specific problem)
I think this post has the answer you're looking for -- download 64-bit version of ACE OLE DB driver. However, apparently it requires installing 64-bit version of Office as well.
Otherwise go and install WoW-enabled 32-bit version of SQL Server 2008 Express. Go to this download page and download SQLEXPR_x86_ENU.exe (note: the one without 32 in the file name). It should install on 64-bit system.
I had the same problem and couldn't install the 64 version because I have 32 bit office installed as well (so the 64 bit installed terminated). I changed the build of my program to x86 instead of AnyCPU and the 32 bit ACE worked as given in this Stack Overflow question
If you are trying to use the 32bit version you will probably need to install the 32 bit version of the Microsoft Office Database engine. However if you have 64bit office installed this will show a message saying that 64bit is already installed.
If you install the Microsoft Office Database engine using the "/PASSIVE" command line argument it will install without the prompt, and then you can use the 32 bit ACE.OleDB.12 driver.
Beware in some situations this can cause complications with Office 64bit.
I had to install the Access 2007 Runtime to fix this. Here: https://www.microsoft.com/en-us/download/details.aspx?id=4438
I've got a client that I wrote an asp front end application 2 yrs ago, which connects to a access 2007 database. All the files sat on a windows server 2000 machine 2 yrs ago. They recently upgraded their server to a windows server 2008 machine (64bit). Now the asp can't connect to the Access database via the ODBC connection. I tried using a dsnless connection, as well as, a manually created dsn connection (the manual dsn was created on the server 2008 machine using the 32bit .exe wizard to create dsn connections)...but that didn't work. I get an error that basically says the database odbc couldn't connect.
I've read that this is a problem between a 64bit 2008 server and a 32bit application (access 2007), but I can't seem to find any solutions to fix this problem.
Can anyone point me in the right direction, or offer some help? I'm really clueless how to solve this for them and they really don't have any other people to help.
Thanks for your help.
On a Windows 2008 x64 the following can be done to enable 32 bit applications in IIS:
Open IIS (inetmgr command)
Locate the application pool that your application is using
In the pool's advanced settings, set Enable 32-bit Applications to true
If that doesn't work, try enabling 32 bit compatibility mode by using the following command:
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 True
Hope it helps!