Strange chglog behavior (8.03.404B)

Yahoo Archive
1
Clive,

You were spot on. SCR 47861 is reported to be fixed in .405.

Thanks,

Jim Pratt

--- In vantage@yahoogroups.com, "clive.1972" <clive.1972@...> wrote:
>
> Jim,
>
> I'm pretty certain that .404 (plain 404 plus A and B) had a bug of
> some sort with the change logs that was fixed in 405, you may want
to
> investigate this further.
>
> --- In vantage@yahoogroups.com, "jmpratt7" <james.pratt@> wrote:
> >
> > I recently was doing some forensics on a problem with jobs being
> issued
> > with the wrong rev of a drawing and discovered a case where
changes
> to
> > the partrev.drawnum field were not being logged in the chglog
file
> by
> > one user when the same change was being logged by me.
> >
> > Has anybody experienced this kind of behavior with chglog? We
are
> > hanging our hats on this chglog system to provide auditable data
> for
> > SOX auditing. If there is a defect in the system I would sure
like
> to
> > know.
> >
> > Regards,
> >
> > Jim Pratt
> > Ameridrives
> > Vantage since 11/27/06
> > 8.03.404B since 9/12/08
> >
>
2
I recently was doing some forensics on a problem with jobs being issued
with the wrong rev of a drawing and discovered a case where changes to
the partrev.drawnum field were not being logged in the chglog file by
one user when the same change was being logged by me.

Has anybody experienced this kind of behavior with chglog? We are
hanging our hats on this chglog system to provide auditable data for
SOX auditing. If there is a defect in the system I would sure like to
know.

Regards,

Jim Pratt
Ameridrives
Vantage since 11/27/06
8.03.404B since 9/12/08
3
Any errors logged in \mfgsys803\server\logs\mfgsys803.server.log file?


--- In vantage@yahoogroups.com, "jmpratt7" <james.pratt@...> wrote:
>
> I recently was doing some forensics on a problem with jobs being
issued
> with the wrong rev of a drawing and discovered a case where changes
to
> the partrev.drawnum field were not being logged in the chglog file
by
> one user when the same change was being logged by me.
>
> Has anybody experienced this kind of behavior with chglog? We are
> hanging our hats on this chglog system to provide auditable data
for
> SOX auditing. If there is a defect in the system I would sure like
to
> know.
>
> Regards,
>
> Jim Pratt
> Ameridrives
> Vantage since 11/27/06
> 8.03.404B since 9/12/08
>
4
Have you inadvertantly set up the other user's user role in a way that prohibits them from writing to the changelog table?

(I've never seen such behavior. We use change logs every where also.)

Rob

--- On Tue, 12/9/08, jmpratt7 <james.pratt@...> wrote:

From: jmpratt7 <james.pratt@...>
Subject: [Vantage] Strange chglog behavior (8.03.404B)
To: vantage@yahoogroups.com
Date: Tuesday, December 9, 2008, 10:56 AM






I recently was doing some forensics on a problem with jobs being issued
with the wrong rev of a drawing and discovered a case where changes to
the partrev.drawnum field were not being logged in the chglog file by
one user when the same change was being logged by me.

Has anybody experienced this kind of behavior with chglog? We are
hanging our hats on this chglog system to provide auditable data for
SOX auditing. If there is a defect in the system I would sure like to
know.

Regards,

Jim Pratt
Ameridrives
Vantage since 11/27/06
8.03.404B since 9/12/08
5
Checking the log produced no relevant error messages.

--- In vantage@yahoogroups.com, "bw2868bond" <bwalker@...> wrote:
>
> Any errors logged in \mfgsys803\server\logs\mfgsys803.server.log
file?
>
>
> --- In vantage@yahoogroups.com, "jmpratt7" <james.pratt@> wrote:
> >
> > I recently was doing some forensics on a problem with jobs being
> issued
> > with the wrong rev of a drawing and discovered a case where
changes
> to
> > the partrev.drawnum field were not being logged in the chglog
file
> by
> > one user when the same change was being logged by me.
> >
> > Has anybody experienced this kind of behavior with chglog? We
are
> > hanging our hats on this chglog system to provide auditable data
> for
> > SOX auditing. If there is a defect in the system I would sure
like
> to
> > know.
> >
> > Regards,
> >
> > Jim Pratt
> > Ameridrives
> > Vantage since 11/27/06
> > 8.03.404B since 9/12/08
> >
>
6
Rob,

I don't know how I could set him up differently. The only feature he
has that I don't is that single sign on is selected. Could it be
that there's an issue with single sign on and chglog?

Jim Pratt

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>
> Have you inadvertantly set up the other user's user role in a way
that prohibits them from writing to the changelog table?
>
> (I've never seen such behavior. We use change logs every where
also.)
>
> Rob
>
> --- On Tue, 12/9/08, jmpratt7 <james.pratt@...> wrote:
>
> From: jmpratt7 <james.pratt@...>
> Subject: [Vantage] Strange chglog behavior (8.03.404B)
> To: vantage@yahoogroups.com
> Date: Tuesday, December 9, 2008, 10:56 AM
>
>
>
>
>
>
> I recently was doing some forensics on a problem with jobs being
issued
> with the wrong rev of a drawing and discovered a case where changes
to
> the partrev.drawnum field were not being logged in the chglog file
by
> one user when the same change was being logged by me.
>
> Has anybody experienced this kind of behavior with chglog? We are
> hanging our hats on this chglog system to provide auditable data
for
> SOX auditing. If there is a defect in the system I would sure like
to
> know.
>
> Regards,
>
> Jim Pratt
> Ameridrives
> Vantage since 11/27/06
> 8.03.404B since 9/12/08
>
7
Jim,

I'm pretty certain that .404 (plain 404 plus A and B) had a bug of
some sort with the change logs that was fixed in 405, you may want to
investigate this further.

--- In vantage@yahoogroups.com, "jmpratt7" <james.pratt@...> wrote:
>
> I recently was doing some forensics on a problem with jobs being
issued
> with the wrong rev of a drawing and discovered a case where changes
to
> the partrev.drawnum field were not being logged in the chglog file
by
> one user when the same change was being logged by me.
>
> Has anybody experienced this kind of behavior with chglog? We are
> hanging our hats on this chglog system to provide auditable data
for
> SOX auditing. If there is a defect in the system I would sure like
to
> know.
>
> Regards,
>
> Jim Pratt
> Ameridrives
> Vantage since 11/27/06
> 8.03.404B since 9/12/08
>