I am repeatedly getting the error:"Error in Watson Visual Recognition service: Cannot execute learning task. : this plan instance can have only 2 custom classifier(s), and 2 already exist." It will not allow me to train my model. Can anyone help? Thank you in advance!
If you do not see 2 custom classifiers when you list yours (GET /classifiers endpoint) then there may be a problem with your account, which would require filing an IBM Cloud technical support ticket to resolve at https://cloud.ibm.com/unifiedsupport/cases/add once you're logged in.
Related
I am using IBM Watson Visual Recognition for a custom model. I have uploaded my dataset as .zip files, which is fine so far. However, I cannot train the model. When I go on my Watson services, it says:
Error fetching custom collections: Error in Watson Visual Recognition service: Recieved invalid status 403 in getAllCollections response for guid crn:v1:bluemix:public:watson-vision-combined:us-south:a/649b0335a5a44f6d80d1fd6909e466f9:8a71daa3-b0be-42ac-bb72-1473de835c19:: at endpoint https://gateway.watsonplatform.net/visual-recognition/api/
When I try to train the model, it says:
"Error in Watson Visual Recognition service: Request Entity Too Large"
To the best of my knowledge, I have checked Google and StackOverflow for solutions, but didn't find any. I am using the Lite version. I only have one project, and one Visual Recognition instance. Please note that it worked for a different Visual Recognition model before, but later I could not use or access that model. So I deleted the older, trained model and tried to create a new one with the above mentioned error.
Does anyone know a solution?
Thanks for your interest in Visual Recognition.
HTTP 403 is a standard HTTP status code communicated to clients by an HTTP server to indicate that access to the requested (valid) URL by the client is Forbidden for some reason. It indicates some problem with your account access.
The "Request Entity Too Large" is a bit misleading, it happens sometimes when the error should be a 403 on POST requests, like training.
As a lite plan user, you may have used up your free credits for the month, for example.
You should double check that you are providing the correct credentials, and check the usage dashboard of your IBM Cloud account, which is described here: https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-viewingusage
If this does not resolve your problem, you can open a support request here https://www.ibm.com/cloud/support
I have used Google Cloud Functions for quite a long time, with no real authentication problem for now.
Today I meet this error while deploying a new function
ERROR: (gcloud.functions.deploy) ResponseError: status=[400], code=[Bad Request], message=[Default service account 'PROJECT-ID#appspot.gserviceaccount.com' doesn't exist. Please recreate this account (for example by disabling and enabling the Cloud Functions API), or specify a different account.]
I tried several things :
disable/enable GCF API : no service account recovered
gcloud beta app repair reference here
No default service account recovered
the undelete API POST call
If I understand well the current GCP features, using the last option is my best solution, but somehow I keep getting a 400 error
I found my unique-id in my log activity at the creation of the default service account
I really can't see where is the problem in the undelete API call and would be really thankful if you could help with it
Thanks to #Maxim, I know now that my problem comes from the fact that the deleting of this service account happened more than 30 days ago. Which means that it has already been purged from the system and it's not recoverable anymore.
In case you meet this same kind of problem, please try out this link :
https://cloud.google.com/iam/docs/creating-managing-service-accounts#undeleting_a_service_account
I see three alternative ways in how to proceed here next:
Create a new project from scratch to work from.
File a support case via the support center.
Open a private issue by providing your project number in the following component.
I believe it's convenient in reaching out GCP Support for help at this stage, and recommend you to do so; seeing as you've attempted most if not all ways of Service Account recovery to no success.
On a last note, as for the latter option, the contents of the private issue will only be visible to you, and to the GCP Support staff (us). If you choose this option, please let me know when it's opened, and I'll start working on it as soon as possible.
I am currently in development mode for the skill. It is using Lambda endpoint. The skill is working in https://developer.amazon.com/alexa/console/ask/test/
When I sent invites for Beta testing and followed the Beta testing instructions on a different (email account with Alexa), the application is giving “Unexpected communication issue: There was a problem communicating with the requested skill”
Request identifier: amzn1.echo-api.request.[some-id]
I am not getting any logs in CloudWatch for my Lambda function
[Update] More info:
The skill is available in all countries and regions where Amazon distributes skills.
This is a dummy skill, with only one intent, triggered by a command like this Alexa open mySkill and tell me a new fact, after which the control passes on to Lambda function which selects a fact string randomly from an array.
Solved it finally. The problem was mainly due to 2 reasons:
I had created multiple skills (for testing) and didn't noticed that
they had similar invocation words (silly me :/ ). One of them was
pointing to an older AWS account. Thanks #ChuckLaPress for the hint.
Language settings. I had used the default en-US language and was trying from India. Solved it by including support for all other english languages. Details here.
I am new to Salesforce and I have to Integrate Bicom in Salesforce to send Fax.I have researched alot on this but no luck.
Any help would be appreciated.
Thanks in Advance.
I've answered the same question on developerforce and stackexchange. Unfortunately it doesn't exist, but we created it. Biscom's solution only handled communications between SFDC and a Faxcom server. Everything inside SFDC had to be built. We just finished a full implementation of the Biscom/Faxcom to SFDC, complete with document generation/handling for faxing out from Accounts/Contacts/Cases as well as inbound routing using a barcode to automatically attach the returned fax to the Contact/Case Object. Be happy to discuss further if you're still interested, otherwise you'll want to reach out to Biscom for their basic connector. Here's pics:
Inbound Fax Wizard and
Sending Outbound Fax
I have a web application that has been up and running for quite some time now using the Windows Live ID delegated authentication. It's been in production for a couple of months, and all of a sudden this morning, it failed with the following error:
There's a problem with the site you are trying to share your information with. Please try again later.
The url of the error page is
https://consent.live.com/pp700/Error.aspx?mkt=en-US&ErrorCode=1017
We require users consent to be able to see what e-mail address they used to log in. Has anybody run into this before? If so, what did you do to resolve it?
Thanks very much!
Still not sure what the error actually means, but the following forum posts give some more details. Basic problem: Microsoft changed the API and didn't tell anyone, Contact.View should be ContactsSync.FullSync when using the contacts API.
http://social.msdn.microsoft.com/Forums/en-IE/wliddev/thread/7f0bcc69-d256-4e2d-a596-25e6318d83b5
http://social.msdn.microsoft.com/Forums/en-IE/wliddev/thread/7ade3e5b-8329-4dde-b08b-a98515363383