Difference between revisions of "Login PI Troubleshooting"

From Login VSI Documentation
Jump to: navigation, search
(No queued session for launcher)
(Troubleshooting)
 
(52 intermediate revisions by 7 users not shown)
Line 1: Line 1:
===Troubleshooting===
+
==Troubleshooting==
This section will describe how to troubleshoot certain issues.
+
To troubleshoot certain issues, please check out our list of [https://loginvsi.zendesk.com/hc/en-us/sections/115000450649-Troubleshooting Knowledge Base] articles that deal with various problems.
  
====Installer debugging====
+
Please also check out our [https://loginvsi.zendesk.com/hc/en-us/sections/115000458625-Known-Issues Known Issues] section for greater details on any recurring problems.
  
To create a logfile of the newest installer please start the installer in a command prompt with the following command:
+
==Logging==
 +
''Information on how to enable various degrees of debugging information.  This will assist in isolating issues within your PI configuration.''
  
<nowiki>msiexec /i "C:\PI-Setup.msi" /l*v "c:\log.log"</nowiki>
+
PI log files are kept in:
 +
''%ProgramData%\Login VSI\Login PI\logs''
 +
This includes normal log-level logging
  
====Engine debugging====
+
'''[https://www.loginvsi.com/blog/487-debugging-login-pi-workloads Debugging Login PI Workloads]'''
 +
 
 +
===Installer debugging - v1.1.21 & later===
 +
 
 +
To create an installation please start the installer in a command prompt with the following command:
 +
 
 +
''<nowiki>msiexec /i "C:\PI-Setup.msi" /l*v "c:\log.log"</nowiki>''
 +
 
 +
===Launcher Logging - v1.1.21 & later===
 +
''Setting logging to true will enable debugging for the launcher component''
 +
 
 +
Log Name - ''%ProgramData%\Login VSI\Login PI\logs\launcher-{Date}.txt''
 +
 
 +
''C:\ProgramData\Login VSI\Login PI\Configuration\launcher.json, “Logging”: true/false''
 +
 
 +
===Launcher Identity Protection Debugging - v1.1.21 & later===
 +
''Enabling this debugging, logs the key exchange actions between the Launcher and the management server''
 +
 
 +
Log Name - ''%ProgramData%\Login VSI\Login PI\logs\launcherIDP-{Date}.txt''
 +
 
 +
''C:\ProgramData\Login VSI\Login PI\Configuration\launcher-idp.json'', “EnableLogging”: true/false
 +
 
 +
===Target Identity Protection Debugging - v1.1.21 & later===
 +
''Enabling this debugging, logs the key exchange actions between the Engine (within session) and the management server''
 +
 
 +
Log Name - ''%ProgramData%\Login VSI\Login PI\logs\targetIDP-{Date}.txt''
 +
 
 +
''C:\ProgramData\Login VSI\Login PI\Configuration\target-idp.json'', “EnableLogging”: true/false
 +
 
 +
===Debugging Launching Sessions - v1.1.21 & later===
 +
''Enabling debugging will log events from the launcher (user) to the target environment''
 +
 
 +
Log name  - ''%ProgramData%\Login VSI\Login PI\logs\server-{Date}.txt''
 +
 
 +
''C:\ProgramData\Login VSI\Login PI\Configuration\sessionbroker.json', “EnableLogging”: true/false
 +
 
 +
==Engine debugging==
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
Line 34: Line 73:
 
Open the database and the tables
 
Open the database and the tables
  
Edit the top 200 rows of the dbo.WorkloadSettings table
+
Edit the top 200 rows of the ''dbo.WorkloadSettings'' table
  
  
Line 43: Line 82:
 
|-
 
|-
 
|
 
|
Change the EngineDebug and WorkloadDebug value to true  
+
Change the ''EngineDebug'' and ''WorkloadDebug'' values to true  
  
 
|
 
|
Line 58: Line 97:
 
|-
 
|-
 
|
 
|
Log files are located in %TMP%\PI\DebugLogging\
+
Log files are located in ''%TMP%\PI\DebugLogging\''
  
 
|
 
|
Line 64: Line 103:
 
|}
 
|}
  
====Launcher debugging====
+
====Configuration Error: initialization of database failed. No connection could be made because the target machine actively refused it====
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
Line 75: Line 114:
 
