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
Related
I have started learning oracle APEX and installed oracle apex 20.2 on my desktop PC just now. I am facing a problem that on running a sample application after install it shows me 404 - Not Found error.
Can anybody help me on this issue?
I had a similar issue when I imported an application. Try this: in application properties untick "Friendly URLs" and run it again.
If you're still getting the issue show the end of your url (all parameters after the server).
I have solved this issue. Actually the issue was with the user rights. I created a new user other the APEX_PUBLIC_USER and then the APEX was not working well because my new user didn't have those rights which APEX_PUBLIC_USER has.
I solved it by configuring the APEX back to the APEX_PUBLIC_USER and it runs well.
I have cloned the click-to-call repository and followed the steps as mentioned. I am able to login with said created user but then get stuck at /rtc API.I got some error in network panel. and "General SSL engine problem in console which is not correct. SSL certificates are all correct." Let me know where i went wrong. Please check the screenshot below :
I have had a talk with nexmo team, they said it is the ssl issue.
https://help.nexmo.com/hc/en-us/articles/207051767-Certificate-for-nexmo-com
Now I am unable to find where to import the certificate to my app?
I am the JavaScript Developer Advocate at Vonage (Nexmo).
You also filed an issue at https://github.com/nexmo-community/client-sdk-click-to-call correct? Thanks for that. I will also post my response here.
From your issue, it looks as if the Conversation Id is not being sent.
We recently merged some changes to the repo.
In your .env file, do you have SUPPORT_PHONE_NUMBER? That should be NEXMO_NUMBER.
Also, when calling the server, previously the code in the client.js around line 34 was application.callServer(); it is now application.callServer(application.me.name);
Let me know if this works for you.
Check with Nexmo - either you are out of balance or your account has been been marked inactive for some reason. Most of the time its because of insufficient balance.
Background: I am working on a product which is built using AngularJS in the front-end, and Microsoft Web Api in the back-end. The website is hosted on a Windows Server 2012 machine running IIS. We are using Windows authentication to connect to the machine.
The problem: Calling various API methods work flawlessly for me and the majority of users. But for some of the users, they cant perform certain API calls. Most of the endpoints work and return valid data, but a few methods never even gets reached.
This is the error in the iislog: 2016-05-26 12:25:23 xx.xx.xxx.xx POST /api/controller/method - 80 domain\user xx.xx.x.xx Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.1;+WOW64;+Trident/6.0) http://xxxxxx.com/#/Pagename 500 0 0 514
In the console in google chrome it says: Error: Access denied.
I have set the api to log all exceptions to a database, and no error is shown. So my theory is that the api doesnt even get reached when trying to perform these specific http methods.
I have tried searching for answers, but without any luck. Does anyone have any idea?
I finally found a solution to my problem, the exception being thrown was a DbEntityValidationException. It was thrown because some of the users names were too long to be inserted into the database table. It was not catched and properly displayed by my own general exception handling. I had to follow this guide to get the proper exception logged:
https://stackoverflow.com/a/6258174/3592773
Thanks for all the help and I hope this might help someone else in the future.
Very simple problem - stuck at step 0.
I've downloaded the SDK, got my application working locally etc.
However when I visit https://appengine.google.com/start and click 'Create Application' I get a page that says
Server Error
A server error has occurred.
This is my first time using App Engine so I can't access dashboards/control panels/account areas or whatever is deeper than the non-functional 'Create Application' button.
I realise that this isn't a programming problem (well, in a sense it is but it's not my programming problem) but I'd really appreciate some help.
Login at appengine with your gmail account.
We have a WPF application...which is deployed using click once approach.
We deployed it in a intranet webserver...and people can install it in their machine from a link available in a web page (index.html).
One of hour team member got the following error
Jit debugging failed with following error: Access denied
jit debugging was initiated by the user account "abc\abc918"
Click the documentation index for "just in time debugging errors for more information"
Please help me to understand what is this error about. Thanks in advance.
This is typically a result of having System.Diagnostics.Debugger.Break in your code. This requires the current user to part of the "Debugger Users" group in order to function. If you are not, then you'll receive this error.
This frequently occurs on hosted ASP.Net sites - see this KB Article for details.