Problem: I have successfully installed IB 4.2/5.x as a service on a NT W/Station, but all of a sudden it refuses to start with an Access Denied 0005 error. Solution: ** Windows NT w/NTFS file system (the SYSTEM account info below will not apply to a FAT file system) Make sure the SYSTEM account has privileges to the InterBase directory. Also, verify the registry key points to the InterBase directory. The key to look at for IB 4.2 is: HKEY_LOCAL_MACHINE SOFTWARE Borland InterBase CurrentVersion. The key to look at for IB 5.x is: HKEY_LOCAL_MACHINE SOFTWARE InterBase Corp InterBase CurrentVersion. Verify the RootDirectory key is pointing to the InterBase directory. Re: SYSTEM ACCOUNT The system account is a little more limited than Administrator. It is an account that NT creates automatically, and one in which most of the services run. It gives full access to the machine (with no network accessibility). The InterBase service, by default, will run as SYSTEM. Giving Administrator privileges to the directory is NOT enough to allow the service to start and run. You must allow the SYSTEM account access to the directory. If, in explorer, you check the permissions on the directory you can show users to get a list of all users. Right click on the interbase directory and select the 'Security' tab. The SYSTEM account will show up in this list. If SYSTEM is not listed there you must add it. You must grant, at least, the SYSTEM account read/write/execute privileges in the interbase dir and subdirs. Source: Brett Bandy - Mers listserve ---------------------------------------------------------------------------------------------- If the InterBase kit is version 4.1, check and see if long directory name (like the default directory /program files/borland/) is used or not. If so, shorten the directory name.
Last Modified: 26-OCT-00