VBS = Error - ASP = OK - Why ??

Hi
I have a .VBS file - contents below:
=====================================================================

dataBaseRoot = "d:\Servers\byers\data\mmailing\"

DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
dataBaseRoot & "data\listShares.mdb"
set ConLS = CreateObject("ADODB.Connection")
ConLS.Open DBConLS

=====================================================================

When I double click on it, the error shown below is generated.

---------------------------
Windows Script Host
---------------------------
Script: D:\Servers\Byers\wwwroot\mmailing\connectionTest.vbs
Line: 7
Char: 1
Error: Provider is not specified and there is no designated default
provider.
Code: 800A0EA9
Source: ADODB.Connection

---------------------------
OK
---------------------------




I have a Classic ASP file - contents below

=====================================================================
dataBaseRoot = "d:\Servers\byers\data\mmailing\"

DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
dataBaseRoot & "data\listShares.mdb"
set ConLS = Server.CreateObject("ADODB.Connection")
ConLS.Open DBConLS


=====================================================================

When I run the ASPage in Internet Explorer - it runs OK
(and actually Opens the Database)


I have tried the "Jet" provider - same results

I have Installed the latest MDAC (2.8)

Why does it work in the ASP but not in the VBS

(It works on other servers - but not this new one)

THE SERVER IS
Operating System Microsoft Windows Server 2003, Standard Edition
OS Service Pack Service Pack 2
Internet Explorer 7.0.5730.11
DirectX 4.09.00.0904 (DirectX 9.0c)


Thank you
Pete (Northolt UK)

CoreyThomasMCSEMCSAMCDBA
Mon Mar 17 09:56:01 CDT 2008

Can you post the code you are using for the Jet provider?

"p byers" wrote:

> Hi
> I have a .VBS file - contents below:
> =====================================================================
>
> dataBaseRoot = "d:\Servers\byers\data\mmailing\"
>
> DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> dataBaseRoot & "data\listShares.mdb"
> set ConLS = CreateObject("ADODB.Connection")
> ConLS.Open DBConLS
>
> =====================================================================
>
> When I double click on it, the error shown below is generated.
>
> ---------------------------
> Windows Script Host
> ---------------------------
> Script: D:\Servers\Byers\wwwroot\mmailing\connectionTest.vbs
> Line: 7
> Char: 1
> Error: Provider is not specified and there is no designated default
> provider.
> Code: 800A0EA9
> Source: ADODB.Connection
>
> ---------------------------
> OK
> ---------------------------
>
>
>
>
> I have a Classic ASP file - contents below
>
> =====================================================================
> dataBaseRoot = "d:\Servers\byers\data\mmailing\"
>
> DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> dataBaseRoot & "data\listShares.mdb"
> set ConLS = Server.CreateObject("ADODB.Connection")
> ConLS.Open DBConLS
>
>
> =====================================================================
>
> When I run the ASPage in Internet Explorer - it runs OK
> (and actually Opens the Database)
>
>
> I have tried the "Jet" provider - same results
>
> I have Installed the latest MDAC (2.8)
>
> Why does it work in the ASP but not in the VBS
>
> (It works on other servers - but not this new one)
>
> THE SERVER IS
> Operating System Microsoft Windows Server 2003, Standard Edition
> OS Service Pack Service Pack 2
> Internet Explorer 7.0.5730.11
> DirectX 4.09.00.0904 (DirectX 9.0c)
>
>
> Thank you
> Pete (Northolt UK)
>
>
>
>
>
>

Bob
Mon Mar 17 10:09:55 CDT 2008

p byers wrote:
> Hi
> I have a .VBS file - contents below:
> =====================================================================
>
> dataBaseRoot = "d:\Servers\byers\data\mmailing\"
>
> DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> dataBaseRoot & "data\listShares.mdb"
> set ConLS = CreateObject("ADODB.Connection")
> ConLS.Open DBConLS
>
> =====================================================================
>
> When I double click on it, the error shown below is generated.
>
> ---------------------------
> Windows Script Host
> ---------------------------
> Script: D:\Servers\Byers\wwwroot\mmailing\connectionTest.vbs
> Line: 7
> Char: 1
> Error: Provider is not specified and there is no designated default
> provider.
> Code: 800A0EA9
> Source: ADODB.Connection
>
> ---------------------------
> OK
> ---------------------------
>
>
>
>
> I have a Classic ASP file - contents below
>
> =====================================================================
> dataBaseRoot = "d:\Servers\byers\data\mmailing\"
>
> DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> dataBaseRoot & "data\listShares.mdb"
> set ConLS = Server.CreateObject("ADODB.Connection")
> ConLS.Open DBConLS
>
>
> =====================================================================
>
> When I run the ASPage in Internet Explorer - it runs OK
> (and actually Opens the Database)
>

A couple versions of MDAC ago, MS separated out the Jet components into a
separate download (their first step towards deprecating the Jet engine
before they realized that they would not be able to). You need to go to the
MSDN site and search for the Jet components download.

