Architecting, installing and maintaining your SAS environment

Unable to update the SID file in Metadata

Reply
New Contributor
Posts: 4

Unable to update the SID file in Metadata

Hi everyone,

 

We are unable to update the SID file in Metadata. Getting the attached error but log is not generating in that configure path. But we can get the SDM log in the home user home directory SASDeploymentWizard. Attached the same here, and it ended with error code -1 as it's failed.Error.png

Trusted Advisor
Posts: 1,569

Re: Unable to update the SID file in Metadata

Hello @EDWSAS,

 

I cannot see any attached log, hence I cannot help you for now. Could you share the log with us with the specific error?

 

Thank you in advance,

Juan

New Contributor
Posts: 4

Re: Unable to update the SID file in Metadata

Posted in reply to JuanS_OCS

Hi Juan,

 

Please find the log file copied below. It's the SDM log as we are not getting the original log which is present in the screenshot. In that location no log at all.

 

Jan 19, 2018 5:40:36 PM com.sas.ssn.Kit main
INFO: Command Arguments: -startuplocation /opt/sas/dev/meta/SASDeploymentManager/9.4 -configure
Jan 19, 2018 5:40:38 PM com.sas.ssn.Kit <init>
INFO: System Properties
      User ID:          sasnew
      User Home:        /users/sasnew
      Temp Directory:   /tmp
      Setup Location:   /tmp/_setup5
      Java Version:     1.7.0_76
      Java Home:        /opt/sas/dev/meta/SASPrivateJavaRuntimeEnvironment/9.4/jre
      OS Name:          Linux
      OS Architecture:  amd64
      OS Version:       2.6.32-642.3.1.el6.x86_64
      Software Version: 904074.0.0.20161005190000_d4deploy74
      Platform Code:    lax
      Host Name:        prodlnx30484.bc.jsplc.net
