Despite using a unique module name (e.g. THIS was not the issue at hand), deploying my smart contract on kadena's testnet failed with the following error message:
: Failure: Tx Failed: Keyset failure (keys-any): '[my keyset name]
The only way to achieve a success was to assign a separate account that I control as the gas payer.
To elaborate for new developers:
When you hit "Deploy" in Chainweaver and fill out the form on the first page of the pop-up, you move to the SIGN tab and choose an account separate from the SENDER to pay for the gas fee.
In the following image we have two keys, red and green. Green is the sender, red is the gas payer. This is a configuration that has worked for me.
It is not clear to me, however, why this is the case or if there is a better solution.
Thank you in advance.
This seems to be just a Chainweaver web client issue.
On the non-web client, you can grant the capability and sign with the same key without issues
I don't think the answer above is correct. The desktop edition does indeed disable the use of unrestricted signing for a key as soon as you select it for a managed capability.
Related
I have 2sxc installed on a site. It was previously registered with the Patrons tokens for Core+, Patron Basic, and Patron Perfectionist.
I patched from 13.10.1 to 14.1.0. Now I get this error on all of my apps:
Warning: Registration is Invalid. Some features may be disabled because of this. Please reactivate the registration in Apps Management.
Under System, even though I tried re-registering my app by deleting the old one and starting a new one, I still see "Registered to: (unregistered)"
I went to reactivate my license but it doesn't make a difference. When I go to Extensions/Features, it shows as "Core (free for everyone)" 4/4 but nothing else.
I tried clicking "Retrieve license" but that doesn't seem to make a difference.
How can I register my app to get rid of this error message?
Sorry for the still clumsy process. We'll try to optimize ASAP.
The warning appeared because a major upgrade changes the fingerprint, so the previous activation is invalid. You will need to register the new fingerprint for things to work again.
On features-tab, just click on register and go through the normal steps to activate that fingerprint.
New to the forum :) - first post. I am trying to set up DocuSign in Salesforce for a client and keep running into an issue when trying to create an envelope template. Some context: my client has a DocuSign Business account (not Gen/ Negotiate), I have added the documents, and can add non-merge fields fine. The only issue is when I try to place the merge field, not create it, I receive an error:
Save Error: Some fields might be out of sync. Unable to connect to the service. Failed to connect to the salesforce service.
So far I have tried: adding IP addresses to Salesforce, removed MFA authentication for API, I have tried clearing cache and cookies, in different browsers, and in incognito mode - no success. I think I just have missed a step in set up? OR is this just not a feature of the client's current account and they need to enable the "Gen" feature to use merge fields?
Appreciate the help - I am also new to Salesforce administration and coding - so I am learning as I go and bear with me if I am not picking up all the "lingo" up front.
It sounds like you're using the legacy DocuSign for Salesforce package if you're not using Gen/Negotiate, so there are typically a couple of issues that could cause the error that you're seeing. The first is a caching issue, so you could try in an incognito browser or by clearing cache and cookies for the browser.
The other issue could be that the connection between DocuSign and Salesforce was broken and needs to be connected again. If that's the case, you could follow the steps in this article. If you're still running into problems, I'd advise to reach out to the DocuSign support team so that they can take a look with you (https://support.docusign.com/).
I have a strange error. When I try to load a public blob from Google Cloud Storage in a browser, I get the error "Your connection is not private".
And more strange, when I go to see the certificate, it is emmited to "*.JUEGOILEGAL.ES". For example https://storage.googleapis.com/ysi_production/newsletter-assets/chica_lupa.png
When I'm connected to wifi, there is no problem, but when I'm connected to mobile data, the error appears. I'm trying with some different network operators from Spain, and with some it happens, and others not. For example, with some MásMóvil and Pepephone it happens, with Movistar not.
What happens?
I suggest you try the following things:
Open the link in Incognito mode
Clear browser cache and cookies
Temporarily turn off your antivirus, just to check if there an issue there
Change DNS settings. For example to the ones provided by Google (8.8.8.8 and 8.8.4.4)
We have setup Notes federated login to provide a single-signon for Notes clients from Active directory. and there seem to be a problem when getting the "in memory" ID file from the Vault.
Here is the scenario
User start Notes (tried both v9 and V10) for the first time
Enter password in the Login screen for the local id file.
Message prompt "ID file is now downloaded for Notes Federated Login"
User click "OK" and a new message show up "Server Error - Entry not in index"
User click "OK" and then the passsword prompt for the local id file is displayed.
So, in short there seem to be a problem when downloading from the Vault but the error message do not really say much.
We have enabled all the client debug options and checked the server logs but nothing really tells us what is wrong.
All we get is this:
An issue that failed to authenticate was reported from the server / domain server: Entry not in index
Id-file is already in use and can't be changed
I can't diagnose the issue from reading your problem description. I suggest you open a support ticket with the steps to reproduce. ERR_NOT_FOUND (not found in index) is a very common return value in Domino, often even being benign. But in the benign cases it is handled by the calling code.
So it's hard to know what method/function threw the error or what the stack was at the time. Hence the advice to open a support ticket.
I've set up the sample program from here: https://github.com/GoogleCloudPlatform/cpp-docs-samples/tree/master/iot/mqtt-ciotc
When I try to run the example, the only error message that I get is:
'Failed to connect, return code 1'
I then moved on and tried the NodeJs version https://github.com/GoogleCloudPlatform/nodejs-docs-samples/tree/master/iot/mqtt_example
Using the same roots.pem, private and public keys, the NodeJs example works perfectly. I can view the incoming messages on Google Console.
Is there any tools available to help me debug what the issue is with the C example? Or any suggestions on what the problem could be?
Thanks,
A
There is a wide range of reasons to why this could be happening, including unsupported versions. The Documentation for Cloud IoT provides some steps that you should verify first, but since you connected from the NodeJS code, we can discard some suggestions. What you could do to check errors is to use gcloud:
gcloud iot devices describe DEVICE_ID --project=PROJECT_ID --region=REGION --registry=REGISTRY_ID
The devices describe command may show additional error messages that can be used to help debug, including to verify that your device's credentials are not expired. Although some errors may not show up, my impression is that bad username or password errors would appear.