|
 |
asp_databases thread: ISS Connectivity - ADO could not find the specified provider
Message #1 by kalyan_ramji@h... on Wed, 25 Jul 2001 14:23:57
|
|
Hello Folks,
I was doing all my asp stuff using personal web server and from a DSN I
changed to a DSN Less OLEDB Connection. This was the code I used to open
my connection.
Connection1.Open "PROVIDER=MICROSOFT.JET.OLEDB.4.0;DATA SOURCE=" & Path
& ";USER ID=;PASSWORD=;"
It was working perfect with PWS. Yesterday, I migrated all my stuff from
PWS to a new IIS Server. And when I tried to execute the same file it gave
me the error
ADODB.Connection error '800a0e7a'.ADO could not find the specified
provider.
I cannot understand where I went wrong cos, it worked fine for me with
PWS. Also, I tried the other form of DSN Less connection and now I open my
connection using the code.
Connect1.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & Path
& ";USER ID=;PASSWORD=;"
And this works absolutely fine. I found out form the Microsoft Site that
we need to register a dll MSDASQL.dll in the server which I just did and
it still refuses to recognise the provider. Any help or suggestion would
be grately appreciated.
Thanks.
Message #2 by "Alan Detki" <detkifamily@a...> on Wed, 25 Jul 2001 16:21:19
|
|
> Hello Folks,
>
> I was doing all my asp stuff using personal web server and from a DSN I
> changed to a DSN Less OLEDB Connection. This was the code I used to open
> my connection.
>
> Connection1.Open "PROVIDER=MICROSOFT.JET.OLEDB.4.0;DATA SOURCE=" & Path
> & ";USER ID=;PASSWORD=;"
>
> It was working perfect with PWS. Yesterday, I migrated all my stuff from
> PWS to a new IIS Server. And when I tried to execute the same file it
gave
> me the error
>
> ADODB.Connection error '800a0e7a'.ADO could not find the specified
> provider.
>
> I cannot understand where I went wrong cos, it worked fine for me with
> PWS. Also, I tried the other form of DSN Less connection and now I open
my
> connection using the code.
>
> Connect1.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & Path
> & ";USER ID=;PASSWORD=;"
>
> And this works absolutely fine. I found out form the Microsoft Site that
> we need to register a dll MSDASQL.dll in the server which I just did and
> it still refuses to recognise the provider. Any help or suggestion would
> be grately appreciated.
>
> Thanks.
Here is what I am currently using:
where path\mdb is you path and access mdb
sConnectionstring ="Provider = Microsoft.Jet.OLEDB.4.0;Data Source
path\mdb; Persist Security Info = False "
Al (New Kid on thee block)
Message #3 by "Eoghan O'Byrne" <Eoghan.O'Byrne@W...> on Wed, 25 Jul 2001 16:29:15 +0100
|
|
You could also try installing access on that machine if its not there
already.
Regards,
Eoghan
-----Original Message-----
From: kalyan_ramji@h... [mailto:kalyan_ramji@h...]
Sent: Wednesday, July 25, 2001 3:24 PM
To: ASP Databases
Subject: [asp_databases] ISS Connectivity - ADO could not find the
specified provider
Hello Folks,
I was doing all my asp stuff using personal web server and from a DSN I
changed to a DSN Less OLEDB Connection. This was the code I used to open
my connection.
Connection1.Open "PROVIDER=3DMICROSOFT.JET.OLEDB.4.0;DATA SOURCE=3D" &
Path
& ";USER ID=3D;PASSWORD=3D;"
It was working perfect with PWS. Yesterday, I migrated all my stuff from
PWS to a new IIS Server. And when I tried to execute the same file it
gave
me the error
ADODB.Connection error '800a0e7a'.ADO could not find the specified
provider.
I cannot understand where I went wrong cos, it worked fine for me with
PWS. Also, I tried the other form of DSN Less connection and now I open
my
connection using the code.
Connect1.Open "DRIVER=3D{Microsoft Access Driver (*.mdb)}; DBQ=3D" &
Path
& ";USER ID=3D;PASSWORD=3D;"
And this works absolutely fine. I found out form the Microsoft Site that
we need to register a dll MSDASQL.dll in the server which I just did and
it still refuses to recognise the provider. Any help or suggestion would
be grately appreciated.
Thanks.
Message #4 by kalyan_ramji@h... on Wed, 25 Jul 2001 16:55:04
|
|
Hey Eoghan,
Is it necessary that we need to have Access on the IIS server if we are
using OLEDB? I mean, will installing access add a few more dll's which
would help the server recognize the OLEDB provider. Just curious.. cos I
know for sure that the server does not have MS Access installed.
> You could also try installing access on that machine if its not there
> already.
>
> Regards,
>
> Eoghan
>
Message #5 by "Eoghan O'Byrne" <Eoghan.O'Byrne@W...> on Wed, 25 Jul 2001 16:56:16 +0100
|
|
Hey Kalyan,
I know that the JET drivers come with access so if you can't download
them install access and see if it works.
-----Original Message-----
From: kalyan_ramji@h... [mailto:kalyan_ramji@h...]
Sent: Wednesday, July 25, 2001 5:55 PM
To: ASP Databases
Subject: [asp_databases] RE: ISS Connectivity - ADO could not find the
specified provider
Hey Eoghan,
Is it necessary that we need to have Access on the IIS server if we are
using OLEDB? I mean, will installing access add a few more dll's which
would help the server recognize the OLEDB provider. Just curious.. cos I
know for sure that the server does not have MS Access installed.
> You could also try installing access on that machine if its not there
> already.
>
> Regards,
>
> Eoghan
>
|
|
|
View Cart
