Question : After SharePoint database restore Web Parts dont function

Hello, I recently had a SharePoint 3.0/MOSS 2007 snafu.  Using Symantec Backup Exec 11d I attempted a full restore of the content database.  This restore completed successfully, but it has left both the (main) Sites and Personal sites sections non-functional.  Although you can pull up the pages, any of the content that was a Web Part now shows Error [#]: Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists. (Needless to say, this equates to about 99% of the content!)

I can create new top-level instances, and those will function.  To keep people working, I created a new instance, and then manually placed all the files into the new instance. (That was sure tons of fun.)

I think I am close, and likely it is some SQL (2005) or IIS / .Net security setting, or a stsadm command that needs be run, but my users (and my nerves) cant take anymore down time, and I have no lab set up for this at the current time.

Answer : After SharePoint database restore Web Parts dont function

okay to close this question.

looks like the restore created its own instance in IIS? then the IIS addresses didnt match in the farm/load balance, so when you were on the old (used to be correct) node it would generate this error.

that may not be the exact thing, but to the best i can tell thats what happened.