Jan 19, 2018 5:40:57 PM com.sas.ssn.SpsSkuData <init>
INFO: No VERSION Value in PRODUCT Data: /opt/sas/dev/meta/SASDeploymentManager/9.4/product_data/sid_files__sps__9BMH7Q/product.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.SpsSkuData <init>
INFO: No VERSION Value in PRODUCT Data: /opt/sas/dev/meta/SASDeploymentManager/9.4/product_data/soi__sps__9BMH7Q/product.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.SpsSkuData <init>
INFO: No VERSION Value in PRODUCT Data: /opt/sas/dev/meta/SASDeploymentManager/9.4/product_data/readmes__sps__9BMH7Q/product.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.SpsSkuData <init>
INFO: No VERSION Value in PRODUCT Data: /opt/sas/dev/meta/SASDeploymentManager/9.4/product_data/ordersummary__sps__9BMH7Q/product.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.SpsSkuData <init>
INFO: No VERSION Value in PRODUCT Data: /opt/sas/dev/meta/SASDeploymentManager/9.4/product_data/quickstart__sps__9BMH7Q/product.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds01.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds01.xml (No such file or directory)
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds02.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds02.xml (No such file or directory)
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds03.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds03.xml (No such file or directory)
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds04.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds04.xml (No such file or directory)
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds05.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds05.xml (No such file or directory)
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds06.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds06.xml (No such file or directory)
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds07.xml
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds07.xml (No such file or directory)
Jan 19, 2018 5:40:57 PM com.sas.ssn.OrderData link
INFO: Volser XML File Not Found: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds08.xml
Jan 19, 2018 5:40:58 PM com.sas.ssn.OrderData link
INFO: /opt/sas/dev/meta/SASDeploymentManager/9.4/media_data/9BMH7Q_ds08.xml (No such file or directory)
Jan 19, 2018 5:41:45 PM com.sas.ssn.PanelSelectSID validateData
INFO: Validating sid file: /tmp/SAS94_9BPY14_70193843_LINUX_X86-64.txt
Jan 19, 2018 5:41:45 PM com.sas.ssn.PanelSelectSID validateData
INFO: Updating the m_sidFileText object with text from: /tmp/SAS94_9BPY14_70193843_LINUX_X86-64.txt
Jan 19, 2018 5:41:47 PM com.sas.ssn.Chaining <init>
INFO: DeploymentSummary file: /users/sasnew/.SASAppData/SASDeploymentWizard/DeploymentSummary_2018-01-19-17.41.47.html
Jan 19, 2018 5:41:47 PM com.sas.ssn.Chaining installNext
INFO: Stage #1 Step #1 (SAS Deployment Manager)
Jan 19, 2018 5:41:48 PM com.sas.ssn.Chaining saveConfigData
INFO: Successfully wrote configBundle.xml to /Lev/Utilities/ dir: /opt/sas/dev/config/Lev4/Utilities/configBundle.xml
Jan 19, 2018 5:42:12 PM com.sas.ssn.PickList <init>
WARNING: sas.rutil.zos.jar was not found in /opt/sas/dev/meta/SASVersionedJarRepository
Jan 19, 2018 5:42:12 PM com.sas.ssn.PickList <init>
WARNING: sas.rutil.zos.nls.jar was not found in /opt/sas/dev/meta/SASVersionedJarRepository
Jan 19, 2018 5:42:12 PM com.sas.ssn.PickList <init>
WARNING: sastpj.rutil.zos.jar was not found in /opt/sas/dev/meta/SASVersionedJarRepository
Jan 19, 2018 5:42:13 PM com.sas.ssn.Configure runAntScript
INFO: CONFIGURE: Launching Ant script - "/opt/sas/dev/meta/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java" -Xmx512M -classpath "/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/ant-launcher.jar" -Dant.home="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz" org.apache.tools.ant.launch.Launcher -logger com.sas.tools.webappconfig.logging.LogTransformer -verbose -Dconfiguration.properties.file="/tmp/_setup5/cfgwizard.configuration.properties" -Dant.log.file="/opt/sas/dev/config/Lev4/Logs/Configure/cfgwizard_loadSetinitintoMetadata_2018-01-19-17.42.12.log" -Dinstall.cfgwizard.utilities.dir="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/cfgwizard__94460__prt__xx__sp0__1/Utilities" -Dinstall.cfgwizard.contrib.dir="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/cfgwizard__94460__prt__xx__sp0__1/Utilities/contrib" -Dconfig.target.name=loadSetinitintoMetadata -l "/opt/sas/dev/config/Lev4/Logs/Configure/cfgwizard_loadSetinitintoMetadata_2018-01-19-17.42.12.log" -lib "/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.batch.localsvc_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.sec.login_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/commons_cli_1.2.0.0_SAS_20121211183202:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sastpj.rutil_6.1.0.0_SAS_20121211183517:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.antlr_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.rutil_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.webdav_904300.1.0.20150218190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.core_904301.11.0.20170221163028_v940m3f:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.batch.metadata_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.storedprocess_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/Log4J_1.2.15.0_SAS_20121211183158:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.rutil.nls_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.framework.core_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.cache_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.batch.core_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/groovy:/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/sas.tools.webappconfig.jar" -f "/opt/sas/dev/meta/SASDeploymentManager/9.4/products/cfgwizard__94460__prt__xx__sp0__1/Config/cfgwizard_config.xml" -Dbasedir="/opt/sas/dev/config/Lev4" -Dwebappsrv.container.type=vfabrictcsvr -Ddefault.groovy.path="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/groovy" -D12byte.groovy.path="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/groovy" loadSetinitintoMetadata
Jan 19, 2018 5:42:13 PM com.sas.ssn.Configure runAntScript
INFO: Return Code: -1
Jan 19, 2018 5:42:13 PM com.sas.ssn.PanelExecute getConfigErrorMsg
WARNING: Configure status file not available: /opt/sas/dev/config/Lev4/Logs/Configure/cfgwizard_config_status.properties
Jan 19, 2018 5:42:20 PM com.sas.ssn.Chaining installNext
SEVERE: Configure failure for: SAS Deployment Manager
Jan 19, 2018 5:42:20 PM com.sas.ssn.Configure runAntScript
INFO: CONFIGURE: Launching Ant script - "/opt/sas/dev/meta/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java" -Xmx512M -classpath "/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/ant-launcher.jar" -Dant.home="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz" org.apache.tools.ant.launch.Launcher -logger com.sas.tools.webappconfig.logging.LogTransformer -verbose -Dconfiguration.properties.file="/tmp/_setup5/cfgwizard.configuration.properties" -Dant.log.file="/opt/sas/dev/config/Lev4/Logs/Configure/cfgwizard_reportMissingScript_2018-01-19-17.42.20.log" -Dinstall.cfgwizard.utilities.dir="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/cfgwizard__94460__prt__xx__sp0__1/Utilities" -Dinstall.cfgwizard.contrib.dir="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/cfgwizard__94460__prt__xx__sp0__1/Utilities/contrib" -Dconfig.target.name=reportMissingScript -l "/opt/sas/dev/config/Lev4/Logs/Configure/cfgwizard_reportMissingScript_2018-01-19-17.42.20.log" -lib "/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.batch.localsvc_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.sec.login_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/commons_cli_1.2.0.0_SAS_20121211183202:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sastpj.rutil_6.1.0.0_SAS_20121211183517:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.antlr_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.rutil_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.webdav_904300.1.0.20150218190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.core_904301.11.0.20170221163028_v940m3f:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.batch.metadata_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.storedprocess_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/Log4J_1.2.15.0_SAS_20121211183158:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.rutil.nls_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.framework.core_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.svc.cache_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASVersionedJarRepository/eclipse/plugins/sas.batch.core_904300.0.0.20150204190000_v940m3:/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/groovy:/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/sas.tools.webappconfig.jar" -f "/opt/sas/dev/meta/SASDeploymentManager/9.4/products/cfgwizard__94460__prt__xx__sp0__1/Config/cfgwizard_config.xml" -Dbasedir="/opt/sas/dev/config/Lev4" -Dwebappsrv.container.type=vfabrictcsvr -Ddefault.groovy.path="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/groovy" -D12byte.groovy.path="/opt/sas/dev/meta/SASDeploymentManager/9.4/products/deploywiz__94460__prt__xx__sp0__1/deploywiz/groovy" reportMissingScript
Jan 19, 2018 5:42:20 PM com.sas.ssn.Configure runAntScript
INFO: Return Code: -1
Jan 19, 2018 5:42:22 PM com.sas.ssn.Kit exitKit
INFO: Exit Code = 0

