Error on Matt Thornton

ASP.NET Core OAuth Facebook cancel causes 500 fix

Wed, 04 Mar 2020 15:16:49 +0000

If you’re using ASP.NET Core built-in authentication to allow your users to sign up / login to your web application using alternative providers, Microsoft provides various out of the box, such as Microsoft, Google, Twitter and Facebook.

Chances are you have something like the following in your startup.cs

services.AddFacebook(options=> ...)

This works pretty nicely. All you need are you keys and secrets (hello Urban Cookie Collective) and all should rock.

However, an issue arises if your user clicks ‘Sign in with ’, which (if they are not already signed-in) takes them to that app to sign in, but if they then cancel that (e.g., clicking the ‘Not Now’ link on the Facebook screen) can result in a ghastly 500 error.

SSRS error: Operation is not valid due to the current state of the object

Fri, 10 Feb 2012 12:27:50 +0000

If you’re using SSRS in SharePoint integrated mode, you may come across this error when using report parameters that have a high number of items in them. A recent security bulletin highlighted some issues and vulnerabilities in ASP.net, and a patch was released to cover some of the items. One of these was the maximum number of items you can have in a collection. If you exceed the limit, then you’ll likely get an error like:

Error occurred in deployment step Activate Features: Invalid field name.

Mon, 12 Sep 2011 13:50:02 +0000

I posted about an issue I had been facing with deploying document sets via XML, where things like the custom welcome page and the shared fields (defined in XmlDocuments) wasn’t showing up.

Here’s a further issue I encountered. I defined my Document Set content type in the usual way. A bunch of Site Fields, then the Content Type definition, and then within the FieldRefs section some FieldRef elements for the fields to use.

At some point, I started to experience a strange error - when I was deploying the solution, I would get an error:

Leopard, iTunes & Airport Express: An unknown error occurred (-3256)

Tue, 27 May 2008 18:07:06 +0000

You may find you get the following problem when trying to stream music to multiple speakers. Streaming to either local computer OR your airport express works, but when you try to stream both, you get an error message that looks like this:

“An error occurred while connecting to the remote speaker ‘speaker_name’. An unknown error occurred (-3256).”

This is most likely caused by a firewall issue. If you’re running Tiger, then there’s a fix here. If, however, you’re running Leopard, then it’s a little different: