Thank you! Here's what we found:
we use SQL jobs for our e-mail alerts, because we have more flexibility that way (we are not 4GL programmersÂ…), and they were causing the problem. Just for the record- if you use SQL jobs for e-mail alerts, make sure your e-mail is configured BEFORE you create the jobs, or it produces a 4GL stop event.
Thanks for the assist!
- leAnn
we use SQL jobs for our e-mail alerts, because we have more flexibility that way (we are not 4GL programmersÂ…), and they were causing the problem. Just for the record- if you use SQL jobs for e-mail alerts, make sure your e-mail is configured BEFORE you create the jobs, or it produces a 4GL stop event.
Thanks for the assist!
- leAnn
--- In vantage@yahoogroups.com, Kevin Simon <ksimon8fw@...> wrote:
>
> LeAnn,
>
> Look at the app server log, that should give you more detail about the
> error.
>
> Kevin
>
> On Mon, Jul 5, 2010 at 2:46 PM, leann_37 <lmarruffo@...> wrote:
>
> >
> >
> > All,
> > We were processing fine, shipping, everything, and WHAM- 4GL stop error
> > when we mark the pack as shipped, after we click "OK" on the "has been
> > printed" notice. We get this on the base form.
> > have you seen this before? How do we fix it?
> > Any assistance would be appreciated!
> > Thanks!
> > - leAnn
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>