(Just a followup, in case anyone is interested)
Epicor had me do all sorts of 'tests' to resolve the problem. Nothing
worked. Since the database itself was stopping, they considered it a
Progress issue, and transferred me to Progress.
The people at Progress were very helpful (thanks, Richard!). First, in
order to 'see' what was going on, we hooked up a modem to the server, and
they VPN'd in to watch it. After watching me crash the server several
times, we tried several 'watchdog' programs to capture what was happening
'behind the scenes'. When this didn't give them the info they needed, I
offered to just *send* them the server. So, off to Massachusetts it goes.
Once Progress gets our server, they try to crash it. It didn't take long.
They then configured another computer on their site, and were able to
replicate the problem (so, it's not a hardware issue <phew!>). So, our
server racks up some more 'frequent flyer miles' on it's way back to
California.
Remember, I had installed the client on the server, for testing? Well,
testing at Progress revealed that Epicor's *** CLIENT *** had a memory leak,
and would eventually suck enough resources to result in the database
starving to death! (And, we've all wondered why our workstations keep having
problems, eh?) So, it's now back in Epicor's court.
Epicor looks into the issue, and acknowledges that there *had* been a
problem with the Vantage.exe file, but it had been 'fixed'. Sigh. They
sent me a copy of the new Vantage.exe file. (As an aside, I don't know
when, or if, this new Vantage.exe was ever incorporated into any new patch.)
Ok, here it gets really 'interesting'. With the new Vantage.exe file in
hand, I rename the old Vantage.exe file (to Vantage.exe.old), and copy the
new file in it's place. Fire up Vantage, and it still crashes. Epicor asks
if I rebooted the server. Hmm, don't remember. So, I reboot the server,
and try again. This time, I'm watching in Task Manager for the memory
problem. Fire up Vantage. Hmmm, that's strange. Vantage is running a
program called VANTAG~1.old . Very strange! I move the file Vantage.exe.old
to another directory. Now, Vantage won't run, saying that it can't find the
file VANTAG~1.old !! What the ???
I search through all the configuration files (.ini, .vtg. etc) for any
reference to this file. No luck. So, I then try in the registry. Ahh HA
!!!
Four places in the registry referenced VANTAG~1.old !!! It seems, when you
right-click on a file, and rename it, registry entries pointing to that now
renamed file changed too!!! Well, I'll be ....
A quick change of these four registry entries, another reboot, and we're off
and running. So far, no crashes.
Ok, it *seems* to work. But, just to be safe, I blow away the whole
computer yesterday, and build it up from scratch (during all the testing,
I'd done so many changes from our 'standard' server install, I just wanted
to clean things up). Ok, load Progress, the service patch, Vantage, the
latest patch ..... oops ...
What's this I hear about the latest Vantage patch? Oh chit .... Ah, the
305 patch is out? Ok, let's download it ...
Ok, it's up and running. So far, there's no 'problems'. At least, it's not
crashing! <g>
Let's see, what else ... Before we can move from 5.1 to 5.2 ... Hmmm ....
1) Gotta upgrade our data collection computers (currently running Win95)
<yea, I know there's a workaround, but ..>
2) Gotta pay Epicor to re-compile all our custom reports
<even when moving from 5.1 to 5.2? Sigh>
Hey, what's this about 6.0 being released in 6-8 weeks?
Thank goodness for the time off next week. I think I need it! <g>
Happy Holidays!
============================================
Malcolm Spann
MIS
Malmberg Engineering
(925) 606-6500 x19
Malcolm@...
============================================
Epicor had me do all sorts of 'tests' to resolve the problem. Nothing
worked. Since the database itself was stopping, they considered it a
Progress issue, and transferred me to Progress.
The people at Progress were very helpful (thanks, Richard!). First, in
order to 'see' what was going on, we hooked up a modem to the server, and
they VPN'd in to watch it. After watching me crash the server several
times, we tried several 'watchdog' programs to capture what was happening
'behind the scenes'. When this didn't give them the info they needed, I
offered to just *send* them the server. So, off to Massachusetts it goes.
Once Progress gets our server, they try to crash it. It didn't take long.
They then configured another computer on their site, and were able to
replicate the problem (so, it's not a hardware issue <phew!>). So, our
server racks up some more 'frequent flyer miles' on it's way back to
California.
Remember, I had installed the client on the server, for testing? Well,
testing at Progress revealed that Epicor's *** CLIENT *** had a memory leak,
and would eventually suck enough resources to result in the database
starving to death! (And, we've all wondered why our workstations keep having
problems, eh?) So, it's now back in Epicor's court.
Epicor looks into the issue, and acknowledges that there *had* been a
problem with the Vantage.exe file, but it had been 'fixed'. Sigh. They
sent me a copy of the new Vantage.exe file. (As an aside, I don't know
when, or if, this new Vantage.exe was ever incorporated into any new patch.)
Ok, here it gets really 'interesting'. With the new Vantage.exe file in
hand, I rename the old Vantage.exe file (to Vantage.exe.old), and copy the
new file in it's place. Fire up Vantage, and it still crashes. Epicor asks
if I rebooted the server. Hmm, don't remember. So, I reboot the server,
and try again. This time, I'm watching in Task Manager for the memory
problem. Fire up Vantage. Hmmm, that's strange. Vantage is running a
program called VANTAG~1.old . Very strange! I move the file Vantage.exe.old
to another directory. Now, Vantage won't run, saying that it can't find the
file VANTAG~1.old !! What the ???
I search through all the configuration files (.ini, .vtg. etc) for any
reference to this file. No luck. So, I then try in the registry. Ahh HA
!!!
Four places in the registry referenced VANTAG~1.old !!! It seems, when you
right-click on a file, and rename it, registry entries pointing to that now
renamed file changed too!!! Well, I'll be ....
A quick change of these four registry entries, another reboot, and we're off
and running. So far, no crashes.
Ok, it *seems* to work. But, just to be safe, I blow away the whole
computer yesterday, and build it up from scratch (during all the testing,
I'd done so many changes from our 'standard' server install, I just wanted
to clean things up). Ok, load Progress, the service patch, Vantage, the
latest patch ..... oops ...
What's this I hear about the latest Vantage patch? Oh chit .... Ah, the
305 patch is out? Ok, let's download it ...
Ok, it's up and running. So far, there's no 'problems'. At least, it's not
crashing! <g>
Let's see, what else ... Before we can move from 5.1 to 5.2 ... Hmmm ....
1) Gotta upgrade our data collection computers (currently running Win95)
<yea, I know there's a workaround, but ..>
2) Gotta pay Epicor to re-compile all our custom reports
<even when moving from 5.1 to 5.2? Sigh>
Hey, what's this about 6.0 being released in 6-8 weeks?
Thank goodness for the time off next week. I think I need it! <g>
Happy Holidays!
============================================
Malcolm Spann
MIS
Malmberg Engineering
(925) 606-6500 x19
Malcolm@...
============================================
> -----Original Message-----
> From: Malcolm Spann [mailto:Malcolm@...]
> Sent: Friday, October 04, 2002 11:22 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Database stopping
>
>
> I'm trying to install Vantage 5.2 onto a server on which we
> had run Vantage 4.0 for over a year and a half. It is a
> generic box using name brand parts (Asus motherboard, Intel
> NIC, Adaptec SCSI card, etc.). I've completely blown away
> the system, and have installed the OS (NT4, sp6a), Progress
> 9.1D SP1, and Vantage 5.20.210. For my initial testing,
> I've installed the client on the server. I also have a
> client installed on a workstation.
>
> I've imported our database from our Vantage 5.1 server, and
> have done the schema change. I've also applied our licenses
> to the training database. The system comes up, the databases
> start up, and I'm able to log into Vantage (both our 'live'
> database & the training database).
>
> My problem is: After logging into Vantage, after a short
> time, the databases shut down. Progress Explorer shows them
> as stopped. I can re-start them, and they will continue to run,
> until I access them again. Then, again, they will stop.
>
> I've re-created this with both our live database and the
> training database. I've recreated this with both the client on
> the server and on a workstation. At Epicor's suggestion, I've
> shut down the Progress Explorer and started up ProServices
> instead. Again, after accessing the databases, they shut down.
>
>
> ============================================
> Malcolm Spann
> MIS
> Malmberg Engineering
> (925) 606-6500 x19
> Malcolm@...
> ============================================