I have defined a new artifact type and am successfully creating new asset instances of it in the publisher - which works well. Recently I was experimenting with my own create_form.hbs under publisher/extensions/assets//themes/default/partials/ and then decided against continuing. After deleting the newly created '/themes/default/partials/create_form.hbs' I then found that when I now try to publish a new instance of the artifact I get the following error thrown:
[2016-11-11 11:17:06,833] ERROR - Failed to invoke action: Create for the asset of id: "9a3a4e55-a5a3-4c94-a2d0-152a10e4ab45".The following exception was thrown: JavaException: org.wso2.carbon.registry.core.exceptions.RegistryException: Preprequest action must be completed before Create {rxt.asset}
[2016-11-11 11:17:06,833] ERROR - org.wso2.carbon.registry.core.exceptions.RegistryException: Preprequest action must be completed before Create {asset_api_endpoints}
org.mozilla.javascript.WrappedException: Wrapped org.wso2.carbon.registry.core.exceptions.RegistryException: Preprequest action must be completed before Create (eval code#1(eval)#87) at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754) at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148) at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:22
Despite this and the fact that I get the user friendly 'Error' message in the publication page telling me the asset was unable to be created, the new instance does in fact get created (I can see it when I go the the asset list page). I can also edit with no problems.
I'm unsure whether this error is related to the create_form.hbs page I previously created (and then deleted) or whether it is just a coincidence.
Is there a caching problem going on?
Any help on what the error means and how to resolve it would be greatly appreciated.
Thanks in advance.
The defaultAction value (under meta lifecycle) in the asset file was defined as "Create" which didn't match what was in the LifeCycle config. This action must match a valid lifecycle value otherwise the publish page displays an error message despite successfully creating the new asset.
Related
My application is running on Elastic beanstalk AL2 with docker. It is still up and running, this issue is not user facing and only internal to AWS.
I upgraded to AL2 about 7 months ago and there were no problems. Recently I logged into to Elastic Beanstalk console to look into upgrading the platform. When I clicked on "Configuration" I get an error and redirected back to the applications list.
The error says:
Error
A problem occurred while loading your page: Configuration validation exception: Invalid option value: 'awseb-e-XXXXXXXX-stack-AWSEBSecurityGroup-XXXXXXXX’ (Namespace: 'aws:autoscaling:launchconfiguration', OptionName: 'SecurityGroups'): The security group 'awseb-e-XXXXXXXX-stack-AWSEBSecurityGroup-XXXXXXXX' does not exist
The error before this actually referenced a launch template so when I created a version 2 of the launch template but without the errored security group (as indicated by the UI) then this error message changed to the one we see above.
I tried redeploying thinking new setting need to take effect. Didn't work. Error still present.
I tried creating a new unrelated environment from scratch, but it has the same error message when clicking on Configuration.
I tried cloning production environment but am blocked with the same error message.
I also posted this question here: https://repost.aws/questions/QU4VTSJDyCT7OtIIgPCblUPA/elastic-beanstalk-unable-to-access-environments-configuration-error-a-problem-occurred-while-loading-your-page-configuration-validation-exception
I tried the suggestions but neither worked.
Any ideas on how to fix or debug this further?
Thank you
When i try to create a stack using cloudformation i get the following error;
PuppetMaster
CREATE_FAILED Received FAILURE signal with UniqueId i-instanceId
WSO2APIManagerSetup-XXXX
CREATE_FAILED
The following resource(s) failed to create: [PuppetMaster].
WSO2APIMPattern1
Status reason
The following resource(s) failed to create: [WSO2APIManagerSetup]
Where do i check what the actual error was for the PuppetMaster task. Is there any logs on either the PuppetMaster(instanceId), WSO2APIMPattern1 or WSO2APIManagerSetup instances that i can go check?
P.S
Nothing in the cloudtrail logs either
I was not able to track down the logs, however i found the issue.
I was populating the WUMUsername and since i don't have a subscription, this was failing. By leaving the WUMUsername and WUMPassword fields blank in the template, everything worked flawlessly.
I suppose i can backtrack to see where in the stack the error would have been thrown, but thats an exercise for another day.
I tried to create a Google Cloud Composer environment but in the page to set it up I get the following errors:
Service Error: Failed to load GKE machine types. Please leave the field
empty to apply default values or retry later.
Service Error: Failed to load regions. Please leave the field empty to
apply default values or retry later.
Service Error: Failed to load zones. Please leave the field empty to apply
default values or retry later.
Service Error: Failed to load service accounts. Please leave the field
empty to apply default values or retry later.
The only parameters GCP lets me change are the region and the number of nodes, but still lets me create the environment. After 30 minutes the environment crashes with the following error:
CREATE operation on this environment failed 1 day ago with the following error message:
Http error status code: 400
Http error message: BAD REQUEST
Errors in: [Web server]; Error messages:
Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later.
If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation.
An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2021-07-20T14:31:23.047Z7050.xd.0: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section.
Got error "Another operation failed." during CP_DEPLOYMENT_CREATING_STANDARD []
Is it a problem with permissions? If so, what permissions do I need? Thank you!
It looks like more of a temporary issue:
the first set of errors is stating you cannot load the metadata :
regions list, zones list ....
you dont have a clear
PERMISSION_DENIED error
the second error: is suggesting also:
This might be a temporary issue.
SBL-EIM-00205: Failed to load the application dictionary.
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-EIM-00205: Failed to load the application dictionary.
This is a generic message, Siebel throws it all the time there is an issue in the repository. You will have to go through the log file and get the actual error message. Increase the component log level for EIM component to maximum and re-submit the job for the logs.
The structure of the EIM tables have to match the final tables, so it could be a mismatch of schema causes this error.
SBL-SVR-01042 this is generic error when this error is encountered while attempting to instantiate a new instance of a given component and is generic. As to why the error has occurred, one needs to review the accompanying error messages which will help provide context and more detailed information
SBL-EIM-00205: There could be many reason for this error.This is caused due to the incorrect ODBC registry entries. or some issue with Foreign key mapping.
You should increase log level and get more details.
I'm getting following errors while trying to stop the PWX logger:
Could not exectute action...
[DOM_10213] Internal error. Could not update the service state in the domain configuration repository because of the following errors:
[RSVCSHARED_00018] Internal error. The request processing failed for the following reason:
['Exception Class[Class javax.persistence.persistenceException] Exception message [org.hibernate.exception.GenericJDBCException: cannot open connection]']
I Tried both complete and Abort option but same issue persists .
Please help me to fix it.
I found the answer.
Actually the password for the informatica user had been expired. I alter the user with the same old password and its working fine.