Differences
This shows you the differences between two versions of the page.
chapi_-_the_chapi_service_is_not_available [2019/01/30 09:22] |
chapi_-_the_chapi_service_is_not_available [2019/01/30 09:22] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== | ||
+ | |||
+ | **Issue**: CHAPI will sometimes not communicate with the SSLIP properly, and will provide this error on the startup of the SSLIP. There are a few basic things to check when you receive this error message, which is shown below. | ||
+ | |||
+ | |||
+ | |||
+ | {{:: | ||
+ | |||
+ | |||
+ | |||
+ | ==== Issue 1: The Chapi service is installed properly and is simply not running. ==== | ||
+ | |||
+ | |||
+ | |||
+ | ====**Steps to resolve**==== | ||
+ | - Go to your Start Menu or Start Screen and type " | ||
+ | - Locate CHAPI.ServiceHost_12556 and confirm that the service does not say Started in the Status column | ||
+ | - If the service is not currently running, click on Start in the upper left side of this window, shown below{{:: | ||
+ | - Once you have done this the service should start properly and will look like the picture below{{:: | ||
+ | - From there you should attempt to start the SSLIP. If you still get the same error, then proceed to Issue 2 below. | ||
+ | |||
+ | |||
+ | |||
+ | ==== Issue 2: The Chapi databases are not actually connected or available. ==== | ||
+ | |||
+ | |||
+ | |||
+ | ====**Steps to resolve**==== | ||
+ | - Open up SQL Studio Management Studio and log into the instance that the SSLIP is pointed at. | ||
+ | - Verify that the Chapi and Chapi_Logging databases are currently there. | ||
+ | - If they are missing, or not attached yet, it will look like the picture below | ||
+ | |||
+ | |||
+ | |||
+ | | ||
+ | - If Chapi is not here, and is not being created by the SSLIP, it probably means that there is a copy of a Chapi database already created on your system that isn't attached yet. | ||
+ | - Open up a Windows Explorer window, and go to the following location: C:\Program Files\Microsoft SQL Server\MSSQL11.CYRIOUS\MSSQL\DATA{{:: | ||
+ | - Verify that you have the databases available as shown above. | ||
+ | - If your Chapi and Chapi_Logging databases are available, go back to your SQL instance, and attach them manually. | ||
+ | - After you have attached the two databases, you should restart your SQL Server service for the Cyrious instance, as well as the Chapi service. | ||
+ | - Once both of those services have restarted, you should attempt to start the SSLIP. | ||
+ | |||
+ | **Note:** If you have completed both of these steps, and you are receiving the same error, a complete reinstall of Chapi may be required. | ||
+ | |||
+ | |||
+ | |||
+ | ==== Issue 3: The Chapi Service is pointed to the wrong location. ==== | ||
+ | |||
+ | |||
+ | |||
+ | ====**Steps to resolve**==== | ||
+ | - Open the services screen (services.msc). | ||
+ | - Double Click on the CHAPI.Service_Host_12556 service. | ||
+ | - Note the **Path to executable**. | ||
+ | |||
+ | **Note:** If this path is not correct, it can be changed in the server' | ||
+ | - Turn off the CHAPI service if it is currently running. | ||
+ | - Open the registry and back it up. | ||
+ | - Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CHAPI.ServiceHost_12556 | ||
+ | - Change the ImagePath to the correct CHAPI folder. | ||
+ | - Ensure the **CHAPI.ServiceHost.exe.config** file has the correct information in that location. | ||
+ | - Start the CHAPI Service. | ||
+ | - Launch the SSLIP. | ||
+ | |||
+ | |||
+ | |||