bcappservice.exe error

[hindtm]

Hello,

We recently purchased bell commander for use at our business to signal break times and end of shift. It has been working great. However, in the eventlog of the computer running bell commander there are many, many application events similar to:

Type: Error
Source: bcappservice.exe
Event ID: 0
Message: Access violation at address 00404C5A in module 'bcappservice.exe'. Read of address 00000001

The service continues to run and sound the "bells" but as I have an system that monitors all our servers event logs for errors it is constantly alerting me.

[admin]

The BellCommander logs in the \Program Files\BellCommander\logs table will have additional information on any errors and when they occured. The log files are standard text files that can be viewed in Notepad or another text editor. You can also email the errors to us and we'll look at the log files.

One of the more common problems is that there could be a corruption on a table. This can occur if there is a hard disk problem or if the PC was shut off immediately due to a power outage or someone holding the power button to turn off the computer. There is also a database tool from the third party database company that will check the tables and repair them. To use the maintenance tool on BellCommander 4.x releases:
1. Download the tool at http://www.acrovista.com/bellcommander/dbsys4.zip
2. Unzip the files and run dbsys.exe.
3. Exit BellCommander and stop the BellCommander Application Service if the service version was installed.
4. Select Utilities|Repair Table.
5. Click the Select button and select the \Program Files\BellCommander\Data directory.
6. Select all tables from the Available Tables list.
7. Check Force index rebuild.
8. Click the Repair button and the process to complete.
9. Close the Database System Utility and start the BellCommander Application Service and BellCommander.

[hindtm]

There wasn't any more error information in the bell commander logs but the database repair tool did the trick. After following your instructions so far no more errors in the event log. Thanks for your timely and helpful information.