<?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 Failed run shared server in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Failed-run-shared-server/m-p/567621#M16542</link>
    <description>&lt;P&gt;In the process of starting the system I encountered errors when starting the Shared Server (I cite the errors below)&lt;BR /&gt;I basically understand the essence of the error, but I have no idea where to start, what to analyze, to begin to correct the error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;[sas@sastest ~]$ /opt/sas/SASConfig/Lev1/sas.servers status
SAS servers status:
SAS Web Infrastructure Data Server is UP
SAS Metadata Server 1 is UP
SAS Object Spawner 1 is UP
SAS Share Server 1 is NOT up
SAS CONNECT Spawner 1 is UP
SAS DIP Job Runner 1 is UP
SAS JMS Broker is UP
SAS Cache Locator Service ins_41415 is UP
SAS Web Server is UP
SAS Web App Server SASServer1_1 is UP
SAS Web App Server SASServer2_1 is UP
SAS Web App Server SASServer6_1 is UP
SAS Environment Manager is UP
SAS Environment Manager Agent is UP&lt;/PRE&gt;&lt;P&gt;And the error itself&lt;/P&gt;&lt;PRE&gt;NOTE: Libref RESPONSE was successfully assigned as follows: 
      Engine:        XML 
      Physical Name: RESPONSE
Note: Using SAS/SHARE Connection.

NOTE: There were 1 observations read from the data set RESPONSE.SHARECLIENTCONNECTIONS.
NOTE: DATA statement used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      

NOTE: Libref RESPONSE has been deassigned.
NOTE: Fileref REQUEST has been deassigned.
NOTE: Fileref RESPONSE has been deassigned.
NOTE: Fileref MAP has been deassigned.
275        
276        /*
277         *   Start the server listening on the port defined in the metadata
278         *
279         *   Note that currently the value of the environment must contain the "__xxxx" syntax if a true port number is specified (as opposed to a service name).
280         *   This may change in the future.
281         */
282        proc server server=&amp;amp;PORT authenticate=req;
&lt;STRONG&gt;ERROR: The &lt;U&gt;SERVER procedure&lt;/U&gt; cannot be run.&lt;/STRONG&gt;
ERROR: Procedure SERVER not found.
283        run;

NOTE: The SAS System stopped processing this step because of errors.
NOTE: SAS set option OBS=0 and will continue to check statements. This might cause NOTE: No observations in data set.
NOTE: PROCEDURE SERVER used (Total process time):
      real time           0.00 seconds
      cpu time            0.01 seconds
      

ERROR: Errors printed on page 1.

NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414
NOTE: The SAS System used:
      real time           0.10 seconds
      cpu time            0.08 seconds&lt;/PRE&gt;&lt;P&gt;What is the procedure "server" that you want to find the system?&lt;/P&gt;</description>
    <pubDate>Thu, 20 Jun 2019 14:12:06 GMT</pubDate>
    <dc:creator>MichaelMakushev</dc:creator>
    <dc:date>2019-06-20T14:12:06Z</dc:date>
    <item>
      <title>Failed run shared server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Failed-run-shared-server/m-p/567621#M16542</link>
      <description>&lt;P&gt;In the process of starting the system I encountered errors when starting the Shared Server (I cite the errors below)&lt;BR /&gt;I basically understand the essence of the error, but I have no idea where to start, what to analyze, to begin to correct the error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;[sas@sastest ~]$ /opt/sas/SASConfig/Lev1/sas.servers status
SAS servers status:
SAS Web Infrastructure Data Server is UP
SAS Metadata Server 1 is UP
SAS Object Spawner 1 is UP
SAS Share Server 1 is NOT up
SAS CONNECT Spawner 1 is UP
SAS DIP Job Runner 1 is UP
SAS JMS Broker is UP
SAS Cache Locator Service ins_41415 is UP
SAS Web Server is UP
SAS Web App Server SASServer1_1 is UP
SAS Web App Server SASServer2_1 is UP
SAS Web App Server SASServer6_1 is UP
SAS Environment Manager is UP
SAS Environment Manager Agent is UP&lt;/PRE&gt;&lt;P&gt;And the error itself&lt;/P&gt;&lt;PRE&gt;NOTE: Libref RESPONSE was successfully assigned as follows: 
      Engine:        XML 
      Physical Name: RESPONSE
Note: Using SAS/SHARE Connection.

NOTE: There were 1 observations read from the data set RESPONSE.SHARECLIENTCONNECTIONS.
NOTE: DATA statement used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      

NOTE: Libref RESPONSE has been deassigned.
NOTE: Fileref REQUEST has been deassigned.
NOTE: Fileref RESPONSE has been deassigned.
NOTE: Fileref MAP has been deassigned.
275        
276        /*
277         *   Start the server listening on the port defined in the metadata
278         *
279         *   Note that currently the value of the environment must contain the "__xxxx" syntax if a true port number is specified (as opposed to a service name).
280         *   This may change in the future.
281         */
282        proc server server=&amp;amp;PORT authenticate=req;
&lt;STRONG&gt;ERROR: The &lt;U&gt;SERVER procedure&lt;/U&gt; cannot be run.&lt;/STRONG&gt;
ERROR: Procedure SERVER not found.
283        run;

NOTE: The SAS System stopped processing this step because of errors.
NOTE: SAS set option OBS=0 and will continue to check statements. This might cause NOTE: No observations in data set.
NOTE: PROCEDURE SERVER used (Total process time):
      real time           0.00 seconds
      cpu time            0.01 seconds
      

ERROR: Errors printed on page 1.

NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414
NOTE: The SAS System used:
      real time           0.10 seconds
      cpu time            0.08 seconds&lt;/PRE&gt;&lt;P&gt;What is the procedure "server" that you want to find the system?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2019 14:12:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Failed-run-shared-server/m-p/567621#M16542</guid>
      <dc:creator>MichaelMakushev</dc:creator>
      <dc:date>2019-06-20T14:12:06Z</dc:date>
    </item>
    <item>
      <title>Re: Failed run shared server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Failed-run-shared-server/m-p/567629#M16543</link>
      <description>&lt;P&gt;SAS/SHARE contains the SERVER procedure. Run proc setinit and proc product_status to determine if SAS/SHARE is licensed and installed.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2019 14:24:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Failed-run-shared-server/m-p/567629#M16543</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2019-06-20T14:24:36Z</dc:date>
    </item>
  </channel>
</rss>

