The cause of your error message is that you have the file open
(probably in Access) and the System Account is trying to read the file.  The
JET engine doesn't allow this.

        Your more significant and potentially more dangerous problem is that
you are using the JDBC-ODBC bridge.  This component is not thread safe and
can't/shouldn't be used in a concurrent threads.  Sun also considers this
component "experimental" and not for production usage.  You can see Java's
BugParade for more information on this.

        Randy


> -----Original Message-----
> From: Sampige, Srinivas [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 19, 2002 8:08 PM
> To: TomcatUser (E-mail)
> Subject: problems connecting to MS Access when Tomca3.2 runs 
> as service
> 
> 
> Hi
> 
>     I am running  Tomcat3.2 on Windows2000. I am facing a 
> problem when I try
> to connect (from a Servlet) to an MS Access database when 
> Tomcat is running
> as an NT service. When I manually run Tomcat from the console the same
> servlet works perfectly. The link
> http://www.apachelabs.org/tomcat-user/200101.mbox/%3COFB012A4B
8.0583C846-ONC
[EMAIL PROTECTED]%3E discusses the problem where the
driver is not getting loaded. But, the error I get is different -

------------------
SQL EXCEPTION OCCURRED CONNECTING TO DB -[Microsoft][ODBC Microsoft Access
Driver] The Microsoft Jet database engine cannot open the file '(unknown)'.
It is already opened exclusively by another user, or you need permission to
view its data.
------------------
 so it seems like the drivers are getting loaded. I am unable to figure out
the problem. Any help would be greately appreciated. I looked at the ODBC
data source that I have created but found nothing that is out of place.

thanks
Srinivas 


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to