BizTalk Server General - Database Lookup Functoid Access Connection String

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > June 2004 > Database Lookup Functoid Access Connection String





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Database Lookup Functoid Access Connection String
Ktz4

2004-06-11, 12:01 am

In Biztalk 2002 we are performing a Database lookup functoid using Provider=MSDASQL.1. When I try to use the same provider in Biztalk 2004 system.data does not support it. Any ideas?
Scott White

2004-06-11, 5:43 pm

Try

provider=SQLOLEDB.1

"Ktz4" wrote:

> In Biztalk 2002 we are performing a Database lookup functoid using Provider=MSDASQL.1. When I try to use the same provider in Biztalk 2004 system.data does not support it. Any ideas?
>

ktz4

2004-06-20, 11:07 pm

I have tried the following and these are the results I get:

Provider=MSDASQL.1;Data Source = DataSourceName

The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc).
-------------------------------------------------------------
Provider=ODBC;Data Source = DataSourceName

The 'ODBC' provider is not registered on the local machine.
-------------------------------------------------------------
Provider=SQLOLEDB.1;Data Source = DataSourceName

Invaild authorization specification
------------------------------------------------------------- The DSN is configured to us
e the Microsoft Access Driver (*.mdb). Any ideas would be greatly appreciated.




"Scott White" wrote:
[vbcol=seagreen]
> Try
>
> provider=SQLOLEDB.1
>
> "Ktz4" wrote:
>
Jan Eliasen

2004-06-20, 11:07 pm

Hi. Try with
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=<database>;Data Source=<db-server>

Replace the strings in brackets with something useful. The above
connectionstring is for integrated security and not username/password.

Jan Eliasen.

On Mon, 14 Jun 2004 12:39:01 -0700, "ktz4"
<ktz4@discussions.microsoft.com> wrote:

>I have tried the following and these are the results I get:
>
>Provider=MSDASQL.1;Data Source = DataSourceName
>
>The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc).
>-------------------------------------------------------------
>Provider=ODBC;Data Source = DataSourceName
>
>The 'ODBC' provider is not registered on the local machine.
>-------------------------------------------------------------
>Provider=SQLOLEDB.1;Data Source = DataSourceName
>
>Invaild authorization specification
>------------------------------------------------------------- The DSN is configured to u

se the Microsoft Access Driver (*.mdb). Any ideas would be greatly appreciated.[vbcol=seagreen]
>
>
>
>
>"Scott White" wrote:
>

--
Jan Eliasen, representing himself and not the company he works for.
ktz4

2004-06-26, 10:51 am

This works great with SQL, but I'm trying to connect to a Microsoft Access database. Any other ideas?

"Jan Eliasen" wrote:

> Hi. Try with
> Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=<database>;Data Source=<db-server>
>
> Replace the strings in brackets with something useful. The above
> connectionstring is for integrated security and not username/password.
>
> Jan Eliasen.
>
> On Mon, 14 Jun 2004 12:39:01 -0700, "ktz4"
> <ktz4@discussions.microsoft.com> wrote:
>
use the Microsoft Access Driver (*.mdb). Any ideas would be greatly appreciated.[vbcol=seagreen]
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>

Jan Eliasen

2004-06-26, 10:51 am

Hi

Well, try removing some part of the string I suggested?

For instance, try removing "Persist Security Info=False" or something.
See if that will work - perhaps one of the others.

Jan Eliasen

On Mon, 21 Jun 2004 11:26:01 -0700, "ktz4"
<ktz4@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>This works great with SQL, but I'm trying to connect to a Microsoft Access database. Any other ideas?
>
>"Jan Eliasen" wrote:
>
o use the Microsoft Access Driver (*.mdb). Any ideas would be greatly appreciated.[vbcol=seagreen]

--
Jan Eliasen, representing himself and not the company he works for.
ktz4

2004-06-29, 5:52 pm

Thanks! I finally got it with: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Directory\dbname.mdb;Persist Security Info=False

"Jan Eliasen" wrote:

> Hi
>
> Well, try removing some part of the string I suggested?
>
> For instance, try removing "Persist Security Info=False" or something.
> See if that will work - perhaps one of the others.
>
> Jan Eliasen
>
> On Mon, 21 Jun 2004 11:26:01 -0700, "ktz4"
> <ktz4@discussions.microsoft.com> wrote:
>
to use the Microsoft Access Driver (*.mdb). Any ideas would be greatly appreciated.[vbcol=seagreen]
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com