System Administrator Guide > System Administrator Guide > Troubleshooting Actian Ingres > Troubleshoot Startup, Shutdown, or Configuration Problems > Check Actian Ingres Installation on Windows
Was this helpful?
Check Actian Ingres Installation on Windows
To check if the installation is working fine, follow these steps:
1. Check that you are logged in as the installation owner. If not, log off and log in again as this user.
2. Check that all users have II_SYSTEM set by issuing the following command at the operating system prompt:
echo %II_SYSTEM%
All users must have Actian Ingres executables in their path variables. Check that everyone has the full search path to %II_SYSTEM%\ingres\bin.
The installation owner must also include %II_SYSTEM%\ingres\utility.
3. Check that each of the Actian Ingres variables has a valid value.
Actian Ingres environment variables are only used and “seen” by Actian Ingres and can be displayed with the following command entered at the operating system prompt:
ingprenv
If you are in doubt about the function or legal value of a particular environment variable, see the chapter “Setting Environment Variables” and the appendix “Environment Variables.”
Actian Ingres environment variables denoting installation locations cannot be reset. To change these, you must unload the databases, rerun the installation program, and reload the databases, as described in Installation Locations on page 112.
4. Check the Actian Ingres environment variables that have been set locally, overriding the installation-level definitions.
Only a small category of Actian Ingres environment variables must be defined in the local user environment: those that permit you to access Actian Ingres, and those that define values that are different for your local environment. They include TERM_INGRES and ING_EDIT.
If you trace the problem to a Actian Ingres environment variable setting, correct the value. For procedures and scenarios for setting these variables, see the chapter “Setting Environment Variables.” If the installation does not start up, continue with this procedure.
5. Check that all Actian Ingres processes are shut down. If there are processes that continue to run, see Check Shutdown Problems on Windows.
6. Restart Actian Ingres. Attempt once again to start up the installation by issuing the following command at the operating system prompt:
ingstart
If startup problems persist, continue diagnostics in the Detect Startup Problems section.
Detect Actian Ingres Startup Problems on Windows
To troubleshoot startup problems on Windows, follow these steps:
1. Determine which Actian Ingres processes are running.
2. Verify that all required Actian Ingres system processes are running. The following processes are the minimum required for a complete installation:
iigcn
Name Server process
iigcc
Communications Server process (present only on sites with Ingres Net)
II_IUSV_nnn
Recovery Server process
dmfacp
Archiver process
iidbms
DBMS Server process
iigcd
Data Access Server process
iistar
Star Server process (present only on sites with Ingres Star)
rmcmd
Remote command process
iigcb
Bridge Server process (present only on sites with Ingres Bridge)
3. If ingstart does not complete successfully, do the following:
b. Check the output from ingstart. This is saved in the file:
%II_SYSTEM%\ingres\files\ingstart.log
Error log files and individual component log files are listed in Logging and Locking Systems on page 35.
c. Try to determine the reason for startup failure.
d. A process failed to start. If a process failed to start, continue on to the detailed sections on startup problems for that specific process.
Last modified date: 07/21/2025