Community Server 2.1 provides excellent support for Forum blogs and album news, and uses cool Ajax, Tag, RSS, and other technologies. Community Server 2.1 adopts ASP. the net2.0 architecture has recently seen many people install Community Server 2.1 locally. However, once you install Community Server 2.1 on a remote web server, I have summarized several common problems and their solutions below. I hope this will be helpful to anyone who remotely installs Community Server 2.1 to a VM:
Problem 1: Community Server 2.1 has no problem on the local machine. Once it is installed on a remote Vm, posts in the forum cannot be opened, and images in the album cannot be opened. If you click Next, cs2.1 will report an error, why is the system unable to find the file?
Solution: Because cs2.1 uses urlrewrite technology to enable search engines to better find the post, this virtual URL is actually completed through the URL rewriting class of cs2.1, in fact, this post or the path of this image does not have a physical path but is virtual. The reason for this problem is that when we install iis60 locally, in fact, "check whether a file exists" on the ISAPI ing corresponding to aspx is not checked, while remote virtual hosts are sometimes in security considerations. During configuration, "check whether the file exists" is directly defaulted, which leads to an error where the file cannot be found, because the URL information has not been added to the ISAPI extension of aspx, It is intercepted by iis60 and an error is reported.
Question 2: The management menu bar in the background is not displayed. A script error is prompted and a class cannot be found?
first, the management menu of cs2.1 is a third-party control (componentart), and a large number of scripts are used in this control package. Therefore, compnentart adopts ASP. the web resources management model provided by NET 2.0 manages external resource slices, scripts, CSS, and so on. This saves a lot of copy and include processes, but this brings about a new problem, that is, if the IIS server is not configured. for this type of ISAPI ing, you cannot manage your external resources by using webresources. The problem is that your local IIS is usually added during installation. in this way, the remote virtual host may not have such a ising, leading to problems.