<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PSMSR126E [Session ID] Failure occurred while handling session. PSMSR133E [Session ID] Failed to create process D:\Program. Code: 2 (Codes: -1, -1) in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310086#M11712</link>
    <description />
    <pubDate>Sat, 01 Feb 2025 06:57:52 GMT</pubDate>
    <dc:creator>S.Rekadi969059</dc:creator>
    <dc:date>2025-02-01T06:57:52Z</dc:date>
    <item>
      <title>PSMSR126E [Session ID] Failure occurred while handling session. PSMSR133E [Session ID] Failed to create process D:\Program. Code: 2 (Codes: -1, -1)</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310086#M11712</link>
      <description />
      <pubDate>Sat, 01 Feb 2025 06:57:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310086#M11712</guid>
      <dc:creator>S.Rekadi969059</dc:creator>
      <dc:date>2025-02-01T06:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSR126E [Session ID] Failure occurred while handling session. PSMSR133E [Session ID] Failed to create process D:\Program. Code: 2 (Codes: -1, -1)</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310087#M11713</link>
      <description>&lt;P&gt;Hello Connections. Receiving this error for few connection components after upgrading the PSM version from 12.2 to 12.6. Anyone experienced the same? if yes, please help me with the fix.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Feb 2025 07:01:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310087#M11713</guid>
      <dc:creator>S.Rekadi969059</dc:creator>
      <dc:date>2025-02-01T07:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSR126E [Session ID] Failure occurred while handling session. PSMSR133E [Session ID] Failed to create process D:\Program. Code: 2 (Codes: -1, -1)</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310088#M11714</link>
      <description>&lt;P&gt;Review your clientapp and Client Dispatcher for the affected connectors &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/pam-self-hosted/12.6/en/content/pasimp/psm_cc_target_settings.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems to me they're not set up correctly and windows is truncating the path. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also make sure applocker hardening has been performed and the executables for the connectors are there. &lt;/P&gt;</description>
      <pubDate>Sat, 01 Feb 2025 09:04:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310088#M11714</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2025-02-01T09:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: PSMSR126E [Session ID] Failure occurred while handling session. PSMSR133E [Session ID] Failed to create process D:\Program. Code: 2 (Codes: -1, -1)</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310089#M11715</link>
      <description>&lt;P&gt;Hi @Malcolm Murray​&amp;nbsp;&lt;/P&gt;&lt;P&gt;The client invoke type is command line for the connection component in question.&lt;/P&gt;&lt;P&gt;My issue is fixed after giving the exe path in double quotes under the connection components settings.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Feb 2025 20:36:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmsr126e-session-id-failure-occurred-while-handling-session/m-p/1310089#M11715</guid>
      <dc:creator>S.Rekadi969059</dc:creator>
      <dc:date>2025-02-05T20:36:41Z</dc:date>
    </item>
  </channel>
</rss>

