UPDATE: Dave Burke here. Ignore this article. It's CRAP! Oh, it works, but use Sean Winstead's fix instead (remove the TextMode attrib from the db_password textbox. That's it!) I also reposted an excerpt of it on CS Forums here. Okay, on your way now.There's a CS Forums thread on an Installer error I encountered this past weekend while setting up a CS 2.0 Demo site on my home office network. I was working with a Telligent client this afternoon on a site configuration issue who told me they encountered the same error. Both with me and the client, walking through the SQL setup scripts brought everything online ship shape and in bristol fashion. Still, this is Community Server we're talking about here. A bug in the Installer? I don't think so.
People on the Forums thread were claiming that the CS 2.0 Installer only worked in .NET 1.1. I didn't have to check with the Telligenti, cause I knew that notion just had to be bogus. They did, however, accurately point to the problem being an ASP.NET 2.0 issue. I never encountered this problem in ASP.NET 1.1. I had to take a couple of minutes to prove that the CS 2.0 Installer did work with ASP.NET 2.0, and with particular attention to working in a shared hosting environment.
Here's the error that people might see using the CS 2.0 Installer in ASP.NET 2.0.
Here's the fix in a nutshell: make sure the IIS account for the CS 2.0 site has ownership of the CS database and that impersonation is turned on in the web.config.
First determine the user account used for anonymous access to the site. With most host providers from my experience this is your user account.
Then make sure that account has ownership of your database. Yeah, yeah. Not the best practice to give ownership to the IIS_WPG as you see below. This is just an example. If you have access to the server and you did indeed run CS 2.0 with IUSR_, you can always remove IIS_WPG access from the database afterward. All SQL access post-Installer is based on the SiteSqlServer connection string.
Remember to add the Identity impersonate="true" to the web.config and that should take us through the Installer steps successfully.
So to wrap up, make sure the IIS account for the CS 2.0 site has ownership of the CS database and that impersonation is enabled in the web.config.
[tags: Community Server, IIS]