I am creating a self hosted integration runtime. There is error in registration after installed the IR on Window.The authentication key is just copied from portal and paste on it. But, the warning says the key is invalid or empty. How can I solve it?
Both Azure Data Factory and on-prem data server are on same time zone so no time delay.
Any suggestion would be great as struggled most of the day.
I have tried by using express route exe and integration runtime msi both but same result no luck :(
It was networking issue as same key working on public endpoint network setting. Now it will fix private endpoint.
Related
My team and I have been working on a NFT distribution app utilizing the flow blockchain. We have everything working and are ready for our first event but I am having a very difficult time getting everything setup on mainnet. It is working great on testnet but I am stuck at the first step in moving it over to mainnet, getting my contracts onto our account. Here is what I have done.
Created an account at port.onflow using blocto
Switched my blocto account to non custodian
Generated a new key in the account
Updated my flow.json file on my local system with the keys and settings according to this tutorial https://docs.onflow.org/flow-cli/configuration/#advanced-format-1
Attempted to add my contract to the account using the CLI
When I run this command
flow -n mainnet accounts add-contract NFTController \NFTController.cdc --signer mainnet-account
I get this error
Command Error: [Error Code: 1006] invalid proposal key: public key 0 on account e76dc37433d8ce45 does not have a valid signature: [Error Code: 1009] invalid envelope key: public key 0 on account e76dc37433d8ce45 does not have a valid signature: signature is not valid
You can see this on the chain at
Transaction ID: 1b6186a61095a8dba90e39c1ae862c3fccdf2f7bd2e2300253f64f44f3024931
When I created my account on testnet I used https://testnet-faucet.onflow.org/ and used the private that I used when creating the account to sign all transactions. I did not need to generate additional keys. Everything else in the process was the same and ran w/o issues.
My question is 2 fold.
Is there a way to generate a non-custodian account on flow mainnet w/o already have an existing account such as what I did on https://testnet-faucet.onflow.org/
Is the format https://docs.onflow.org/flow-cli/configuration/#advanced-format-1 correct for CLI v 0.33.0? If not what format should I be using?
Any help would be greatly appreciated.
I recently signed up for the Lite version (free) of Db2 in IBM. When I select 'open console', I receive an error message: {"trace":"89cc4337d11c197f1e4c12c51f027b77","errors":[{"code":"authentication_failure","message":"HWCSEC0016E: Authentication failed for SSO. This may caused by failed to generate access token in console side using existing credentials.","target":{"type":"","name":""},"more_info":""}]}. I've placed a couple of ticktets with IBM, but they say since I signed up for the 'free' service that they are unable to assist even though I only need assistance to access the service. Any thoughts?
Deleted the existing DB instance and created a new one in different location. And that worked for me.
There are multiple articles online, which tell you about the process to setup an self hosted integration runtime, and I understand we need to copy the authentication key provided by ADF and use it when registering the integration runtime on self hosted machine.
But I would like to understand:
(1) more details on how this handshake actually happens ? Does the auth key have certificate thumbprint ?
(2) does this key gets refreshed to ensure better security ?
(1) more details on how this handshake actually happens ? Does the
auth key have certificate thumbprint ?
Two main statements:
1.Self-hosted integration runtime node encrypts the credentials by using Windows Data Protection Application Programming Interface (DPAPI) and saves the credentials locally.
2.Azure Data Factory communicates with the self-hosted integration runtime via a control channel that uses a shared Azure Service Bus Relay connection.
Actually you could get more details about the Self-Hosted Command flow,especially the No.3 and No.4 points.
(2) does this key gets refreshed to ensure better security ?
Based on my investigations, there is no evidence that the auth key will be refreshed.If you concerns the security anyway, you could refresh it manually by yourself.
I've been getting this "useful" error message when deploying an experimental data factory pipeline that has a DotNetActivity within it.
Entity provisioning failed: The blob supplied is not valid. Blob:
customactivity/package.zip. Error code: . Error message: .
I've been reading trouble shooting tips and double checking connection strings, but to no avail.
After double checking everything in particular blob storage connection strings, I was eventually able to resolve it by copying the connection string from the azure portal -> storage account -> access keys into the azure storage linked service settings.
I can only theorize that there is a subtlety in the connection string format which results in a poor error message from the pipeline provisioning.
Interestingly, I can now put a completely wrong access key into the storage account linked service, redeploy it along with the the pipeline and it doesn't complain about provisioning. So perhaps there is additional checks done on the first provision.
We are using Blockchain as a service on a Bluemix account.
We have been using node-sdk to deploy, invoke, and query transactions on Bluemix.
Currently, we are facing an error on Bluemix when I call, invoke, or query function for the first time. The error says internal_metadata error. But if I call the functions for a second time, it works correctly. After some time (say 10 minutes) if we again call this function, it gives the same error.
Problem is similar to 38893402
I work for IBM Blockchain support. For this type of problem I suggest that you open a support ticket via the Bluemix dashboard. We will be happy to assist you with providing a solution.
Thanks for using IBM and blockcahin.