Default host is invalid error when running reports
Issue/Symptom/Question
In the test database, we are receiving the following error running PENTA legacy reports.
"The default host you have set up is not valid. The default host is the name of the server on which the reports will be run. This is setup in the 'Preferences' window of the 'Report Initiation' window."
Applies To
Penta for Windows
Linux server
PENTA Legacy Reports
Resolution/Fix/Answer
This error usually happens when the process SYP105 is not running on the Linux server.
Checking the Status of SYP105
Log in to the Linux server as the ‘penta’ user.
At the command line type in ‘bgrptctl status’, you should see the following if SYP105 is running. The output can vary depending on the number and name of your environments.
Comand Output
prod.penta: SYP105 RUNNING train.penta: SYP105 RUNNING test.penta: SYP105 RUNNINGIf you see the following output, then SYP105 is not running
prod.penta: SYP105 NOT RUNNING train.penta: SYP105 NOT RUNNING test.penta: SYP105 NOT RUNNING
Starting SYP105
Log in to the Linux server as the ‘penta’ user.
Type in the following command to start SYP105: ‘bgrptctl start’
Type in the command ‘bgrptctl status’ again to find out if SYP105 is running.
If this issue is not resolved, try stopping and starting the SYP105 process
Stopping and starting SYP105
Type 'bgrptctl stop'
Type 'bgrptctl start'
If this issue is not resolved, it could be an issue with the default_host value in the user_preferences table. The default_host value should be set to the name of the Linux Server.
Login to the database using SQL Plus or Golden
The following query will return the value of default_host in the user_preferences table:
select * from user_preferences where key_name = 'default_host'
If the default_host value is incorrect, you can run the following SQL to update the default_host (Replace ruby with the name of your Linux Server)
update user_preferences set pref_text = 'ruby' where key_name = 'default_host'
If this issue is still not resolved, please submit a Service Desk ticket and reference this article.