installation with IIS

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
12 years ago
I'm running IIS 6.0 (and know very little about IIS and/or web development in general) and trying to get Nopcommerce with DEMO data running (it runs fine within VS2010) with IIS on a test server running Windows Server 2003 R2 SP2. Here's what I've done so far:

1. Successfully ran Nopcommmerce within VS2010
2. Successfully ran Prepare.bat
3. Successfully ran Deploy.bat
4. Created a folder named nopcommerce under c:\inetpub\wwwroot
5. Copied all of the files and folders from the Deployable folder (created by Deploy.bat) and PASTED these into c:\inetpub\wwwroot\nopcommerce folder  (user guide said to "Upload them to the root of your directory that is setup for your domain).  However, I have no domain.
6. From IIS selected New, Web Site and pointed the new site to the path c:\inetpub\wwwroot\nopcommerce
7. Select ASP.NET 4.0 as the targeted framework for the new website created in step 6
8. restarted iis via iisreset
9. Opened a browser and entered http://Server1 (the name of the server being used).  
10. Received http error 403: the website declined to show this webpage

Can anyone point me in the right direction?  

Thank you for any assistance you can provide.
12 years ago
If its for testing, create a web application under the default website then you shoul be able to access nop under server1/nopcommerce (assuming you keep the same folder structure)
12 years ago
Thank you for responding, Keesjan.  I had previously DELETED the Default website which is automatically created by IIS6 upon installation.  I was thinking (apparenly incorrrectly) that the new webiste which I created in IIS for nopcommerce would automatically be my new "default" website for Server1.

Thank you for your help!
12 years ago
I just entered http://Server1/filenotfound.htm in my browser and the FileNotFound page is executed.  So, I suppose that means IIS is pointing to the right website....it just seems that there's no "default" page or code to be executed in my default website path???  not sure what I'm doing wrong
12 years ago
do this steps.

open iis. under site>default websites right click add new new application> select your application pool (asp .net 4.0)> select and give physical path. and press OK button. then right click your site application>manage application > browse.

your site will open. if not opening check mvc3 platform installed on iis. check application pool is started.

http://www.elaamart.com
12 years ago
register asp with IIS by running the command line app: aspnet_regiis -i
12 years ago
make sure you new website has the correct binding (port 80 for all
ip addresses)
12 years ago
Thank you for your assistance efforts!  Here's what I've done today:
1.   I ran aspnet_regiis -i from the .net4.0 framework directory...it registered fine.

2.   I ran iisreset to restart iis...no problem there

3.   I check bindings to port 80 for all IP address

4.   open browser and entered http://server1/errorpage.htm (thinking that this may be a test whether iis is pointing to the correct website...???).  The errorpage.htm page displays fine.

5.  entered http://server1/install (instructions says to enter http://www.yourstore.com/install .... however I have no domain)....so I thought maybe http://server1/install would be the localhost counterpart.  However, I received "The page cannot be found" (http error 404)

Is there a specific page which needs to be executed??  Thanks again for any insight you can provide!
12 years ago
Mystery solved, thanks to the efforts of an experienced web developer.  In MY particular case, everything was apparently setup correctly for the website.  However, when I would attempt to run http://myservername/install, I would receive an error message.  As it turns out, my IIS installation was not able to run a file with a .cshtml file extension...specifically the file index.cshtml found inside the INSTALL folder.  The remedy was to add an entry in the application configuration mappings for the .cshtml extension and the Executable path for the aspnet_isapi.dll for the .net 4.0 framework.  After that was added, I was able to proceed with the installation.


Thanks again to the community for your efforts!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.