|-
 
|-
 
|
 
|
To troubleshoot launcher issues debugging should be turned on.
+
Steps on fixing the error
 +
“initialization of database failed. No connection could be made because the target machine actively refused it”
  
Open Microsoft SQL Server Management Studio
+
Note: This assumes that you will be using the default SQL Ports.
  
  
  
  
 +
|
 +
[[File:PI_Conf_Error_step1.png|400px|thumb]]
  
 +
|-
 
|
 
|
[[File:ED1.png|400px|thumb]]
+
Step 1: Open the SQL Server Configuration Manager
  
|-
 
 
|
 
|
Open the database and the tables
 
  
Edit the top 200 rows of the dbo.WorkloadSettings table
 
  
 +
|-
 +
|
 +
Step 2: Make sure that TCP/IP is enabled
  
  
 
|
 
|
 +
[[File:PI_Conf_Error_step2.png|400px|thumb]]
  
[[File:ED2.png|400px|thumb]]
 
 
|-
 
|-
 
|
 
|
Change the LauncherDebug value to true
+
Step 3: Now Right Click on TCP/IP and go to Properties
  
 +
|-
 
|
 
|
[[File:LD1.PNG|400px|thumb]]
+
Step 4: Then open the IP Addresses Tab, and change the TCP Port under IP1 and change it to 1422
 +
 
  
|-
 
 
|
 
|
The Login PI server will now provide more LauncherDebug information (for example, why the scheduled sessions are not initiating).  
+
[[File:PI_Conf_Error_step4.png|400px|thumb]]
 
 
  
 +
|-
 
|
 
|
 +
Step 5: Now scroll down the list to IPAll and change the TCP Port to 1433
  
  
|-
 
 
|
 
|
The LauncherDebug information can be found in the windows Event Log.
+
[[File:PI_Conf_Error_step5.png]]
  
 
|
 
|
[[File:LD2.PNG|400px|thumb]]
 
 
|}
 
|}
  
====Engine error: 8002009====
+
====Engine error: 8002009 - Please be aware the following is valid for version 1.0.1 ONLY====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 133: Line 176:
 
|
 
|
 
Engine will report  
 
Engine will report  
A com error occured
+
A com error occurred
  
 
This is caused by an access denied to the database
 
This is caused by an access denied to the database
Line 372: Line 415:
 
|}
 
|}
  
====The launcher seems to be stuck====
+
==Webpage does not work using hostname or FQDN==
 
 
{| class="wikitable"
 
|-
 
|
 
'''Description'''
 
 
 
|
 
'''Screenshot'''
 
 
 
|-
 
|
 
It can happen the launcher is not launching any sessions for a while
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
|
 
[[File:LS1.png|400px|thumb]]
 
 
 
|-
 
|
 
Open the interface and and select Jobs
 
 
 
 
 
 
 
 
 
|
 
 
 
[[File:LS2.png|400px|thumb]]
 
|-
 
|
 
Click the reset button
 
 
 
 
 
|
 
[[File:LS3.png|400px|thumb]]
 
 
 
|-
 
|
 
When resetting a job you have to make sure all sessions are logged out
 
 
 
Click Ok
 
 
 
 
 
 
 
 
 
|
 
[[File:LS4.png|400px|thumb]]
 
 
 
|-
 
|
 
The launcher will reset the job and start on the scheduled interval
 
 
 
|
 
[[File:LS5.png|400px|thumb]]
 
|}
 
 
 
 
 
====No queued session for launcher====
 
