4. Problems that may be encountered when publishing to IIS

    In fact, there is no difficulty here, and students who have experience in using IIS can do it by themselves. At that time, I encountered two problems, which I guess are typical problems. One is that I can leave a memorial in my blog to commemorate the pits that I have filled; the other is for those students who are likely to fall in these pits.

1. Service mode error

    First of all, VS itself has the function of publishing a website. The mvc program you develop can use the publishing function of Vs to publish to the Azure cloud, IIS server, and specified directory. I choose to build a website in IIS first, create a hard disk directory, authorize IIS access rights, and configure the application pool is the key. For our MVC program, we must select the option of .NET v4.5, and then IIS can automatically recognize it. If you choose the classic mode, the MVC5 program will report an error when running, telling you directly that you need to use the integrated pipeline mode.


2. Failed to map path error

    The screenshot of the error is as follows:


    This is actually caused by the hard disk path permission problem. Orchard needs full control permissions. There are a total of 4 directories, namely App_Data, Media, Modules, and Themes. Set them as IIS browsing users with full control permissions.


    Then restart the IIS service, pay attention not to restart the website. I have been here for a long time, and finally restarted the computer and it was done. After thinking about it, it's right. IIS needs the permissions of this directory. Of course, IIS needs to be restarted.

    The above pits took me a long time. I believe that with this set of blog posts of mine, you can solve these problems in an hour or even half an hour.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325572054&siteId=291194637