Trusted Advisor
Posts: 1,569

Re: Unable to update the SID file in Metadata

Hi @EDWSAS , Saranya,

 

I see a few warning there regarding not found jar libraries for zos, but I am not sure if that is the problem. What is your installed OS? zOS? Something seems not right there, but I cannot help you here if this is the case, only SAS Technical Support.

 

However, I see a SEVERE error related to a previous warning. An important file that is not being found.

 

 

WARNING: Configure status file not available: /opt/sas/dev/config/Lev4/Logs/Configure/cfgwizard_config_status.properties
Jan 19, 2018 5:42:20 PM com.sas.ssn.Chaining installNext
SEVERE: Configure failure for: SAS Deployment Manager

 

 

Let us focus on that one:

 

this means, that either the SDM program could not find or generate the properties file, or just your user cannot. I am more inclined to think there is a deviation in the process than in the software in this case.

 

If I see

 

 

INFO: System Properties
      User ID:          sasnew
      User Home:        /users/sasnew
      Temp Directory:   /tmp
      Setup Location:   /tmp/_setup5
      Java Version:     1.7.0_76
      Java Home:        /opt/sas/dev/meta/SASPrivateJavaRuntimeEnvironment/9.4/jre
      OS Name:          Linux
      OS Architecture:  amd64
      OS Version:       2.6.32-642.3.1.el6.x86_64
      Software Version: 904074.0.0.20161005190000_d4deploy74
      Platform Code:    lax
    

Is this sasnew user the one that originally installed the software and the owner of the installation?

To check onwerships, you could run a ls -la /opt/sas/dev/config/Lev4/Logs/Configure/ as good example, or ls  -la /opt/sas/dev/meta/SASPrivateJavaRuntimeEnvironment/9.4/jre

 

 

As best practice, for making changes into the SAS deployment itself, you should only use the user that did the initial installation (by default named sas or sasinst), and this user needs to be in the appropriate group (by default, sas, sasusers,..)

 

Once you get this user, try to re-run the SDM with it. Also, please run it with /opt/sas/dev/meta/SASDeploymentManager/9.4/sasdm.sh -loglevel 2 , to get more information on the problem.

 

New Contributor
Posts: 4

Re: Unable to update the SID file in Metadata

Posted in reply to JuanS_OCS

Hi Juan,

 

Yes sasnew is the installer id. And I have tried the command ls -la /opt/sas/dev/config/Lev4/Logs/Configure/ as good example, or ls  -la /opt/sas/dev/meta/SASPrivateJavaRuntimeEnvironment/9.4/jre, both are working can able to see the list in the locations. And can able to create new file and modify the old file also in these locations.

 

Ran the command /opt/sas/dev/meta/SASDeploymentManager/9.4/sasdm.sh -loglevel 2  and got the same message, now where I need to check for more information please?.

 

And we are not thinking it's OS issue as the SID have been updated last year without any issue, but now we are facing an issue please.

 

Thanks,

Saranya D.

Trusted Advisor
Posts: 1,569

Re: Unable to update the SID file in Metadata

[ Edited ]

Hi @EDWSAS,

 

well, I am not saying this is due to the OS, but I am saying there is a deviation since last year. So it must be one of these option:

 

- Software: did anything changed on the binaries or the config during this past year, etc

- Procedure: a different user, system, changed permissions, etc

- License: you could have received a wrong license by mistake. I seriously doubt it, but if above do not make a difference, you can try.

 

 

Here is the procedure I would follow in your case:

1. Check the items mentioned above, to be sure where the deviation is.

2. Get all the relevant info from your system ( http://support.sas.com/kb/48/928.html ) and send it to SAS Technical Support. I am sure they will coop very well with you to find the problem and solution.

3. Run a Installation Qualification and  check deviations on binaries from expected https://support.sas.com/documentation/installcenter/en/ikinstqualtoolug/66614/PDF/default/qualificat...

 

 

 

New Contributor
Posts: 4

Re: Unable to update the SID file in Metadata

Posted in reply to JuanS_OCS

@JuanS_OCS,

 

Thanks for your response. Yes we are in contact with vendor and we will look into these deviations please.

 

Thanks,

EDWSAS Support.

Ask a Question
Discussion stats
  • 6 replies
  • 197 views
  • 3 likes
  • 2 in conversation