{| class="wikitable"
 
|-
 
|
 
'''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
 
 
 
 
 
 
 
 
 
 
 
|
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
[[File:ED1.png|400px|thumb]]
 
 
 
|-
 
|
 
Open the database and the tables
 
 
 
Edit the top 200 rows of the dbo.WorkloadSettings table
 
 
 
 
 
 
 
|
 
 
 
[[File:ED2.png|400px|thumb]]
 
|-
 
|
 
Change the LauncherDebug value to true
 
 
 
|
 
[[File:LD1.png|400px|thumb]]
 
 
 
|-
 
|
 
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.
 
 
 
|
 
[[File:LD3.png|400px|thumb]]
 
|}
 
 
 
====VMware Horizon View Executable path does not exist====
 
 
 
{| class="wikitable"
 
|-
 
|
 
'''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
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
|
 
[[File:VW1.png|400px|thumb]]
 
 
 
|-
 
|
 
Verify the location of the VMware Horizon View client on the launcher machine
 
 
 
The directory is “Program Files (x86)” instead of “Program Files”
 
 
 
 
 
 
 
 
 
 
 
|
 
 
 
[[File:VW2.png|400px|thumb]]
 
|-
 
|
 
Open SQL management studio and open the dbo.Connectors table
 
 
 
Here the connectors are located
 
 
 
 
 
 
 
|
 
[[File:VW3.png|400px|thumb]]
 
 
 
|-
 
|
 
Change the path of VMware Horizon View 5.x and 6.x
 
 
 
 
 
 
 
 
 
|
 
[[File:VW4.png|400px|thumb]]
 
 
 
|-
 
|
 
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)
 
 
 
 
 
|
 
[[File:VW5.png|400px|thumb]]
 
|}
 
 
 
====Webpage does not work using hostname or FQDN====
 
 
Opening the Login PI Webpage via 'localhost' works.
 
Opening the Login PI Webpage via 'localhost' works.
  
Line 616: Line 438:
  
 
Do you see a 'binding' for the FQDN of the Login PI server? If not, add it and try again.
 
Do you see a 'binding' for the FQDN of the Login PI server? If not, add it and try again.
 +
 +
==Debug logging for 1.0 versions of PI==
 +
'''Session managing logs:'''
 +
 +
Location: C:\Program Files\Login PI\Interface\Web.Config
 +
How to turn on: change the key EnableSessionLogging to true, don’t forget to restart the PI Interface website.
 +
Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\server-{Date}.txt
 +
 +
'''Launcher IDP logs – Identity provider (key exchange for launcher)'''
 +
 +
Location:  C:\Program Files\Login PI\IDP\LauncherIDP\Web.config
 +
How to turn on: change the key UseLogging to true, don’t forget to restart the PI Launcher IDP website.
 +
Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\launcherIDP-{Date}.txt
 +
 +
'''Target IDP logs – Identity provider (key exchange with the Login PI engine)'''
 +
 +
Location:  C:\Program Files\Login PI\IDP\targetIDP\Web.config
 +
How to turn on: change the key UseLogging to true, don’t forget to restart the PI Target IDP website.
 +
Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\targetIDP-{Date}.txt
 +
 +
'''Launcher logs:'''
 +
 +
Location:  C:\Program Files\Login PI\Launcher\Launcher.exe.config
 +
How to turn on: change the key EnableLogging to true
 +
Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\launcher-{Date}.txt
 +
  
 
[[Category:Login PI]]
 
[[Category:Login PI]]

Latest revision as of 11:55, 12 September 2017

Troubleshooting

To troubleshoot certain issues, please check out our list of Knowledge Base articles that deal with various problems.

Please also check out our Known Issues section for greater details on any recurring problems.

Logging

Information on how to enable various degrees of debugging information. This will assist in isolating issues within your PI configuration.

PI log files are kept in: %ProgramData%\Login VSI\Login PI\logs This includes normal log-level logging

Debugging Login PI Workloads

Installer debugging - v1.1.21 & later

To create an installation please start the installer in a command prompt with the following command:

msiexec /i "C:\PI-Setup.msi" /l*v "c:\log.log"

Launcher Logging - v1.1.21 & later

Setting logging to true will enable debugging for the launcher component

Log Name - %ProgramData%\Login VSI\Login PI\logs\launcher-{Date}.txt

C:\ProgramData\Login VSI\Login PI\Configuration\launcher.json, “Logging”: true/false

Launcher Identity Protection Debugging - v1.1.21 & later

Enabling this debugging, logs the key exchange actions between the Launcher and the management server

Log Name - %ProgramData%\Login VSI\Login PI\logs\launcherIDP-{Date}.txt

C:\ProgramData\Login VSI\Login PI\Configuration\launcher-idp.json, “EnableLogging”: true/false

Target Identity Protection Debugging - v1.1.21 & later

Enabling this debugging, logs the key exchange actions between the Engine (within session) and the management server

Log Name - %ProgramData%\Login VSI\Login PI\logs\targetIDP-{Date}.txt

C:\ProgramData\Login VSI\Login PI\Configuration\target-idp.json, “EnableLogging”: true/false

