tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier>
Subject Re: Access dbf files outside context/docbase
Date Fri, 16 Dec 2011 11:03:11 GMT
André Warnier wrote:
> David Kerber wrote:
>> On 12/15/2011 4:47 PM, Pid wrote:
>>> On 15/12/2011 20:56, David kerber wrote:
>>>> I am trying to figure out how to access .dbf files that are on a
>>>> networked drive from my TC 5.5.xx server.  I have no trouble with the
>>>> coding; it all works fine from my Eclipse dev environment.  I believe
>>>> the issue is tomcat's contexts on the production server.  I've seen
>>>> plenty of suggestions for just reading and streaming files from outside
>>>> the docbase, but nothing for accessing them for database purposes.  I'm
>>>> using the Microsoft DBF driver.
>>>> As I said above, it all works fine in my dev environment through
>>>> Eclipse, connection to the dbf files in their real home on the network.
>>>>   However, when I try to do it from my production server, I get the
>>>> following log entries:
>>>> 2011-12-15 14:47:53:  debugValue = 32: In WraDbfJdbc:  Connect params:
>>>> urlPrefix=jdbc:odbc:DRIVER={Microsoft dBase Driver (*.dbf)};DBQ=,
>>>> databaseName = //
>>>> Thu Dec 15 14:47:53 EST 2011:  Exception in class:
>>>> com.wra.websira.WraDbfJdbc, Msg: 'Creating database:
>>>> //', Exception: java.sql.SQLException:
>>>> [Microsoft][ODBC Driver Manager] Data source name not found and no
>>>> default driver specified
>>>> I belive that means it can't get to the UNC name listed as the 
>>>> database.
>>>> Any hints?  I've been googling and reading for a couple of hours now,
>>>> and haven't come up with anything.
>>> Obvious first question: file permissions?
>>> p
>> Wide open.  And from previous experience, permissions and file-in-use 
>> errors give different text in the message.
> Are you sure that the driver understands UNC path notation ?
> What if you "map" that path to a "device letter" on the local system, 
> and try to connect using that local path ?
Addendum : but if your are indeed running Tomcat as a Service, then the previous 
explanation from Mark Eggers is more likely to be the problem.
(and my suggestion won't help, because it's still a network drive, and the LocalSystem 
account does not have access to Windows network resources (like network drives and 
printers e.g.)).

You should try starting Tomcat under your own user-id, in a command window, using the 
startup.bat script, and then see if it can connect.
If it can then, then your problem is the LocalSystem account.
If it still can't, then it may be the UNC path notation.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message