|
|
You're in the
iis security
group:Problems with MS Access data source
iis security:
http://www.aspfaq.com/show.asp?id=3D2009
--=20 Tom Kaminski IIS MVP http://www.iistoolshed.com/ - tools, scripts, and utilities for running = IIS http://mvp.support.microsoft.com/ http://www.microsoft.com/windowsserver2003/community/centers/iis/ =20 [quoted text, click to view] "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message = An ms access database is set up as a system data source and used in =news:eOVGCrfSDHA.3088@TK2MSFTNGP10.phx.gbl... asp application. When second user tries to open asp page which connects = to the database and fetches data, the following error is raised: Microsoft OLE DB Provider for ODBC Drivers error '80004005'=20 [Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; = file already in use.=20 Server is IIS 6.0, error occurs both in worker process and IIS 5.0 = isolation mode. The same configuration works fine with no errors on IIS = 5.0 server. --=20 Dmitry Korolyov, d__k@nosmapformorons.mail.ru
I'm not a mind reader, you didn't say what investigation you did.
[quoted text, click to view] "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message = Tom, this is very helpful indeed, but don't you think that I've posted =news:OSNekagSDHA.1724@TK2MSFTNGP10.phx.gbl... the original message without investigating the problem first? Note also = that exactly the same configuration (NTFS permissions, system data = source configuration, authentication settings on IIS) works just fine on = IIS 5.0. Access database is located physically on the same server in = both cases. Yes, I do agree that "something" is locking up the file, = however I suspect that this "something" is IIS itself or one of its = working processes. Note the behavior: when you first time open the page, = it works, whe you open it from another computer on in different browser = window (i.e. in another IIS session), it fails with the error message = quoted in the first posting. [quoted text, click to view] "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message = http://www.aspfaq.com/show.asp?id=3D2009news:beu7hv$9j410@kcweb01.netnews.att.com... --=20 Tom Kaminski IIS MVP http://www.iistoolshed.com/ - tools, scripts, and utilities for = running IIS http://mvp.support.microsoft.com/ http://www.microsoft.com/windowsserver2003/community/centers/iis/ =20 [quoted text, click to view] "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message = An ms access database is set up as a system data source and used =news:eOVGCrfSDHA.3088@TK2MSFTNGP10.phx.gbl... in asp application. When second user tries to open asp page which = connects to the database and fetches data, the following error is = raised: Microsoft OLE DB Provider for ODBC Drivers error '80004005'=20 [Microsoft][ODBC Microsoft Access Driver] Could not use = '(unknown)'; file already in use.=20 Server is IIS 6.0, error occurs both in worker process and IIS 5.0 = isolation mode. The same configuration works fine with no errors on IIS = 5.0 server. --=20 Dmitry Korolyov, d__k@nosmapformorons.mail.ru
An ms access database is set up as a system data source and used in asp =
application. When second user tries to open asp page which connects to = the database and fetches data, the following error is raised: =20 Microsoft OLE DB Provider for ODBC Drivers error '80004005'=20 [Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; = file already in use.=20 Server is IIS 6.0, error occurs both in worker process and IIS 5.0 = isolation mode. The same configuration works fine with no errors on IIS = 5.0 server. --=20 Dmitry Korolyov, d__k@nosmapformorons.mail.ru
Tom, this is very helpful indeed, but don't you think that I've posted =
the original message without investigating the problem first? Note also = that exactly the same configuration (NTFS permissions, system data = source configuration, authentication settings on IIS) works just fine on = IIS 5.0. Access database is located physically on the same server in = both cases. Yes, I do agree that "something" is locking up the file, = however I suspect that this "something" is IIS itself or one of its = working processes. Note the behavior: when you first time open the page, = it works, whe you open it from another computer on in different browser = window (i.e. in another IIS session), it fails with the error message = quoted in the first posting. [quoted text, click to view] "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message = http://www.aspfaq.com/show.asp?id=3D2009news:beu7hv$9j410@kcweb01.netnews.att.com... --=20 Tom Kaminski IIS MVP http://www.iistoolshed.com/ - tools, scripts, and utilities for = running IIS http://mvp.support.microsoft.com/ http://www.microsoft.com/windowsserver2003/community/centers/iis/ =20 [quoted text, click to view] "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message = An ms access database is set up as a system data source and used in =news:eOVGCrfSDHA.3088@TK2MSFTNGP10.phx.gbl... asp application. When second user tries to open asp page which connects = to the database and fetches data, the following error is raised: Microsoft OLE DB Provider for ODBC Drivers error '80004005'=20 [Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; = file already in use.=20 Server is IIS 6.0, error occurs both in worker process and IIS 5.0 = isolation mode. The same configuration works fine with no errors on IIS = 5.0 server. --=20 Dmitry Korolyov, d__k@nosmapformorons.mail.ru
But you didn't try to answer the original question too. Well nevermind =
then. [quoted text, click to view] "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message = I'm not a mind reader, you didn't say what investigation you did.news:beua7n$9j411@kcweb01.netnews.att.com... [quoted text, click to view] "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message = Tom, this is very helpful indeed, but don't you think that I've =news:OSNekagSDHA.1724@TK2MSFTNGP10.phx.gbl... posted the original message without investigating the problem first? = Note also that exactly the same configuration (NTFS permissions, system = data source configuration, authentication settings on IIS) works just = fine on IIS 5.0. Access database is located physically on the same = server in both cases. Yes, I do agree that "something" is locking up the = file, however I suspect that this "something" is IIS itself or one of = its working processes. Note the behavior: when you first time open the = page, it works, whe you open it from another computer on in different = browser window (i.e. in another IIS session), it fails with the error = message quoted in the first posting. "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in = message news:beu7hv$9j410@kcweb01.netnews.att.com... http://www.aspfaq.com/show.asp?id=3D2009 --=20 Tom Kaminski IIS MVP http://www.iistoolshed.com/ - tools, scripts, and utilities for = running IIS http://mvp.support.microsoft.com/ http://www.microsoft.com/windowsserver2003/community/centers/iis/ =20 "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in = message news:eOVGCrfSDHA.3088@TK2MSFTNGP10.phx.gbl... An ms access database is set up as a system data source and used = in asp application. When second user tries to open asp page which = connects to the database and fetches data, the following error is = raised: Microsoft OLE DB Provider for ODBC Drivers error '80004005'=20 [Microsoft][ODBC Microsoft Access Driver] Could not use = '(unknown)'; file already in use.=20 Server is IIS 6.0, error occurs both in worker process and IIS = 5.0 isolation mode. The same configuration works fine with no errors on = IIS 5.0 server. --=20 Dmitry Korolyov, d__k@nosmapformorons.mail.ru
Dmitry, did you look at the reference supplied? Have you checked
permissions, did you check the LDB lock file, have you configured authorization correctly? Remember that just because it worked in IIS5, on a W2K system, has no bearing on whether you've correctly applied permissions on an IIS6 system, which is Server 2003 and comes with permissions locked down. 80004005 errors are almost always permission related. Though at your request I'm also perfectly willing to 'never mind'. Jeff On Mon, 14 Jul 2003 17:58:53 +0400, "Dmitry Korolyov" [quoted text, click to view] <d__k@nospamformorons.mail.ru> wrote:
>But you didn't try to answer the original question too. Well nevermind then. > "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message news:beua7n$9j411@kcweb01.netnews.att.com... > I'm not a mind reader, you didn't say what investigation you did. > > > "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message news:OSNekagSDHA.1724@TK2MSFTNGP10.phx.gbl... > Tom, this is very helpful indeed, but don't you think that I've posted the original message without investigating the problem first? Note also that exactly the same configuration (NTFS permissions, system data source configuration, authentication settings on IIS) works just fine on IIS 5.0. Access database is located physically on the same server in both cases. Yes, I do agree that "something" is locking up the file, however I suspect that this "something" is IIS itself or one of its working processes. Note the behavior: when you first time open the page, it works, whe you open it from another computer on in different browser window (i.e. in another IIS session), it fails with the error message quoted in the first posting. > "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message news:beu7hv$9j410@kcweb01.netnews.att.com... > http://www.aspfaq.com/show.asp?id=2009 > > -- > Tom Kaminski IIS MVP > http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS > http://mvp.support.microsoft.com/ > http://www.microsoft.com/windowsserver2003/community/centers/iis/ > > "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message news:eOVGCrfSDHA.3088@TK2MSFTNGP10.phx.gbl... > An ms access database is set up as a system data source and used in asp application. When second user tries to open asp page which connects to the database and fetches data, the following error is raised: > > Microsoft OLE DB Provider for ODBC Drivers error '80004005' > > [Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; file already in use. > > > Server is IIS 6.0, error occurs both in worker process and IIS 5.0 isolation mode. The same configuration works fine with no errors on IIS 5.0 server. > > -- > Dmitry Korolyov, > d__k@nosmapformorons.mail.ru > To e-mail me, remove "nospamformorons".
Yes, I did check everything. File system permissions both for the website
itself and the database (mdb file) are very easy to check and veryfy that they are the same on both systems. System DSNs are configured exactly in the same manner on both systems. This can be easily verified as well. Talking about "Locked down" state of IIS, I see no problem here. Both web servers are configured to user intergated windows authentication and do not allow anynomous connections. There may be other differences, but I do not see how they would affect ODBC connectivity. Web app does not use ISAPI filters or anything. Since my original post we narrowed it down to performing a single select statement, and the problem still exist. In other words, I would not suggest looking into general IIS troubleshooting part - because it does work fine on IIS 5.0. And the reference says nothing about how "locked down" configuration of IIS 6.0 may affect database connectivity - it simply knows nothing about IIS 6.0 existense. -- Dmitry Korolyov d__k@nospamformorons.mail.ru To e-mail me, remove "nospamformorons" from the address. [quoted text, click to view] "Jeff Cochran" <jcochran.nospam@naplesgov.com> wrote in message posted the original message without investigating the problem first? Notenews:3f1a0eb6.1844826229@msnews.microsoft.com... > Dmitry, did you look at the reference supplied? Have you checked > permissions, did you check the LDB lock file, have you configured > authorization correctly? Remember that just because it worked in > IIS5, on a W2K system, has no bearing on whether you've correctly > applied permissions on an IIS6 system, which is Server 2003 and comes > with permissions locked down. > > 80004005 errors are almost always permission related. > > Though at your request I'm also perfectly willing to 'never mind'. > > Jeff > > On Mon, 14 Jul 2003 17:58:53 +0400, "Dmitry Korolyov" > <d__k@nospamformorons.mail.ru> wrote: > > >But you didn't try to answer the original question too. Well nevermind then. > > "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message news:beua7n$9j411@kcweb01.netnews.att.com... > > I'm not a mind reader, you didn't say what investigation you did. > > > > > > "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message news:OSNekagSDHA.1724@TK2MSFTNGP10.phx.gbl... > > Tom, this is very helpful indeed, but don't you think that I've also that exactly the same configuration (NTFS permissions, system data source configuration, authentication settings on IIS) works just fine on IIS 5.0. Access database is located physically on the same server in both cases. Yes, I do agree that "something" is locking up the file, however I suspect that this "something" is IIS itself or one of its working processes. Note the behavior: when you first time open the page, it works, whe you open it from another computer on in different browser window (i.e. in another IIS session), it fails with the error message quoted in the first posting. [quoted text, click to view] > > "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message in asp application. When second user tries to open asp page which connectsnews:beu7hv$9j410@kcweb01.netnews.att.com... > > http://www.aspfaq.com/show.asp?id=2009 > > > > -- > > Tom Kaminski IIS MVP > > http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS > > http://mvp.support.microsoft.com/ > > http://www.microsoft.com/windowsserver2003/community/centers/iis/ > > > > "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message news:eOVGCrfSDHA.3088@TK2MSFTNGP10.phx.gbl... > > An ms access database is set up as a system data source and used to the database and fetches data, the following error is raised: [quoted text, click to view] > > 5.0 isolation mode. The same configuration works fine with no errors on IIS> > Microsoft OLE DB Provider for ODBC Drivers error '80004005' > > > > [Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; file already in use. > > > > > > Server is IIS 6.0, error occurs both in worker process and IIS 5.0 server. [quoted text, click to view] > > > > -- > > Dmitry Korolyov, > > d__k@nosmapformorons.mail.ru > > To e-mail me, remove "nospamformorons". >
On Tue, 15 Jul 2003 02:25:50 +0400, "Dmitry Korolyov"
[quoted text, click to view] <d__k@nospamformorons.mail.ru> wrote: >Yes, I did check everything. File system permissions both for the website >itself and the database (mdb file) are very easy to check and veryfy that >they are the same on both systems. Same on both systems or correct for Server 2003? [quoted text, click to view] >System DSNs are configured exactly in the same manner on both systems. This >can be easily verified as well. Okay, so you're using ODBC then instead of OLEDB. Does your ODBC work if you use a client such as Access to attach to the database? [quoted text, click to view] >Talking about "Locked down" state of IIS, I see no problem here. Both web >servers are configured to user intergated windows authentication and do not >allow anynomous connections. There may be other differences, but I do not >see how they would affect ODBC connectivity. Web app does not use ISAPI >filters or anything. Since my original post we narrowed it down to >performing a single select statement, and the problem still exist. In other words it works for everything but that SELECT statement? Post the SELECT statement. And do a Response.Write of the SQL statement to see what's actually getting sent. [quoted text, click to view] >In other words, I would not suggest looking into general IIS troubleshooting >part - because it does work fine on IIS 5.0. Again, IIS6 is *not* IIS5. I have an oil filter that worked fine on my Pinto, but doesn't seem to work on my Mazda. Troubleshoot the current setup, not the old one. [quoted text, click to view] >And the reference says nothing >about how "locked down" configuration of IIS 6.0 may affect database >connectivity - it simply knows nothing about IIS 6.0 existense. I'm getting to feel sorry I ever tried to help here. Is your application a .NET app, straight ASP or something else? Have you tried a very basic connection, then the SELECT statement? Have you tried an OLEDB connection instead of the ODBC? The error you posted is almost always a permissions error. With Access, it could be an exclusive lock, such as having Access or VS.NET open on the server, it could be file permissions, it could be Temp file creation, it could be the ODBC key in the registry, it could be Access security or it could be the specific code you use. Make sure you're configuring permissions according to the account the app is running under, which may or may not be the logged in user. Jeff
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |