Could not map ordinals

Server: Msg 7351, Level 16, State 2, Line 1
OLE DB provider 'SQLOLEDB' could not map ordinals for one
or more columns of object 'DBSCHEMA_COLUMNS'.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
IColumnsInfo::MapColumnIDs returned 0x40eda:
[COLUMN_NAME=IS_COMPUTED ORDINAL=-1]].
I have 5 SQL 2000, Enterprise Edition, SP3 servers running
Windows 2000 Advanced Server w/SP3.
I have set up linking between each of these servers using
the sa username/password 'be made using this security
context.' They all work but one, SQL2. I can access any
other server from SQL2 but from any other server cannot
access tables on SQL2. I get the message above.
I had this before on this same server, but since then have
formatted the system, made sure all the hardware is
working correctly, installed SQL Server not using the same
system databases, and the error is back.
Anyone have ideas for me to try? I have searched
support.microsoft.com, groups.google.com, yahoo.com,
sqlservercentral.com, sqlmag.com to no avail.
Thanks,
Michelle
Please reply to the newsgroup or email me at
daxemail-microsoft'at'yahoo'dot'comI ended up calling Microsoft PSS. I received wonderful
assistance from Chandra who discovered the instcat.sql
script in the service pack did not run correctly on my
system. We backed up the master database, ran the script,
and I now have access to the linked servers.
Thanks! Hope this helps someone in the future,
Michelle
>--Original Message--
>Server: Msg 7351, Level 16, State 2, Line 1
>OLE DB provider 'SQLOLEDB' could not map ordinals for one
>or more columns of object 'DBSCHEMA_COLUMNS'.
>OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
>IColumnsInfo::MapColumnIDs returned 0x40eda:
>[COLUMN_NAME=IS_COMPUTED ORDINAL=-1]].
>I have 5 SQL 2000, Enterprise Edition, SP3 servers
running
>Windows 2000 Advanced Server w/SP3.
>I have set up linking between each of these servers using
>the sa username/password 'be made using this security
>context.' They all work but one, SQL2. I can access any
>other server from SQL2 but from any other server cannot
>access tables on SQL2. I get the message above.
>I had this before on this same server, but since then
have
>formatted the system, made sure all the hardware is
>working correctly, installed SQL Server not using the
same
>system databases, and the error is back.
>Anyone have ideas for me to try? I have searched
>support.microsoft.com, groups.google.com, yahoo.com,
>sqlservercentral.com, sqlmag.com to no avail.
>Thanks,
>Michelle
>Please reply to the newsgroup or email me at
>daxemail-microsoft'at'yahoo'dot'com
>.
>

Could not get the data of the row from the OLE DB provider 'SQLOLE

