I have a 'IBM Watson Studio Desktop Academic Trial' which is valid till June 17, 2020. I am getting the above message while launching the Watson Studio. Please let me know how to resolve it.
Contacted IBM Digital Commerce Site Support and they redirected me here.
We checked the backend, we see 2 accounts are using the same machine. To fix this issue, you need to move first user's subscription to a different machine (logout and login on a different machine). Please let us know if this info helps.
Id used to login to Watson studio needs to be checked in back-end system to ensure it is active.
Related
I have TFS 2018. I'm trying to connect visual studio 2019. I can already use tfs via web browser. I can log in and everything is fine. But when I try to connect through vs, I can't get authorized. I get
Server 'https://Myserver:8080/tfs' was not added. TF30063. You are not authorized to access https://myserver:8080/tfs
I researched the error code and tried all the fixes including deleting the windows credentials, running vs as admin and others. Like I said, I can log in via my web browser with no problem.
When I try to connect to project, It has my Microsoft account. I enter the above url and I'm prompted for my windows login (same for the browser) and I keep getting the error. I thought maybe I add the account before connecting, but when I try to add an account, the only popup wants me to use a Microsoft account or GitHub account. I can't add my Windows account.
So how do I connect my visual studio to my tfs server?
Thank you.
You should not get a Microsoft Account Prompt if you are trying to connect locally. The prompt is to validate your instance of VS towards your MSDN subscription. You would need to "login" with you Microsoft or Azure AD user that can validate your VS license and to be able to synchronize your settings from one VS to another. This login is the one here
Notice the account settings there, if you click on this you can also add your Visual Studio 2019 Static Key and then you don't need to login every month unless you want to sync your settings.
Bottom line, when connecting to TFS 2018 it will not ask you for Microsoft Credentials.
Please check whether you use the correct URL, and use http instead of https. Also, try the following items:
Close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService.
Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache
Click Add Azure DevOps Server and add the server URL:
I am using Appium Studio Community Edition for last 6 months; recently it is showing a dialog for SeeTestCloud SaaS Registration. Unable to use the Appium Studio without registration.
While trying to do registration process it is always showing error at email address filed like below. How to resolve the problem or how to keep continue free use of community edition?
If any one face this issue please avoid gmail, yahoo, and outlook email address for SeeTestCloud SaaS Registration. I have completed it by using gmx email id.
I am creating an application using ASP.NET MVC which has to integrate with salesforce.
I have created a developer account and also a trial account for Salesforce. Using my developer account I am able to achieve my desired outcome however when using my trial salesforce account I get this error
"The REST API is not enabled for this Organization."
I have also used another developer account of my mate it worked fine.
You are using Trail Edition (i.e. Professional Edition). Trail Edition doesn't include API access. If you want to try out api please use Developer Edition. Trial Edition expires after 30 days, but DE account doesn't expire.
Here is the list of salesforce editions with api access.
I am new to Windows Azure.
I got a subscription to use Windows Azure, However i am not able to publish my sample web site.
The Error is,
This subscription not registered use to following resources: Website The remote server returned unexpected response(400). Bad request.
My question is, How to register the subscription?
Thanks in Advance!!!
Senthilnathan Kumarasamy.
I just encountered this issue.
What you need to do is to logon into the Azure web console and create a web site through by clicking:
New > Compute > WebSite > Quick Create.
Then from within Visual Studio when you try to publish your web app, you will see the account in the import wizard dialog.
On my development machine (which has the Quickbooks SDK installed) I can connect and interact with QB just fine; the standard workflow of granting access to the external app from w/i QB works. However, on my production machine I get various and sundry errors:
Can't start QB.
Can't start QB because it's already running.
Can't open more than one company file.
The dev docs lead you to believe that the app must be signed while elsewhere I've found examples where you could run an un-signed example app. So what is it? If signing isn't strictly required then any clues as to why I can't get this to work?
Production Machine
QuickBooks Pro 2011 Release R9P (US)
Our installed, OOB, Silverlight app
Dev Machine
Quickbooks Premier Contractor Edition 2010 Release R13P (US)
Silverlight 4 using COM/C# to connect to QB
Quickbooks SDK 11.0
As I've said, the dev machine works as it should. On the production machine we've tried every combo of not having QB open, having it open but no client file open, having it open and a client file open and we'll get one error or another right at the point we're trying to open a connection. Also, our app never shows up in the integrated applications settings page (but it does show up on the dev machine's QB). We've tried both admin and non admin.
No, you DO NOT need to sign your apps.
You didn't provide anywhere near enough information for us to really give you a solution.
Did you check your SDK logs?
What version/year/edition/country of QuickBooks?
Are you building for the Web Connector, or using C#, or VB .NET, or...?
If you're using the Web Connector, what do your Web Connector logs look like?
Are you logged in as the QuickBooks admin user?
Is QuickBooks already running?
Is there another QuickBooks company file already open?
Did you revoke permission from the integrated application?
If you expect answers, you have to post some details.
It's a Silverlight app with full trust. It looks as though it was something with SL itself. Once we upgraded to SL5 it worked fine.