Error "System.Data.OracleClient requires Oracle client software version 8.1.7 or greater" While uploading on IIS - oracle9i

I'm Using ASP.Net With oracle 9i database,when i trying to upload project on iis server,it gives me error like "System.Data.OracleClient requires Oracle client software version 8.1.7 or greater" is there any need of installing client software or any other solution on that?
Thanks in Advance..

Yes, ADO.NET (i.e. System.Data.OracleClient) requires an Oracle client to be installed, otherwise it does not work.

Related

Error while installing SQL Server 2017 Express showing sqlncli.msi is missing in some path

I am trying to install SQL Server 2017 Express, but it is throwing this error:
sqlncli.msi is not found in the path
Screenshot illustrating the sqlncli.msi error:
I had the same issue, if you click cancel the next error should say something about a package from SQL Server 2012 Native Client is missing.
I then tried to install the sqlncli from https://www.microsoft.com/en-us/download/details.aspx?id=50402 and it said I already have a new version. I had to unistall "Microsoft SQL Server 2012 Native Client" on add or remove programs, and install the sqlncli again from the website I mention and it all worked out.
I had the same problem.
My solution, I uninstalled SQL Server 2012 Native Client and reinstall the SQL Server 2017.
The first two answers are more helpful and straight forward. Another way of installing sqlncli.msi is installing Microsoft SQL Server 2012 SP4 Feature Pack. It contains many packages including sqlncli.msi, which adds an additional value to your SQL server.
If you download only the native client as per #fpp.jesus's answer and if you want to install it using the command-line for some reason, the following command will be helpful.
msiexec /i sqlncli.msi ADDLOCAL=ALL APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
'ADDLOCAL=All' argument will install SDK components along with the client components.

DBX error in Delphi XE3, when connecting to a SQL Server database

When I try to connect to a MS SQL Server database using DBX an error pops up saying that the driver is not properly installed, or missing. I tried with ADO driver and it worked like charm, but the thing is that I need DBX driver to work because I want to modify an app that has been developed with DBX technology.
I reinstalled Delphi XE3, and also asked a friend of mine to test it and the error is the same. Does somebody has any ideea on how to solve it ?
The exactly message was this:
Borland.Data.TDBXError: DBX Error: Driver could not be properly
initialized. Client library may be missing, not installed properly,
of the wrong version, or the driver may be missing from the system
path.
I must mention that I tried it on a local instance of MSSQL Server 2012 and on a remote MSSQL Server 2008 instance. My OS win8 x64;
Best regards,
This is most likely caused by the wrong version of the SQL Native Client installed on your system. DBX will only work with V10, while you probably have V11 installed. Try to install the V10 version of the client.

Biztalk wcf-sql not able to configure

I am running into a weird problem with the installation / configuration of the BizTalk 2010 Adapter Pack. I am running BizTalk 2010 cluster on Windows Server 2008 R2, wanted to get WCF-SQL to work so I installed the 64 bit of LOB, 64-bit BizTalk Adapter Pack, 32-bit BizTalk Adapter Pack.
I was able to see the WCF-SQL adapter in the list of adapters, and created a new handler for it. Everything seemed to be working fine. However when I created a receive location that uses the WCF-SQL type, and click on Configure, I got this error:
Exception has been thrown by the target of an invocation. (mscorblib)
Additional information: Binding not found: sqlBinding
(Microsoft.Adapters.Common.Biztalk).
I double checked the machine.config for both framework and framework64, .net framework 2.0 and 4.0, they all have "sqlbindings" entries.
By the way, I had it working on one of my development box, but when I tried to set up my server and that's when I run into this problem.
Any help is appreciated!
Install in the following order:
64-bit WCF LOB Adapter SDK SP2
64-bit BizTalk Adapter Pack
32-bit BizTalk Adapter Pack
It turns out that I have been doing things not correctly. Instead of manually installing those components, go to BizTalk setup, one of the menu item is to install the adapter pack. Just follow the instruction there, and everything worked out for me.
I think the reason of this weird behaviour is maybe you have installed the wrong version of BizTalk Adapter Pack.
For BizTalk 2010, you have to install the 2010 version of the Adapter Pack, which can be found on BizTalk 2010 DVD/image.
You also have to pay attention to WCF LOB Adapter SDK version: you need the 2010 version which can be also found on the DVD/image.
The former versions of WCF LOB Adapter SDK and BizTalk Adapter Pack can be installed (nothing will stop you on that), but only works with BizTalk 2009.
Not being facetious, but have you restarted your Host Instance?
Adding a handler requires a Host Instance restart.

How to run a win32 native application that requires sql server native client on MacOSX with winebottler?

I am experimenting with WineBottler and I would like to try to run my win32 native application written in Delphi on OSX.
The application runs, but I stop at login screen since I cannot connect to SQL Server.
Does anyonw know how to install and configure SQL Server native client on OSX so that it is usable with WineBottler?
Note: I put "wine" as tag since "winebottler" is not available.
I have a Delphi application that uses MDAC 2.8 for ADO connection to the Jet provider. I use Winetricks to install MDAC 2.8, and it works great. If you can't get SQL Server Native Client to install, perhaps your application can use the OLEDB SQL Server provider by tweaking your connection strings. Are you using any features that are only in SQL Server Native Client?
You would have a lot less trouble if you put in some middleware like kbmMW, Remote Objects, or DataSnap. All of them can use plain TCP/IP (via http or like higher level protocol), and don't require client side libs. You will need an extra server, but it is easy to create one that just forwards your SQL and data between clients and SQL server. Note that SQL server licensing remains.
On the other hand, you can try to install SQL Server native client, some older version of it - eg. for SQL Server 2005, in that "bottle" with your application. Yet, I'm not sure if that is legal thing to do. I think that MS prohibits native client installation on OS other than Windows.
There is FreeTDS native client that works with MSSQL from unices, but it is not ported to be usable from Delphi (like dbx driver).

Can you install Silverlight 3 Tools on Server 2008 (64bit)

I have been able to install 'VS2008 SP1' and 'VS2008 Tools for Silverlight' on my Windows Server 2008 development machine, but I have not been able to install the MSI for 'Silverlight Toolkit July 2009'. The install fails with the following:
"The system administrator has set policies to prevent this installation"
I am a local admin on the box. I have seen something similar when try to to 32-bit MSI on a 64-bit machine. Is that the problem that I am having?
I don't think that you need to install the SL toolkit on the server. At least, we haven't had to. We're using 64-bit Windows Server 2003, and any required Silverlight DLLs, etc., just get included in our .xap file, and get downloaded by the client when it downloads that file. All the server knows is that it's got to pass the .xap file down to a client when it requests it. The only thing that any server-side process might need to know about is the System.ServiceModel.PollingDuplex.dll (if you're using duplex WCF services), but if you simply install the SL 3.0 SDK on your dev machine, and then reference that DLL from your WCF project, it'll get included with your WCF project when you roll it out to the server in question.
The only reason you'd need to install those things on the server is if you're planning to do development on the server, which I suppose you might want to, but certainly isn't normal :-).

Resources