We are running SQL2000 SP3 on two servers. One is Server 2003 the other is
Server 2000. Both servers are linked to one another. The 2003 server is
running DTC. We are running several lightweight jobs that are occasionally,
and more often than we like, having the following error:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp basically set variables with data from both the primary server A and
the linked server B using views. This part is successful. The next step is
updating information in server B via a view. This appears to be where the
job is creating the above error. The last part of the sp is another update
entirely on the local server A.
I appreciate your help...
Thanks...Hi
Error 7312 is "Could not set up parameter for remote server '%.*ls'."
I have sometimes seen this error when a remote server has a deadlock or when
a lock can not be acquired to satisfy the request. Have a look at what is
happening on the linked server when this occurs.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisD" <ChrisD@.discussions.microsoft.com> wrote in message
news:D508BC5E-178C-4518-BF00-D17BA13143DF@.microsoft.com...
> We are running SQL2000 SP3 on two servers. One is Server 2003 the other
is
> Server 2000. Both servers are linked to one another. The 2003 server is
> running DTC. We are running several lightweight jobs that are
occasionally,
> and more often than we like, having the following error:
> Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
> [SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB
error
> trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
> [SQLSTATE 01000] (Error 7300). The step failed.
> The sp basically set variables with data from both the primary server A
and
> the linked server B using views. This part is successful. The next step
is
> updating information in server B via a view. This appears to be where the
> job is creating the above error. The last part of the sp is another
update
> entirely on the local server A.
> I appreciate your help...
> Thanks...
>

Could not get the data of the row from the OLE DB provider 'SQLOLE

I am running SQL2000 on two different machines. One is 2003 server, the
other is 2000 server. DTC is setup on the 2003 server. Both servers are
linked to one another. I am running several small jobs that simply execute a
sp. I am consistantly getting the following error message:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp that is running to cause this is error is one of two that consist of
Several varialbes that get their set values from select statements with
views back into Server B and some of them are setting values from the local
server A.
The error occurs after these are set, and when I try to do one of the two
following updates.
One is an update From Server A via a view into Server B. There are no date
values being passed or updated, but the view does include date fields.
The second update is all on the local server. Updating a source table flag.
Any help would be greatly appreciated.
Thanks...
You might want to post your actual T-SQL statements and some configuration
values.
Sincerely,
Anthony Thomas

"ChrisD" <ChrisD@.discussions.microsoft.com> wrote in message
news:1E63096F-95DF-480E-9BFB-6B36BEE44901@.microsoft.com...
I am running SQL2000 on two different machines. One is 2003 server, the
other is 2000 server. DTC is setup on the 2003 server. Both servers are
linked to one another. I am running several small jobs that simply execute
a
sp. I am consistantly getting the following error message:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp that is running to cause this is error is one of two that consist of
Several varialbes that get their set values from select statements with
views back into Server B and some of them are setting values from the local
server A.
The error occurs after these are set, and when I try to do one of the two
following updates.
One is an update From Server A via a view into Server B. There are no date
values being passed or updated, but the view does include date fields.
The second update is all on the local server. Updating a source table flag.
Any help would be greatly appreciated.
Thanks...

Could not get the data of the row from the OLE DB provider 'SQLOLE

I am running SQL2000 on two different machines. One is 2003 server, the
other is 2000 server. DTC is setup on the 2003 server. Both servers are
linked to one another. I am running several small jobs that simply execute
a
sp. I am consistantly getting the following error message:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE D
B error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp that is running to cause this is error is one of two that consist of
Several varialbes that get their set values from select statements with
views back into Server B and some of them are setting values from the local
server A.
The error occurs after these are set, and when I try to do one of the two
following updates.
One is an update From Server A via a view into Server B. There are no date
values being passed or updated, but the view does include date fields.
The second update is all on the local server. Updating a source table flag.
Any help would be greatly appreciated.
Thanks...You might want to post your actual T-SQL statements and some configuration
values.
Sincerely,
Anthony Thomas
"ChrisD" <ChrisD@.discussions.microsoft.com> wrote in message
news:1E63096F-95DF-480E-9BFB-6B36BEE44901@.microsoft.com...
I am running SQL2000 on two different machines. One is 2003 server, the
other is 2000 server. DTC is setup on the 2003 server. Both servers are
linked to one another. I am running several small jobs that simply execute
a
sp. I am consistantly getting the following error message:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE D
B error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp that is running to cause this is error is one of two that consist of
Several varialbes that get their set values from select statements with
views back into Server B and some of them are setting values from the local
server A.
The error occurs after these are set, and when I try to do one of the two
following updates.
One is an update From Server A via a view into Server B. There are no date
values being passed or updated, but the view does include date fields.
The second update is all on the local server. Updating a source table flag.
Any help would be greatly appreciated.
Thanks...

Could not get the data of the row from the OLE DB provider 'SQLOLE

I am running SQL2000 on two different machines. One is 2003 server, the
other is 2000 server. DTC is setup on the 2003 server. Both servers are
linked to one another. I am running several small jobs that simply execute a
sp. I am consistantly getting the following error message:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp that is running to cause this is error is one of two that consist of
Several varialbes that get their set values from select statements with
views back into Server B and some of them are setting values from the local
server A.
The error occurs after these are set, and when I try to do one of the two
following updates.
One is an update From Server A via a view into Server B. There are no date
values being passed or updated, but the view does include date fields.
The second update is all on the local server. Updating a source table flag.
Any help would be greatly appreciated.
Thanks...You might want to post your actual T-SQL statements and some configuration
values.
Sincerely,
Anthony Thomas
"ChrisD" <ChrisD@.discussions.microsoft.com> wrote in message
news:1E63096F-95DF-480E-9BFB-6B36BEE44901@.microsoft.com...
I am running SQL2000 on two different machines. One is 2003 server, the
other is 2000 server. DTC is setup on the 2003 server. Both servers are
linked to one another. I am running several small jobs that simply execute
a
sp. I am consistantly getting the following error message:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp that is running to cause this is error is one of two that consist of
Several varialbes that get their set values from select statements with
views back into Server B and some of them are setting values from the local
server A.
The error occurs after these are set, and when I try to do one of the two
following updates.
One is an update From Server A via a view into Server B. There are no date
values being passed or updated, but the view does include date fields.
The second update is all on the local server. Updating a source table flag.
Any help would be greatly appreciated.
Thanks...

Could not get the column information from the OLE DB provider IBMDA400

Hello

I'm trying to get data from as400 server to sql server, trough a job.
The job executes a stored procedure that retrieves data from a view in an other database on the same server. That view gets the data from as400.
Now, when i run the mentioned stored procedure in the query analyzer, everything works fine, but when the stored procedure is executed from the scheduled job, it fails each time giving the error

"Could not get the column information from the OLE DB provider 'IBMDA400'. [SQLSTATE 42000] (Error 7350). The step failed."

on random points during that process (by that i mean the lenght of time it runs)

does anyone know what the diffrence is between executing an sp in query analyzer or using a job, keeping in mind retrieving data from as400?

thanksSQLAgent service account should have the same permissions as yours. If you're piping data from AS/400 using linked server, make sure mapping entry exists for SQLAgent account as well.

Could not find stored procedure

I used ASP + mssql and got the following error:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
procedure 'my_db..po_fundprice_listVal'.
what is the error?
and how to solve it?
many many thanks.
If you are sure the stored procedure exists, I suggest you check the server
name and database context specified in the connection string to be certain
you are looking in the correct database.
Hope this helps.
Dan Guzman
SQL Server MVP
<Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
>I used ASP + mssql and got the following error:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
> procedure 'my_db..po_fundprice_listVal'.
>
> what is the error?
> and how to solve it?
> many many thanks.
>
|||thanks for your reply.
since i am a newbie of sql server, how can I check whether the stored
procedure exists?
should I open the enterpise manager to check?
moreover, the db is newly given to us and we just import from the previous
vendor who exported all the data as a mdb file.
is it possible that they forgot to give us the stored procedure records?
thanks again. :-)
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
news:%23aufNl8jEHA.3852@.tk2msftngp13.phx.gbl g...
> If you are sure the stored procedure exists, I suggest you check the
server
> name and database context specified in the connection string to be certain
> you are looking in the correct database.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
>
|||You can use the object browser in SQL Server Enterprise Manager or Query
Analyzer to see if the procedure exists. Expand the desired database node
and then stored procedures.
I'm not sure exactly what you and the vendor did to export/import the SQL
Server database but there are no stored procedures in and Access mdb.
Perhaps this is why the proc was omitted in the process ...
Hope this helps.
Dan Guzman
SQL Server MVP
<Blue> wrote in message news:etoMlr8jEHA.2764@.TK2MSFTNGP11.phx.gbl...
> thanks for your reply.
> since i am a newbie of sql server, how can I check whether the stored
> procedure exists?
> should I open the enterpise manager to check?
> moreover, the db is newly given to us and we just import from the previous
> vendor who exported all the data as a mdb file.
> is it possible that they forgot to give us the stored procedure records?
> thanks again. :-)
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
> news:%23aufNl8jEHA.3852@.tk2msftngp13.phx.gbl g...
> server
>
|||ic... thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
news:%23nKyaS9jEHA.592@.TK2MSFTNGP11.phx.gbl g...[vbcol=seagreen]
> You can use the object browser in SQL Server Enterprise Manager or Query
> Analyzer to see if the procedure exists. Expand the desired database node
> and then stored procedures.
> I'm not sure exactly what you and the vendor did to export/import the SQL
> Server database but there are no stored procedures in and Access mdb.
> Perhaps this is why the proc was omitted in the process ...
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <Blue> wrote in message news:etoMlr8jEHA.2764@.TK2MSFTNGP11.phx.gbl...
previous
>

