When I tried other rest apis for Azure Mangement, it works without any issue. But when I try this recommendedElasticPools , I am getting internal server error all times.
{
"code": "InternalServerError",
"message": "There was an internal server error that occurred during this request.",
"target": null,
"details": [],
"innererror": []
}
We had a problem with this API that should be fixed now. Thanks for reporting this. The API you were calling is on the deprecation path and I recommend using new API instead:
/subscriptions/{SubscriptionId}/resourcegroups/{GroupName}/providers/Microsoft.sql/servers/{ServerName}/elasticPoolEstimates/
Related
As part of a durable function app deployment, I am deploying azure storage.
On deploying the fileServices/shares, I am getting the following error:
error": {
"code": "InvalidHeaderValue",
"message": "The value for one of the HTTP headers is not in the correct format.\nRequestId:6c0b3fb0-701a-0058-0509-a8af5d000000\nTime:2022-08-04T13:49:24.6378224Z"
}
I would appreciate any advice as this is eating up a lot of time and I am no closer to resolving it.
Section of arm template for the share deployment is below:
{
"type": "Microsoft.Storage/storageAccounts/fileServices/shares",
"apiVersion": "2021-09-01",
"name": "[concat(parameters('storageAccount1_name'), '/default/FuncAppName')]",
"dependsOn": [
"[resourceId('Microsoft.Storage/storageAccounts/fileServices', parameters('storageAccount1_name'), 'default')]",
"[resourceId('Microsoft.Storage/storageAccounts', parameters('storageAccount1_name'))]"
],
"properties": {
"accessTier": "TransactionOptimized",
"shareQuota": 5120,
"enabledProtocols": "SMB"
}
}
Answer to this: removing the property "accessTier": "TransactionOptimized" resolves the issue. The default value for this is TransactionOptimized.
Although the template exported from azure portal includes this property, deployment fails if this parameter is present.
I created the "UDO" & "UDT", register it using object registration wizard but whenever I try to access the table via Service Layer I am getting the following error can you one please let me know some solution on this :
{
"error": {
"code": -1000,
"message": {
"lang": "en-us",
"value": "Unknown entity."
}
}
}
Restart the service, and try again
/etc/init.d/b1s restart
Stop the service for about 2 minutes and then start it again:
/etc/init.d/b1s stop
...
/etc/init.d/b1s start
I used Apache JMeter to call OrientDB REST API to test workload of server.
I have tested with 50 concurrent user and see that ~ 30%-45% request was failed with response message as below
{
"errors": [
{
"code": 400,
"reason": "Bad request",
"content": "Error on parsing parameters from request body\u000d\u000a\u0009DB name=\"data_dev\"\u000aYou have reached maximum pool size for given partition"
}
]
}
I have checked and found no error occur on Server.
I have tried to change
script.pool.maxSize to 200, db.pool.max to 200
But this issue still occurred
Any suggestion?
UPDATED
This issue already reported on Github at here
Thanks.
Try to increase the maximum number of instances in the pool of script engines:
script.pool.maxSize
Ref: OrientDB documentation.
When trying to restore a backup to a new cloud sql instance I get the following message when using curl:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "invalidOperation",
"message": "This operation isn\"t valid for this instance."
}
],
"code": 400,
"message": "This operation isn\"t valid for this instance."
}
}
When trying via google cloud console, after clicking 'ok' in the 'restore instance from backup' menu nothing happens.
I'll answer even thought this is a very old question, maybe useful for someone else (would have been for me).
I just had the same exact same error, my problem was that the storage capacity for the target instance was different than the one for the source instance. My source instance was accidentally deleted so this was a bit troublesome to figure out. This check list helped me https://cloud.google.com/sql/docs/postgres/backup-recovery/restore#tips-restore-different-instance
when recived the answer from MongoDB, know that my error is a duplicate key but why status=500 ?, it should be 4**.
I'm using nodejs (sails/express.js)
{ "error": {
"error": "E_UNKNOWN",
"status": 500,
"summary": "Encountered an unexpected error",
"raw": {
"name": "MongoError",
"code": 11000,
"err": "E11000 duplicate key error index: eReporterDB.users.$name_1 dup key: { : \"codin\" }"
} } }
the answer is here for nodejs
Operational errors vs. programmer errors
It's helpful to divide all errors into two broad categories:
Operational errors represent run-time problems experienced by correctly-written programs. These are not bugs in the program. In
fact, these are usually problems with something else: the system
itself (e.g., out of memory or too many open files), the system's
configuration (e.g., no route to a remote host), the network (e.g.,
socket hang-up), or a remote service (e.g., a 500 error, failure to
connect, or the like). Examples include:
failed to connect to server
failed to resolve hostname
**invalid user input**
request timeout
server returned a 500 response
socket hang-up
system is out of memory
Programmer errors are bugs in the program. These are things that can always be avoided by changing the code. They can never be handled
properly (since by definition the code in question is broken).
tried to read property of "undefined"
called an asynchronous function without a callback
passed a "string" where an object was expected
passed an object where an IP address string was expected