Server Error in '/' Application.

I am not using any foreign characters.  I still cannot send any PM or edit ascents that I have added to my ticklist. Up to date firefox or IE.  Not browser related.

Thanks. We have bought more space from the server provider. It will take some days until it is up and running. It seems to work in 98 % of the time. Please be patient.

I tried today and I was able to edit my ascents and I can send messages now. Thanks Jonas / Jens.

Work's almost fine, thank you very much. But still there is a encoding problem. When I search crags and type Rzędkowice it's gets translated to Rzędkowice ( Łutowiec -> Łutowiec , etc. ) So each time I add an ascent (with polish chars in it) then I have to go to my scorecard and correct everything.  Could it be fixed to ?

I have the same problem when searching for Tick Lists for crags that are not popular enough to get auto completion. Happens even without strange characters in the crag name. Same result in Firefox and IE9, irrespectively if I'm logged in or not. One example where it happens all the time is "Billingen". Stack trace: [NullReferenceException: Object reference not set to an instance of an object.] scorecard_Search.ButtonSimple_Click(Object sender, EventArgs e) +1927 System.Web.UI.WebControls.Button.OnClick(EventArgs e) +111 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +110 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +36 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565

Obviously it happens any time you search for a crag that is not yet registered in the crag database - even when people have used that exact crag name in their ascents. I'd expect that if it doesn't find the crag name in the database, it would instead find the ascents that are registered with this crag name. And if nobody has used that crag name ever, the error message should be replaced with a more informative message.