Oops! after deleting posts directly from be_Posts

Nov 13, 2009 at 4:23 AM
Edited Nov 13, 2009 at 5:17 AM


I had a site that was working fine, until I deleted directly from be_Posts in the BE database three test posts that had been created ... meaning I didn't use the web front end to do the deletes.

Now the major features of the site - default.aspx, archive.aspx, admin cpanel, etc... all result in Ooops message and


500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.


This all started when I did the manual delete.  I've tried refreshing the IIS cache, but no luck...

Any advice?


Nov 13, 2009 at 4:15 PM
Edited Nov 13, 2009 at 4:15 PM

Hey everyone, this turned out to be caused by some columns in the be_Posts table where I had inserted NULL values.  It seems be_posts columns allow NULLS, but if you leave the columns NULL you will have trouble.  Solution was to add default values instead of NULLs.

if you don't feel like digging thru .net source code, an easy way to see which default values to use is to create a dummy post and then look at the result in be_posts....