Re: Data View OLE DB connection to Sybase

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



you may need to add that OLE DB provider so that sharepoint trusts it. i
had to do this with my MS Access OLE DB

http://groups.google.com/group/microsoft.public.frontpage.client/browse_thread/thread/5e321ecbaaf0c867/48f73a2ecfd4f9ce?lnk=gst&q=an+error+occurred+while+retrieving+the+list+of+Databases&rnum=6#48f73a2ecfd4f9ce

to see the list of trusted providers on your site, do:
stsadm -o getproperty -propertyname data-retrieval-services-oledb-providers

if you don't see your OLE DB listed, you will need to add it.


"Ivan Yu" <IvanYu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1D566AA1-9B9C-482C-99CB-B3D28F7287EA@xxxxxxxxxxxxxxxx
Does anybody have experience on this?

"Ivan Yu" wrote:

I have an OLE DB provider (driver) installed on the SharePoint host, and
I
have written a short 5 lines of code to create an ADO object and use that
provider to connect to the Sybase I want to connect to, everything works
no
problem.

But when I try to connect to the same database from FP2003 (with
connection
to SharePoint site), it fails, giving the "Server Error: An error
occurred
while retrieving the list of Databases from ..."

Using the same connection string, on the SharePoint host, has no problem
connecting to the Sybase, so this cannot be a physical network, firewall
issue, nor some OLE DB system dll issue.

Connection string looks like
Provider=DataDirect Sybase ADO Provider; Data Source=xxxxx; Initial
Catalog=yyyy; User id=zzzz; Password=.....

Is there something that I need to permission in SharePoint to enable
connection to Sybase (or any arbitrary database) even after an OLE DB
provider is installed?

I have also tried to define an OLE DB Data Source name as well on the
SharePoint host (kind of like ODBC DSN). VBA again connects no problem,
but
FP2003 cannot.

The SharePoint installation is a simple standalone one, with SS and IIS
running on the same host.

Running out of ideas here, thanks in advance for any pointers on this.


.



Relevant Pages

  • Re: ODBC/OLE DB Connection Pool
    ... but most OLE DB providers are. ... OLE DB provider indicates is supports a Free Threaded model ... >> connection be kept open for the application as this will serialize all ... >> The ADO Connection object implicitly uses IDataInitialize. ...
    (microsoft.public.data.ado)
  • Re: ODBC/OLE DB Connection Pool
    ... but most OLE DB providers are. ... OLE DB provider indicates is supports a Free Threaded model ... >> connection be kept open for the application as this will serialize all ... >> The ADO Connection object implicitly uses IDataInitialize. ...
    (microsoft.public.inetserver.asp.db)
  • Re: ODBC/OLE DB Connection Pool
    ... but most OLE DB providers are. ... OLE DB provider indicates is supports a Free Threaded model ... >> connection be kept open for the application as this will serialize all ... >> The ADO Connection object implicitly uses IDataInitialize. ...
    (microsoft.public.data.oledb)
  • Re: multi-user update in SQL Server 2000
    ... > I have tried to use OLE DB provider and adOpenDynamic, ... > Dim db As Connection ... >> cursors should be unusable with a single connected user. ...
    (microsoft.public.vb.database.ado)
  • Re: multi-user update in SQL Server 2000
    ... Dim db As Connection ... >> I have already tried to change the cursor to server side. ... > You should use the OLE DB provider instead, I'm not certain it will directly ...
    (microsoft.public.vb.database.ado)