Could not find stored procedure

I used ASP + mssql and got the following error:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
procedure 'my_db..po_fundprice_listVal'.
what is the error?
and how to solve it?
many many thanks.If you are sure the stored procedure exists, I suggest you check the server
name and database context specified in the connection string to be certain
you are looking in the correct database.
--
Hope this helps.
Dan Guzman
SQL Server MVP
<Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
>I used ASP + mssql and got the following error:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
> procedure 'my_db..po_fundprice_listVal'.
>
> what is the error?
> and how to solve it?
> many many thanks.
>|||thanks for your reply.
since i am a newbie of sql server, how can I check whether the stored
procedure exists?
should I open the enterpise manager to check?
moreover, the db is newly given to us and we just import from the previous
vendor who exported all the data as a mdb file.
is it possible that they forgot to give us the stored procedure records?
thanks again. :-)
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> ¦b¶l¥ó
news:%23aufNl8jEHA.3852@.tk2msftngp13.phx.gbl ¤¤¼¶¼g...
> If you are sure the stored procedure exists, I suggest you check the
server
> name and database context specified in the connection string to be certain
> you are looking in the correct database.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
> >I used ASP + mssql and got the following error:
> >
> > Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
> > procedure 'my_db..po_fundprice_listVal'.
> >
> >
> > what is the error?
> > and how to solve it?
> > many many thanks.
> >
> >
>|||You can use the object browser in SQL Server Enterprise Manager or Query
Analyzer to see if the procedure exists. Expand the desired database node
and then stored procedures.
I'm not sure exactly what you and the vendor did to export/import the SQL
Server database but there are no stored procedures in and Access mdb.
Perhaps this is why the proc was omitted in the process ...
--
Hope this helps.
Dan Guzman
SQL Server MVP
<Blue> wrote in message news:etoMlr8jEHA.2764@.TK2MSFTNGP11.phx.gbl...
> thanks for your reply.
> since i am a newbie of sql server, how can I check whether the stored
> procedure exists?
> should I open the enterpise manager to check?
> moreover, the db is newly given to us and we just import from the previous
> vendor who exported all the data as a mdb file.
> is it possible that they forgot to give us the stored procedure records?
> thanks again. :-)
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> ¦b¶l¥ó
> news:%23aufNl8jEHA.3852@.tk2msftngp13.phx.gbl ¤¤¼¶¼g...
>> If you are sure the stored procedure exists, I suggest you check the
> server
>> name and database context specified in the connection string to be
>> certain
>> you are looking in the correct database.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> <Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
>> >I used ASP + mssql and got the following error:
>> >
>> > Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>> > [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
>> > procedure 'my_db..po_fundprice_listVal'.
>> >
>> >
>> > what is the error?
>> > and how to solve it?
>> > many many thanks.
>> >
>> >
>>
>|||ic... thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> ¦b¶l¥ó
news:%23nKyaS9jEHA.592@.TK2MSFTNGP11.phx.gbl ¤¤¼¶¼g...
> You can use the object browser in SQL Server Enterprise Manager or Query
> Analyzer to see if the procedure exists. Expand the desired database node
> and then stored procedures.
> I'm not sure exactly what you and the vendor did to export/import the SQL
> Server database but there are no stored procedures in and Access mdb.
> Perhaps this is why the proc was omitted in the process ...
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <Blue> wrote in message news:etoMlr8jEHA.2764@.TK2MSFTNGP11.phx.gbl...
> > thanks for your reply.
> > since i am a newbie of sql server, how can I check whether the stored
> > procedure exists?
> > should I open the enterpise manager to check?
> >
> > moreover, the db is newly given to us and we just import from the
previous
> > vendor who exported all the data as a mdb file.
> > is it possible that they forgot to give us the stored procedure records?
> >
> > thanks again. :-)
> >
> > "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> ¦b¶l¥ó
> > news:%23aufNl8jEHA.3852@.tk2msftngp13.phx.gbl ¤¤¼¶¼g...
> >> If you are sure the stored procedure exists, I suggest you check the
> > server
> >> name and database context specified in the connection string to be
> >> certain
> >> you are looking in the correct database.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> <Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
> >> >I used ASP + mssql and got the following error:
> >> >
> >> > Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
> >> > [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored
> >> > procedure 'my_db..po_fundprice_listVal'.
> >> >
> >> >
> >> > what is the error?
> >> > and how to solve it?
> >> > many many thanks.
> >> >
> >> >
> >>
> >>
> >
> >
>

Could not find stored procedure

I used ASP + mssql and got the following error:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find st
ored
procedure 'my_db..po_fundprice_listVal'.
what is the error?
and how to solve it?
many many thanks.If you are sure the stored procedure exists, I suggest you check the server
name and database context specified in the connection string to be certain
you are looking in the correct database.
Hope this helps.
Dan Guzman
SQL Server MVP
<Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
>I used ASP + mssql and got the following error:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find
stored
> procedure 'my_db..po_fundprice_listVal'.
>
> what is the error?
> and how to solve it?
> many many thanks.
>|||thanks for your reply.
since i am a newbie of sql server, how can I check whether the stored
procedure exists?
should I open the enterpise manager to check?
moreover, the db is newly given to us and we just import from the previous
vendor who exported all the data as a mdb file.
is it possible that they forgot to give us the stored procedure records?
thanks again. :-)
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
news:%23aufNl8jEHA.3852@.tk2msftngp13.phx.gbl g...
> If you are sure the stored procedure exists, I suggest you check the
server
> name and database context specified in the connection string to be certain
> you are looking in the correct database.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <Blue> wrote in message news:ekYzXX8jEHA.3632@.TK2MSFTNGP09.phx.gbl...
>|||You can use the object browser in SQL Server Enterprise Manager or Query
Analyzer to see if the procedure exists. Expand the desired database node
and then stored procedures.
I'm not sure exactly what you and the vendor did to export/import the SQL
Server database but there are no stored procedures in and Access mdb.
Perhaps this is why the proc was omitted in the process ...
Hope this helps.
Dan Guzman
SQL Server MVP
<Blue> wrote in message news:etoMlr8jEHA.2764@.TK2MSFTNGP11.phx.gbl...
> thanks for your reply.
> since i am a newbie of sql server, how can I check whether the stored
> procedure exists?
> should I open the enterpise manager to check?
> moreover, the db is newly given to us and we just import from the previous
> vendor who exported all the data as a mdb file.
> is it possible that they forgot to give us the stored procedure records?
> thanks again. :-)
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
> news:%23aufNl8jEHA.3852@.tk2msftngp13.phx.gbl g...
> server
>|||ic... thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> bl
news:%23nKyaS9jEHA.592@.TK2MSFTNGP11.phx.gbl g...
> You can use the object browser in SQL Server Enterprise Manager or Query
> Analyzer to see if the procedure exists. Expand the desired database node
> and then stored procedures.
> I'm not sure exactly what you and the vendor did to export/import the SQL
> Server database but there are no stored procedures in and Access mdb.
> Perhaps this is why the proc was omitted in the process ...
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <Blue> wrote in message news:etoMlr8jEHA.2764@.TK2MSFTNGP11.phx.gbl...
previous[vbcol=seagreen]
>

