This site worked ok on Win98SE using PWS with this connection string:



Set objCon =3D Server.CreateObject("ADODB.Connection")

objCon.Open "DSN=3Dmydb"



On Win2k using IIS 5.0 with the same db and webpages, I get these 

behaviors:



Problem A    (this error is intermittent)

Error Type:

Provider (0x80004005)

Unspecified error

/mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

Browser Type:

Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)



Problem B  (this error always occurs if I have the Access db open):

Error Type:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)

[Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; 

file already in use.

/mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

Browser Type:

Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)



Any advice?



Thanks in advance,



Mike

Did you create the DSN in the Win2k machine?



Did you assign correct NTFS permissions for the IUSR_<machinename> account

to the actual .mdb file? Also to the directory that the .mdb file is in (to

create and destroy the .ldb lockfile)?



Cheers

Ken





~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

----- Original Message -----

From: "Mike Goldman" <mg188@h...>

To: "ASP Database Setup" <asp_database_setup@p...>

Sent: Monday, June 11, 2001 7:38 AM

Subject: [asp_database_setup] need help to migrate to win2k





:

: This site worked ok on Win98SE using PWS with this connection string:

:

: Set objCon =3D Server.CreateObject("ADODB.Connection")

: objCon.Open "DSN=3Dmydb"

:

: On Win2k using IIS 5.0 with the same db and webpages, I get these 

: behaviors:

:

: Problem A    (this error is intermittent)

: Error Type:

: Provider (0x80004005)

: Unspecified error

: /mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

: Browser Type:

: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

:

: Problem B  (this error always occurs if I have the Access db open):

: Error Type:

: Microsoft OLE DB Provider for ODBC Drivers (0x80004005)

: [Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; 

: file already in use.

: /mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

: Browser Type:

: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

:

: Any advice?

:

: Thanks in advance,

:

: Mike

:

: ---

: STAY UP TO DATE ON ASP.NET, C#, VB.NET, SQL and XML

: Developersdex indexes over 100 of the top ASP, SQL, VB

: and XML sites bringing in more than 5,000 new resources

: every day.  They even integrate all the top .NET

: newsgroups so you can search/post/reply across

: multiple newsgroups within their site.  The next time

: you want to find an answer on ASP, C#, SQL, VB or XML

: think of Devdex!  http://www.developersdex.com/



ken@a...


$subst('Email.Unsub')

The second error is expected when you have the Access dB open. When you open

an access dB with the Access client it locks the dB from anyone else

changing anything. You can not have the Access dB open through the Access

client and still use it on the web.



The first error leads me to thinking of security problems- does the

IUSER_Machinename account have write access to the directory that the MDB is

in? it needs to have it in order to write the lock file.





Hal Levy

StarMedia Network, Inc.

Intranet Development Manager



-----Original Message-----

From: Mike Goldman [mailto:mg188@h...]

Sent: Sunday, June 10, 2001 5:39 PM

To: ASP Database Setup

Subject: [asp_database_setup] need help to migrate to win2k







This site worked ok on Win98SE using PWS with this connection string:



Set objCon =3D Server.CreateObject("ADODB.Connection")

objCon.Open "DSN=3Dmydb"



On Win2k using IIS 5.0 with the same db and webpages, I get these 

behaviors:



Problem A    (this error is intermittent)

Error Type:

Provider (0x80004005)

Unspecified error

/mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

Browser Type:

Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)



Problem B  (this error always occurs if I have the Access db open):

Error Type:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)

[Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; 

file already in use.

/mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

Browser Type:

Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)



Any advice?



Thanks in advance,



Mike

Thanks Hal, and Ken Schaefer also,



win2k crashed (corrupt files) again, so I'm back on win98 for the time

being.  I'll try setting the iuser_machinename access when I get back to

win2k.



Funny, but in win98, I can access the db (while the db is open) from ASP

pages on PWS.  So this is a win2k thing?



By the way, I've had numerous problems with corrupt files using win2k.  I've

used win2k drivers throughout but still it's flaky.  My plan now is to dual

boot with win98 on c: and win2k on d:   - both under FAT32 this time around.

I'm hoping this will give me a stabler environment.  Any comments?



Mike

----- Original Message -----

From: Hal Levy <hal.levy@s...>

