Architecting, installing and maintaining your SAS environment

No MetadataServer listener was detected.

Reply
New Contributor
Posts: 3

No MetadataServer listener was detected.

I'm trying to upgrade our 9.3 to 9.4 but I got this error message:

____________________________________________________________________________________________

The following problem was encountered while configuring SAS Metadata Server Configuration:

No MetadataServer listener was detected. Host=XXXXX.DomainName.local. Port=8561.

Configuration script:

C:\Program Files\SASHome2\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml

For more information, see the log file located at

C:\SAS\Config\Lev1\Logs\Configure\metadatasrv_configureMetadata_2016-04-22-12.05.54.log

You should confirm that this configuration error will not lead to errors with other products before ignoring
the error by answering Yes or Yes to All to the continuation question below. If you select Yes or Yes to All,
you will not be able to retry any ignored steps without completely unconfiguring and then configuring again.
If you are uncertain, contact SAS Technical Support for guidance before continuing with this deployment.

Would you like to continue with the remaining configuration steps?

________________________________________________________________________________________________________

 

And this is what it says in the log:

 

<var name="metadatasrv.server.is.running"  unset="true" />
            <var name="metadatasrv.recover.is.allowed" unset="true" />
            <var name="metadatasrv.running.as.service" unset="true" />
            <propertyregex property="metadatasrv.windows.server.state.tag" input="${metadatasrv.windows.server.state.line}" regexp=".*STATE.*:.*[0-9]  ([A-Z]*) $" select="\1" casesensitive="true" />
            <if><equals arg1="${metadatasrv.windows.server.state.tag}" arg2="RUNNING" casesensitive="True"/>
               <then>
                  <echo message="The service &quot;${local.metadatasrv.service.name}&quot; is running." />
                  <property name="metadatasrv.server.is.running"  value="true"  />
                  <property name="metadatasrv.recover.is.allowed" value="false" />
                  <property name="metadatasrv.running.as.service" value="true"  />
               </then>
               <else>
                  <echo message="The service &quot;${local.metadatasrv.service.name}&quot; is not running." />
                  <property name="metadatasrv.server.is.running"  value="false" />
                  <property name="metadatasrv.recover.is.allowed" value="true"  />
                  <property name="metadatasrv.running.as.service" value="true"  />
               </else>
            </if>
         </then>
         <else>
            <var name="metadatasrv.server.is.running"  unset="true" />
            <var name="metadatasrv.recover.is.allowed" unset="true" />
            <if><isset property="onZosHosts"/>
               <then>
                  <!-- ensure z/OS server.HOSTNAME.pid file exists and the port is listening -->
                  <waitfor timeoutproperty="noMetadataServerListener" maxwait="${metadataserver.listener.zos.timeout}" maxwaitunit="second" checkevery="2" checkeveryunit="second">
                     <and>
                        <available file="${metadatasrv.config.dir}/${metadatasrv.pid.filename}"/>
                        <socket server="${iomsrv.metadatasrv.}" port="${iomsrv.metadatasrv.port}"/>
                     </and>
                  </waitfor>
               </then>
               <else>
                  <waitfor timeoutproperty="noMetadataServerListener" maxwait="${metadatasrv.listener.timeout}" maxwaitunit="second" checkevery="2" checkeveryunit="second">
                     <socket server="${iomsrv.metadatasrv.host}" port="${iomsrv.metadatasrv.port}"/>
                  </waitfor>

 

Where the error says "Host=XXXXX.DomainName.local. Port=8561." The XXXXX.DomainName I edited to that but in that name, our server name has an underscore there and would have been XX_XXX.DomainName but the wizard wouldn't let me enter the "_" in some steps but in others, I was able to enter the complete name with the underscore.

 

Could the unerscore in our server name be causing the problem?

 

This is only my 2nd time upgrading and both times are 9.3 to 9.4. I didn't have any problems the first time I upgraded.

Super User
Posts: 5,256

Re: No MetadataServer listener was detected.

A quick search at support.sas.com indicates that there are some issues with underscores within host names when it comes to the Web and mid tiers.
So a general guideline would be to avoid such naming.
But if you wish to keep the host name intact I sugest that you open a track to SAS tech support.
Data never sleeps
New Contributor
Posts: 3

Re: No MetadataServer listener was detected.

Thank you.

 

I actually spent a couple days looking through as much as I could to find any indication one way or another about naming and any issues but my searches kept coming empty. Not sure why except I must used wrong search criteria somehow.

 

Would it be easier to rename the server?

 

This server's been set up for a few years now so there's other network issues to consider.

Super User
Posts: 3,106

Re: No MetadataServer listener was detected.

I would say there is enough evidence to confirm having underscores in SAS server host names is not a good idea:

 

http://support.sas.com/kb/51/129.html

 

All SAS installs I've been involved with stick with just alpha characters. The fact that you have been unable to specify an underscore during the install process is another indication.

 

I'd suggest discussing the implications of a name change with your IT guys.

 

 

New Contributor
Posts: 3

Re: No MetadataServer listener was detected.

Exactly what I was thinking even before the error came up.

 

Some windows in the wizard will let me enter the underscore and some won't which is why I wasn't too surprised to see this error.

Ask a Question
Discussion stats
  • 4 replies
  • 632 views
  • 0 likes
  • 3 in conversation