Could not fetch a row using a bookmark from OLE DB provider 'VFPOLEDB'.

I'm trying to update a VFP table via a linked server in SQL 2000, I'm able to use "openquery" to view the records from the table, but when I try the following command:

Update M2MEDI...x830rels

Set favailship = 100

I get the following error

[OLE/DB provider returned message: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.]

OLE DB error trace [OLE/DB Provider 'VFPOLEDB' IRowsetLocate::GetRowsByBookmark returned 0x80040e21: 01000000].

Msg 7333, Level 16, State 2, Line 1

Could not fetch a row using a bookmark from OLE DB provider 'VFPOLEDB'.

How do I fix this

Thanks

David Davis

For the linked tables use the four-part naming and make sure that the 'Distributed Transaction Coordinator' service is running on your server.

HTH

|||

Isn't this

M2MEDI...x830rels

the 4 part naming convention

David Davis

|||Looks like you have three dots, not two

Could not fetch a row from OLE DB provider 'VFPOLEDB'

I keep getting the error "Could not fetch a row from OLE DB provider 'VFPOLEDB' when I do a query on a FoxPro Linked Server through SQL 2000. If the query returns 0 rows I don't get an error I just get the structure of the table. But if the query returns rows I get the error. I can replicate this on a test machine but my development machine works fine.

