Re: ISA2004 - logging to msaccess database via odbc system dsn
- From: "OJ" <oj@xxxxxxxxxxxx>
- Date: Wed, 1 Jun 2005 14:26:46 +0100
OK thanks for your replies - i do appreciate the feedback.
The reason we use access is that we have a few access gurus here - what they
don't know about access really isn't worth knowing. They have written an
application that does all of the reporting from the database.
I'll keep plugging away with it for a while - at the moment, we are logging
to text files and then importing that into access.
If all else fails then we'll look at MSDE
many thanks again
"Phillip Windell" <@.> wrote in message
news:Orsl2wqZFHA.2756@xxxxxxxxxxxxxxxxxxxxxxx
> Then it is usually an NTFS permissions issue against the MDB file. There
is
> also a difference between a User DSN and a System DSN,...I don't remember
> which ISA uses. Personally I consider logging to an MDB file to be so
> undependable that I stay as far away from it as I can get, so I don't have
> much "live" experience with it.
>
> If you don't have an SQL Server you could use MSDE (its free) and log it
to
> that. If you get the older one based on SQL7 it comes with a management
> tools, while the newer ones don't and you have to invent your own.
>
> Using a Jet-based database file in a web application is the only place I
> have found that it is dependable and that is only when using a DSN-Less
(no
> DSN) connection.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "OJ" <oj@xxxxxxxxxxxx> wrote in message
> news:%23fBcn4nZFHA.3320@xxxxxxxxxxxxxxxxxxxxxxx
> > Thanks for the reply, but the file is definatly not in use by any other
> > process. The error occurs even after a reboot and I have checked that
> there
> > are no LDB files meaning that the file is in use.
> >
> > any other ideas?
> >
> > OJ
> > thanks
> > "Phillip Windell" <@.> wrote in message
> > news:ewMQZ1fZFHA.3184@xxxxxxxxxxxxxxxxxxxxxxx
> > > The error means that the MDB file is already opened by something else.
A
> > > file can only be opened and "in use" by one process at a time.
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > > "OJ" <oj@xxxxxxxxxxxx> wrote in message
> > > news:Oa%23NipfZFHA.3288@xxxxxxxxxxxxxxxxxxxxxxx
> > > > Dear All,
> > > > Following an upgrade from ISA2000 i have an issue with logging to an
> MS
> > > > Access database.
> > > > This worked in ISA2000 and the system DSN has not changed. We have
> > > changed
> > > > the field definitions so that they match up, but everytime i specify
> the
> > > > logging options to log to an SQL database, specify the correct DSN
and
> > > table
> > > > name, the firewall service will not start. We get a ODBC error (
> > > > The ISA Server Web filter was unable to open ODBC Data Source
> ProxyLog,
> > > > Table: tblProxyLogs, under User Name []. The ODBC Error description
> is:
> > > > [State=S1000][Error=-1024][Microsoft][ODBC Microsoft Access Driver]
> > Could
> > > > not use '(unknown)'; file already in use)
> > > >
> > > > Can anyone shed any light on this - i do not want to log to a SQL
> > > database,
> > > > but Access is ODBC compliant and should work.
> > > >
> > > >
> > > >
> > > > Many thanks
> > > >
> > > >
> > > >
> > > > OJ
> > > >
> > > >
> > >
> > >
> >
> >
>
>
.
- References:
- Prev by Date: Re: ISA2004 SP1 - Authenication & Streaming
- Next by Date: Re: ISA 2000 and Frontpage publishing
- Previous by thread: Re: ISA2004 - logging to msaccess database via odbc system dsn
- Next by thread: ISA 2004: Denied connection due to tcp high ports..
- Index(es):
Relevant Pages
|
