Azure SQL database TransparentDataEncryptionProtector InternalServerError: An unexpected error occured while processing the request - sql

I am trying to configure transparent data encryption for my Azure SQL databases using the steps documented in https://learn.microsoft.com/en-us/azure/sql-database/transparent-data-encryption-byok-azure-sql-configure
The command Set-AzSqlServerTransparentDataEncryptionProtector in step 3 is trowing me an error
InternalServerError: An unexpected error occured while processing the
request. Tracking ID: '8decc6a3-b1e5-4860-acc6-37b1114bcc33'.
When I look in the Azure portal at the Activity Log I see the same error "The resource operation completed with terminal provisioning state Failed.
"statusMessage":
"{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The
resource operation completed with terminal provisioning state
'Failed'.\",\"details\":[{\"code\":\"InternalServerError\",\"message\":\"An
unexpected error occured while processing the request. Tracking ID:
'82fbc867-e16a-4681-96af-d410400e97f9'\"}]}}"
Anybody any idea how to trace what goes wrong?

Related

AWS Glue Job error: An error occurred while calling o82.parquet. Not Found

We use AWS Glue Jobs for some of our data processing. We use pyspark to process the data, but from time to time we see this error on some step of a job:
An error occurred while calling o82.parquet. Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: ABC111; S3 Extended Request ID: ABC111abc111)
This error seems to be intermittent and sometimes just rerunning the same job with same parameters seems to run fine, but it is definitely not a very descriptive error and we'd like to avoid it as our number of automated jobs grows.
In the Cloudwatch logs the latest logs I see:
WARN [Executor task launch worker for task 1318] client.YarnClient (YarnClient.java:makeRestApiRequest(66)) - The GET request failed for the URL http://0.0.0.0:8088/ws/v1/cluster/apps/application_1583197528647_0001
om.amazon.ws.emr.hadoop.fs.shaded.org.apache.http.conn.HttpHostConnectException: Connect to 0.0.0.0:8088 [/0.0.0.0] failed: Connection refused (Connection refused)
at com.amazon.ws.emr.hadoop.fs.shaded.org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:158)
...
Caused by: java.net.ConnectException: Connection refused (Connection refused)
...
ERROR [SIGTERM handler] executor.CoarseGrainedExecutorBackend (SignalUtils.scala:apply$mcZ$sp(43)) - RECEIVED SIGNAL TERM
The overview of the job:
reading json files using Glue Data Catalog, writes aggregated data into s3 in parquet format (I see a new partition here, but pretty sure it fails at this step as I don't see any messages that I put into the code after this); reads the data from the last step, reads csv mapping file from s3, joins 2 datasets, doing some additional calculations using pyspark, finally writes output to s3 in csv format.

Repeated Error in SQL Server 2017 Error Log (Error: 15404, error-code 0x5)

I'm relatively new to SQLServer2017 Developer and System Center Operations Manager however I was asked to set up a SCOM test environment for our network. However, I keep receiving this error about one of my SCOM service accounts. I have already looked at some fixes and applied them however after refreshing the log the same error message still keeps appearing.
2020-02-13 14:03:09.05 spid47s An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'OMDASTest', error code 0x5.

TWS MakePlan failure with AWSJDB818E

TWS MakePlan is failing with error message: AWSJDB818E
"AWSJDB818E An internal error has occurred while connecting to the
database. The internal error message is: "CWTE_NORMAL_J2CA1009"." cannot
be obtained from the database, or is incorrect.
Which is the root cause?
in that case the error message
"AWSJDB818E An internal error has occurred while connecting to the
database. The internal error message is: "CWTE_NORMAL_J2CA1009"." cannot
be obtained from the database, or is incorrect.
With "internal error message: CWTE_NORMAL_J2CA1009" is an indicator that no DB connections are available.
For TWS 9.4
Edit the file:
/WAS/TWSProfile/config/cells/TWSNodeCell/nodes/TWSNode/servers
/PSLITE-TIV01/resources.xml
In the "DB2 Universal Type 4 JDBC Driver DataSource"
change the value minConnections="1" maxConnections="30" to
minConnections="0" maxConnections="100"
A restart of the WAS is required
thanks.

Mobilefirst can not store userid into worklight database

We are using adapter-based authenticators. WL.Server.setActiveUser was called on the adapter.
I user WL.Logger.info to print out the parameters which I send to setActiveUser. They are correct.
In WL console, DeviceId got updated ,but we can not saw the userid in the device table.
enter image description here
we are using MFP 7.1 version.
We got below error in the log file. not sure it is related to the issue.
[9/5/16 23:09:48:567 EDT] 000000f4 GadgetAPIServ E com.worklight.gadgets.serving.GadgetAPIServlet createAjaxRequestExceptionJSON FWLSE0020E: Ajax request exception: Optimistic locking errors were detected when flushing to the data store. The following objects may have been concurrently modified in another transaction: [com.ibm.pushworks.server.entities.PushSubscription-com.ibm.pushworks.server.entities.PushSubscription-2] [project ]
[9/5/16 23:09:48:579 EDT] 000000f4 GadgetAPIServ E createAjaxRequestExceptionJSON FWLSE0117E: Error code: 1, error description: INTERNAL_ERROR, error message: FWLSE0069E: An internal error occurred during gadget request [project ]Optimistic locking errors were detected when flushing to the data store. The following objects may have been concurrently modified in another transaction: [com.ibm.pushworks.server.entities.PushSubscription-com.ibm.pushworks.server.entities.PushSubscription-2], User Identity {wl_directUpdateRealm=(name:null, loginModule:WLDirectUpdateNullLoginModule), SubscribeServlet=null, wl_authenticityRealm=null, ServicesRealm=(name:xxx#cn.ibm.com, loginModule:StrongDummy), wl_remoteDisableRealm=(name:null, loginModule:WLRemoteDisableNullLoginModule), SampleAppRealm=(name:xxx#cn.ibm.com, loginModule:StrongDummy), wl_antiXSRFRealm=(name:qmd8e821mcil59j4tedagchnvi, loginModule:WLAntiXSRFLoginModule), wl_deviceAutoProvisioningRealm=null, wl_deviceNoProvisioningRealm=(name:D07571B0-2685-4F6F-9C42-37B616F52190, loginModule:WLDeviceNoProvisioningLoginModule), myserver=(name:ea57e780-ce09-4bbd-aee5-5a1701388b72, loginModule:WeakDummy), wl_anonymousUserRealm=(name:ea57e780-ce09-4bbd-aee5-5a1701388b72, loginModule:WeakDummy)}. [project ]
It seems the security test defined in Authentication config file is not mentioned in Application Descriptor file . Please cross check security test in AuthenticatonConfig.xml and applicationDescription.xml
please follow below link.
https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/6.3/authentication-security/adapter-based-authentication/

Liferay stopped at database shutdown caused a crash

I was stopping the Liferay portal, but few seconds after, I stopped the database (db2 quiesce, that means, that the connections are closed) and apparently, Liferay did not stopped correctly its execution.
After that, I restarted the database and liferay, but the portal does not work now. It shows this message in the browser:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet execution threw an exception
com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:72)
...
root cause
java.lang.NoSuchMethodError: com.liferay.portal.util.PortalUtil.getCDNHostHttp()Ljava/lang/String;
com.liferay.portal.events.ServicePreActionExt.servicePre(ServicePreActionExt.java:937)
After looking in the logs, I found the following messages (they are edited):
SEVERE: Error waiting for multi-thread deployment of directories to completehostConfig.deployWar=Deploying web application archive {0}
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1000)
WARN [DefaultConnectionTester:203] SQL State '08001' of Exception which occurred during a Connection test (fallback DatabaseMetaData test) implies that the database is invalid, and the pool should refill itself with fresh Connections.
com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2030][11211][3.63.75] A communication error occurred during operations on the connection's underlying socket, socket input stream, or socket output stream. Error location: Reply.fill() - insufficient data (-1). Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001
at com.ibm.db2.jcc.am.fd.a(fd.java:321)
WARN [DefaultConnectionTester:136] SQL State '08001' of Exception tested by statusOnException() implies that the database is invalid, and the pool should refill itself with fresh Connections.
WARN [C3P0PooledConnectionPool:708] A ConnectionTest has failed, reporting that all previously acquired Connections are likely invalid. The pool will be reset.
WARN [NewPooledConnection:486] [c3p0] A PooledConnection that has already signalled a Connection error is still in use!
WARN [NewPooledConnection:487] [c3p0] Another error has occurred [ com.ibm.db2.jcc.am.SqlNonTransientConnectionException: [jcc][t4][10335][10366][3.63.75] Invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003 ] which will not be reported to listeners!
com.ibm.db2.jcc.am.SqlNonTransientConnectionException: [jcc][t4][10335][10366][3.63.75] Invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003
WARN [BasicResourcePool:1841] com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask#4fad5112 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (3). Last acquisition attempt exception:
com.ibm.db2.jcc.am.SqlNonTransientConnectionException: DB2 SQL Error: SQLCODE=-20157, SQLSTATE=08004, SQLERRMC=FUT5MAN;QUIESCE DATABASE;;, DRIVER=3.63.75
ERROR [PortalJobStore:109] MisfireHandler: Error handling misfires: Unexpected runtime exception: null
org.quartz.JobPersistenceException: Unexpected runtime exception: null [See nested exception: java.lang.reflect.UndeclaredThrowableException]
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy279.prepareStatement(Unknown Source)
at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.countMisfiredTriggersInState(StdJDBCDelegate.java:413)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1319)
Now, I see that it is almost impossible to start the current Liferay installation. However, I have the database (I made a full backup), and the lucene's data directory. How can I recreate a Liferay installation with these two things? I would like to recover some of this data in a new installation, but I do not how.
This is not the best solution, but I installed Liferay with a new database. Once it was configured, I change the database configuration in order to use the other one.
Probably, it was a problem with the ROOT deployment, but this is very weird.
I could recover all the data from the Lucene and the database.
The database is still quiesced and the Liferay user doesn't have the QUIESCE_CONNECT privilege.
Unquiesce the database and restart Liferay.
Using DB2 instance owner (if you're on Windows, any administrator):
db2 connect to DBNAME
db2 unquiesce database
db2 connect reset
Regards.