JB and Bonnie....

From what I heard from others, I thought this was an issue with the default ASP.NET user account not having the necessary rights.

I was able to reproduce Bonnie's problem - but when I made the default asp.net account a member of practically every SQL Server group on my machine, it didn't take care of it.

So I'm curious about the answer myself. Maybe if Rick Strahl is reading this thread, he'll have an answer.

Kevin