Installation - missing a step?

Hi:

I am trying to install nopcommerce on a dedicated server.  The automatic install package can't be used because it keeps asking for the SQL SERVER password for "sa" even though the SQLSERVER is only using Windows Authentication.  So, I'm trying to install it manually. I created the folder, placed the files in them and created a website in IIS pointing to the new nopcommerce folder.  The application pool is set to use .NET 4.0 and is in integrated mode.  But, when I navigate to the site, internet explorer returns the "page cannot be displayed message".  No other error message is thrown and there is nothing in the standard windows events logs that give a clue as to what is happening.  So, I think I am missing a step but everywhere I look it seems that I took the proper steps for the manual install.  Looking for ideas on what I might have missed that may not be in the official documentation.

Thanks in advance.

-eLindy

Check the documentation.

(P.S.  There is an option for "Use Integrated Windows Authentication")

Thanks for this.  I did go through the manual multiple times before I posted my issue.  Unless I am misunderstanding the documentation, I have two options for installation without source code - use the web installer or do a manual install.

If I use the webs installer, no nopcommerce files are present at the time of installation so there are no options to edit anything except what the installer provides.  And it only provides for login to SQL SERVER using the "sa" user.  Since I used integrated windows login, I can't proceed beyond that dialog box so I have to abort the installation.

If I do the manual install, I run into the issue I mentioned in the OP - I never even get to the page where I can connect to the server.

I hope you can see my dilemma.  

Thanks.

-eLindy

New York wrote:

Ok, so it looks like there were a few footnotes missing in the manual for my unique situation.  

IF you want to allow the installer to create the database AND you want to use only Windows Authentication then you are going to run into security related issues because the security identity used by the web server application pool are not sufficient to accomplish these things.

First, you want to temporarily change the identity used by the web application pool to the windows administrator account. Run the installer so it can install the database.  After the installer runs you'll get the home page of the site.  At this time, reset the web server application pool to the default of "ApplicationPoolIdentity".  After you do this and you restart the pool, if you refresh you new home page you're going to get another security error.

The error will be something stating that the database cannot be opened because the login failed for "IIS APPPOOL\YourAppPoolName".

To fix this one has to realize that the "ApplicationPoolIdentity" is really a hidden windows user that was created at the time the application pool was created on the web server.  So, hidden inside windows is a user that you can't see called IIS APPPOOL\YourAppPoolName.  The full name will show up in the error message - copy this name to the windows clipboard.

In SQL Server, create a new login and paste this name in as the login name.  DO NOT click the search button.  Make the default database of this login your new nopCommerce database.  Next, go to the nopCommerce database and create a new user.  Make the User name and Login Name this same name (paste in from the clipboard).  Do not use the search function.  Make it a database adminstrator.

Now you can go back to your web browser and you should be able to navigate to the home page.

I don't know how many other people know about this combination of steps but if someone is an editor of the manual, maybe its worth putting some of this information in there in the installation section?  It certainly would have saved me a ton of time if it was there.  Normal installations that use the "sa" login will never encounter these security related complications.