Newest KB Articles in ASP.NET

ASP.NET application error: "Unrecognized attribute 'targetFramework'"

Thu, 13 May 2010 23:15:15 GMT

You may experience the following error when you attempt to open your web application:

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

The error indicates that your account is configured to use an older version of the ASP.Net framework.

To resolve the problem simply click the ASP.NET Version icon in the "Site Tools" section of Control Panel to switch to the correct framework. See this Knowledge Base article for more information.

Parser Error Message: "The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty"

Tue, 04 May 2010 22:24:49 GMT

If you receive the following error from your web application:

Parser Error Message: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

The solution is to modify your application's web.config file and add the following line to the connection string element:

<connectionStrings> 
  <remove name="LocalSqlServer" /> 
  <add name="LocalSqlServer" connectionString="Data Source=DBServerName;Integrated Security=false;Initial Catalog=DBName;User ID=DBLogin;Password=DBPassword" providerName="System.Data.SqlClient" />
</connectionStrings>

You must ensure that you add the correct values for the connection string. Log in to Control Panel and review your database information and DB login credentials in the Site Info Manager/MS SQL Manager section.

Error when accessing a WCF service: "This collection already contains an address with scheme http. There can be at most one address per scheme in this collection."

Wed, 21 Apr 2010 21:01:56 GMT

You can resolve this error by changing the web.config file.

If you are using ASP.NET 4.X, add the following lines to your web.config:

<system.serviceModel> 
     <serviceHostingEnvironment multipleSiteBindingsEnabled="true" /> 
</system.serviceModel>

If you are using ASP.NET 2.0/3.0/3.5, add the following lines to your web.config:

<system.serviceModel> 
     <serviceHostingEnvironment> 
          <baseAddressPrefixFilters> 
               <add prefix="http://www.HostingAccountDomain.com"/> 
          </baseAddressPrefixFilters> 
     </serviceHostingEnvironment> 
</system.serviceModel>

Errors commonly associated with inadequate Trust Level

Thu, 03 Dec 2009 20:17:23 GMT

By default, the trust level on our servers is configured to "Medium trust." If your application generates any of the error messages below, the most likely cause is that your application requires a trust level higher than medium.

You can override the default trust level of your application by modifying the web.config file. See this Knowledge Base article for instructions.

- - -

Security Exception:
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

- - -

Error:
System.Security.SecurityException: That assembly does not allow partially trusted callers.

- - -

Stack Trace:
[SecurityException: Request for the permission of type 'System.Net.WebPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.]

- - -

Error:
Request for the permission of: type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

- - -

Unable to connect to any of the specified MySQL hosts. ---> System.Security.SecurityException: Request for the permission of type 'System.Net.SocketPermission, System,

- - -

Error:
Request for the permission of type
'System.Net.Mail.SmtpPermission, System, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' failed.

Changing the default ASP.NET trust level

Tue, 18 Aug 2009 00:24:28 GMT

The default ASP.NET trust level is Medium. Most applications will run fine under Medium Trust. If your application requires Full Trust, you can override the trust level at the application level by adding the following to your web.config file:

<configuration> 
  <system.web> 
    <trust level="Full" /> 
  </system.web> 
</configuration>

If you run in to problems using this code, please post in our community forum. Technical support cannot assist with specific coding related issues.

Configuration error when executing an application in a subdirectory

Fri, 14 Aug 2009 23:15:04 GMT

If you get the following error when attempting to execute an application in a sub directory:

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

It could be that your application is being run out of a subfolder and the subfolder is not configured in IIS to run as an application.

To resolve this error, you can create an IIS application starting point in the Site Tools section of Control Panel.

How to enable ASP.NET SQL Server Session for your web application

Fri, 14 Aug 2009 22:57:11 GMT

In ASP.NET, there are 3 different modes for storing session information:

    InProc
    StateServer
    SQLServer

We support both InProc and SQLServer session. By default, ASP.NET session is stored in-process (InProc). There are benefits and drawbacks for each method.

InProc mode offers the fastest performance because session is stored in the IIS Worker Process. The downside of InProc session is that sessions can be lost if the worker process is recycled for any reason.

SQL Server session on the other hands is slower than InProc, about 15-20% slower, but the session information remains persistent even after the worker process is recycled.

You should choose a state management mode that is appropriate for your application. For example, if losing session is not acceptable, you should consider using SQL Session rather than InProc.

To enable SQL Server Session

- While not required, we recommend adding a new MS SQL database in the Site Tools section of Control Panel, dedicated for sessions storage only, to avoid potential conflicts (if you have a Basic account you will have to upgrade to a Max account to add a second database).

- Create a support ticket to request an installation. Include the Database name and the version of ASP.NET you are using.

- You will receive an email as soon as the Session State database schema is created.

- Update your web.config file as follows:

< sessionState
  mode="SQLServer"
  allowCustomSqlDatabase = "true"
  sqlConnectionString="data Source=<SQLSERVERNAME>;database=<SQLDATABASENAME>;user id=<SQLUSER>;password=<SQLPASSWORD>"
    cookieless="false"
  timeout="15"
/>

Session information should be stored in your SQL database now.

If you run in to problems using this code, please post in our community forum. Technical support cannot assist with specific coding related issues.

How to configure the ASP.NET Membership/Roles Provider

Fri, 14 Aug 2009 21:42:46 GMT

The following steps create the full Application Services database schema on our SQL Server database:

Open the command prompt on your local computer, and navigate to:

C:\WINDOWS\Microsoft.NET\Framework\[framework version]

Execute the command:

aspnet_regsql.exe -S DBServerName -U DBLogin -P DBPassword -A all -d DBName

Currently, there is no management interface to manage the membership database other than using Visual Web Developer or creating your own application using the membership provider class. Here is an example of how to configure Visual Studio or Visual Web Developer to manage the membership database:

    1. Create a web application in Visual Web Developer or Visual Studio.
    2. Open the web.config.
    3. The default membership provider uses a connection string called "LocalSqlServer". Therefore, replace:

<connectionStrings/>

with:

<connectionStrings>
  <remove name="LocalSqlServer" />
  <add name="LocalSqlServer" connectionString="Data Source=DBServerName;Integrated Security=false;Initial Catalog=DBName;User ID=DBLogin;Password=DBPassword" providerName="System.Data.SqlClient" />
</connectionStrings>

    4. Save and close the web.config.
    5. Go to Website menu, and run the ASP.NET Configuration tool. This will open the Web Site Administration tool.
    6. In the Web Site Administration tool, go to the Security tab.
    7. Click on "Select authentication type".
    8. Select "From the internet". Click the Done button.
    9. Create your admin roles and users.
    10. Then create access rules.
    11. Create a rule that applies to the "Anonymous users" with "Deny" permissions.
    12. Create another rule that applies to the admin role you created with "Allow" permissions.

Your application is now ready to use the membership provider, and you can begin creating your log in forms.

If you run in to problems using this code, please post in our community forum. Technical support cannot assist with specific coding related issues.