For reference, I found out what the problem is.
Tracing is enabled per computer, using the mfgsys.exe.config file. Set the DataTrace value to 0 to disable tracing. I had deployed a number of users with this config, which is where the problem was.
This is one of those silly and frustrating things that I think that Tier 1 support should know about.
Tracing is enabled per computer, using the mfgsys.exe.config file. Set the DataTrace value to 0 to disable tracing. I had deployed a number of users with this config, which is where the problem was.
This is one of those silly and frustrating things that I think that Tier 1 support should know about.
--- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
>
> As a guess: enable customization privs for that MES user, so you can get
> to tracing. And turn them back off later, of course.
>
> Brian.
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of cubcrafters_it
> Sent: Wednesday, February 08, 2012 2:19 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Remote App MES always seems to log a trace and
> other RDP glitchies
>
>
>
>
>
> So that's what the Epicor Tech suggested. I logged in as my user and
> sure enough, tracing was on. I thought it was a per instance thing.
>
> *However*, I logged in with /MESC using one of our MES users, and I
> don't have the right-click option for Tracing at all.
>
> Any ideas there?
>
> As far as the other RDP issues, we run RDP for our second location over
> the VPN. They're on ethernet to the switch over there, but then have to
> traverse the VPN, so there's a speed hit there, but it's not terrible.
>
> Sometimes upon connecting to the RemoteApp they just see a black screen,
> and again I have to go and bump the session.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Brian Roberts" <broberts@> wrote:
> >
> > I see mention of the tracedata file and GB worth of logs... is it
> > possible that tracing was turned on for the MES username and never got
> > turned off? Would explain intermittent conflicts trying to write to
> the
> > same file. To fix: start Epicor with /MESC, right click in the main
> > screen & disable tracing.
> >
> >
> >
> > Brian.
> >
> >
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > Of cubcrafters_it
> > Sent: Friday, February 03, 2012 11:28 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Remote App MES always seems to log a trace and
> other
> > RDP glitchies
> >
> >
> >
> >
> >
> > (9.05.607A Progress 32-bit)
> >
> > So every once in a while when starting MES through our Remote Desktop
> > server, the client sees an Access Denied message to a TraceData.txt
> > file.
> >
> > Often launching the app again will get around it, but I finally looked
> > at the log folder today, and there's over 2 GB of log files in there.
> >
> > Is there a setting I'm missing that will disable tracing all the time?
> >
> > Also, occasionally our remote MES users won't be able to get into MES
> at
> > all, and the app just appears to hang. I've got to go onto the remote
> > server, boot their session, and usually they're okay after that. But
> > it's a little bit of a hassle to have to maintain it that way.
> >
> > Has anyone else had this kind of problem, and how have you resolved
> it?
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>