https://communities.sas.com/t5/SAS-Data-Management/metadata-cluster-problem-in-quorum/m-p/483295#M15068 <P>Hi all,</P><P>Problem of connecting data management server as Object spawner is not UP</P><P>&nbsp;</P><P>we have 3 metadata data servers but we have made it only one metadata is is active (no quorum) after restart all the servers&nbsp;</P><P>the data management server object spawner is not up.</P><P>&nbsp;</P><P>thanks in advance!</P> Thu, 02 Aug 2018 06:59:25 GMT vallsas 2018-08-02T06:59:25Z https://communities.sas.com/t5/SAS-Data-Management/metadata-cluster-problem-in-quorum/m-p/483295#M15068 <P>Hi all,</P><P>Problem of connecting data management server as Object spawner is not UP</P><P>&nbsp;</P><P>we have 3 metadata data servers but we have made it only one metadata is is active (no quorum) after restart all the servers&nbsp;</P><P>the data management server object spawner is not up.</P><P>&nbsp;</P><P>thanks in advance!</P> Thu, 02 Aug 2018 06:59:25 GMT https://communities.sas.com/t5/SAS-Data-Management/metadata-cluster-problem-in-quorum/m-p/483295#M15068 vallsas 2018-08-02T06:59:25Z https://communities.sas.com/t5/SAS-Data-Management/metadata-cluster-problem-in-quorum/m-p/484322#M15105 <P>The Data Management Servers do not always start automatically. Sometimes there is a timing issue and they attempt to start but fail when the metadata server is not running. Double-check in SAS Metadata Console that your DM Server configuration is pointing to the right metadata server and then try to manually restart DM Server. Look in the DM Server directory structure to find the log that might give you more information.</P> <P>&nbsp;</P> <P>Two common things that prevent DM Server from starting is that it can't connect to a metadata server or something is misconfigured, like pointing to a nonexistent log file location.</P> <P>&nbsp;</P> <P>Ron</P> Mon, 06 Aug 2018 11:49:13 GMT https://communities.sas.com/t5/SAS-Data-Management/metadata-cluster-problem-in-quorum/m-p/484322#M15105 RonAgresta 2018-08-06T11:49:13Z