Debugging Launching Sessions - v1.1.21 & later

Enabling debugging will log events from the launcher (user) to the target environment

Log name - %ProgramData%\Login VSI\Login PI\logs\server-{Date}.txt

C:\ProgramData\Login VSI\Login PI\Configuration\sessionbroker.json', “EnableLogging”: true/false

Engine debugging

Description

Screenshot

To troubleshoot engine issue engine debugging should be turned on.

Open Microsoft SQL Server Management Studio



ED1.png

Open the database and the tables

Edit the top 200 rows of the dbo.WorkloadSettings table


ED2.png

Change the EngineDebug and WorkloadDebug values to true

ED3.png

The engine will show the label in red which indicate debug mode is enabled


Login PI Troubleshooting 4.png

Log files are located in %TMP%\PI\DebugLogging\

Login PI Troubleshooting 5.png

Configuration Error: initialization of database failed. No connection could be made because the target machine actively refused it

Description

Screenshot

Steps on fixing the error “initialization of database failed. No connection could be made because the target machine actively refused it”

Note: This assumes that you will be using the default SQL Ports.



PI Conf Error step1.png

Step 1: Open the SQL Server Configuration Manager


Step 2: Make sure that TCP/IP is enabled


PI Conf Error step2.png

Step 3: Now Right Click on TCP/IP and go to Properties

Step 4: Then open the IP Addresses Tab, and change the TCP Port under IP1 and change it to 1422


PI Conf Error step4.png

Step 5: Now scroll down the list to IPAll and change the TCP Port to 1433


PI Conf Error step5.png

Engine error: 8002009 - Please be aware the following is valid for version 1.0.1 ONLY

Description

Screenshot

Engine will report A com error occurred

This is caused by an access denied to the database




ER1.png

Verify if the user has access to the database

Please see the verify installation section



DB6.png

Open the DDBC Data Sources to validate access to the database

ER3.png

Click Add


ER4.png

Select SQL Server

ER5.png

Provide a name and enter the server name

Click next




ER6.png

Click Next


ER7.png

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


ER8.png

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


ER9.png

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


ER10.png

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


ER11.png

Save the database.config and start the engine


ER12.png

If the connection is correct the engine will run

ER13.png

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




ES1.png

In the target machine go to %TMP%\PI\DebugLogging\ and open the PI_Debug_E.log file



ES2.png

The query is logged which can be used to verify the results

The query is located under the sentence: User <username> logging on


ES3.png

Open SQL management studio and make a new query

Copy the query from the target machine and execute the query


ES4.png

The result will show Msg 208, Level 16, State 62

ES5.png

Open the dbo.SessionLogs table

The UserName in the table does not match the UserName in the session




ES6.png

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



ES7.png

Webpage does not work using hostname or FQDN

Opening the Login PI Webpage via 'localhost' works.

Example:


Opening the Login PI Webpage via 'hostname' or 'FQDN' does not work.

Example:


Solution:

Go to the IIS Manager of the Login PI machine and open the bindings for the Login PI interface:

In IIS manager expand sites,

  • Right click PI Interface
  • Select Edit bindings

Do you see a 'binding' for the FQDN of the Login PI server? If not, add it and try again.

Debug logging for 1.0 versions of PI

Session managing logs:

Location: C:\Program Files\Login PI\Interface\Web.Config How to turn on: change the key EnableSessionLogging to true, don’t forget to restart the PI Interface website. Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\server-{Date}.txt

Launcher IDP logs – Identity provider (key exchange for launcher)

Location: C:\Program Files\Login PI\IDP\LauncherIDP\Web.config How to turn on: change the key UseLogging to true, don’t forget to restart the PI Launcher IDP website. Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\launcherIDP-{Date}.txt

Target IDP logs – Identity provider (key exchange with the Login PI engine)

Location: C:\Program Files\Login PI\IDP\targetIDP\Web.config How to turn on: change the key UseLogging to true, don’t forget to restart the PI Target IDP website. Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\targetIDP-{Date}.txt

Launcher logs:

Location: C:\Program Files\Login PI\Launcher\Launcher.exe.config How to turn on: change the key EnableLogging to true Where are the logs stored: default: %ProgramData%\Login VSI\Login PI\logs\launcher-{Date}.txt