<?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 Re: 9.4 M7 to 9.4 M8 UIP - failing at configuration step in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918467#M28075</link>
    <description>&lt;P&gt;In that case I suggest you open a Tech Support track for your problem. I'm assuming that your metadata server has all services running.&lt;/P&gt;</description>
    <pubDate>Thu, 29 Feb 2024 19:07:06 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2024-02-29T19:07:06Z</dc:date>
    <item>
      <title>9.4 M7 to 9.4 M8 UIP - failing at configuration step</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918359#M28071</link>
      <description>&lt;P&gt;I am working on UIP from 9.4 M7 to 9.4 M8 on Linux 7.9 environment. The installation was successful, when it comes to the configuration step, the connection to the metadata server keeps failing using the &lt;A href="mailto:sasadm@saspw" target="_blank"&gt;sasadm@saspw&lt;/A&gt;&amp;nbsp;user. sasauth.conf is set use PAM Authenticaion, I've also added the openssl lib to the path. I've already opened a case for this, but it is moving really slow. If any of you faced this issue or have some ideas, I would really appreciate it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2024-02-28T14:36:39,045 INFO [00000032] 2:sas - Client connection 2 for user sasadm@saspw closed.&lt;BR /&gt;2024-02-28T14:36:39,045 DEBUG [00000032] 2:sas - SecurityTokenDestroy: calling bkTokenDestroy(a0acd080)&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - SecurityThreadSetIdentity [ENTER]: 7fe256f30c00 provider:1&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - Create Authenticated Token&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - Client connection id: 4&lt;BR /&gt;2024-02-28T14:37:55,153 DEBUG [00000035] :sas - User/Pass authentication for user sasadm@saspw&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - User: sasadm, domain: saspw&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - Domain match found&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - Calling auth provider(3)...&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - Internal account provider called for user sasadm&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - Provider domain: saspw&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - Validating incoming internal user: sasadm&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - IOM CALL {compRef:7fe29404d4c0}-&amp;gt;OMI::InternalAuthentication():&lt;BR /&gt;2024-02-28T14:37:55,153 TRACE [00000035] :sas - PUBLIC Credential obtained for &amp;lt;ANONYMOUS&amp;gt;. This is normal during internal authentication.&lt;BR /&gt;2024-02-28T14:37:55,153 DEBUG [00000035] :sas - GetCookie: Task CONTEXT 0000002F getting cookie number 16.&lt;BR /&gt;2024-02-28T14:37:56,164 DEBUG [00000035] :sas - PutCookie: Task CONTEXT 0000002F returning cookie number 16.&lt;BR /&gt;2024-02-28T14:37:56,164 TRACE [00000035] :sas - IOM RETURN 0={compRef:7fe29404d4c0}-&amp;gt;OMI::InternalAuthentication():&lt;BR /&gt;retval=0&lt;BR /&gt;2024-02-28T14:37:56,164 DEBUG [00000035] :sas - Provider failed: 80bfd100&lt;BR /&gt;2024-02-28T14:37:56,164 DEBUG [00000035] :sas - SecurityTokenDestroy: calling bkTokenDestroy(a0acd080)&lt;BR /&gt;2024-02-28T14:37:56,165 TRACE [00000035] :sas - SecurityThreadSetIdentity [EXIT]: 7fe256f30c00 status=0x80bfd100&lt;BR /&gt;2024-02-28T14:37:56,165 WARN [00000035] :sas - New client connection (4) rejected from server port 8561 for user sasadm@saspw. Peer IP address and port are [172.30.93.197]:59458 for APPNAME=ConnectionService 904800.&lt;BR /&gt;2024-02-28T14:37:56,165 INFO [00000035] :sas - Client connection 4 closed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 02:45:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918359#M28071</guid>
      <dc:creator>Sainathns</dc:creator>
      <dc:date>2024-02-29T02:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: 9.4 M7 to 9.4 M8 UIP - failing at configuration step</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918362#M28072</link>
      <description>&lt;P&gt;I think you need to use an OS account for configuration, not a SAS metadata account. The SAS install account is a good choice.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 03:15:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918362#M28072</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2024-02-29T03:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: 9.4 M7 to 9.4 M8 UIP - failing at configuration step</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918363#M28073</link>
      <description>&lt;P&gt;Thanks for your reply. So, I am using &lt;A href="mailto:sasadm@saspw" target="_blank"&gt;sasadm@saspw&lt;/A&gt;&amp;nbsp;which is an internal account. I tried your suggestion and used sas user which is the OS account, it still gives the same error "Unable to connect to a SAS Metadata Server with the specified connection information"&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 03:37:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918363#M28073</guid>
      <dc:creator>Sainathns</dc:creator>
      <dc:date>2024-02-29T03:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: 9.4 M7 to 9.4 M8 UIP - failing at configuration step</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918467#M28075</link>
      <description>&lt;P&gt;In that case I suggest you open a Tech Support track for your problem. I'm assuming that your metadata server has all services running.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 19:07:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918467#M28075</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2024-02-29T19:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: 9.4 M7 to 9.4 M8 UIP - failing at configuration step</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918834#M28104</link>
      <description>&lt;P&gt;Yes, A Track has already been opened and have been told that this is an isolated issue and no one has reported so far. I will update this thread when we have found a solution.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 14:35:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/9-4-M7-to-9-4-M8-UIP-failing-at-configuration-step/m-p/918834#M28104</guid>
      <dc:creator>Sainathns</dc:creator>
      <dc:date>2024-03-04T14:35:36Z</dc:date>
    </item>
  </channel>
</rss>

