Vantage 8.03.403x Stability

Yahoo Archive
1
We have also seen problems with passwords less than 7 characters.

Making the password 7 characters eliminated some strange errors is the
log.



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jennifer
Sent: Tuesday, May 20, 2008 2:04 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.403x Stability



Is your manager password longer than 7 characters? There is a known
issue with this in 8.03.400. Change it to 7 characters or less and
this should fix your problem. If you stand on 1 foot and hop 3
times, you may be able to solve the 7145 error as well.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"lapulsifer" <sharon.pulsifer@...>
wrote:
>
> Hello. I am interested to hear about other people's experience so
> far with Vantage. We have been live for almost 2 months. At first
> Vantage crashed multiple times a day. Now things are a little
> better, but we have server stability problems about 3 days a week.
> We run in a SQL Server environment. I have read other threads
about
> instability with the Progress database as well.
>
> Our server configuration is quad Xeon 3mhz (multi-threading is
> disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for
OS
> and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.
>
> We regularly get application errors (7224, 7145 etc). The system
> also hangs up 3-4 times a week. When this happens, I notice that
the
> Server Processor counters are at 100%. About twice a week, our
> nightly MRP job hangs up and does not complete. We have noticed in
> certain areas, like order entry, the performance is bad. It is
> especially slow in moving between Order lines.
>
> I'm frustrated in the lack of visibility of user processes. I
tried
> to run SQL profiler, but Vantage stopped responding for all users.
>
> So far, we have done the following.
>
> 1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.
>
> 2. Re-installed Vantage for all Heavy users.
>
> 3. Performed some Progress tweaks recommended in an Epicor Document
> for SQL Server installations.
>
> 4. Disabled hyper-threading.
>
> 5. Updated our Progress Schema holders. Epicor sent us new
Progress
> schema holders, because they thought we might have a schema
mismatch.
>
> 6. Ran a Epicor-written SQL server unique index script.
>
> 7. We re-index and update statistics on our database regularly.
>




########################################################################
Attention:
This email message is privileged and confidential. If you are not the
intended recipient please delete the message and notify the sender.
Any views or opinions presented are solely those of the author.

This email message has been scanned for Viruses and Content and cleared
by MailMarshal SMTP

For more information go to http://www.ramsys.com
########################################################################


[Non-text portions of this message have been removed]
2
Hello. I am interested to hear about other people's experience so
far with Vantage. We have been live for almost 2 months. At first
Vantage crashed multiple times a day. Now things are a little
better, but we have server stability problems about 3 days a week.
We run in a SQL Server environment. I have read other threads about
instability with the Progress database as well.

Our server configuration is quad Xeon 3mhz (multi-threading is
disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for OS
and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.

We regularly get application errors (7224, 7145 etc). The system
also hangs up 3-4 times a week. When this happens, I notice that the
Server Processor counters are at 100%. About twice a week, our
nightly MRP job hangs up and does not complete. We have noticed in
certain areas, like order entry, the performance is bad. It is
especially slow in moving between Order lines.

I'm frustrated in the lack of visibility of user processes. I tried
to run SQL profiler, but Vantage stopped responding for all users.

So far, we have done the following.

1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.

2. Re-installed Vantage for all Heavy users.

3. Performed some Progress tweaks recommended in an Epicor Document
for SQL Server installations.

4. Disabled hyper-threading.

5. Updated our Progress Schema holders. Epicor sent us new Progress
schema holders, because they thought we might have a schema mismatch.

6. Ran a Epicor-written SQL server unique index script.

7. We re-index and update statistics on our database regularly.
3
We, like every other vantage user, have many application error
problems too. But our biggest problem is that every week or so, we
have record accessing conflicts. Users are able to view and retrieve
data but vantage locks up upon saving. We have had this problem since
going live months ago. Support just flounders around and doesn't
help. Has anyone else experienced this issue?
4
I also experience those same issues within the Progress Environment. The
application crashes about every third day and at least once a week the
server locks up. My MR fails about once every 2 weeks. I have a few
clients that crash 4-5 times per day. Re-installing has done little. We
no longer call support to discuss the issues. System glitches have just
become part of our processes.



Tom Morrison

Load Rite



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of lapulsifer
Sent: Thursday, March 20, 2008 10:32 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Vantage 8.03.403x Stability



Hello. I am interested to hear about other people's experience so
far with Vantage. We have been live for almost 2 months. At first
Vantage crashed multiple times a day. Now things are a little
better, but we have server stability problems about 3 days a week.
We run in a SQL Server environment. I have read other threads about
instability with the Progress database as well.

Our server configuration is quad Xeon 3mhz (multi-threading is
disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for OS
and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.

We regularly get application errors (7224, 7145 etc). The system
also hangs up 3-4 times a week. When this happens, I notice that the
Server Processor counters are at 100%. About twice a week, our
nightly MRP job hangs up and does not complete. We have noticed in
certain areas, like order entry, the performance is bad. It is
especially slow in moving between Order lines.

I'm frustrated in the lack of visibility of user processes. I tried
to run SQL profiler, but Vantage stopped responding for all users.

So far, we have done the following.

1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.

2. Re-installed Vantage for all Heavy users.

3. Performed some Progress tweaks recommended in an Epicor Document
for SQL Server installations.

4. Disabled hyper-threading.

5. Updated our Progress Schema holders. Epicor sent us new Progress
schema holders, because they thought we might have a schema mismatch.

6. Ran a Epicor-written SQL server unique index script.

7. We re-index and update statistics on our database regularly.





[Non-text portions of this message have been removed]
5
Can't believe I'm going to stick up for Vantage(!) but here goes:

We find the product quite stable at this point. We started on v8.00
two years ago and definitely had stability issues, but the upgrades
to 8.03.305 and then to 8.03.403 have fixed most of those.

We run Vantage (on OpenEdge 10.1b) off one main server and our users
(c. 20) use two Terminal Servers. Only a few users have Vantage
installed on their own PCs.

I do re-boot the main server about once a month, usually for an
appserver gone wild, but other than that we haven't experienced
anywhere near the issues that have been mentioned here.

We're only starting to get into Service Connect, though. We starting
trading thru EDI over the coming weeks and will be using SC rather
heavily for that.

We definitely still have issues with the overall speed of Vantage,
but, as I said, we do find it quite stable.


Nigel.
6
I am going to "second that emotion". We are very pleased with the
improved stability we have seen since starting with 8.00.808, through
8.03.305, particularly after the move to 403. We rarely have a
problem now. The last flareup we had was fixed by moving to SP3 on
Open Edge.

We are Progress and 403B. We have about 60 manufacturing people
running MES on terminals connected to two terminal servers, and about
50 office people with Vantage loaded on their computers. It is now
rare when we have to kick everyone out and restart the database, and
it had been very common (sometimes daily) in the "old" days.

-Peter Volkert
Symetrics Industries

--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...>
wrote:
>
>
> Can't believe I'm going to stick up for Vantage(!) but here goes:
>
> We find the product quite stable at this point. We started on v8.00
> two years ago and definitely had stability issues, but the upgrades
> to 8.03.305 and then to 8.03.403 have fixed most of those.
>
> We run Vantage (on OpenEdge 10.1b) off one main server and our
users
> (c. 20) use two Terminal Servers. Only a few users have Vantage
> installed on their own PCs.
>
> I do re-boot the main server about once a month, usually for an
> appserver gone wild, but other than that we haven't experienced
> anywhere near the issues that have been mentioned here.
>
> We're only starting to get into Service Connect, though. We
starting
> trading thru EDI over the coming weeks and will be using SC rather
> heavily for that.
>
> We definitely still have issues with the overall speed of Vantage,
> but, as I said, we do find it quite stable.
>
>
> Nigel.
>
7
Interesting to hear about these problems, as our 8.03.305K system also
suffered from the same exact maladys for over 10 months after go-live.
We upgraded our SQL installation from SQL-2000 to SQL-2005, have set
our schema-holder db to 'read-only', have run the SQL-reindexing
script, have a Quad-processor, dual-core HP system, running WK2003
Enterprise OS, with 8GB RAM, & have largely stopped the frequent
system 'crashes' since early January (I've only been forced to restart
2 or 3 times since then). However, we do still see performance
problems with end-of-month/month-end-close lengthy reporting, & have
to carefully watch for CPU utilization saturation @ 100% during these
times. Every time it does, I can usually track the culprit to one or
more lengthy report(s). Also, the Progress AppServers still have a
known problem with 'abandoning' during heavy loads (like overnight
MRP), which Progress is still stuggling to fix. I say 'interesting'
because we are being strongly advised by Epicor to upgrade to
8.03.403X, to improve printing and Terminal-Server performance. This
thread of messages sure leads me to believe we might not get the
improvement we're still seeking, to be honest.

- Gary -

--- In vantage@yahoogroups.com, "lapulsifer" <sharon.pulsifer@...> wrote:
>
> Hello. I am interested to hear about other people's experience so
> far with Vantage. We have been live for almost 2 months. At first
> Vantage crashed multiple times a day. Now things are a little
> better, but we have server stability problems about 3 days a week.
> We run in a SQL Server environment. I have read other threads about
> instability with the Progress database as well.
>
> Our server configuration is quad Xeon 3mhz (multi-threading is
> disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for OS
> and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.
>
> We regularly get application errors (7224, 7145 etc). The system
> also hangs up 3-4 times a week. When this happens, I notice that the
> Server Processor counters are at 100%. About twice a week, our
> nightly MRP job hangs up and does not complete. We have noticed in
> certain areas, like order entry, the performance is bad. It is
> especially slow in moving between Order lines.
>
> I'm frustrated in the lack of visibility of user processes. I tried
> to run SQL profiler, but Vantage stopped responding for all users.
>
> So far, we have done the following.
>
> 1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.
>
> 2. Re-installed Vantage for all Heavy users.
>
> 3. Performed some Progress tweaks recommended in an Epicor Document
> for SQL Server installations.
>
> 4. Disabled hyper-threading.
>
> 5. Updated our Progress Schema holders. Epicor sent us new Progress
> schema holders, because they thought we might have a schema mismatch.
>
> 6. Ran a Epicor-written SQL server unique index script.
>
> 7. We re-index and update statistics on our database regularly.
>
8
We also use Service Connect to connect Vantage to our Gentran EDI
Translator. It's absolutely been the most stable part of our Vantage
implementation.....It was expensive to get setup, but does work quite
well, once you're there...

Gary

--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...> wrote:
>
>
> Can't believe I'm going to stick up for Vantage(!) but here goes:
>
> We find the product quite stable at this point. We started on v8.00
> two years ago and definitely had stability issues, but the upgrades
> to 8.03.305 and then to 8.03.403 have fixed most of those.
>
> We run Vantage (on OpenEdge 10.1b) off one main server and our users
> (c. 20) use two Terminal Servers. Only a few users have Vantage
> installed on their own PCs.
>
> I do re-boot the main server about once a month, usually for an
> appserver gone wild, but other than that we haven't experienced
> anywhere near the issues that have been mentioned here.
>
> We're only starting to get into Service Connect, though. We starting
> trading thru EDI over the coming weeks and will be using SC rather
> heavily for that.
>
> We definitely still have issues with the overall speed of Vantage,
> but, as I said, we do find it quite stable.
>
>
> Nigel.
>
9
We also have record accessing conflicts. We get a message that someone
else has changed the record and that we need to refresh. We refresh
and try again and receive the same message. We know that nobody else
is in the same record. Our consultants wrote a program that has helped
to get rid of the problem.

Linda Lowney

--- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@...>
wrote:
>
> We, like every other vantage user, have many application error
> problems too. But our biggest problem is that every week or so, we
> have record accessing conflicts. Users are able to view and retrieve
> data but vantage locks up upon saving. We have had this problem since
> going live months ago. Support just flounders around and doesn't
> help. Has anyone else experienced this issue?
>
10
We have had the same problem. We are on 8.03.305K, and were told that
8.03.400 would fix it, but on our test server (which has 8.03.404) the
problem still exists.

--- In vantage@yahoogroups.com, "lindalowney" <llowney@...> wrote:
>
> We also have record accessing conflicts. We get a message that someone
> else has changed the record and that we need to refresh. We refresh
> and try again and receive the same message. We know that nobody else
> is in the same record. Our consultants wrote a program that has helped
> to get rid of the problem.
>
> Linda Lowney
>
> --- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@>
> wrote:
> >
> > We, like every other vantage user, have many application error
> > problems too. But our biggest problem is that every week or so, we
> > have record accessing conflicts. Users are able to view and retrieve
> > data but vantage locks up upon saving. We have had this problem since
> > going live months ago. Support just flounders around and doesn't
> > help. Has anyone else experienced this issue?
> >
>
11
The 'other user' that changed the record is likely you.

In some applications, simply tabbing through certian fields will cause a record update that, for some ridiculous reason (sloppy programming), doesn't result in a form refresh.

Keep track of what applications and activation of specific fields results in the error message. You can then write simple event triggered cleanup routines for each offending control with a simple otrans.refresh() and/or otrans.update() as the action.

Rob Brown


lindalowney <llowney@...> wrote:
We also have record accessing conflicts. We get a message that someone
else has changed the record and that we need to refresh. We refresh
and try again and receive the same message. We know that nobody else
is in the same record. Our consultants wrote a program that has helped
to get rid of the problem.

Linda Lowney

--- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@...>
wrote:
>
> We, like every other vantage user, have many application error
> problems too. But our biggest problem is that every week or so, we
> have record accessing conflicts. Users are able to view and retrieve
> data but vantage locks up upon saving. We have had this problem since
> going live months ago. Support just flounders around and doesn't
> help. Has anyone else experienced this issue?
>






---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

[Non-text portions of this message have been removed]
12
I believe this is a very 'old' problem that goes back to the initial
release of version 8.xx. With some patch levels, it seems to go away,
but we've seen this rather consistently ever since we upgraded to
version 8.03......The Developers have been to our site, acknowledge
the problem exists, but we have not yet seen anything that completely
eradicates the issue. I'd be guessing at a root cause, so I won't.


Gary

--- In vantage@yahoogroups.com, "jkeyes0" <jordan.keyes@...> wrote:
>
> We have had the same problem. We are on 8.03.305K, and were told that
> 8.03.400 would fix it, but on our test server (which has 8.03.404) the
> problem still exists.
>
> --- In vantage@yahoogroups.com, "lindalowney" <llowney@> wrote:
> >
> > We also have record accessing conflicts. We get a message that
someone
> > else has changed the record and that we need to refresh. We refresh
> > and try again and receive the same message. We know that nobody else
> > is in the same record. Our consultants wrote a program that has
helped
> > to get rid of the problem.
> >
> > Linda Lowney
> >
> > --- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@>
> > wrote:
> > >
> > > We, like every other vantage user, have many application error
> > > problems too. But our biggest problem is that every week or so, we
> > > have record accessing conflicts. Users are able to view and
retrieve
> > > data but vantage locks up upon saving. We have had this problem
since
> > > going live months ago. Support just flounders around and doesn't
> > > help. Has anyone else experienced this issue?
> > >
> >
>
13
As far as the record access conflicts... "the record has been modified
by another user please refresh and save again." I was getting that
frequently following our conversion to 8.03.404. I performed a Dump &
Load of the database which seems to have resolved what I was calling
orphaned record locks that support says may have pre-dated the
conversion.

Lee Ingalls
Commercial Tool

________________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Gary Franks
Sent: Monday, March 24, 2008 11:34 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.403x Stability

I believe this is a very 'old' problem that goes back to the initial
release of version 8.xx. With some patch levels, it seems to go away,
but we've seen this rather consistently ever since we upgraded to
version 8.03......The Developers have been to our site, acknowledge
the problem exists, but we have not yet seen anything that completely
eradicates the issue. I'd be guessing at a root cause, so I won't.

Gary

--- In vantage@yahoogroups.com, "jkeyes0" <jordan.keyes@...> wrote:
>
> We have had the same problem. We are on 8.03.305K, and were told that
> 8.03.400 would fix it, but on our test server (which has 8.03.404) the
> problem still exists.
>
> --- In vantage@yahoogroups.com, "lindalowney" <llowney@> wrote:
> >
> > We also have record accessing conflicts. We get a message that
someone
> > else has changed the record and that we need to refresh. We refresh
> > and try again and receive the same message. We know that nobody else

> > is in the same record. Our consultants wrote a program that has
helped
> > to get rid of the problem.
> >
> > Linda Lowney
> >
> > --- In vantage@yahoogroups.com, "laidig.systems" <laidig.systems@>
> > wrote:
> > >
> > > We, like every other vantage user, have many application error
> > > problems too. But our biggest problem is that every week or so, we
> > > have record accessing conflicts. Users are able to view and
retrieve
> > > data but vantage locks up upon saving. We have had this problem
since
> > > going live months ago. Support just flounders around and doesn't
> > > help. Has anyone else experienced this issue?
14
We used to have this issue, but with recent upgrades it's largely
disappeared.

We were told that it is caused by rements in the database following
upgrades (particularly from v8.00 to v8.03.3xx) and that a "Dump &
Load" would help.

Nigel.


--- In vantage@yahoogroups.com, "Gary Franks" <garyfr2003@...> wrote:
>
> I believe this is a very 'old' problem that goes back to the initial
> release of version 8.xx. With some patch levels, it seems to go
away,
> but we've seen this rather consistently ever since we upgraded to
> version 8.03......The Developers have been to our site, acknowledge
> the problem exists, but we have not yet seen anything that
completely
> eradicates the issue. I'd be guessing at a root cause, so I won't.
>
>
> Gary
>
> --- In vantage@yahoogroups.com, "jkeyes0" <jordan.keyes@> wrote:
> >
> > We have had the same problem. We are on 8.03.305K, and were told
that
> > 8.03.400 would fix it, but on our test server (which has
8.03.404) the
> > problem still exists.
> >
> > --- In vantage@yahoogroups.com, "lindalowney" <llowney@> wrote:
> > >
> > > We also have record accessing conflicts. We get a message that
> someone
> > > else has changed the record and that we need to refresh. We
refresh
> > > and try again and receive the same message. We know that
nobody else
> > > is in the same record. Our consultants wrote a program that has
> helped
> > > to get rid of the problem.
> > >
> > > Linda Lowney
> > >
> > > --- In vantage@yahoogroups.com, "laidig.systems"
<laidig.systems@>
> > > wrote:
> > > >
> > > > We, like every other vantage user, have many application error
> > > > problems too. But our biggest problem is that every week or
so, we
> > > > have record accessing conflicts. Users are able to view and
> retrieve
> > > > data but vantage locks up upon saving. We have had this
problem
> since
> > > > going live months ago. Support just flounders around and
doesn't
> > > > help. Has anyone else experienced this issue?
> > > >
> > >
> >
>
15
--- In vantage@yahoogroups.com, "lapulsifer" <sharon.pulsifer@...>
wrote:
>
> Hello. I am interested to hear about other people's experience so
> far with Vantage. We have been live for almost 2 months. At first
> Vantage crashed multiple times a day. Now things are a little
> better, but we have server stability problems about 3 days a week.
> We run in a SQL Server environment. I have read other threads
about
> instability with the Progress database as well.
>
> Our server configuration is quad Xeon 3mhz (multi-threading is
> disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for
OS
> and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.
>
> We regularly get application errors (7224, 7145 etc). The system
> also hangs up 3-4 times a week. When this happens, I notice that
the
> Server Processor counters are at 100%. About twice a week, our
> nightly MRP job hangs up and does not complete. We have noticed in
> certain areas, like order entry, the performance is bad. It is
> especially slow in moving between Order lines.
>
> I'm frustrated in the lack of visibility of user processes. I
tried
> to run SQL profiler, but Vantage stopped responding for all users.
>
> So far, we have done the following.
>
> 1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.
>
> 2. Re-installed Vantage for all Heavy users.
>
> 3. Performed some Progress tweaks recommended in an Epicor Document
> for SQL Server installations.
>
> 4. Disabled hyper-threading.
>
> 5. Updated our Progress Schema holders. Epicor sent us new
Progress
> schema holders, because they thought we might have a schema
mismatch.
>
> 6. Ran a Epicor-written SQL server unique index script.
>
> 7. We re-index and update statistics on our database regularly.
>
16
Did you set the schema holders to read only (KB article 8782MPS)? We are
on 8.03.403something and have had no problems since we did this. We
don't run MRP. We ran 8.0 on RAID 1 and RAID 10 and even though we had
RAID 10 it was slow. When we went to a SAN life improved 100%. When we
went to 8.03 we separated SQL on a server from Vantage in a virtual
machine and went with 64bit SQL 2005. It was horrible until we set the
schema holders to read only and the other things mentioned in that KB
article.



Joe Luster

Network Administrator

Cold Jet, LLC

513-831-3211 ext. 308

513-831-1209 FAX





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Rick Bird
Sent: Tuesday, April 22, 2008 11:00 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.403x Stability



--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"lapulsifer" <sharon.pulsifer@...>
wrote:
>
> Hello. I am interested to hear about other people's experience so
> far with Vantage. We have been live for almost 2 months. At first
> Vantage crashed multiple times a day. Now things are a little
> better, but we have server stability problems about 3 days a week.
> We run in a SQL Server environment. I have read other threads
about
> instability with the Progress database as well.
>
> Our server configuration is quad Xeon 3mhz (multi-threading is
> disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for
OS
> and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.
>
> We regularly get application errors (7224, 7145 etc). The system
> also hangs up 3-4 times a week. When this happens, I notice that
the
> Server Processor counters are at 100%. About twice a week, our
> nightly MRP job hangs up and does not complete. We have noticed in
> certain areas, like order entry, the performance is bad. It is
> especially slow in moving between Order lines.
>
> I'm frustrated in the lack of visibility of user processes. I
tried
> to run SQL profiler, but Vantage stopped responding for all users.
>
> So far, we have done the following.
>
> 1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.
>
> 2. Re-installed Vantage for all Heavy users.
>
> 3. Performed some Progress tweaks recommended in an Epicor Document
> for SQL Server installations.
>
> 4. Disabled hyper-threading.
>
> 5. Updated our Progress Schema holders. Epicor sent us new
Progress
> schema holders, because they thought we might have a schema
mismatch.
>
> 6. Ran a Epicor-written SQL server unique index script.
>
> 7. We re-index and update statistics on our database regularly.
>





[Non-text portions of this message have been removed]
17
I have thought of setting the schema holders to read-only. We use
Service connect, which is a 3rd party application. The instructions
say that if 3rd party applications are accessing the database, then
you can't set the schema holders to read-only.

I haven't been able to get an answer from Epicor yet about whether
this is a problem for Service Connect or not.

I may try this and see if it causes problems with Service Connect.

Thanks for the suggestion.

--- In vantage@yahoogroups.com, "Joe Luster" <jluster@...> wrote:
>
> Did you set the schema holders to read only (KB article 8782MPS)?
We are
> on 8.03.403something and have had no problems since we did this. We
> don't run MRP. We ran 8.0 on RAID 1 and RAID 10 and even though we
had
> RAID 10 it was slow. When we went to a SAN life improved 100%. When
we
> went to 8.03 we separated SQL on a server from Vantage in a virtual
> machine and went with 64bit SQL 2005. It was horrible until we set
the
> schema holders to read only and the other things mentioned in that
KB
> article.
>
>
>
> Joe Luster
>
> Network Administrator
>
> Cold Jet, LLC
>
> 513-831-3211 ext. 308
>
> 513-831-1209 FAX
>
>
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of Rick Bird
> Sent: Tuesday, April 22, 2008 11:00 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Vantage 8.03.403x Stability
>
>
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "lapulsifer" <sharon.pulsifer@>
> wrote:
> >
> > Hello. I am interested to hear about other people's experience so
> > far with Vantage. We have been live for almost 2 months. At first
> > Vantage crashed multiple times a day. Now things are a little
> > better, but we have server stability problems about 3 days a
week.
> > We run in a SQL Server environment. I have read other threads
> about
> > instability with the Progress database as well.
> >
> > Our server configuration is quad Xeon 3mhz (multi-threading is
> > disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1
for
> OS
> > and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.
> >
> > We regularly get application errors (7224, 7145 etc). The system
> > also hangs up 3-4 times a week. When this happens, I notice that
> the
> > Server Processor counters are at 100%. About twice a week, our
> > nightly MRP job hangs up and does not complete. We have noticed
in
> > certain areas, like order entry, the performance is bad. It is
> > especially slow in moving between Order lines.
> >
> > I'm frustrated in the lack of visibility of user processes. I
> tried
> > to run SQL profiler, but Vantage stopped responding for all
users.
> >
> > So far, we have done the following.
> >
> > 1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.
> >
> > 2. Re-installed Vantage for all Heavy users.
> >
> > 3. Performed some Progress tweaks recommended in an Epicor
Document
> > for SQL Server installations.
> >
> > 4. Disabled hyper-threading.
> >
> > 5. Updated our Progress Schema holders. Epicor sent us new
> Progress
> > schema holders, because they thought we might have a schema
> mismatch.
> >
> > 6. Ran a Epicor-written SQL server unique index script.
> >
> > 7. We re-index and update statistics on our database regularly.
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
18
Is your manager password longer than 7 characters? There is a known
issue with this in 8.03.400. Change it to 7 characters or less and
this should fix your problem. If you stand on 1 foot and hop 3
times, you may be able to solve the 7145 error as well.


--- In vantage@yahoogroups.com, "lapulsifer" <sharon.pulsifer@...>
wrote:
>
> Hello. I am interested to hear about other people's experience so
> far with Vantage. We have been live for almost 2 months. At first
> Vantage crashed multiple times a day. Now things are a little
> better, but we have server stability problems about 3 days a week.
> We run in a SQL Server environment. I have read other threads
about
> instability with the Progress database as well.
>
> Our server configuration is quad Xeon 3mhz (multi-threading is
> disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for
OS
> and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.
>
> We regularly get application errors (7224, 7145 etc). The system
> also hangs up 3-4 times a week. When this happens, I notice that
the
> Server Processor counters are at 100%. About twice a week, our
> nightly MRP job hangs up and does not complete. We have noticed in
> certain areas, like order entry, the performance is bad. It is
> especially slow in moving between Order lines.
>
> I'm frustrated in the lack of visibility of user processes. I
tried
> to run SQL profiler, but Vantage stopped responding for all users.
>
> So far, we have done the following.
>
> 1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.
>
> 2. Re-installed Vantage for all Heavy users.
>
> 3. Performed some Progress tweaks recommended in an Epicor Document
> for SQL Server installations.
>
> 4. Disabled hyper-threading.
>
> 5. Updated our Progress Schema holders. Epicor sent us new
Progress
> schema holders, because they thought we might have a schema
mismatch.
>
> 6. Ran a Epicor-written SQL server unique index script.
>
> 7. We re-index and update statistics on our database regularly.
>
19
Can't help you much with the SQL database. I know progress has an issue
with the 7 character password limit but I never had the server lock up
or crash because of it. I have had MRP lock up on many occasions. I
was sometimes able to determine the cause and other times I was not.
The main cause I found for the MRP lockups is a sub-assembly not having
an approved revision. It seems that if MRP hits this circumstance
during its process it will stop completely. I imagine it would be the
same for an SQL database. I have also found that since version 8.03.40x
I am unable to run MRP with multiple schedulers or multiple MRP
processes. I used to run 2 and 2 on 8.03.305x. If I do that on the new
version MRP will never complete. That is the case even with 8.03.404
for which Epicor listed a fix to allow MRP to run with more than one
process.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jennifer
Sent: Tuesday, May 20, 2008 2:04 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.403x Stability



Is your manager password longer than 7 characters? There is a known
issue with this in 8.03.400. Change it to 7 characters or less and
this should fix your problem. If you stand on 1 foot and hop 3
times, you may be able to solve the 7145 error as well.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"lapulsifer" <sharon.pulsifer@...>
wrote:
>
> Hello. I am interested to hear about other people's experience so
> far with Vantage. We have been live for almost 2 months. At first
> Vantage crashed multiple times a day. Now things are a little
> better, but we have server stability problems about 3 days a week.
> We run in a SQL Server environment. I have read other threads
about
> instability with the Progress database as well.
>
> Our server configuration is quad Xeon 3mhz (multi-threading is
> disabled), 12gb ram, Raid 1 for Logs, Raid 10 for data, Raid 1 for
OS
> and applications. Windows 2003 Stn 64-bit and SQL 2005 64-bit.
>
> We regularly get application errors (7224, 7145 etc). The system
> also hangs up 3-4 times a week. When this happens, I notice that
the
> Server Processor counters are at 100%. About twice a week, our
> nightly MRP job hangs up and does not complete. We have noticed in
> certain areas, like order entry, the performance is bad. It is
> especially slow in moving between Order lines.
>
> I'm frustrated in the lack of visibility of user processes. I
tried
> to run SQL profiler, but Vantage stopped responding for all users.
>
> So far, we have done the following.
>
> 1. Upgraded to Open Edge 10.1 SP 3 Hotfix 7.
>
> 2. Re-installed Vantage for all Heavy users.
>
> 3. Performed some Progress tweaks recommended in an Epicor Document
> for SQL Server installations.
>
> 4. Disabled hyper-threading.
>
> 5. Updated our Progress Schema holders. Epicor sent us new
Progress
> schema holders, because they thought we might have a schema
mismatch.
>
> 6. Ran a Epicor-written SQL server unique index script.
>
> 7. We re-index and update statistics on our database regularly.
>



Charles Carden
Manager, MIS
Manitex, Inc.
Phone: 512-942-3086
Fax: 512-942-3089


DISCLAIMER:
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.



[Non-text portions of this message have been removed]