Re: problems w/ fn_trace_gettable

From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 09/24/04 

Date: Fri, 24 Sep 2004 18:10:04 -0400

Is E: a mapped drive by any chance? If so try using a UNC instead. 

-- 
Andrew J. Kelly  SQL MVP
"bzqpv4" <anonymous@discussions.microsoft.com> wrote in message
news:1c1701c4a27f$6c49aad0$a301280a@phx.gbl...
> The line giving the error is:
>
> SELECT * INTO SQL22_STAGE_TABLE FROM ::fn_trace_gettable
> ('E:\SQLTrace\FDYSQL22\TRACE.TRC',default)
>
> The trace files are located on the server running the SQL
> command.  I am able to open the trace files w/ Profiler
> and they seem fine.
>
> >-----Original Message-----
> >Can you show us the exact command you are using? Where
> are the trace files?
> >On the SQL Server or on a network location?
> >-- 
> >Vyas, MVP (SQL Server)
> >SQL Server Articles and Code Samples @
> http://vyaskn.tripod.com/
> >
> >
> >"bzqpv4" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:27ba01c4a27c$68d88040$a401280a@phx.gbl...
> >> I receive the following error when running
> >> fn_trace_gettable using a perfectly fine trace file as
> >> the @filename argument:
> >>
> >> File '' either does not exist or is not a recognizable
> >> trace file. Or there was an error opening the file.
> >> [SQLSTATE 42000] (Error 567).  The step failed.
> >>
> >> I've used the advice in KB #'s 273972 and 270599, and I
> >> still haven't been able to run the fn_trace_gettable
> >> function without receiving the error.  The trace files
> >> are in the location specified in the argument, when I
> >> open them with profiler everything seems fine.
> >>
> >> Anybody run into this?  Any help provided would be
> >> great.  Thanks.
> >
> >
> >.
> >

Relevant Pages
Quantcast