11 Feb 2011
23 Feb 2011
Link to this post
After trying to replicate this several times in my local environment, here's what I think is happening.
There's a known timeout issue with Sitefinity 4, and it may be possible for you to be trying to come back in but your session/auth ticket have expired and thus you're going to get the message that everyone else would be getting.
After receiving this message the first time, I killed the database and attempted to run through initial setup again and didn't have the problem. I do, however, still get kicked out after a bit of time (15-20 minutes) which would correspond to the known timeout issue.
The site I was working with is on shared hosting and the app pool recycles, which is what's causing the timeout - look up the SP1 release and you'll find a note about it there. I believe it's slated for rollout sometime this week.
Long story short, my issue has been resolved by recreating the database, but it seems like once the app gets in that state, it has some unfinished processing that never gets to be done because you're kicked out of the Admin site. Maybe resetting IIS works, I don't know, but redeploying it to the host fixed it for me.