Cannot create an instance of OLE DB provider "VFPOLEDB"

I created a view refer to a visual foxpro with ole db for visual foxpro which was working fine before. But now, I received an error while select the view

Msg 7302, Level 16, State 1, Line 1
Cannot create an instance of OLE DB provider "VFPOLEDB" for linked server "ORST3".

Please advise. Thanks in advance

Hi Stephanie,

You posted this question to microsoft.public.data.oledb on April 3. Later in the thread you said you were successful getting it working, partly due to enabling "Allow inprocess" in the OLE DB setup.

Is this a new problem since you posted on April 3?

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server

System:Win 2003, SQL Server 2005, Using an AD win account that is not a member of the Admin group on the server.

Error message from Management Studio query window:

Msg 7302, Level 16, State 1, Line 1

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server "Sname".

Event messages associated with this error:

App Event ID: 19036

The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.

Sys Event ID: 10016

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2206CDB0-19C1-11D1-89E0-00C04FD7A829}

to the user domain\user SID (S-1-5-21-126051702-1034962659-2130403006-7826). This security permission can be modified using the Component Services administrative tool.

I’m getting this error message when trying to run an openquery statement through a linked server to DB2. (SELECT * FROM OPENQUERY(Sname, 'SELECT * FROM tablename’))

The linked server has a remote login and password that it uses to connect to DB2.

I found this from another post on how to fix this error:

Expand Component Services - Computers - My Computer - DCOM Config Select MSDAINITIALIZE Right Click properties then security

Under Security - Launch Permission: enable Local Launch and Local Activation for your SQL Service account

Under Security - Access permissions: Allow System: Local Access and Remote Access.

After completing these steps I still get the error message but the events are no longer generated.I’ve also tried different variations of these steps.The only way I can get this to work is to either make the AD user a member of the Admin group on the server or by putting in a user account that has admin rights to the server in the MSDAINITIALIZE properties – Identity Tab – Run this App as this User.

Can someone please tell me the steps that I’m missing?

Additional info:

If I set the providers allowinprocess to 1 with this,

EXEC master.dbo.sp_MSset_oledb_prop N'IBMDADB2', N'AllowInProcess', 1

It responds with this error:

OLE DB provider "IBMDADB2" for linked server "LName" returned message " SQL10007N Message "0" could not be retrieved. Reason code: "2".

".

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "IBMDADB2" for linked server "LName".

Cannot create an instance of OLE DB Provider "MSDAC"

Hey Guys,
I'm trying to query a couple of Excel 2007 spreadsheets for some reports
using OpenDataSource in my query to pull in the data.
Everything is find with the preview inside the IDE, but when I deploy my
report I recieve the following error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set 'Regression'.
(rsErrorExecutingCommand)
Cannot create an instance of OLE DB provider "MSDASC" for linked
server "(null)".
I've installed 2007 Data Connectivity Components on the report server and
this allowed me to query the data while developing. I'm at a loss why this is
not working after I deploy.
The SQL I'm using to query the data is:
SELECT *
FROM OPENDATASOURCE('Microsoft.ACE.OLEDB.12.0',
'Data Source="\\server\document.xlsm";Extended Properties="Excel 12.0
Macro;HDR=YES"')...Sheet1$
Any ideas/suggestions?My guess if this works in development and not in deployment that it has to
do with file security. The report is executed under a different user account
and that account doesn't have rights to the folder where the Excel data
resides. Just a guess because I have never done this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"shaggydog" <shaggydog@.discussions.microsoft.com> wrote in message
news:55853C99-FB58-422B-8FB7-EECD3EF37715@.microsoft.com...
> Hey Guys,
> I'm trying to query a couple of Excel 2007 spreadsheets for some reports
> using OpenDataSource in my query to pull in the data.
> Everything is find with the preview inside the IDE, but when I deploy my
> report I recieve the following error:
> An error has occurred during report processing. (rsProcessingAborted)
> Query execution failed for data set 'Regression'.
> (rsErrorExecutingCommand)
> Cannot create an instance of OLE DB provider "MSDASC" for linked
> server "(null)".
> I've installed 2007 Data Connectivity Components on the report server and
> this allowed me to query the data while developing. I'm at a loss why this
> is
> not working after I deploy.
> The SQL I'm using to query the data is:
> SELECT *
> FROM OPENDATASOURCE('Microsoft.ACE.OLEDB.12.0',
> 'Data Source="\\server\document.xlsm";Extended Properties="Excel 12.0
> Macro;HDR=YES"')...Sheet1$
>
> Any ideas/suggestions?
>|||Thanks for your response, while not directly related to file security, it was
a security problem. Here's what I did to solve my problem in case anyone
comes across this thread in the future...
I was using a shared data source which connected using windows
authentication. No matter how I tweaked and fiddled around I could not get
windows authentication to work.
So I setup a SQL account with limited rights. Then provided me with a new
error message stating:
Ad hoc access to OLE DB provider 'Microsoft.ACE.OLEDB.12.0' has been denied.
You must access this provider through a linked server.
While I have Ad hoc access enabled via Surface Configuration, it would not
allow me to perform an ad hoc query if the user account wasn't a sysadmin to
the SQL Server. Ugh!
I played around with tweaking the DisallowAdhocAccess registry setting for
the provider, but I didn't find a way to allow non-sysadmin accounts the
ability to perform ad hoc queries.
In the end using a SQL authentication with a sysadmin account allowed
OpenDataSource to pull in the external data.
For what it's worth....
"Bruce L-C [MVP]" wrote:
> My guess if this works in development and not in deployment that it has to
> do with file security. The report is executed under a different user account
> and that account doesn't have rights to the folder where the Excel data
> resides. Just a guess because I have never done this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "shaggydog" <shaggydog@.discussions.microsoft.com> wrote in message
> news:55853C99-FB58-422B-8FB7-EECD3EF37715@.microsoft.com...
> > Hey Guys,
> >
> > I'm trying to query a couple of Excel 2007 spreadsheets for some reports
> > using OpenDataSource in my query to pull in the data.
> >
> > Everything is find with the preview inside the IDE, but when I deploy my
> > report I recieve the following error:
> >
> > An error has occurred during report processing. (rsProcessingAborted)
> > Query execution failed for data set 'Regression'.
> > (rsErrorExecutingCommand)
> > Cannot create an instance of OLE DB provider "MSDASC" for linked
> > server "(null)".
> >
> > I've installed 2007 Data Connectivity Components on the report server and
> > this allowed me to query the data while developing. I'm at a loss why this
> > is
> > not working after I deploy.
> >
> > The SQL I'm using to query the data is:
> > SELECT *
> > FROM OPENDATASOURCE('Microsoft.ACE.OLEDB.12.0',
> > 'Data Source="\\server\document.xlsm";Extended Properties="Excel 12.0
> > Macro;HDR=YES"')...Sheet1$
> >
> >
> > Any ideas/suggestions?
> >
>
>

Cannot connection to Oracle DB

I create my datasource using the OLE DB data provider for oracle an when i
test the connection it is successful. When I create the dataset it cannot
connect to the database and says "System.Data.Oracle Client requires Oracle
Client Software version 8.1.7 or greater". I am using PL/SQL Developer that
says it is 9i compatible. Im so lost here and need help. Thanks.We had the Oracle client set up quite a while ago so forgot the steps to set
it up. We did run into some issues. If my memory serves me right, the default
9i installation allows the oci.dll to admin group only, and the web app
(ASPNET by default) or reporting service account (the one you chose during
setup) may not have the necessary permission to see this file. It is one
possible reason.
"Steve" wrote:
> I create my datasource using the OLE DB data provider for oracle an when i
> test the connection it is successful. When I create the dataset it cannot
> connect to the database and says "System.Data.Oracle Client requires Oracle
> Client Software version 8.1.7 or greater". I am using PL/SQL Developer that
> says it is 9i compatible. Im so lost here and need help. Thanks.
>|||Specifically, you may want to check this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;870668
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Terence Leung" <TerenceLeung@.discussions.microsoft.com> wrote in message
news:9349134D-7982-4C1E-995B-3A761058945E@.microsoft.com...
> We had the Oracle client set up quite a while ago so forgot the steps to
> set
> it up. We did run into some issues. If my memory serves me right, the
> default
> 9i installation allows the oci.dll to admin group only, and the web app
> (ASPNET by default) or reporting service account (the one you chose during
> setup) may not have the necessary permission to see this file. It is one
> possible reason.
> "Steve" wrote:
>> I create my datasource using the OLE DB data provider for oracle an when
>> i
>> test the connection it is successful. When I create the dataset it
>> cannot
>> connect to the database and says "System.Data.Oracle Client requires
>> Oracle
>> Client Software version 8.1.7 or greater". I am using PL/SQL Developer
>> that
>> says it is 9i compatible. Im so lost here and need help. Thanks.|||Niether of those ideas worked. I do not have and oci.dll file on my system
and I am developing on an XP system not a 2003 server system.
"Robert Bruckner [MSFT]" wrote:
> Specifically, you may want to check this KB article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;870668
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Terence Leung" <TerenceLeung@.discussions.microsoft.com> wrote in message
> news:9349134D-7982-4C1E-995B-3A761058945E@.microsoft.com...
> > We had the Oracle client set up quite a while ago so forgot the steps to
> > set
> > it up. We did run into some issues. If my memory serves me right, the
> > default
> > 9i installation allows the oci.dll to admin group only, and the web app
> > (ASPNET by default) or reporting service account (the one you chose during
> > setup) may not have the necessary permission to see this file. It is one
> > possible reason.
> >
> > "Steve" wrote:
> >
> >> I create my datasource using the OLE DB data provider for oracle an when
> >> i
> >> test the connection it is successful. When I create the dataset it
> >> cannot
> >> connect to the database and says "System.Data.Oracle Client requires
> >> Oracle
> >> Client Software version 8.1.7 or greater". I am using PL/SQL Developer
> >> that
> >> says it is 9i compatible. Im so lost here and need help. Thanks.
> >>
>
>|||If there is no oci.dll on your machine, then the Oracle client software is
not installed. It won't work without it. You can download the Oracle client
software from Oracle Technology Network (www.oracle.com/otn).
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"steve" <steve@.discussions.microsoft.com> wrote in message
news:9BDF4BD5-DF7E-4134-8873-94FBFB5E35AD@.microsoft.com...
> Niether of those ideas worked. I do not have and oci.dll file on my
> system
> and I am developing on an XP system not a 2003 server system.
>
> "Robert Bruckner [MSFT]" wrote:
>> Specifically, you may want to check this KB article:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;870668
>>
>> -- Robert
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Terence Leung" <TerenceLeung@.discussions.microsoft.com> wrote in message
>> news:9349134D-7982-4C1E-995B-3A761058945E@.microsoft.com...
>> > We had the Oracle client set up quite a while ago so forgot the steps
>> > to
>> > set
>> > it up. We did run into some issues. If my memory serves me right, the
>> > default
>> > 9i installation allows the oci.dll to admin group only, and the web app
>> > (ASPNET by default) or reporting service account (the one you chose
>> > during
>> > setup) may not have the necessary permission to see this file. It is
>> > one
>> > possible reason.
>> >
>> > "Steve" wrote:
>> >
>> >> I create my datasource using the OLE DB data provider for oracle an
>> >> when
>> >> i
>> >> test the connection it is successful. When I create the dataset it
>> >> cannot
>> >> connect to the database and says "System.Data.Oracle Client requires
>> >> Oracle
>> >> Client Software version 8.1.7 or greater". I am using PL/SQL
>> >> Developer
>> >> that
>> >> says it is 9i compatible. Im so lost here and need help. Thanks.
>> >>
>>

Cannot connect SQL 2005 with OLE DB Provider for SQL Server

Cannot connect SQL 2005 with OLE DB Provider for SQL Server

MSSQL 2000 Utilities & MSDE was uninstalled.
After installation SQL 2005 Standard Full all connections was OK (tested).
Aftert restarting the computer I cannot connect to MSSQL with OLE DB Provider for SQL Server.
I try to connect from Delphi 5 SP2 (ADOConnection) and from MS Access 2003 SP2.

Error "SQL Server denied or does not exists or access denied"

Versions:
Windows Xp Pro SP 2
ADO/MDAC: 2.81.1117.0 (xpsp_sp2_rtm.040803-2158)
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Connection sting:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=pwd;Data Source=GMSAlexHome;Initial Catalog=GMSSample;Application Name="GMS Office Tools Service Pack"

Question: how to connect to SQL 2005 with SQL DB Provider.
All old applications does not work.

On local machine when ServerName = 'localhost' or '.' - all OK.
When using SQL server name - error.
Before rebooting all was OK.

Thanks in advance.

If you try to connect from the local PC and it works fine, but does not work from the network then most likely SQL Server is not enabled to accept external network requests. Also if your server name contains instance name, then it also suppose to be specified in your connection string, like servername\instancename|||

On local computer connection avaible only as <localhost> and <.>.

There is no instance name and other sql servers.

SQLSRV Works more than 3 times slower than MSDE 2000 on small test DB (about 100 mb).

VERY many bugs in tools and very slow.... $(((

What comps in MS? I have P4 3MHz 1 Gb SATA - VERY slow.

Sory for digression.

|||

Do you compare performance based on exact same data and structure? If your indexes are not the same as in MSDE 2000 then you cannot compare performance.

About bugs. If you have any, you could report them here. If you do this and they really exist, I believe, it will help to improve product

|||

As Val mentioned, please double check using "SQL Server Configuration Manager" tool that your SQL instance has remote TCP and/or Named Pipe support enabled.

Also, please make sure that the Windows Firewall is not blocking the ports used by SQL Server. You can explicitly add TCP port 1433 to the exception list or you can add Sqlservr.exe program to the exception list (to ensure both TCP and Named Pipes are not blocked).

Jimmy Wu