Login PI Troubleshooting
Contents
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
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
|
|
|
Open the database and the tables Edit the top 200 rows of the dbo.WorkloadSettings table
|
|
|
Change the EngineDebug and WorkloadDebug values to true |
|
|
The engine will show the label in red which indicate debug mode is enabled
|
|
|
Log files are located in %TMP%\PI\DebugLogging\ |
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.
|
||
|
Step 1: Open the SQL Server Configuration Manager |
| |
|
Step 2: Make sure that TCP/IP is enabled
|
||
|
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
|
||
|
Step 5: Now scroll down the list to IPAll and change the TCP Port to 1433
|
|
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
|
|
|
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
|
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:
- http://<hostname>.<FQDN>:8080/ (http://LoginPI.webserver.net:8080/)
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
