The garbage text is something that I've seen with BE many times. It shows up when an unhandled error occurs. Depending on where the error is occurring, you'll sometimes get a more normal error message, and sometimes you'll get those garbage characters.
You could try replacing the Application_Error handler in the global.asax file with the one below. It might work better. I think what might be happening now is that the unhandled error occurs, Application_Error is picking this up, but then another
unhandled error is occurring within that.
If you cannot get an actual error message, you could try deleting data out of the be_DataStoreSettings table. I think someone else recently had a problem with data in that table that caused an error. Not sure if that's the case here too.
Extension and widget data is in that table. Probably only deleting the Extension data is necessary (I'm guessing the widget data is okay). So the DELETE statement would be:
delete be_DataStoreSettings where ExtensionType = 0
... and here's that modified Application_Error handler for the global.asax file you could try using before deleting any data.
void Application_Error(object sender, EventArgs e)
HttpContext context = ((HttpApplication)sender).Context;
Exception ex = context.Server.GetLastError();
if (ex == null || !(ex is HttpException) || (ex as HttpException).GetHttpCode() == 404)
StringBuilder sb = new StringBuilder();
sb.AppendLine("Url : " + context.Request.Url);
sb.AppendLine("Raw Url : " + context.Request.RawUrl);
while (ex != null)
sb.AppendLine("Message : " + ex.Message);
sb.AppendLine("Source : " + ex.Source);
sb.AppendLine("StackTrace : " + ex.StackTrace);
sb.AppendLine("TargetSite : " + ex.TargetSite);
ex = ex.InnerException;
catch (Exception ex2)
sb.AppendLine("Error logging error : " + ex2.Message);