Introduction Occasionally, users will report error messages when opening windows in Estitrack. This is a sign that we need to do data...
Introduction
Occasionally, users will report error messages when opening windows in Estitrack. This is a sign that we need to do database maintenance.
Everyone will need to be out of the database.
Go to the V: drive and open Loadm64.exe. Log in with your
Steps (15 total)
Immediately, send out a message to all users, Please Exit Visual Estitrack, Visual Books and Remote Time Entry so that we can perform maintenance on the database.
Everyone will need to be out of the database.
Using Loadm64.exe, send out a message telling all Estitrack users to get out to the system.
It will then generate a partial list of who is in the system. After 5 minutes, if no one appears on the list, press the Shutdown the System button.
Check for open files. Open Computer Management, connect to remote computer
Teton2015-VM-2
Teton2015-VM-2
Check open files
You will see who has C:\Vet files open. Go to those users and talk to them. If they are not here, turn their computer off.
You will see who has C:\Vet files open. Go to those users and talk to them. If they are not here, turn their computer off.
Using Computer Management,
Look at the share security for VET. Remove the VETUSER from the Share. This will prevent people from accidentally trying to get into Estitrack before it is fixed.
After everyone is out of the VET folder (you might need to force close some open files)
Go back to LOADM64.exe
Click the Shutdown System Button
Go back to LOADM64.exe
Click the Shutdown System Button
Click the button (3) Database Optimization
After the database has optimized once,
Check the "Pack Tables" check box
Click the button (3) Database Optimization again
Check the "Pack Tables" check box
Click the button (3) Database Optimization again
Restart System
Email all the users that Estitrack is back online.
Email all the users that Estitrack is back online.
keep the system shutdown
when you get an error saying bad index, go to v:\app\memoscan and scan the table in question
1. open the .dbf
2. click blue links
3. click computer geek head :) NOTE: NEVER EVER EVER click the broom!!!!
4. close memoscan
1. open the .dbf
2. click blue links
3. click computer geek head :) NOTE: NEVER EVER EVER click the broom!!!!
4. close memoscan
open data vet excl
vali data
close data
(then press Ctrl+W)
vali data
close data
(then press Ctrl+W)
Once the data validates, optimize (Step) If it blows up again on a different table, repeat steps 10 and 11 until all errors are fixed.
After the database has optimized once,
Check the "Pack Tables" check box
Click the button (3) Database Optimization again
Check the "Pack Tables" check box
Click the button (3) Database Optimization again
Restart System
Email all the users that Estitrack is back online.
Email all the users that Estitrack is back online.
And you can't fix them with Memoscan, contact the Henning Software Help Desk.
Conclusion
Don't be afraid to call in the Henning Help Desk. They are very helpful and know how to fix recalcitrant foxpro databases.
No comments
Post a Comment