>
> I have tried the "Jet" provider
>
... which you should be using regardless. Always choose a native provider
for the database you aare using rather than going through the ODBC provider



Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Richard
Mon Mar 17 10:20:18 CDT 2008

The connection string I use for MS Access databases is similar to (in
VBScript):

strConnect = "DRIVER=Microsoft Access Driver (*.mdb);" _
& "FIL=MS Access;DriverId=25;" _
& "DefaultDir=" & databaseRoot & "data;" _
& "DBQ=" & databaseRoot & "data\listShares.mdb;"

Notice that DefaultDir is the folder where the mdb file resides. I don't
know if that is necessary. The FIL and DriverID parameters are probably
important.

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--

"p byers" <pb@sst-ltd.co.uk> wrote in message
news:47DE3F39.E3537C10@sst-ltd.co.uk...
> Hi
> I have a .VBS file - contents below:
> =====================================================================
>
> dataBaseRoot = "d:\Servers\byers\data\mmailing\"
>
> DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> dataBaseRoot & "data\listShares.mdb"
> set ConLS = CreateObject("ADODB.Connection")
> ConLS.Open DBConLS
>
> =====================================================================
>
> When I double click on it, the error shown below is generated.
>
> ---------------------------
> Windows Script Host
> ---------------------------
> Script: D:\Servers\Byers\wwwroot\mmailing\connectionTest.vbs
> Line: 7
> Char: 1
> Error: Provider is not specified and there is no designated default
> provider.
> Code: 800A0EA9
> Source: ADODB.Connection
>
> ---------------------------
> OK
> ---------------------------
>
>
>
>
> I have a Classic ASP file - contents below
>
> =====================================================================
> dataBaseRoot = "d:\Servers\byers\data\mmailing\"
>
> DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> dataBaseRoot & "data\listShares.mdb"
> set ConLS = Server.CreateObject("ADODB.Connection")
> ConLS.Open DBConLS
>
>
> =====================================================================
>
> When I run the ASPage in Internet Explorer - it runs OK
> (and actually Opens the Database)
>
>
> I have tried the "Jet" provider - same results
>
> I have Installed the latest MDAC (2.8)
>
> Why does it work in the ASP but not in the VBS
>
> (It works on other servers - but not this new one)
>
> THE SERVER IS
> Operating System Microsoft Windows Server 2003, Standard Edition
> OS Service Pack Service Pack 2
> Internet Explorer 7.0.5730.11
> DirectX 4.09.00.0904 (DirectX 9.0c)
>
>
> Thank you
> Pete (Northolt UK)
>
>
>
>
>

Bob
Mon Mar 17 14:16:27 CDT 2008

Richard Mueller [MVP] wrote:
> The connection string I use for MS Access databases is similar to (in
> VBScript):
>
> strConnect = "DRIVER=Microsoft Access Driver (*.mdb);" _
> & "FIL=MS Access;DriverId=25;" _
> & "DefaultDir=" & databaseRoot & "data;" _
> & "DBQ=" & databaseRoot & "data\listShares.mdb;"
>
> Notice that DefaultDir is the folder where the mdb file resides. I
> don't know if that is necessary.

It's not.

> The FIL and DriverID parameters are
> probably important.

Very true. In fact, the connection string that should be used is simply:

strConnect = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & databaseRoot & "data\listShares.mdb;"
If available, the native provider for whatever database is involved should
be used instead of going through the deprecated ODBC provider.

However, even this will likely fail for the OP (in fact, I'm pretty sure he
said it did fail):
his error message indicates the Jet components are not installed on the
machine where his connection attempts are failing
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

p
Mon Mar 17 16:17:20 CDT 2008

Folks,

Thank you for your wise words so far.



I looked at http://support.microsoft.com/kb/239114/
(How to determine the current release level of Jet 4.0)

I have:
4.0.9505.0 - Windows Server 2003 SP2

Looks like the latest to me.

Will dig out the .VBS and .ASP for the Jet 4 Provider and post them.

Please remember that I did say in the original post that I had tried
the "Jet" and got the same error.


I have got several dozen VBS files (some with Jet) - they all worked on
the previous server that I am trying to move off !!


I still have the problem of getting my mind around the fact that ASP works and
VBS does not.

I am in your hands gentlemen !!! <grin>

Pete (Northolt UK)



"Bob Barrows [MVP]" wrote:

> p byers wrote:
> > Hi
> > I have a .VBS file - contents below:
> > =====================================================================
> >
> > dataBaseRoot = "d:\Servers\byers\data\mmailing\"
> >
> > DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> > dataBaseRoot & "data\listShares.mdb"
> > set ConLS = CreateObject("ADODB.Connection")
> > ConLS.Open DBConLS
> >
> > =====================================================================
> >
> > When I double click on it, the error shown below is generated.
> >
> > ---------------------------
> > Windows Script Host
> > ---------------------------
> > Script: D:\Servers\Byers\wwwroot\mmailing\connectionTest.vbs
> > Line: 7
> > Char: 1
> > Error: Provider is not specified and there is no designated default
> > provider.
> > Code: 800A0EA9
> > Source: ADODB.Connection
> >
> > ---------------------------
> > OK
> > ---------------------------
> >
> >
> >
> >
> > I have a Classic ASP file - contents below
> >
> > =====================================================================
> > dataBaseRoot = "d:\Servers\byers\data\mmailing\"
> >
> > DBConLS = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
> > dataBaseRoot & "data\listShares.mdb"
> > set ConLS = Server.CreateObject("ADODB.Connection")
> > ConLS.Open DBConLS
> >
> >
> > =====================================================================
> >
> > When I run the ASPage in Internet Explorer - it runs OK
> > (and actually Opens the Database)
> >
>
> A couple versions of MDAC ago, MS separated out the Jet components into a
> separate download (their first step towards deprecating the Jet engine
> before they realized that they would not be able to). You need to go to the
> MSDN site and search for the Jet components download.
>
> >
> > I have tried the "Jet" provider
> >
> ... which you should be using regardless. Always choose a native provider
> for the database you aare using rather than going through the ODBC provider
>
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"

Bob
Mon Mar 17 16:43:19 CDT 2008

p byers wrote:

> Will dig out the .VBS and .ASP for the Jet 4 Provider and post them.

Huh?

> I looked at http://support.microsoft.com/kb/239114/
> (How to determine the current release level of Jet 4.0)
>

No, you did not use the right keywords when you searched: "jet components
download"

The second link when I used those keywords in google led to:
http://support.microsoft.com/default.aspx?kbid=239114#7

And this is the link for you to download the latest Jet service pack:
http://download.microsoft.com/download/a/a/c/aacdba68-214d-484c-b8ac-164fe7261668/windowsserver2003-kb829558-x86-enu.exe

Install it on the machine where you are having the symptoms (we are talking
about two different machines aren't we?) and see if it solves your problem.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

p
Tue Mar 18 01:41:54 CDT 2008



"Bob Barrows [MVP]" wrote:

>
>
> And this is the link for you to download the latest Jet service pack:
> http://download.microsoft.com/download/a/a/c/aacdba68-214d-484c-b8ac-164fe7261668/windowsserver2003-kb829558-x86-enu.exe
>
> Install it on the machine where you are having the symptoms (we are talking
> about two different machines aren't we?) and see if it solves your problem.

Thanks Bob for this link.

Downloaded it

When I tried to install it,

Message "This KB829558 is for a different hardware platform"

The new server is 64-bit

Have hunted in MS site and cannot find the equivalent download for 64-bit.

So sorry - should have said that it was 64-bit on my first post for this subject.

Pete (Northolt UK)

>
>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"

Bob
Tue Mar 18 04:39:47 CDT 2008

p byers wrote:
> "Bob Barrows [MVP]" wrote:
>
>>
>>
>> And this is the link for you to download the latest Jet service pack:
>> http://download.microsoft.com/download/a/a/c/aacdba68-214d-484c-b8ac-164fe7261668/windowsserver2003-kb829558-x86-enu.exe
>>
>> Install it on the machine where you are having the symptoms (we are
>> talking
>> about two different machines aren't we?) and see if it solves your
>> problem.
>
> Thanks Bob for this link.
>
> Downloaded it
>
> When I tried to install it,
>
> Message "This KB829558 is for a different hardware platform"
>
> The new server is 64-bit
>
> Have hunted in MS site and cannot find the equivalent download for
> 64-bit.
>
> So sorry - should have said that it was 64-bit on my first post for
> this subject.
>

You're right, that would have saved much time. Read and weep:
http://www.google.com/search?sourceid=ie7&rls=com.microsoft:en-US&ie=utf8&oe=utf8&q=64-bit+Jet+provider

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

p
Tue Mar 18 09:52:18 CDT 2008



"Bob Barrows [MVP]" wrote:

> p byers wrote:
> > "Bob Barrows [MVP]" wrote:
> >
>
>
> >You're right, that would have saved much time. Read and weep:
> http://www.google.com/search?sourceid=ie7&rls=com.microsoft:en-US&ie=utf8&oe=utf8&q=64-bit+Jet+provider
>

Looks like Im in for trouble when I migrate the ASPages that use the Jet Provider !!

BUT

When I run my VBS files using WSCRIPT.EXE from "sysWOW64" they work so whooppee !!

Apologies for leading you around such a circuitous route - and thank you for your advice and pointers.

Pete (Northolt UK)


>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"

Bob
Tue Mar 18 10:06:14 CDT 2008

p byers wrote:
> "Bob Barrows [MVP]" wrote:
>
>> p byers wrote:
>>> "Bob Barrows [MVP]" wrote:
>>>
>>
>>
>>> You're right, that would have saved much time. Read and weep:
>>> http://www.google.com/search?sourceid=ie7&rls=com.microsoft:en-US&ie=utf8&oe=utf8&q=64-bit+Jet+provider
>>
>
> Looks like Im in for trouble when I migrate the ASPages that use the
> Jet Provider !!

Actually no: at least one of the links in that google search talked about
setting IIS to 32-bit mode, which would enable it to use the 32-bit jet
provider.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"