I have checked the SVRNETCN and the CLICONFG apps in SQL Server and they seem to be set the same on both machines. I am using NamedPipes on the server. I tried starting the DTS and that didn't fix the issue.

Would anyone know what I don't have working correctly?

NOTE: I also posted this in the MSDN Newsgroups

Hi Evan,

First, be sure you have the latest FoxPro and Visual FoxPro OLE DB data provider, downloadable from msnd.microsoft.com/vfoxpro/downloads/updates .

Can you describe your data in more detail? Do you have exactly the same data on the machine that works and the machine that fails? There's a possibility you have some anomaly in the data.

To make sure your linked server is set up correctly, do you have any other data that works on both machines?

What does your query look like? If you select only a few fields, especially character fields since they are the "safest" can you get the expected rows from the bad machine?

|||

Lets leave this answer as me being dumb. My installer isn't working correctly. I wasn't getting some things installed. It is still kind of weird that it would return no rows ok, but once there was data it wouldn't work.

Could not create an instance of OLE DB provider 'MSDASQL'

When trying to run an application we use called Taxware
I get the following error:
[Microsoft][ODBC SQL Server Driver]Could not create an
instance of DB provider 'MSDASQL'.
Taxware uses the free Microsoft SQL server 7. If I
uninstall the application MSSQL7 stays on the computer
(it's still running in the system tray) The error occurs
whrn I tell Taxware where our timesheet file is (generated
by casware time and shared by both applications)
Could anybody help?
You might want to contact the vendor of the application to find out what is
going on at this point in the application. He might be able to give you
better inforamtion about what is happening.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Could not create an instance of OLE DB provider 'MSDASQL'

When trying to run an application we use called Taxware
I get the following error:
[Microsoft][ODBC SQL Server Driver]Could not create an
instance of DB provider 'MSDASQL'.
Taxware uses the free Microsoft SQL server 7. If I
uninstall the application MSSQL7 stays on the computer
(it's still running in the system tray) The error occurs
whrn I tell Taxware where our timesheet file is (generated
by casware time and shared by both applications)
Could anybody help?You might want to contact the vendor of the application to find out what is
going on at this point in the application. He might be able to give you
better inforamtion about what is happening.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Could not create an instance of OLE DB provider 'MSDASQL'

When trying to run an application we use called Taxware
I get the following error:
[Microsoft][ODBC SQL Server Driver]Could not create an
instance of DB provider 'MSDASQL'.
Taxware uses the free Microsoft SQL server 7. If I
uninstall the application MSSQL7 stays on the computer
(it's still running in the system tray) The error occurs
whrn I tell Taxware where our timesheet file is (generated
by casware time and shared by both applications)
Could anybody help?You might want to contact the vendor of the application to find out what is
going on at this point in the application. He might be able to give you
better inforamtion about what is happening.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Could not create an instance of OLE DB provider 'Microsoft.Jet.OLE

hi,
I am running the following query and getting this error.
Could not create an instance of OLE DB provider 'Microsoft.Jet.OLEDB.4.0'.
OLE DB error trace [Non-interface error: CoCreate of DSO for
Microsoft.Jet.OLEDB.4.0 returned 0x80040e73].
I am using Windows XP SP2 and Access 2003 and running this query on a SQL
server 200 which is on a network.
SELECT *
FROM OPENdatasource(
'Microsoft.Jet.OLEDB.4.0',
'Data Source="\\machineNameOnNetwork\c:\Test.mdb;"
User ID=admin;Password=somePassword;"'
).Test.dbo.Employees
Thanks
Regards,
tech@.77A shot in the dark: the UNC path you're specifying doesn't look quite normal
.
Did you mean
\\machineNameOnNetwork\c$\Test.mdb
?
"tech77" wrote:

> hi,
> I am running the following query and getting this error.
> Could not create an instance of OLE DB provider 'Microsoft.Jet.OLEDB.4.0'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for
> Microsoft.Jet.OLEDB.4.0 returned 0x80040e73].
> I am using Windows XP SP2 and Access 2003 and running this query on a SQL
> server 200 which is on a network.
> SELECT *
> FROM OPENdatasource(
> 'Microsoft.Jet.OLEDB.4.0',
> 'Data Source="\\machineNameOnNetwork\c:\Test.mdb;"
> User ID=admin;Password=somePassword;"'
> ).Test.dbo.Employees
> Thanks
> Regards,
> tech@.77|||A few pointers. Don't know whcih one is applicable for you though
1. If you are accessing a network share ,then the account in which SQL
Server is running should have access to that share.
2. Do not use C:, use C$ like this..
\\machineNameOnNetwork\c$\Test.mdb;"
Hope this helps.

Could not create an instance of OLE DB provider 'Microsoft.Jet

Thanks for the replies.I changed C: to C$ but I still get the same error.
The machineNameOnNetwork is my local computer name which is on the corporate
network.Where am i going wrong?
Thanks for your help.
"Omnibuzz" wrote:

> A few pointers. Don't know whcih one is applicable for you though
> 1. If you are accessing a network share ,then the account in which SQL
> Server is running should have access to that share.
> 2. Do not use C:, use C$ like this..
> \\machineNameOnNetwork\c$\Test.mdb;"
> Hope this helps.Is your machine shared on the network?
i.e.
Can you access c:\test.mdb from another PC?
Is the database also running on your PC?
"tech77" <tech77@.discussions.microsoft.com> wrote in message
news:993B9891-0894-4046-AB32-A098D36C0FAD@.microsoft.com...
> Thanks for the replies.I changed C: to C$ but I still get the same error.
> The machineNameOnNetwork is my local computer name which is on the
corporate
> network.Where am i going wrong?
> Thanks for your help.
>
> "Omnibuzz" wrote:
>|||Not the account in which you have connected to SQL Server.
The account in which the SQL Server Service is running should have access to
your machine and your folder.
Or the best way is to copy this file to a folder in your SQL Server and use
that path in the ODS.|||thanks Omnibuzz,Jim and Mark for your responses.
.The machine on which SQL Server is running might not have access to my
machine and my folder.Its on a remote server.
And I cannot configure that machine so it has access to my machine.
So I have to install SQL Server locally else I cant accomplish what I am
trying to do or is there some workaround?
thanks
"Omnibuzz" wrote:

> Not the account in which you have connected to SQL Server.
> The account in which the SQL Server Service is running should have access
to
> your machine and your folder.
> Or the best way is to copy this file to a folder in your SQL Server and us
e
> that path in the ODS.|||Create a share on your system, and put the mdb file in it. Enable the guest
account for your system, and give the guest user write permissions to the
file (both through-share, and NTFS if necessary).
You'll have to enable the guest account for it to work, because the SQL
server is more than likely running under the Local System context on the
system it resides on. Local System has no authority over the network, so whe
n
the SQL system tries to connect to you, it appears as guest.
Another method involves trusting the SQL server for delagation, but since
you said you can't modify it, it's not worth going into detail.
HTH
"tech77" wrote:
> thanks Omnibuzz,Jim and Mark for your responses.
> .The machine on which SQL Server is running might not have access to my
> machine and my folder.Its on a remote server.
> And I cannot configure that machine so it has access to my machine.
> So I have to install SQL Server locally else I cant accomplish what I am
> trying to do or is there some workaround?
> thanks
>
> "Omnibuzz" wrote:
>|||You can put the MDB on the database server, instead of your PC. Make it a
share if others need access to it.
You can put the MDB on a network server that the SQL Server account would
have access to.
You can grant the SQL Server account access to the MDB on your machine.
(the above two require proper network security, but should not be difficult)
You can drop the MDB database entirely and move the tables to SQL Server,
which is probably the best bet. If you absolutely need to access these
tables via MS Access, you can create linked tables pointing to SQL Server.
This will put all the tables local in SQL Server, but still let you use your
access front end.
Is there really a need to have SQL server access your local MDB, rather than
migrating the tables and data to SQL Server?
"tech77" <tech77@.discussions.microsoft.com> wrote in message
news:7B9F4484-F46C-493F-8830-A5602EC96B55@.microsoft.com...
> thanks Omnibuzz,Jim and Mark for your responses.
> .The machine on which SQL Server is running might not have access to my
> machine and my folder.Its on a remote server.
> And I cannot configure that machine so it has access to my machine.
> So I have to install SQL Server locally else I cant accomplish what I am
> trying to do or is there some workaround?
> thanks
>
> "Omnibuzz" wrote:
>
access to
use|||Finally it was decided to download SQL Server express edition 2005 and copy
the Access tables to SQL Server and use for our requirement .
Thanks all for your help.I learnt quite a few things from you all.
Regards,
tech@.77
"Jim Underwood" wrote:

> You can put the MDB on the database server, instead of your PC. Make it a
> share if others need access to it.
> You can put the MDB on a network server that the SQL Server account would
> have access to.
> You can grant the SQL Server account access to the MDB on your machine.
> (the above two require proper network security, but should not be difficul
t)
> You can drop the MDB database entirely and move the tables to SQL Server,
> which is probably the best bet. If you absolutely need to access these
> tables via MS Access, you can create linked tables pointing to SQL Server.
> This will put all the tables local in SQL Server, but still let you use yo
ur
> access front end.
> Is there really a need to have SQL server access your local MDB, rather th
an
> migrating the tables and data to SQL Server?
>
> "tech77" <tech77@.discussions.microsoft.com> wrote in message
> news:7B9F4484-F46C-493F-8830-A5602EC96B55@.microsoft.com...
> access to
> use
>
>

Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'?

Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
now BULK INSERT doesn't seem to work.
Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
11:38:51
create table ##Holding_Tank (full_record varchar(500))
BULK INSERT ##Holding_Tank
FROM 'g:\narf.txt'
WITH
(
ROWTERMINATOR = '0x0a',
TABLOCK
)
Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for
BULKIMPORTSTREAM returned 0x8007045a].
Any suggestions?
On Mar 2, 11:17 am, bour...@.gmail.com wrote:
> Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
> now BULK INSERT doesn't seem to work.
> Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
> 11:38:51
> create table ##Holding_Tank (full_record varchar(500))
> BULK INSERT ##Holding_Tank
> FROM 'g:\narf.txt'
> WITH
> (
> ROWTERMINATOR = '0x0a',
> TABLOCK
> )
> Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for
> BULKIMPORTSTREAM returned 0x8007045a].
> Any suggestions?
The fix appears to be to re-register the impprov dll, followed by
restarting the service.

Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'?

Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
now BULK INSERT doesn't seem to work.
Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
11:38:51
create table ##Holding_Tank (full_record varchar(500))
BULK INSERT ##Holding_Tank
FROM 'g:\narf.txt'
WITH
(
ROWTERMINATOR = '0x0a',
TABLOCK
)
Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for
BULKIMPORTSTREAM returned 0x8007045a].
Any suggestions?On Mar 2, 11:17 am, bour...@.gmail.com wrote:
> Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
> now BULK INSERT doesn't seem to work.
> Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
> 11:38:51
> create table ##Holding_Tank (full_record varchar(500))
> BULK INSERT ##Holding_Tank
> FROM 'g:\narf.txt'
> WITH
> (
> ROWTERMINATOR = '0x0a',
> TABLOCK
> )
> Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for
> BULKIMPORTSTREAM returned 0x8007045a].
> Any suggestions?
The fix appears to be to re-register the impprov dll, followed by
restarting the service.

Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'?

Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
now BULK INSERT doesn't seem to work.
Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
11:38:51
create table ##Holding_Tank (full_record varchar(500))
BULK INSERT ##Holding_Tank
FROM 'g:\narf.txt'
WITH
(
ROWTERMINATOR = '0x0a',
TABLOCK
)
Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for
BULKIMPORTSTREAM returned 0x8007045a].
Any suggestions?On Mar 2, 11:17 am, bour...@.gmail.com wrote:
> Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
> now BULK INSERT doesn't seem to work.
> Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
> 11:38:51
> create table ##Holding_Tank (full_record varchar(500))
> BULK INSERT ##Holding_Tank
> FROM 'g:\narf.txt'
> WITH
> (
> ROWTERMINATOR = '0x0a',
> TABLOCK
> )
> Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for
> BULKIMPORTSTREAM returned 0x8007045a].
> Any suggestions?
The fix appears to be to re-register the impprov dll, followed by
restarting the service.

Could not create an instance of OLE DB provider BULKIMPORTSTREAM.

Run this script:

bulk insert viewdisp
from 'd:\downloads\assessment05_preload\viewdisp.txt'
with (
check_constraints,
datafiletype = 'widechar',
firstrow = 1,
maxerrors = 0
)
go

Get this error:

Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for BULKIMPORTSTREAM returned 0x80040154].

SQL Server 2000 - SP3a
Logged in as sa with system admin, bulk insert admin, dbo, ddl admin, local admin, king of the world... you name it.

Is this a OLE DB Driver or MDAC issue?

Anyone else ever had this issue. You would think that Microsoft would have all of their error messages on their own WebSite, but that must be too much trouble for them.Based on the HRESULT you posted (80040154), you've got at least one DLL class that isn't registered properly. The simple answer is to remove the SQL client tools using the Control Panel, then reinstall the SQL Client tools.

If you know (or at least strongly suspect) which DLL has gone AWOL, you can certainly try to register it manually.

-PatP|||Do you know which DLLs I should look at? Is the the ODBC or the SQL Server?

Thanks.|||Operative word being "should", the problem should be in the SQL Server.

-PatP