topic Re: 9.4 installation - SAS Metadata Server Configuration Error in Administration and Deployment

9.4 installation - SAS Metadata Server Configuration Error

tvinner — Wed, 20 Jul 2016 02:17:02 GMT

Hi,

installing solution on 1 VM, stuck at configuration step 1:

createService:
[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties
[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties
     [exec] Current OS is Windows Server 2012 R2
     [exec] Output redirected to property: sc.output
     [exec] Executing 'sc' with arguments:
     [exec] 'query'
     [exec] '"SAS [Config-Lev2] SASMeta - Metadata Server"'
     [exec]
     [exec] The ' characters around the executable and arguments are
     [exec] not part of the command.
     [exec] Result: 1060
[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties
[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties
     [echo] execCmd: cmd = C:\SAS\Config\Lev2\SASMeta\MetadataServer\MetadataServer.bat
     [echo] execCmd: cmd.line = install exit
     [echo] execCmd: dir = C:\SAS\Config\Lev2\SASMeta\MetadataServer
     [echo] execCmd: fail = false
     [echo] execCmd: displayLog = false
     [echo] execCmd: logdir = C:\SAS\Config\Lev2\Logs\Configure
     [echo] execCmd: callingTarget = installServices
[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties
[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties
     [exec] Current OS is Windows Server 2012 R2
     [exec] Output redirected to property: stdout
     [exec] Executing 'C:\SAS\Config\Lev2\SASMeta\MetadataServer\MetadataServer.bat' with arguments:
     [exec] 'install'
     [exec] 'exit'
     [exec]
     [exec] The ' characters around the executable and arguments are
     [exec] not part of the command.
     [exec] 'chcp' is not recognized as an internal or external command,
     [exec] operable program or batch file.
     [exec] 'netstat' is not recognized as an internal or external command,
     [exec] operable program or batch file.
     [exec] Result: 255
[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties
[antcall] Exiting C:\Program Files\SASHome\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml.
[antcall] Exiting C:\Program Files\SASHome\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml.

BUILD FAILED
C:\Program Files\SASHome\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml:933: The following error occurred while executing this line:
C:\Program Files\SASHome\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml:2576: The following error occurred while executing this line:
C:\Program Files\SASHome\SASDeploymentManager\9.4\products\cfgwizard__94430__prt__xx__sp0__1\Utilities\configuration_targets.xml:1528: The following error occurred while executing this line:
C:\Program Files\SASHome\SASDeploymentManager\9.4\products\cfgwizard__94430__prt__xx__sp0__1\Utilities\configuration_scripts.xml:177: rc:255 output:
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:217)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:134)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:217)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:134)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:134)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.Main.runBuild(Main.java:698)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)

Re: 9.4 installation - SAS Metadata Server Configuration Error

PaulHomes — Wed, 20 Jul 2016 03:58:32 GMT

I would suggest you contact SAS Technical Support about this issue.

From the error message it look like it might be failing because the installation process can't find/use the standard Windows netstat and chcp commands. You might want to check with your Windows sys admin to see if there is any reason why those might not be available to the account being used to install SAS on that machine.

If you log into the server and open a command window, what happens if you issue the netstat and chcp commands? Are they not found, or do they run and generate output.

What do you get if you run the path command to print the command search path?

Re: 9.4 installation - SAS Metadata Server Configuration Error

tvinner — Wed, 20 Jul 2016 06:15:07 GMT

Thank you for advice.

I can start both from cmd and they produce output.

I can manually start Metadata service, but run into MetadataServerBackupManifest.xml issue.

Re: 9.4 installation - SAS Metadata Server Configuration Error

JuanS_OCS — Wed, 20 Jul 2016 07:00:32 GMT

Hi @tvinner,

besides the great advise provided by @PaulHomes, it is worthy a shot to check if your SAS Foundation is correctly installed:

Could you please try to run SAS 9.4 (or directly the sas.exe)? You might find all kind of strange errors if your Foundation is incorrect and not installed on a drive with the 8.3 naming convention enabled on that volume.

Re: 9.4 installation - SAS Metadata Server Configuration Error

tvinner — Wed, 20 Jul 2016 07:11:58 GMT

Hi @JuanS_OCS,

Thank you for advice. Works without any issues.

Re: 9.4 installation - SAS Metadata Server Configuration Error

JuanS_OCS — Wed, 20 Jul 2016 07:18:48 GMT

Hi @tvinner, thanks for trying. Good to know that the installation seems fine so far.

Did you contacted Technical Support already? Probably the sooner, the better for you.

In the meantime, let's keep moving on. First, i would fix this issue with the xml. The issue and procedire to recover that error is on http://support.sas.com/kb/45/508.html ( and http://support.sas.com/kb/43/649.html). Then, try to manually start the metadata again, and let's see if you get the same message again or not.

Re: 9.4 installation - SAS Metadata Server Configuration Error

tvinner — Wed, 20 Jul 2016 08:37:13 GMT

Hi,

yes, waiting for reply. Will call later.

Did several combinations:

1. install metadata service manually, fix xml, run - port is used

2. install metadata service manually, fix xml, run, stop - no repositories defined on this server error

3. insinstall metadata service manually, fix xml, run, stop, clean folders, start MC - server paused, no pause comment (running in services)

The following problem was encountered while configuring SAS Metadata Server Configuration: sgpvmw2k12r2.test.com:8562 - There was an error in attempting to start this host as the requested port is already in use. Configuration script: C:\Program Files\SASHome\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml For more information, see the log file located at C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_configureMetadata_2016-07-20-15.29.15.log

validatePorts:

[propertyfile] Updating property file: C:\SAS\Config\Lev2\Logs\Configure\metadatasrv_config_status.properties

Checking for listener at sgpvmw2k12r2.test.com:8562

waitfor: condition was met

[antcall] Exiting C:\Program Files\SASHome\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml.

BUILD FAILED

C:\Program Files\SASHome\SASFoundation\9.4\core\sasmisc\sasconf\metadatasrv\config\metadatasrv_config.xml:631: The following error occurred while executing this line:

C:\Program Files\SASHome\SASDeploymentManager\9.4\products\cfgwizard__94430__prt__xx__sp0__1\Utilities\configuration_targets.xml:1337: There was an error in attempting to start this host as the requested port is already in use.

at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)

