Service keeps stopping

[Former Member]

Hi,

I have a SQL Anywhere database that is used by SAP Business Objects for its repository database.

I've tried to move the db files but couldn't get the db started again. So I moved the db files back to their original location. However, the database service that was created by SAP Business Objects keeps stopping now.

Do I need the db with a different start line, could that be the problem? I can get the database to start, it just stops after some time.

In the EventViewer I get this message:

The description for Event ID 1 from source SQLANY 12.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

SQLANYs_BOE120SQLAW Cannot access "C:Program Files (x86)Business ObjectsSQLAnyWhere12BinBOE120_AUDIT.db": another process may be using the file

[VolkerBarth]

Besides Dan's suggestion, using -o on the server command line might be worthwhile - cf. this answer...

[jeff_albion]

SQLANYs_BOE120SQLAW Cannot access "C:\\Program Files (x86)\\Business Objects\\SQLAnyWhere12\\Bin\\BOE120_AUDIT.db": another process may be using the file

This error is suggesting that the database server can't access the database file (e.g. the permissions have changed or another process is already reading the database file - another database service, perhaps?), thus you can't start the requested database service.

You can see which process may have a lock on this file by checking with an OS file-locking utility, such as:

• handle
• Process Explorer (Find -> Find Handle or DLL...)
• Unlocker

Otherwise, you should trace the database start-up activities with Process Monitor to see if there are any logged permission errors in that output trying to access the database file on the file system.

[Dan_Cummins]

To troubleshoot this I suggest retrieving the command line that the service is trying to start, then run that manually from the command line, to get more details about what is happening.

To get the names of the installed SA services you can use:

dbsvc -l

The name of the service above appears to be "BOE120SQLAW". You can retrieve the command line being run by that SA service using something like the following:

dbsvc -cm -g BOE120SQLAW

HTH, Dan