BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.

Hi Co's,

 

Could you please suggest on below error:

 

kumarsandip975_0-1724415743495.png

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
ronf_sas
SAS Employee

It indicates a "warning" occurred.   Warnings are usually explained in <sas-config-dir>\Lev1\Documents\Instructions.html

Alternatively, you can inspect the metadatasrv_configureMetadata_yyyy-mm-dd.hh.ss.log file at <sas-config-dir>\Lev1\Logs\Configure and search for "insertWarning"

One possible cause for the warning is that in the first attempt, the metadatasrv_configureMetadata script created the Metadata Server service in Windows, but then failed for a different reason.  Upon hitting Retry, the SAS Deployment Wizard detected that the Metadata Server service already existed in Windows due to the previous execution of the script it and did not recreate the service and threw the warning.

But to confirm, you'd need to inspect Instructions.html and/or the metadatasrv_configureMetadata_yyyy-mm-dd.hh.ss.log

View solution in original post

6 REPLIES 6
ronf_sas
SAS Employee

There is not enough information in your screenshot to help.  The screenshot links you to a log file where you will find more information about the cause.

You can search the log for "build failed" and/or "caused by" to try to get to the relevant part of the log.

Depending upon the nature of the error, you might also need check the Metadata Server log at c:\sas\configmeta\lev1\sasmeta\metadataserver\logs

Additionally, you might want to open a case with SAS Technical Support.

kumarsandip975
Pyrite | Level 9

After rerun , it got moved, but still I see issues with it, should I check same log to troubleshoot. 

kumarsandip975_0-1724427755469.png

 

ronf_sas
SAS Employee

It indicates a "warning" occurred.   Warnings are usually explained in <sas-config-dir>\Lev1\Documents\Instructions.html

Alternatively, you can inspect the metadatasrv_configureMetadata_yyyy-mm-dd.hh.ss.log file at <sas-config-dir>\Lev1\Logs\Configure and search for "insertWarning"

One possible cause for the warning is that in the first attempt, the metadatasrv_configureMetadata script created the Metadata Server service in Windows, but then failed for a different reason.  Upon hitting Retry, the SAS Deployment Wizard detected that the Metadata Server service already existed in Windows due to the previous execution of the script it and did not recreate the service and threw the warning.

But to confirm, you'd need to inspect Instructions.html and/or the metadatasrv_configureMetadata_yyyy-mm-dd.hh.ss.log

kumarsandip975
Pyrite | Level 9

I am leaving this warning as it is. 

Moving with other compute components, I am getting stuck here. Could you please suggest. 

 

kumarsandip975_0-1724460414455.png

 

Log file below - To fix this I tried 51852 - "ERROR: Failed to update agent metadata in the SAS Metadata Server!" occurs when you are per..., but no success. 

I guess, somehow SAS Deployment Agent service is not starting. 

 

BUILD FAILED
: Failed to update agent metadata in the SAS Metadata Server: null
at org.apache.tools.ant.taskdefs.Exit.execute(Exit.java:142)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at groovy.util.AntBuilder.nodeCompleted(AntBuilder.java:178)
at groovy.util.BuilderSupport.doInvokeMethod(BuilderSupport.java:153)
at groovy.util.AntBuilder.doInvokeMethod(AntBuilder.java:132)
at groovy.util.BuilderSupport.invokeMethod(BuilderSupport.java:64)
at org.codehaus.groovy.runtime.InvokerHelper.invokePogoMethod(InvokerHelper.java:777)
at org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:753)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:167)
at embedded_script_in_D__Program_Files_SASHome_SASDeploymentManager_9.4_products_cfgwizard__94560__prt__xx__sp0__1_config_cfgwizard_config.run(embedded_script_in_D__Program_Files_SASHome_SASDeploymentManager_9.4_products_cfgwizard__94560__prt__xx__sp0__1_config_cfgwizard_config.xml:14)
at org.codehaus.groovy.ant.Groovy.execGroovy(Groovy.java:348)
at org.codehaus.groovy.ant.Groovy.execute(Groovy.java:228)
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:498)
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:498)
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:498)
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 net.sf.antcontrib.logic.RunTargetTask.execute(RunTargetTask.java:48)
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:498)
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)
 
Total time: 1 minute 25 seconds

 

ballardw
Super User

Did you read the LOG file mentioned?

 

The file is plain text. You should consider copying the text in the LOG file and on the forum opening a text box using the </> icon above the message window and then pasting the text.

 

Without the contents of the log we really do not have sufficient information to provide much in the way of relevant suggestions.

kumarsandip975
Pyrite | Level 9

looks like metadata services and related services are running after configuration, but only question with warning while configuration. 

kumarsandip975_0-1724429323662.png

 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 1145 views
  • 0 likes
  • 3 in conversation