at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)

at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)

at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)

016-07-20T15:21:38,260 INFO [00000003] :SYSTEM@SGPVMW2K12R2 - SAH011001I SAS Metadata Server (8562), State, starting

2016-07-20T15:21:38,260 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - The maximum number of cluster nodes was set to 8 as a result of the OMA.MAXIMUM_CLUSTER_NODES option.

2016-07-20T15:21:38,260 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - OMACONFIG option 1 found with value OMA.SASSEC_LOCAL_PW_SAVE and processed.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Using AES for password storage.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Using SASPROPRIETARY for password fetch.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Using SHA-256 for password hash.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SAS Metadata Authorization Facility Initialization.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SYSTEM@SGPVMW2K12R2 is an adminUser.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SASTRUST@SASPW is a trustedUser.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SASADM@SASPW is an unrestricted adminUser.

2016-07-20T15:21:38,342 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - INSTALLER-ID@SGPVMW2K12R2 is an unrestricted adminUser.

2016-07-20T15:21:38,370 INFO [00000015] :SYSTEM@SGPVMW2K12R2 - User libref, RPOSMGR, assigned to path, C:\SAS\Config\Lev2\SASMeta\MetadataServer\rposmgr, with server libref, I0000001.

2016-07-20T15:21:38,386 WARN [00000007] :SYSTEM@SGPVMW2K12R2 - Normal operation requires the presence of a Foundation repository, but none was found.

2016-07-20T15:21:38,386 WARN [00000007] :SYSTEM@SGPVMW2K12R2 - The server is being switched to an administrator mode because of the errors and warnings noted above.

2016-07-20T15:21:38,386 INFO [00000015] :SYSTEM@SGPVMW2K12R2 - User libref, RPOSMGR, deassigned from path, C:\SAS\Config\Lev2\SASMeta\MetadataServer\rposmgr, and server libref, I0000001.

2016-07-20T15:21:38,386 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - CloseRepository Id=A0000001, Name=REPOSMGR.

2016-07-20T15:21:38,386 INFO [00000015] :SYSTEM@SGPVMW2K12R2 - User libref, RPOSMGR, assigned to path, C:\SAS\Config\Lev2\SASMeta\MetadataServer\rposmgr, with server libref, I0000002.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SAS version 9.04.01M3P062415.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SAS Metadata Server initialization.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SAS Metadata Server Model 16.01.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SAS Metadata Server current directory C:\SAS\Config\Lev2\SASMeta\MetadataServer.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SAS Metadata Server configuration parameters.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - <?xml version="1.0" encoding="UTF-8"?>

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - <OMAconfig>

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - <InternalAuthenticationPolicy

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - HashPasswords="SHA256"/>

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - <OMA ADMINUSERS="adminUsers.txt"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - TRUSTEDUSERS="trustedUsers.txt"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - GROUPSFORMEMBERASSOCDELETE="DESKTOP_PORTALPAGES_GROUP,

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Portlet Template Group,

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - OrderingGroup,

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - DESKTOP_PAGEHISTORY_GROUP,

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Portal Collection"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - ALERTEMAIL="admin@test.com"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - JOURNALTYPE="NONE"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - MAXIMUM_CLUSTER_NODES="8"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - RETURNPASSWORDS="sas002"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - STOREPASSWORDS="sas003"

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - SASSEC_LOCAL_PW_SAVE="1"/>

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - <RPOSMGR PATH="rposmgr"/>

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - </OMAconfig>

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - OpenRepositoryManager Id=A0000001, Name=REPOSMGR.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Server is executing on host SGPVMW2K12R2 (::1).

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Also known as:

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - localhost

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - ::1

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - 127.0.0.1

