When you try to access, modify, or save a Smart Form, an error occurs when its tries to load the XSLT document. The error appears most often after a server migration, name change, upgrade, and so on, and is often caused by a communications issue on the server with the server unable to resolve its name into its IP address. Some operations, such as reading an XSLT file, require the server to make a request to itself. It the document cannot be loaded, the error results.
Error loading XSLT document.
Note: the SERVER is accessing this URL. Stylesheet must start either with an 'xsl:stylesheet' or an 'xsl:transform' element, or with a literal result element that has an 'xsl:version' attribute, where prefix 'xsl' denotes the 'http://www.w3.org/1999/XLS/Transform' namespace. Line 1, position 1.
Ensure the server can resolve its own name to it IP address by adding it to the hosts file. If your site is accessible by www. sitename .com and sitename .com you will need to add both names. On the CMS server, open the hosts file with a text editor such as Notepad (Run as Administrator). The file is located at C:\WINDOWS\system32\drivers\etc\hosts . Add the server IP address and name following the pattern in the file. For example:
# Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 220.127.116.11 rhino.acme.com # source server # 18.104.22.168 x.acme.com # x client host # localhost name resolution is handled within DNS itself.127.0.0.1 localhost::1 localhost192.168.14.999 ektronCMS01
- If adding the site name and IP of the site does not resolve the issue. Confirm in IIS that the bindings for the site and the settings in the hosts file match.
- If the bindings are correct, the proper IP and site names are listed in the hosts file, try adding in the localhost IP of 127.0.0.1. For example: 127.0.0.1 localhost . Then, reevaluate the behavior. Also, you can try adding the IP and machine name as well as the site name.
- If the above steps do not work, make sure that the site's WSPath can be resolved from the server hosting the site. The How to verify your wspath KB article contains more information on verifying the WSPath and updating it within the web.config file.
- If none of these steps help resolve the issue, test the behavior on the server vs. off-server, and see if the behavior is the same. This will help Ektron Support to evaluate a possible root cause.