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.
Related
awsapps login page shows -It's not you, it's us We couldn't complete your request right now. Please try again later
or
access key and secret could not connect aws account with an error message as
"An error occurred (InvalidSignatureException) when calling the DescribeCluster operation: Signature expired: 20220801T134645Z is now earlier than 20220801T143813Z (20220801T144313Z - 5 min.)"
Both the errors are due to date and time mismatch, ie.. try syncing system time settings to your exact location and login,that worked for me.
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.
Installing Superset with docker-compose. App is up and running. When adding a new database using PyAthena connector, error Unexpected error occurred, please check your logs for details happens with no details in the logs.
First, if you are using docker-compose, check whether you have added driver to the build environment.
echo "PyAthena>1.2.0" >> ./docker/requirements-local.txt
If you don't you will get Driver not found error.
Second, check your URI scheme. It must be of the following form:
awsathena+rest://AKIAXXXX:XXXXXX#athena.{region}.amazonaws.com/{database_name}?s3_staging_dir=s3://{bucket_name_for_results}
If you are missing the query string part you may get mysterious error without a detail reason.
Also note that PyAthena does not check you AK/SK against the staging bucket.
This is the error am getting in work flow log:
ERROR 7/15/2020 3:00:19 PM node01_DESKTOP-CK55616 7080 LM_36320 Session task instance [s_m_Importing_XML1]: Execution failed.
I cannot open the session log.. even session fails means also we can open the session log, but now I can't able to open the session log.
session log error:
An internal exception occurred with [LGS_10052]
help me out!!
There may be few causes.
Workflow failed to start the session at all - check workflow log.
Session log config is invalid - review and fix
Session log has been deleted from file system
Sharing workflow log details would shed some light.
You cannot open the session logs in case you have issue with the workflow configurations. Informatica will fail during the start of the workflow itself and there will not be any session logs, therefore it throes error when you try to open session logs. Open the workflow log, identify and fix the issue you are getting in the workflow.
I am at my wits end on this and can't figure this out. In sitecore v6.2 something has changed that is causing an error message as follows
"The operation could not be completed. Your session may have been lost due to a time-out or server failure".
looks like this is coming from Sitecore.Web.UI.Sheer.ClientPage?
The request info:
https://sitecore.test.domain.com/sitecore/shell/sitecore/content/Applications/Content%20Editor.aspx?ic=People%2f16x16%2fcubes_blue.png
the response:
{"commands":[{"command":"Alert","value":"The operation could not be completed.\n\nYour session may have been lost\ndue to a time-out or a server failure.\n\nTry again."}]}
At first, I assumed it was because plugged in some new HttpModules so I moved them into the sitecore pipeline model and the problem kept persisting. I removed them from the entire application and the problem kept persisting.
A google search on the error gets me to some information on the keepalive.aspx stuff, but addressing that has no bearing.
I decompiled the code with reflector, but can't find anywhere this particular error is raised. It must be in sitecore.nexus or something.
According to my superiors we will open a ticket once we get the build resolved, but here's to hoping someone here has some suggestions.
The constant for this error message is THE_OPERATION_COULD_NOT_BE_COMPLETED_YOUR_SESSION_MAY_HAVE_BEEN_LOSTDUE_TO_A_TIMEOUT_OR_A_SERVER_FAILURE_PLEASE_TRY_AGAIN
This might happened if you server restarts while some dialog opened