Answers

Common Problems

Broken Image Links after Deploying to a New Server

Since version 3.1, Sitefinity uses Dynamic Link Parser whose function is to modify links added through modules based on Generic Content. By appending the protocol, domain and port to the front, the Dynamic Link Parser changes the links with a URL in the local machine to absolute links, independent of the application or server name. So for example, when you move your project to the production server, the links with local URLs are changed automatically. Note that the parser is dynamic; this means that the content is changed only on demand and stays unmodified in the database.

By default, the Dynamic Link Parser is enabled. To turn it off, you should add the disableLinkParser attribute of the corresponding generic content provider in telerik > cmsEngine > providers section in the application web.config file and set it to true.

If however, your image paths are wrong after deploying the site to a new server, try one of the following:

If you have added your images through the Image control, run this script into the database:
UPDATE sf_CmsControlProperty SET Value = REPLACE(Value, '/VirtualDirectory/', '/') WHERE (Value LIKE '%/VirtualDirectory/%')
If you have added your images though the Sitefinity modules, run this script into the database:
UPDATE sf_CmsTextContent SET Content = REPLACE(Content, '/VirtualDirectory/', '/') WHERE (Content LIKE '%/VirtualDirectory/%')

Note that you must cast ntext to varchar(8000) or nvarchar(4000) in order to use the REPLACE function in SQL Server 2000. For example:


                 UPDATE    sf_CmsControlProperty 
                 SET    Value = REPLACE(CAST(Value AS VARCHAR(8000)), '/VirtualDirectory/', '/')

Disabled ContentPlaceHolders

Back to topWhen you go to the Pages > Templates tab and try to edit a template, you may notice that you cannot drag controls to the ContentPlaceholders. Sometimes the Edit button in the control header is unreachable.
To eliminate this problem:

Open the .master file your template is using.
Make sure that there are no characters between the opening and closing <asp:ContentPlaceHolder> tags:
<asp:ContentPlaceHolder ID="main" runat="server"></asp:ContentPlaceHolder>

Alternatively, you can close the tags like this:
<asp:ContentPlaceHolder ID="main" runat="server" />

Single Posts and Comments do not open

Back to topIf you have a Blog Posts control on a page and you duplicate this page, you will not be able to open single posts or comments on the result page.
The resolution is to edit the result page and publish it afterwards.

Cannot log in a new project

