"Mike Barnett" <MikeBarnett@discussions.microsoft.com> wrote in message
news:4D940251-F19A-45F2-9887-3E34AF824158@microsoft.com...
>I have an application I've been running for over two years on three
>different
> Windows 2000 Servers, but it fails on Windows 2003 Server (SP1, standard,
> 32-bit).
>
> The reason the app fails is that IIS on the Win 2003 Server inserts a
> forward slash in front of the file name in the 'target' column of the
> Inetlog
> table to which I'm loggig FTP activity. This does not happen with the
> older
> W2K Server systems.
>
> For example, the entry in the 'target' column of Inetlog on the 2003
> server
> is "/CASE_20060415062506.TXT", whereas on the 2000 Server, it's
> "CASE_20060415062506.TXT". The trigger on the 'target' column is looking
> for
> the name "CASE_<date-time stamp>.TXT", of course.
>
> I tried "lcd"ing to the local directory where the source file lives to see
> if that would make a difference, but it doesn't. There is nothing in any
> of
> my scripts which would affect this, and I can't find anything else related
> to
> IIS logging which might explain it.
>
> Has anyone else seen this anomaly?
> --
> OUM

"Mike Barnett" <MikeBarnett@discussions.microsoft.com> wrote in message
news:25AF9F38-3264-40D1-BA47-E5A81BADD72A@microsoft.com...
> OK, I give up. I searched TechNet and even the W3C standards for logging,
> but
> can find no clue as to why MS changed the format of the 'target' field to
> include a leading slash in front of the file name. BC is right, the only
> thing I can do is change the trigger filter to include the slash, which I
> did, and now the app runs, but I'm still frustrated that MS has once
> again,
> without explanation, made a change to a product which causes existing code
> to
> crash.
> --
> OUM
>
>
> "Bernard Cheah [MVP]" wrote:
>
>> I don't have ODBC logging to test now. but if IIS 6 logging detail
>> changed
>> from 5, I guessed you need to change your app to fit it.
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.iis-resources.com/
>> http://www.iiswebcastseries.com/
>> http://msmvps.com/blogs/bernard/
>>
>>
>> "Mike Barnett" <MikeBarnett@discussions.microsoft.com> wrote in message
>> news:4D940251-F19A-45F2-9887-3E34AF824158@microsoft.com...
>> >I have an application I've been running for over two years on three
>> >different
>> > Windows 2000 Servers, but it fails on Windows 2003 Server (SP1,
>> > standard,
>> > 32-bit).
>> >
>> > The reason the app fails is that IIS on the Win 2003 Server inserts a
>> > forward slash in front of the file name in the 'target' column of the
>> > Inetlog
>> > table to which I'm loggig FTP activity. This does not happen with the
>> > older
>> > W2K Server systems.
>> >
>> > For example, the entry in the 'target' column of Inetlog on the 2003
>> > server
>> > is "/CASE_20060415062506.TXT", whereas on the 2000 Server, it's
>> > "CASE_20060415062506.TXT". The trigger on the 'target' column is
>> > looking
>> > for
>> > the name "CASE_<date-time stamp>.TXT", of course.
>> >
>> > I tried "lcd"ing to the local directory where the source file lives to
>> > see
>> > if that would make a difference, but it doesn't. There is nothing in
>> > any
>> > of
>> > my scripts which would affect this, and I can't find anything else
>> > related
>> > to
>> > IIS logging which might explain it.
>> >
>> > Has anyone else seen this anomaly?
>> > --
>> > OUM
>>
>>
>>