To: ASP Database Setup <asp_database_setup@p...>

Sent: Monday, June 11, 2001 6:05 AM

Subject: [asp_database_setup] RE: need help to migrate to win2k





> The second error is expected when you have the Access dB open. When you

open

> an access dB with the Access client it locks the dB from anyone else

> changing anything. You can not have the Access dB open through the Access

> client and still use it on the web.

>

> The first error leads me to thinking of security problems- does the

> IUSER_Machinename account have write access to the directory that the MDB

is

> in? it needs to have it in order to write the lock file.

>

>

> Hal Levy

> StarMedia Network, Inc.

> Intranet Development Manager

>

> -----Original Message-----

> From: Mike Goldman [mailto:mg188@h...]

> Sent: Sunday, June 10, 2001 5:39 PM

> To: ASP Database Setup

> Subject: [asp_database_setup] need help to migrate to win2k

>

>

>

> This site worked ok on Win98SE using PWS with this connection string:

>

> Set objCon =3D Server.CreateObject("ADODB.Connection")

> objCon.Open "DSN=3Dmydb"

>

> On Win2k using IIS 5.0 with the same db and webpages, I get these 

> behaviors:

>

> Problem A    (this error is intermittent)

> Error Type:

> Provider (0x80004005)

> Unspecified error

> /mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

> Browser Type:

> Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

>

> Problem B  (this error always occurs if I have the Access db open):

> Error Type:

> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)

> [Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; 

> file already in use.

> /mg53rev1/mypage.asp, line 14    (line 14 is the objcon.open line above)

> Browser Type:

> Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

>

> Any advice?

>

> Thanks in advance,

>

> Mike

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

: From: "Mike Goldman" <mg188@h...>

: Subject: [asp_database_setup] RE: need help to migrate to win2k

:

: win2k crashed (corrupt files) again, so I'm back on win98 for the time

: being.  I'll try setting the iuser_machinename access when I get back to

: win2k.

:

: Funny, but in win98, I can access the db (while the db is open) from ASP

: pages on PWS.  So this is a win2k thing?



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



You may not be opening the database in exclusive mode. Just opening the

database by itself in later versions of Access opens the database in shared

mode. That said, certain actions, eg opening a table in design mode,

generate exclusive locks (eg try opening the database in Access, then

opening a table in design mode. Then try to insert a record using ASP - I

bet you it will fail).



Additionally, when you use NTFS (with WinNT or Windows2000), you introduce

the concept of file/directory permissions - these don't exist when using FAT

or FAT32. When using NTFS, each user needs specific permission to be able to

perform certain actions (read, write, execute, delete etc) on each and every

file. The website uses the IUSR_<machinename> account to read files from the

hard disk to execute them. This account needs sufficient privaleges to open

the Access database, make changes to it, and to create and destory the

Access .ldb lock file. If it doesn't, then either it can't open the database

in the first place, or it can't delete the .ldb lockfile (and thus can't

open the database after the first access).



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

: By the way, I've had numerous problems with corrupt files

: using win2k.  I've used win2k drivers throughout but still it's flaky.

: My plan now is to dual boot with win98 on c: and win2k on d:   -

: both under FAT32 this time around. I'm hoping this will give me a

: stabler environment.  Any comments?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



I'm not sure what you mean by "corrupt files" - how do you know these files

are corrupt? Are you installing off original Microsoft media? Does your hard

disk have problems? There's a very good WindowsNT/2k list at:

http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

be prepared to give lots of details up front, since vague descriptions don't

cut it with the very experienced people on that list.



Cheers

Ken

> I'm not sure what you mean by "corrupt files" - how do you know these

files

> are corrupt? Are you installing off original Microsoft media? Does your

hard

> disk have problems? There's a very good WindowsNT/2k list at:

> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

> be prepared to give lots of details up front, since vague descriptions

don't

> cut it with the very experienced people on that list.

>

> Cheers

> Ken

>

I got error message saying such-and-such a file is corrupt.   Yes on

original MS media.  Hard disk recently replaced from Dell - still have

problems.  Starting to wonder if it's other hardware problem(s).  All cable

and card connections are tight - though I realize there could still be bad

connections.  Beyond that I don't know how to troubleshoot hardware.



Thanks for the Sunbelt tip - I just signed up.



Mike