Back to topSometimes, after you create a project, you are directed to the Sitefinity Login page, skipping through the phase that sets up the project database and the site administrator account. In other words, you are never directed to the Project Startup wizard (http://localhost/YourProject/sitefinity/cmsstartup.aspx). This happens quite often and is basically due to incorrect IIS settings. To troubleshoot this, make sure the Sitefinity3.x (Project Manager) virtual directory is moved to the Classic.NET AppPool:

Launch IIS Manager from Control Panel > Administrative Tools.
Expand the tree in the Connections pane and then expand Web Sites.
Right-click the Sitefinity3.x directory and select Advanced Settings.
Change the Application Pool setting to Classic .NET AppPool.
Click OK to apply the changes.
Restart the Classic .NET AppPool.

The Project Startup wizard should then continue to the step where the database is configured.
However, if this does not happen, you need to check if the pool is configured as described in section Configuring the Classic.NET AppPool of the Sitefinity User Manual.

No CSS?

Back to topIf Sitefinity looks as if its css is not applied, you need to check Handler Mappings in IIS.

Launch IIS Manager from Control Panel > Administrative Tools.
Expand Default Web Site, expand telerik and click Sitefinity3.x.
Double-click Handler Mappings and scroll down to StaticFile.
Right-click StaticFile and from the dropdown menu, select Edit.
In the Edit Module Mappings dialog, go to the Module field and paste this:
StaticFileModule,DefaultDocumentModule.
Click Request Restrictions… and at the Mappings tab, make sure you select these options:
Invoke handler only if request is mapped to: File or Folder.
At the Verbs tab, make sure the All verbs option is selected.
Click OK.
Restart the application.

Problems in administration area when running in Integrated pipeline mode

Back to topIt is recommended to switch to Classic pipeline mode. Here is how to do it:

Launch IIS Manager from Control Panel > Administrative Tools.
In the left pane, double-click Application Pools.
Double-click Classic.NET AppPool in the list.
Select Classic for Managed pipeline mode.

Cannot recover Sitefinity admin user credentials

Back to topFollow the steps below to modify the existing admin user account in the database:

Run Microsoft SQL Server Management Studio.
Find a user with administrative privileges.

select Users.UserName, Users.Password, Roles.RoleName  
                   from   telerik_Users as Users inner join   
                   telerik_UsersInRoles as UsersInRoles on UsersInRoles.UserId = Users.UserId inner join   
                   telerik_Roles as Roles on Roles.RoleId = UsersInRoles.RoleId  
                   where  Roles.RoleName = 'administrators'

Open the telerik_Users table.
Set the PasswordFormat for the chosen user to 0.
Change the Password of the same user (for example to admin).
Log in the web site with the corresponding UserName and Password.

Cannot access the Project Manager

Back to topWhen your Sitefinity application is configured as the “Default Web Site” in IIS, the Project Manager becomes a sub-application and its proper functioning is hindered because of ASP.NET web.config inheritance. This is why if you attempt to access the Project Manager, a Configuration Error is thrown.
To prevent this, you need set the following in the web.config file:


                    <?xml version="1.0"?>
  
                    <configuration>

                    ...
    
                    <location path="." inheritInChildApplications="false">
    
                    <system.web>

                    ...

                    </system.web>
    
                    </location>

                    ... 

                    </configuration>

Note that the inheritInChildApplications attribute does not appear in the Visual Studio intellisense.
Using the inheritInChildApplications attribute prevents settings that are specific to a certain location (such as the root directory of a Web site) from being inherited by applications that exist in subdirectories.

Error Messages

You are running a trial version of Sitefinity

If you have installed the Sitefinity Standard Edition and have not applied license keys, it is normal to get trial messages. These should be disabled once a Standard Edition Commercial License is purchased and a license key is applied.
Go through the points below to establish why the messages are still displayed.

Generate your license key:
1. Sign in to your Client.net account.
2. In the left pane, click Licenses.
3. Follow the on-screen instructions. The key is generated automatically and sent to your e-mail.
Check the licensed domain. Note that the license key is tied to the top level domain name. You can view your key details from Licenses > Key Details at your Client.net.
Make sure the company name is spelled correctly.
Make sure that your license key is in a file named LicenseFile.xml.
Make sure LicenseFile.xml is located in
~/[YourWebsite]/Sitefinity folder.
Restart your application when you save the LicenseFile.xml in your project Sitefinityfolder.
Note that there is a problem accessing the site through IP address with Sitefinity 3.1 official release.
To check if you have this particular version, in your project bin folder, right-click the Telerik.Cms.dll and in Properties, click the Version tab. If the version is 3.1.1412.2 or 3.1.1412.3, you need to upgrade to the latest version of Sitefinity.

The account, you have authenticated with, has no permissions to create virtual directories. Please make sure that Windows Authentication is enabled.

Back to topThis error message is sometimes displayed at the first step of the Project Creation Wizard, after you enter the project name and click Next, even when Windows Authentication is enabled.
Usually, to eliminate the problem, it is enough to run your web browser as administrator:

Right-click the browser icon and from the context menu, select Run as administrator.
In the address bar, paste the path to the Sitefinity Project Manager http://localhost/telerik/Sitefinity3.x/.
Click Create new project, type the project name and click Next.

If the above does not help, check the security settings for the Sitefinity3.x virtual folder and make sure that:

Anonymous Authentication is disabled.
ASP.NET Impersonation is enabled.
Forms Authentication is disabled.
Windows Authentication is enabled.
You are using the original Project Manager web.config file that is located in this folder if you have not changed the default installation path:
C:\Program Files\telerik\Sitefinity3.x\ProjectManager

Unable to create the virtual directory. Unknown name.

Back to topSometimes the Project Creation Wizard copies all files and folders from the Empty Project folder but cannot create the virtual directory in IIS and throws this error.
Check the security settings for the Sitefinity3.x virtual folder and make sure that:

Anonymous Authentication is disabled.
ASP.NET Impersonation is enabled.
Forms Authentication is disabled.
Windows Authentication is enabled.
You are using the original Project Manager web.config file that is located in this folder if you have not changed the default installation path:
C:\Program Files\telerik\Sitefinity3.x\ProjectManager

If IIS is set as described above and you are still getting the error, you need to create the project manually. This is how to do it:

Create a new folder in C:\Program Files\telerik\Sitefinity3.x\WebSites.
Copy the contents of the C:\ProgramFiles\telerik\Sitefinity3.x\ProjectManager\App_Data\EmptyProject.zip file to the folder you created in step 1.
Grant the ASPNET account full permissions for the App_Data folder.
Create a virtual directory in IIS and choose the physical folder for its content.
Set up the script handlers for the .template, .rss, .sflb and .tmb file extensions as described here:
.template mappings
.rss mappings
.sflb and .tmb mappings

This project will be accessible through the virtual directory from the browser. If you want it to appear in the Project Manager list, you need to register it in this file:
/Sitefinity3.x/ProjectManager/App_Data/Projects.xml.
Add a new <project> element. The href attribute is the path to the virtual directory you have created, and the path attribute is the physical path on the server.

Error creating virtual directory telerik/Sitefinity 3.2. Exception details: The system could not find the path specified.

Back to topBefore running the installation file again, make sure of the following:

You are logged in as administrator.
"Default Web Site" is present in IIS and is not stopped, otherwise the Sitefinity installer will not be able to create the virtual directories.
All system requirements are met. Refer to the Sitefinity Installation Guide for details:
Installation Guide

Could not load file or assembly 'RadInput.Net2, Version=x.x.x.x, Culture=neutral, PublicKeyToken=xxxx' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

Back to topThis error is thrown when Sitefinity tries to load a different version of the respective assembly. There is a way to fix this by setting assembly binding redirects in the application web.config file. This will tell Sitefinity to use the new assembly instead of the old one. However, if there are changes such as removed properties that are requested by the Sitefinity code, you may get errors. In most situations, though, it will work perfectly.
Follow the steps below to upgrade your RadControls.

Copy all assemblies from RadControls to your project bin folder.
Copy the RadControls folder to the application root.
Open your project for editing with Sitefinity.
Note down the name, version and publicKeyToken of each assembly that throws this error.
Open the application web.config file to specify the binding redirection information for every assembly using the <assemblyBinding> element:

<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="RadInput.Net2" publicKeyToken="a1432cd341173140" /> <bindingRedirect oldVersion="1.0.0.0" newVersion="2.0.2.0" /> </dependentAssembly> </assemblyBinding> </runtime>
Substitute the name, the publicKeyToken and oldVersion with the ones from the error message.
Find out the version of the new assembly you have copied to the bin folder and substitute the newVersion attribute.
Save the web.config file and restart the application.

You can find more information about setting assembly binding redirects, in the following MSDN articles:
Assembly Binding Redirection
bindingRedirect Element

Error 401.2 - Unauthorized

Back to topYou may sometimes get the error when trying to launch the Sitefinity Project Manager under Windows ® Vista.
Check the security settings for the Sitefinity3.x virtual folder and make sure that:

Anonymous Authentication is disabled.
ASP.NET Impersonation is enabled.
Forms Authentication is disabled.
Windows Authentication is enabled.

Refer to section Installing Sitefinity under Windows® Vista of the User Manual for more details.

Error 404 when Starting Sitefinity from All Programs

Back to topIf you are trying to access the Sitefinity Project Manager through Start > All Programs and you get a 404 Page Not Found error, this means the application is prevented from running on your IIS Web Server.
Here is how to allow IIS to serve dynamic content:

Open IIS, expand the master server node (that is the Servername node), and then select the Web Service Extensions node.
In the right pane, right-click ASP.NET v2.0.50727.
Click Allow.

For more information about Web service extensions, please refer to this article:
HTTP Error 404

Error 404 when Trying to Edit Templates

Back to topYou may get this error when trying to open or edit templates at the Pages > Templates tab. It is thrown because IIS cannot pass the request to ASP.NET for processing as the necessary handler mappings are not set. The most popular solution is to add the .template ISAPI filter into the IIS configuration on the server.
This is how to do it in IIS 6.x:

Click All Programs > Administrative Tools > Internet Information Services (IIS) Manager.
Expand the tree on the left until you see Web Sites.
Expand the Web Sites folder.
Right-click your Web site to select Properties.
Click Configuration.
Click Add to open the Add/Edit Application Extension Mapping dialog.
For the value of the Executable field, browse to select the c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll.
In the Extension field, type .template.
Select the All verbs option.
Clear the Verify that file exists checkbox.
Click OK to close the Add/Edit Application Extension Mapping dialog.
Click OK to close the Application Configuration dialog.

If for some reason you cannot add .template mappings, you can add wildcard application mappings instead.

Click Configuration.
Click Insert… to open the Add/Edit Application Extension Mapping dialog.
Browse to select the c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll file for the value of the Executable field.
Clear the Verify that file exists checkbox.
Click OK to close the Add/Edit Application Extension Mapping dialog.
Click OK to close the Application Configuration dialog.

Error 404 when Trying to Access RSS

Back to topYou may get this error when trying to access an RSS feed created with the RSS control. It is thrown because IIS cannot pass the request to ASP.NET for processing as the necessary handler mappings are not set. The solution is to add the .rss ISAPI filter into the IIS configuration on the server.
This is how to do it in IIS 6.x:

Click All Programs > Administrative Tools > Internet Information Services (IIS) Manager.
Expand the tree on the left until you see Web Sites.
Expand the Web Sites folder.
Right-click your Web site to select Properties.
Click Configuration.
Click Add to open the Add/Edit Application Extension Mapping dialog.
For the value of the Executable field, browse to select the c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll.
In the Extension field, type .rss.
Select the All verbs option.
Clear the Verify that file exists checkbox.
Click OK to close the Add/Edit Application Extension Mapping dialog.
Click OK to close the Application Configuration dialog.

Error 404 when Uploading Files

Back to top You get this error when uploading a file larger than the maximum allowed upload file size as set in the application web.config:
<httpRuntime maxRequestLength="51200" />
The maxRequestLength attribute specifies the limit for the input stream buffering threshold, in KB. This limit can be used to prevent denial of service attacks that are caused, for example, by users posting large files to the server. To enable large file uploads, you need to change the value of this attribute to the largest allowed combined file size for your application. If someone selects and uploads files, with total size larger than maxRequestLength, s/he will get the "Page not found" error (which is the default error of the Framework).

Error 404 with Image and Document Files

Back to topTo be able to download files and see images and thumbnails in the Images & Documents module, you should set the ISAPI mappings for .sflb and .tmb extensions on your IIS virtual directory. These should be set automatically by the Sitefinity installer; however, you need to add them manually if you have upgraded using a patch or if you are deploying the site on another server.
To eliminate the problem, follow the steps below:

Add .sflb ISAPI filters into the IIS 6.x configuration:
1. Click All Programs > Administrative Tools > Internet Information Services (IIS) Manager.
2. Expand the tree on the left until you see Web Sites.
3. Expand the Web Sites folder.
4. Right-click your Web site to select Properties.
5. Click Configuration.
6. Click Add to open the Add/Edit Application Extension Mapping dialog.
7. For the value of the Executable field, browse to select the c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll.
8. In the Extension field, type .sflb.
9. Select the All verbs option.
10. Clear the Verify that file exists checkbox.
11. Click OK to close the Add/Edit Application Extension Mapping dialog.
12. Click OK to close the Application Configuration dialog.
Follow the same steps to add the .tmb extension.
Make sure the ContentHttpHandler handler for these extensions is registered in the application web.config:
<httpHandlers> <add verb="GET" path="*.sflb" type="Telerik.Cms.Engine.ContentHttpHandler, Telerik.Cms.Engine" /> <add verb="GET" path="*.tmb" type="Telerik.Cms.Engine.ContentHttpHandler, Telerik.Cms.Engine" /> </httpHandlers>

Error 404 with Some URLs

Back to top If you have requested a URL such as www.mysite.com/home and you get 404 Page Not Found errors, this means your site is not configured to handle URLs without extensions.
This is how to do it in IIS 6.x:

Click All Programs > Administrative Tools > Internet Information Services (IIS) Manager.
Expand the tree on the left until you see Web Sites > Default Web Site.
Expand the Default Web Site folder.
Right-click your project virtual folder and select Properties.
At the Custom Errors tab, select HTTP error 404.
Click Edit.
From the Message Type list, choose URL.
In the URL field, type the path to sf404.aspx in your project like this:
/ProjectName/sf404.aspx
Click OK.

Error 500 - Internal Server Error

Back to topIf you get this error, most probably you need to enable 32-bit applications in the Classic.NET AppPool. This is how to do it:

Launch IIS Manager from Control Panel > Administrative Tools.
In the left pane, double-click Application Pools.
Right-click Classic.NET AppPool in the list.
Click Advanced Settings.
Find Enable 32-Bit Applications and set it to true.

If the above does not help, you can check if the application pool is configured as described in section Configuring the Classic.NET AppPool of the Sitefinity User Manual.

You don't have the necessary permission to do this. Please contact your administrator.

Back to topThis error is normally displayed when the currently logged in user is:

not assigned to any user role. By default, in this case s/he belongs to default role "everyone", but the permission CMS access is not granted for this role;
trying to access the administrative backend of Sitefinity and the role s/he belongs to is not granted the CMS access permission;
requesting a page for which the View permission is not granted and Anonymous access is set to Deny.

Note that only one user can be logged in an application at a time, so for example, when you log in using TestUser, you are no longer logged as "admin". Also, when you sometimes view a restricted page despite the fact that you are not logged in (or logged in with an account that is not granted the necessary permissions), this is quite probably caused by your browser's cache.

Role feature is not enabled

Back to topYou may get this error at the second step of the Project Creation Wizard, when asked to choose the project database. Usually, refreshing the page fixes the problem.
Note that roles are not disabled in the Community Edition. Actually, they are originally set to false in the Empty Project web.config file, but at the second wizard step are programmatically set to true. If the error persists after refreshing the page, open the application web.config file and check if the property has been set to true:
<roleManager enabled="true" cacheRolesInCookie="true" defaultProvider="Sitefinity">
Save the web.config file and refresh the page.

Directory listing denied

Back to topThis error is most probably caused by the fact that IIS cannot find a default document to open in the directory, that is, Default.aspx is not in the list of default documents.
To add it:

In IIS, right-click the virtual directory and select Properties.
Click the Documents tab.
Select the Enable default content page checkbox.
Click Add and type Default.aspx in the textbox.
Click OK twice.

A folder “MySite” already exists in ‘C:\ProgramFiles\telerik\Sitefinity3.1\WebSites.’ Please specify another project name.

Back to topYou may get this error at the first step of the Project Creation wizard, when asked to type the project name. Typically, the error occurs when you have removed “MySite” from the Project Manager List. This operation actually deletes the virtual folder, but the physical folder still stays under the Web Sites folder. If this is the case, you need to rename this folder or delete it manually before creating a project with the same name.

Thank you for visiting our web site

Back to topThis message is normally displayed when:

There are no pages created.
There are no published pages.
The home page for the web site is not set.

The page is under construction

Back to topThis message is displayed when the home page is not published or when there is no template selected for the page you are trying to access.

Object reference not set to an instance of an object (Pages > Templates)

Back to topOne of the numerous occasions on which this error can be displayed is when the <form> tag is missing in the master page.
The error is thrown at the Pages > Templates tab, after clicking Edit for a template.
To eliminate the problem:

Open the .master file your template is using.
Make sure that it contains the @ Master directive, as well as all of the top-level HTML elements for a page, such as <html>, <head> and <form>.

For more details, please refer to the MSDN library: ASP.NET Master Pages.

Object reference not set to an instance of an object (Pages > Site Map)

Back to topYou may get this error at the Pages > Site Map tab, when you select a page whose template has been deleted. The only way out of this is to delete the page. We'll provide a fix for this soon.

A required control was not found…

Back to topOften, after clicking the Administration link, an error similar to this may occur:
A required control was not found in the template for "Telerik.Search.WebControls.Admin.ControlPanel+xxxx". The control must be assignable form type "xxxx" and must have ID "xxxx".

Go through the list below to troubleshoot this:

In the application web.config file, check if the name of the defaultProvider is set to "Search".
Most probably, after applying the upgrade patch for version 3.1 SP2, you have omitted to change this according to the upgrading instructions.
The whole section telerik/search should look like this:

<search defaultProvider="Search"> < providers> <clear/> <add name="Search" type="Telerik.Search.Data.DefaultProvider, Telerik.Search.Data" connectionStringName="DefaultConnection"/> </providers> <indexingClients> <add name="PageIndex" type="Telerik.Cms.Web.PageIndexingClient, Telerik.Cms" settingsControl="Telerik.Cms.Web.UI.PageIndexSettings, Telerik.Cms" viewSettingsControl="Telerik.Cms.Web.UI.SearchViewControl, Telerik.Cms" description="Provides indexing services for CMS Pages."/> </indexingClients> </search>
The error may indicate the absence of a required control in the template. If you have modified some of the templates, you might have deleted the control with the specified ID and type.
In the following example, the error reads:
“A required control was not found in the template for "Telerik.Lists.WebControls.Admin.ControlPanel+AllListsContainer". The control must be assignable form type " System.Web.UI.WebControls.IButtonControl " and must have ID "createNewEmpty".
This means that a button control with ID "createNewEmpty" was not found in the template. To fix the problem,you should add a control with this ID in the corresponding template.

There is a problem when publishing web sites with Visual Studio with the option "Allow this precompiled site to be updatable" UNCHECKED. The control templates (.ascx files) are not copied to the published precompiled site. If you check 'Allow this precompiled site to be updatable', you will not need to do that extra copy of control templates next time.
To resolve the problem:
- Copy the following folders manually from your development site to the precompiled one:
  ~/Sitefinity/Admin/ControlTemplates
  ~/Sitefinity/ControlTemplates
- Remove the App_LocalResources folder from the above folders, as this folder is not allowed in the precompiled web application.
This error is displayed if Sitefinity is not able to find the necessary template and is trying to load the default one that has no implementation. In this case, you need to create your own template or implement the default one.
If you are using a custom provider for a Sitefinity module (e.g. Breaking_News for News), make sure you have copied and renamed the necessary templates. In this example, the News folder should be copied in ~/Sitefinity/ControlTemplates and ~/Sitefinity/Admin/ControlTemplates and renamed to Breaking_News.

The structure of your project Sitefinity folder may be corrupted. You can compare it to the C:\ProgramFiles\telerik\Sitefinity3.x\ProjectManager\EmptyProject\Sitefinity folder and, if needed, overwrite some files. If you are overwriting the whole folder, be careful not to overwrite any changes made to the files.

You may have corrupted your web.config file and thus broken the paths to the default templates. In this case, you should overwrite your application web.config file with the one located in C:\ProgramFiles\telerik\Sitefinity3.x\ProjectManager\EmptyProject. Do not forget to change the connection string if needed.

Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.

Back to topThis error usually occurs if you force postback before waiting for the whole page to load. This is so due to the fact that ASP.NET event validation is enabled and the corresponding JavaScript code is located at the end of the page. If an attempt for postback is called before the page load, this script is not loaded yet and an error is thrown. In a nutshell, event validation is a technique used by ASP.NET 2.0 to ensure that the data being sent back to the server on postback is an expected value and is designed to help prevent injection attacks. Fortunately, there is an option to disable the event validation from the application web.config file. Add a page element to the <system.web> section and set the enableEventValidation attribute to false.

User ‘xxx’ is not allowed to view this page. Sign in as a different user or contact your administrator.

Back to topThis error is displayed when the currently logged user:

is trying to access the Sitefinity admin part and is not granted the CMS access permission
is not granted the View permission for the requested page
is not assigned to any role; in this case s/he belongs to role 'everyone' and by default the CMS access permission is not granted for this role

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

Back to topThis error suggests that remote connections are currently not allowed for SQL Server.
Refer to this article for instructions: How to configure SQL Server 2005 to allow remote connections

Failed to access IIS metabase

Back to topYou may get this error if you install IIS after the .NET Framework. The error means that the .NET Framework is not properly registered in the IIS and the permissions for the account that runs the ASPNET worker process are not set correctly.
To troubleshoot this, you need to run the following in the Command Prompt (cmd.exe)
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –i.

Troubleshooting

Common Problems

Error Messages

Answers

Common Problems

Error Messages