Forums » Bugs & Problems » Read Thread

Server Error in '/' Application.

Value cannot be null.
Parameter name: source

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: source

Source Error:
 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:
 

[ArgumentNullException: Value cannot be null. Parameter name: source] System.Linq.Enumerable.Where(IEnumerable`1 source, Func`2 predicate) +5901004 ChooseYourStory.WebApplication.Pages.Forums.ForumsListPage.CreateChildControls() in c:\BuildMasterAgent\_AGTTMP\_A4\_S11\SRC\ChooseYourStory.WebApplication\Pages\Forums\ForumsListPage.cs:83 System.Web.UI.Control.EnsureChildControls() +189 System.Web.UI.Control.PreRenderRecursiveInternal() +60 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4297

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34280

 

It's back. This annoying error has struck once more. It won't allow you to go to a general forums page (Like the games or lounge) and forces you to edit your url in order to get where you need to go.

Any solutions?

Well, now it's cleared up.

You (and all the hundreds of other people who have put this exact thing in the B&P forum) should read these things, they provide a wealth of info regardless of your expertise or understanding. Even a complete noob could understand. Read the description, "An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code." sure you might not know what this means but you can infer based on general knowledge of some of the words meanings.

Such as "unhandled exception during the execution of the current web request" - alright, so something was unhandled - probably creating this error message. In fact, it was unhandled during the execution of a web request. So let's reverse this, there was a request - we can presume this is your computer "requesting" to access the site via the interwebs; and during the execution of this task, something went unhandled. Who knows what?

Actually, we know because it's listed at the very top! How helpful! A "server error" - "so what?" You might ask. "I don't know what a server is; and I can tell there was an error."

Ah, but you do know what a server is. Think about the word and it's meaning - one which serves. What does that mean out of the context of a restaurant and in the context of a website? Well, obviously this means that an internet version of a "server" is serving the website to you, because you ordered it by executing a request. See how it all connects? Just by reading these small laymans terms in the error, and focusing on what we know we have found out that:

1. We made a web request; a request to view the site.
2. There was an unhandled event which stopped us from viewing the site.
3. This caused an error; but not our error - after all, we didn't do anything wrong or unusual. It was the server which made the error.

When a restaurant server makes an error, they apologize and give you a reason; in the same way, the internet server has given you a reason for the blunder. In a restaurant, the server does not just stand there and do nothing while you mull over their error - they fix it and come back later with the proper requested item. In this case, the web server is the same way - it will not stand idle until the end of time, it will start over, clean up the error, try again, and bring you the requested website into view.

P.S. sometimes the mess is so big they need help from their boss - ie the admins to clean stuff up and fix things; however most bosses don't fire their worker for 1 blunder, so it's alright because they trust the server can handle itself. We should trust that the server can handle itself as well; and give it time to correct itself. Nothing is perfect, not even computers.

TL;DR: pay attention to Ford

Lol.