2022-09-14T07:37:21.040Z - error: [DiscoveryResultsProcessor]: parseDiscoveryResults[User] - Channel:mychannel received discovery error:failed constructing descriptor for chaincodes:<name:"User" >
Failed to submit transaction: Error: DiscoveryService: User error: failed constructing descriptor for chaincodes:<name:"User" >
when I hit API from post man i receive this error
This error usually comes when the chaincode name given is wrong. Make sure the chaincode('User' in this case) is committed to channel mychannel before sending transactions using SDK.
Related
I followed here.
In next step(verify the installation),
When I create deployment in cluster2(remote cluster), sidecar injector not working like below...
kubectl get event -n sample
LAST SEEN TYPE REASON OBJECT MESSAGE
42m Warning FailedCreate replicaset/helloworld-v2-79bf565586 Error creating: Internal error occurred: failed calling webhook "namespace.sidecar-injector.istio.io": failed to call webhook: Post "https://istiod.istio-system.svc:443/inject/cluster/cluster2/net/network1?timeout=10s": unsupported service type "ExternalName"
2m45s Warning FailedCreate replicaset/helloworld-v2-79bf565586 Error creating: Internal error occurred: failed calling webhook "namespace.sidecar-injector.istio.io": failed to call webhook: Post "https://istiod.istio-system.svc:443/inject/cluster/cluster2/net/network1?timeout=10s": unsupported service type "ExternalName"
53m Normal ScalingReplicaSet deployment/helloworld-v2 Scaled up replica set helloworld-v2-79bf565586 to 1
41m Normal ScalingReplicaSet deployment/helloworld-v2 Scaled up replica set helloworld-v2-79bf565586 to 1
Is this issue about firewalld ? (I used AWS EKS v1.24)
When I searched something about this, Other people's message is context deadline exceeded in here...
Can anybody help me? :(
Search Internet, and re install istio at all...
I use ApiKit to receive queries. Occasionally I get the following line in a log file:
WARN org.mule.module.http.internal.listener.grizzly.ResponseCompletionHandler - HTTP response sending task failed with error: Locally closed
It seems that in this case the integration has not sent a response to the party that called the integration. I thought that there might be a sort of timeout before ApiKit closes the connection to caller but based on timestamps that might not be the case as everything happens within a second.
In this case the payload is sent to Artemis queue before this warning and despite the warning the message is read from Artemis normally and the whole flow works otherwise just fine besides this warning and not sending the response.
So, am I correct when I think that this warning is an indication why the response is not sent? In addition to that what can be done to prevent this situation?
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?
I currently registered my Quecklink GV500 to cumulocity and I'm able to receive some events and measurements.
But when I try to send command to my Quecklink GV500 registered in Cumulocity but I always hava a FAILED response. For example, I tried to send this command (which is fully supported by the GV500) from SHELL tab: AT+GTTMA=gv500,+,1,0,0,,,,,,FFFF$
And as result I got:
Failure reason: Command currently not supported
I also tried to get the agent logs by using "Log file request" in the "Log" tab of my Device and as result I got:
Failure reason: Cannot build command. Search parameters only allow the
following characters [a-zA-Z0-9_]
Is it normal?
When I look the general information in "Info" tab I have:
Send connection: online
Push connection: inactive
Is it normal that Push connection is marked as inactive?
The tracker-agent in it current state does not use a push connection for receiving operations but does a polling of the operations. Therefore the push connection is always shown as inactive.
If you receive "Failure reason: Command currently not supported" it is an error from the agent not the device. The agent seems not to support shell operations for Queclink.
As for the error on the log file request it seems that there was an unsupported character in the search parameter. Maybe you can share what you entered for the parameters in the UI
Thanks for your answer. For the log file request I let blank value in the search input field. If I try to enter "gl200", I get the following error: Command currently not supported.
So to resume can you confirm that Quecklink devices can't be managed from Cumulocity for the moment? It's supported for which device?
I'm attempting to call a Stored proc, get some data back, map that to the desired schema, output the result.
However, I'm getting the following error:
The Messaging engine failed to process a message submitted by
adapter:WCF-SQL Source
URL:mssql://master-biztalk//ReportServer?InboundId=batman. Details:The
published message could not be routed because no subscribers were
found. This error occurs if the subscribing orchestration or send port
has not been enlisted, or if some of the message properties necessary
for subscription evaluation have not been promoted. Please use the
Biztalk Administration console to troubleshoot this failure.
I'm not quite certain why I'm getting this error. Searching the web hasn't enlightened me any further. Following are some of the steps I've undertaken
Consume adapter = generated schema.
Map this schema to desired output.
Receive port in the Orchestration which connects to a receive message which has the Schema generated by the consume adapter as the type.
Added a receive port in Biztalk, configured WCF-SQL and setup bindings. (Typed polling)
Linked this receive port to the logical receive port in orchestration.
I haven't promoted any elements in messages.
Thanks for the help
EDIT: I updated the pipeline to XML, and now I'm getting the following error:
There was a failure executing the receive pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive,
Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive
Port: "DatabaseReceiveport" URI:
"mssql://master-biztalk//ReportServer?InboundId=batman" Reason:
Finding the document specification by message type
"http://schemas.microsoft.com/Sql/2008/05/TypedPolling/batman#TypedPolling"
failed. Verify the schema deployed properly.
I'm not quite sure what it's trying to do above.
This means that either:
The Project/Assembly with the specified Schema has not been deployed.
The WCF SQL configuration is off somehow, frequently the InBoundId parameter. That's where "batman" would come from.
In the All Artifacts Application, check the Schemas folder for that Schema by Root Node and Namespace.