This is caused by the installation or uninstallation of another software program whereby an ActiveX control (presumably used by both programs) was negatively impacted - either moved, deleted, or unregistered.
Generally Service2000 will still run so this is not an emergency situation.
Resolution
==========
Single User systems: The resolution consists of the following: back up your database and reinstall right over your existing installation. Do not uninstall the existing Service2000 installation. The program will be "replaced" by the new installation. The database will be left in place, so you should not have to restore it.
However, you MUST pay attention to build numbers. Here are the steps involved:
1. Back up your database
2. Determine the current build number
3. Find your original Service2000 installation CD and determine it's build number
4. Find any Service2000 update CD media
5. Reinstall Service2000 right over your existing installation.
6. Update it from any update CDs
7. Perform any web updates that might be available.
8. Start Service2000 and verify build number.
Network Edition systems: Reinstall the Service2000 Network Client on the affected PC and then update it (from the server).
If you have any question about this, it is best that you call GenesisFour Technical Support before proceding.
|
 |
|
|
|
No Related Articles Available.
|
|
|
|
|
No Attachments Available.
|
|
|
|
|
No Related Links Available.
|
|
|
|
|
|
|
|
|
|
No user comments available for this article.
|
|
|
|
|
|
|