A cup of Joe for 8.03.400 upgrade

Yahoo Archive
1
I too, had the 'word break 2' issue and used the same band aid fix...

How did a reference to an obsolete file get into the database and how
does one get rid of it???


--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
> >
> > How did you access the progress explorer tool?
> >
>
> I used the 10.1B version, so the answer is "It is just me" because
this was a
> case of premature instantiation. Once I loaded SP2 for Progress, I
had no
> trouble...
>
> Well, almost.
>
> When it was time to start the database, it would not start. The
Application
> Event Log said that the Word Break 2 file was missing. This
happened to us
> once before and support had us copy the one from another machine.
In this
> case, I copied <drive:>\epicor\oe100b\proword.2 to
> <drive:>\epicor\oe101b\proword.2 and it started right up. Our schema
> conversion is now running and we'll patch to 403C this weekend.
>
> Thanks!
>
> Mark W.
>
2
We're doing our due diligence and installing 8.03.400 on a test machine but
the OpenEdge 10.1B did not seem to finish and if I try to use the new Progress
Explorer, I get a missing Java object error. Sound familiar to anyone or is it
just me?

Mark W.
3
How did you access the progress explorer tool?



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Friday, October 26, 2007 2:50 PM
To: vantage@yahoogroups.com
Subject: [Vantage] A cup of Joe for 8.03.400 upgrade...



We're doing our due diligence and installing 8.03.400 on a test machine
but
the OpenEdge 10.1B did not seem to finish and if I try to use the new
Progress
Explorer, I get a missing Java object error. Sound familiar to anyone or
is it
just me?

Mark W.





[Non-text portions of this message have been removed]
4
>
> How did you access the progress explorer tool?
>

I used the 10.1B version, so the answer is "It is just me" because this was a
case of premature instantiation. Once I loaded SP2 for Progress, I had no
trouble...

Well, almost.

When it was time to start the database, it would not start. The Application
Event Log said that the Word Break 2 file was missing. This happened to us
once before and support had us copy the one from another machine. In this
case, I copied <drive:>\epicor\oe100b\proword.2 to
<drive:>\epicor\oe101b\proword.2 and it started right up. Our schema
conversion is now running and we'll patch to 403C this weekend.

Thanks!

Mark W.