We were experiencing some issues a few weeks after go live on .404b.
Users were having problems saving, tasks took forever to complete
(meanwhile locking up other users),reports didn't print right away,
and server logging didn't tell me much. If you are running SQL 2005
and haven't done so already, call tech support and get the SQL Unique
Index Script. Apparently quite a few functionality fixes were
released with the b patch. The SQL settings need to be adjusted to
accomodate this.
Try this:
- Make sure SQL Database running in 2005 mode.
- SQL Unique Index Script had not been run. ==> Ran SQL Index
Script (Get this from Epicor).
- SQL Full Text Catalogs = OK, track changes not enabled
- Mfgsys.pf Settings:
-- Added: -tmpbsize 8 and -ttmarshal 5
-- Added: PRGRS_NATIVE_LOCKWAIT,60000
-- Changed: -Bt 5000
- Progress Explorer Tool Settings:
-- Increased primary appserver from Max of 20 to 25
--- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@...>
wrote:
Users were having problems saving, tasks took forever to complete
(meanwhile locking up other users),reports didn't print right away,
and server logging didn't tell me much. If you are running SQL 2005
and haven't done so already, call tech support and get the SQL Unique
Index Script. Apparently quite a few functionality fixes were
released with the b patch. The SQL settings need to be adjusted to
accomodate this.
Try this:
- Make sure SQL Database running in 2005 mode.
- SQL Unique Index Script had not been run. ==> Ran SQL Index
Script (Get this from Epicor).
- SQL Full Text Catalogs = OK, track changes not enabled
- Mfgsys.pf Settings:
-- Added: -tmpbsize 8 and -ttmarshal 5
-- Added: PRGRS_NATIVE_LOCKWAIT,60000
-- Changed: -Bt 5000
- Progress Explorer Tool Settings:
-- Increased primary appserver from Max of 20 to 25
--- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@...>
wrote:
>We
> Thanks, that's very helpful.
> Daniel
>
> --- In vantage@yahoogroups.com, melissa hietala <kevmel822@> wrote:
> >
> > Here are some issues I came up against. If anyone has any fixes or
> ideas for me instead of waiting for Epicor I would appreciate it..
> > 1. Scheduling Board - Multiple issues.
> > a.The addition of queue and move time when rescheduling using
> the Operation Only option. If you use the Preceding Operations or
> Subsequent Operations it does not add the queue and move time.
> > b. The board is not recognizing calendar exceptions and is
> scheduling some jobs further out it the future because it is not
> picking up the calendar exceptions for weekends.
> > c. Load leveling using Operation only also adds queue and move
> time and also will not recognize the "Accept All' changes function.
> have to accept each job individually.also.
> > 2. Job Adjustments are not working. Getting an 'Unexpected error'
> message. See Apperver logs. Did job adjs in our test environment all
> the time with no issues. Cannot close jobs in scheduling boards
> You can check boxes, but does not do it. Ops still show open in jobfor
> tracker.
> > 3.BAQ's and dashboards not working. Was getting an 4GLStop error
> all base and custom BAQ's and would not load up the dashboardsrecords,
> attached to them. Epicor did get me a fix and applied it. Now
> everything works fine. There was some character length on one of the
> fields they had to do something with. This does not affect all
> installs, just a handful. They may add it to a patch in the future.
> > 4. Labor entry issues. When updating or adding labor detail
> Save does not save correctly. You save and then have to Refresh inmultiple
> order for the pay hours and labor hours to update. If you do
> days edits and hit Save and then refresh, it deletes out the 2ndthe
> day's edits and you have to redo.
> > 5. Using the * in the 'Where part description contains' field on
> part search screen does not work now. I can't get any records tofor
> populate using the * or the %. My engineers used this all the time
> looking up tooling.
> > 6. System commission report runs for an hour and a half and
> the invoice\payments dates it uses are not correct. Epicor has
> recognized this previously and is in .405 I think.
> > Thanks everyone.... :)
> > Melissa Hietala
> > UMC, Inc.
> > melissah@
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>