Hi,
While validating service Architecture following message is displayed.
service Architecture validation failed. emi_init cannot continue. Errors are:
Service Architecture is not initialized, but APM ETL is enabled.
Can anyone help out how to initialized Service Architecture.
Thanks.
I have a track opened with Tech Support regarding some issues that we have with our Service Architecture framework. They sent me this link: https://support.sas.com/rnd/emi/SASEnvMgr/EVSAF/index.html. There are some more links at the bottom of the page for initializing.
Thanks for respond.
I followed the link and steps it mentioned in below links, i.e.
./validate.sh --level 2 result of this is
Service Architecture Validation - Thu Apr 13 14:32:14 EDT 2017
Starting level 1 validation...
Level 1 validation completed with 0 error(s)
Starting extended level 2 validation (this could take a while)...
Level 2 validation completed with 1 error(s) in 25.197 sec
Service Architecture validation completed with 1 error(s)
Errors:
1) Service Architecture is not initialized, but APM ETL is enabled.
./emi_init.sh -i result for this is
Service Architecture Initialization Utility - Thu Apr 13 14:34:51 EDT 2017
Validating environment...
Validating external connections...
Service Architecture validation failed. emi_init cannot continue. Errors are:
Service Architecture is not initialized, but APM ETL is enabled
Stopping execution.
Any advice what to do next.
I would think you should disable APM ETL and then validate the service architecture framework again to see if that error is resolved.
Thanks for reply
I tried to do but got same error.
./emi_init.sh --disable APM
Service Architecture Initialization Utility - Thu Apr 13 16:10:24 EDT 2017
Validating environment...
Validating external connections...
Service Architecture validation failed. emi_init cannot continue. Errors are:
Service Architecture is not initialized, but APM ETL is enabled
Stopping execution
Hello @Yarlanil59,
first, you can always check the status of your initialized components on EMI like this:
$ ./emi_init.sh -s Service Architecture settings: Level Root Dir : [/opt/sas/config/Lev1] Base Dir : [/opt/sas/config/Lev1/Web/SASEnvironmentManager/emi-framework] Initialized : [true] Enabled : [true] APM Initialized : [true] ACM Initialized : [false] APM Enabled : [true] ACM Enabled : [false] VA Feed Enabled : [false]
Then you need to ensure what is initialized and whatnot.
Secondly, you have some additional parameters that are useful, such as "force"
$ ./emi_init.sh -h usage: emi_init [options] [(--enable|--disable) ] Initializes Service Architecture and/or enables components Options: -d,--debug Enable debug output --disable <[APM,ACM,ALL]> Components to disable (can't be used with --enable) --enable <[APM,ACM,ALL]> Components to enable (can't be used with --disable) -f,--force Re-initialize and overwrite settings -h,--help Show usage information -i,--initialize Initialize Service Architecture -k,--loadKits Load kits --resetDB Reset the Data Mart, purging all existing ACM and APM data, non-recoverable --resetFlags Resets all initialized and enabled flags to false. Note: This does not undo changes made during initialization or component enablement. -s,--status Show operational status -v,--verbose Enable verbose output --vafeed Enable VA Feed Exit status: 0 if OK 1 if minor issues are encountered 2 if an error is encountered -1 for invalid usage
whilst you might have other kind of problems, I would strongly suggest you to start by forcing the initialization. It does help many times.
Your command would be emi_init -i -f -enable APM
Additionally, and to wrap it up, my best suggestion, when you are debugging or solving a problem, add the parameters -d and -v on every emi_init and validate commands. You will be able to see additional information on realtime on your screen, at the moment of the errors.
Hope it helps!
Juan
Thanks for the reply.
I tried with
./emi_init.sh -f, initially it showed the same error. I tried with different option ./emi_init.sh --enable ACM ./emi_init.sh --enable APM and again ./emi_init.sh -i and the ./emi_init.sh -f. Every time it throughs me errors, I don't know where exactly it worked finally it worked.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.