2016-07-20T15:21:38,401 ERROR [00000007] :SYSTEM@SGPVMW2K12R2 - No repositories defined on this server.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Reserved IPv6 port 8562 for server listen (connection 1).

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Allowed trusted SAS Peer client type: SAS

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Trusted SAS Peer username: All client usernames are trusted.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Trusted SAS Peer address: All client machine IP addresses are trusted.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Trusted SAS Peer support has been enabled.

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - Activated listen on IPv6 port 8562 (connection 1).

2016-07-20T15:21:38,401 INFO [00000007] :SYSTEM@SGPVMW2K12R2 - No domain controller was found. SPN registration will not be performed for port 8562. Initialization will continue.

2016-07-20T15:21:38,401 INFO [00000003] :SYSTEM@SGPVMW2K12R2 - SAH011999I SAS Metadata Server (8562), State, running

2016-07-20T15:29:34,167 INFO [00000022] :SYSTEM@SGPVMW2K12R2 - The Bridge Protocol Engine Socket Access Method lost contact with a peer (2) during protocol recognition.

2016-07-20T15:29:34,437 INFO [00000023] :SYSTEM@SGPVMW2K12R2 - The Bridge Protocol Engine Socket Access Method lost contact with a peer (3) during protocol recognition.

2016-07-20T15:32:56,496 DEBUG [00000025] :SYSTEM@SGPVMW2K12R2 - START Perf.ARM.IOM.OMI.Server.Stop 452f5d8 0 0

2016-07-20T15:32:56,496 INFO [00000025] :SYSTEM@SGPVMW2K12R2 - Server stopped

2016-07-20T15:32:56,496 INFO [00000003] :SYSTEM@SGPVMW2K12R2 - SAH019001I SAS Metadata Server (8562), State, stopping

2016-07-20T15:32:56,496 WARN [00000025] :SYSTEM@SGPVMW2K12R2 - /sas/wky/mva-v940m3/tkmeta/src/tkomsBackupmf.c: Close was called for manifest file Backups/MetadataServerBackupHistory.xml but it was not open.

2016-07-20T15:32:56,496 INFO [00000015] :SYSTEM@SGPVMW2K12R2 - User libref, RPOSMGR, deassigned from path, C:\SAS\Config\Lev2\SASMeta\MetadataServer\rposmgr, and server libref, I0000002.

2016-07-20T15:32:56,496 INFO [00000025] :SYSTEM@SGPVMW2K12R2 - CloseRepository Id=A0000001, Name=REPOSMGR.

2016-07-20T15:32:56,496 INFO [00000025] :SYSTEM@SGPVMW2K12R2 - SAS Metadata Authorization Facility Termination.

2016-07-20T15:32:56,496 INFO [00000025] :SYSTEM@SGPVMW2K12R2 - SAS Metadata Server termination.

2016-07-20T15:32:56,496 DEBUG [00000025] :SYSTEM@SGPVMW2K12R2 - STOP Perf.ARM.IOM.OMI.Server.Stop 0 0

2016-07-20T15:32:56,496 INFO [00000003] :SYSTEM@SGPVMW2K12R2 - SAH019999I SAS Metadata Server (8562), State, stopped

2016-07-20T15:32:56,496 INFO [00000011] :SYSTEM@SGPVMW2K12R2 - Bridge PE SAM listen thread is exiting (0).

2016-07-20T15:32:56,496 INFO [00000006] :SYSTEM@SGPVMW2K12R2 - For the IOM thread puddle, there were 13 requests processed. The maximum number of requests queued was 0. The maximum number of worker threads was 1.

2016-07-20T15:32:56,496 INFO [00000006] :SYSTEM@SGPVMW2K12R2 - For the overflow thread puddle, there were 2 requests processed. The maximum number of requests queued was 0. The maximum number of worker threads was 1.

2016-07-20T15:32:56,496 INFO [00000006] :SYSTEM@SGPVMW2K12R2 - Bridge protocol engine has quiesced.

2016-07-20T15:32:56,496 INFO [00000006] :SYSTEM@SGPVMW2K12R2 - Bridge protocol engine is unloading.

2016-07-20T15:32:56,496 INFO [00000008] :SYSTEM@SGPVMW2K12R2 - NOTE: The SAS System used:

2016-07-20T15:32:56,496 INFO [00000008] :SYSTEM@SGPVMW2K12R2 - real time 11:18.32

2016-07-20T15:32:56,496 INFO [00000008] :SYSTEM@SGPVMW2K12R2 - cpu time 0.23 seconds

2016-07-20T15:32:56,496 INFO [00000008] :SYSTEM@SGPVMW2K12R2 -

Re: 9.4 installation - SAS Metadata Server Configuration Error

Ololade — Fri, 18 Sep 2020 18:23:30 GMT

Hi tvinner,
We are currently experiencing this rc 255 output error for object spawner on the compute-tier server during our update hostname deployment tool, how did you get this resolved?

Re: 9.4 installation - SAS Metadata Server Configuration Error

JuanS_OCS — Tue, 22 Sep 2020 08:00:20 GMT

@Ololade , for your issue I would like to suggest you to open a different thread in the communities. An issue on Metadata server installation looks very likely it is not the same issue than an already running Object Spawner.

I hope it helps.

Best regards,

Juan