Login PI Troubleshooting

Description	Screenshot
To troubleshoot engine issue engine debugging should be turned on. Open Microsoft SQL Server Management Studio
Open the database and the tables Edit the top 200 rows of the dbo.WorkloadSettings table
Change the EngineDebug and WorkloadDebug value to true
The engine will show the label in red which indicate debug mode is enabled
Log files are located in %TMP%\PI\DebugLogging\

Launcher debugging

Description	Screenshot
To troubleshoot launcher issues debugging should be turned on. Open Microsoft SQL Server Management Studio
Open the database and the tables Edit the top 200 rows of the dbo.WorkloadSettings table
Change the LauncherDebug value to true. The Login PI server will now provide more LauncherDebug information (for example, why the scheduled sessions are not initiating).
The LauncherDebug information can be found in the windows Event Log.

Engine error: 8002009

Description	Screenshot
Engine will report A com error occured This is caused by an access denied to the database
Verify if the user has access to the database Please see the verify installation section
Open the DDBC Data Sources to validate access to the database
Click Add
Select SQL Server
Provide a name and enter the server name Click next
Click Next
This error displays the current user has no access to the database You have to make sure the user can access the database and has the correct permissions See section verify installation
When the connection to the database is successful in the Data source probably the problem is located in the database.config The database.config can be found on two location The database.config located on the \\PIserver\shared\bin\target\ is the main which is copied to %tmp%\PI\Runtime in the target machine
For quick troubleshooting editing the local database.config is the quickest way to verify if the connection details Edit the database.config and you will see this connection is encrypted by default
Replace the encrypted string with the following details: <appSettings> <add key="Username" value="" /> <add key="Password" value="" /> <add key="IntegratedSecurity" value="True" /> <add key="ProviderName" value="System.Data.SqlClient" /> <add key="Datasource" value="RB-SQL02\SQL,1433" /> <add key="InitialCatalog" value="LoginPI" /> </appSettings> It is important to change the datasource including the servername\instace,portnumber Change the initialCatalog to the database name
Save the database.config and start the engine
If the connection is correct the engine will run

Engine error: SessionLog not found

Description	Screenshot
Engine will report SessionLog not found The launched session could be found in the database probably because of the missing domain name
In the target machine go to %TMP%\PI\DebugLogging\ and open the PI_Debug_E.log file
The query is logged which can be used to verify the results The query is located under the sentence: User <username> logging on
Open SQL management studio and make a new query Copy the query from the target machine and execute the query
The result will show Msg 208, Level 16, State 62
Open the dbo.SessionLogs table The UserName in the table does not match the UserName in the session
Open the dbo.ConnectionUsers table Verify if the connection name is correct, if not remove and add the user form the interface Restart the job and close the Microsoft SQL Server Management Studio Restart the PILauncher The error is now solved

The launcher seems to be stuck

Description	Screenshot
It can happen the launcher is not launching any sessions for a while
Open the interface and and select Jobs
Click the reset button
When resetting a job you have to make sure all sessions are logged out Click Ok
The launcher will reset the job and start on the scheduled interval

No queued session for launcher

Description	Screenshot
It can happen that the launcher is not launching any sessions at all and just idles. While everything is correctly configured: - A profile is created and selected, - Workload settings are configured/saved, - A connection is configured, user is provided and the connection type is enabled, - A dataserver is configured and enabled, - A webserver is configured and enabled, - A Launcher is configured, added to the profile and enabled, - A job is configured, start date/time, interval is set and the job is enabled - The Launcher.exe agent is running (connected successfully with the PI-database) To troubleshoot these launcher issues debugging should be turned on. Open Microsoft SQL Server Management Studio
Open the database and the tables Edit the top 200 rows of the dbo.WorkloadSettings table
Change the LauncherDebug value to true. The Login PI server will now provide more LauncherDebug information (for example, why the scheduled sessions are not initiating).
The LauncherDebug information can be found in the windows Event Log.

VMware Horizon View Executable path does not exist

Description	Screenshot
When using the connector VMware Horizon View 5.x or 6.x the launcher is reporting the executable path cannot be found This can be caused when a x86 version is installed on a x64 operating system
Verify the location of the VMware Horizon View client on the launcher machine The directory is “Program Files (x86)” instead of “Program Files”
Open SQL management studio and open the dbo.Connectors table Here the connectors are located
Change the path of VMware Horizon View 5.x and 6.x
Start the launcher and make sure the Job is running The launcher will get the correct location from the database and can successfully start the connection (when properly configured)