Configure Session Time-out (IIS 7)

User Interface

To Use the UI

1. Open IIS Manager and navigate to the level you want to manage. For information about opening IIS Manager, see Open IIS Manager (IIS 7). For information about navigating to locations in the UI, see Navigation in IIS Manager (IIS 7).

2. In Features View, double-click ASP.

1. On the ASP page, under Services, expand Session Properties.

2. In the Time-out field, enter a time-out value in the format hh:mm:ss. For example, enter 00:15:00 for 15 minutes.

3. In the Actions pane, click Apply.

Display Hierarchical Data with TreeView in ASP.NET 2.0

Check This link

http://aspalliance.com/732

Steps to Create and Deploy SSIS Package as a SQLAgent Job

Microsoft says that SQL Server Integration Services (SSIS) “is a platform for building high performance data integration solutions, including extraction, transformation, and load (ETL) packages for data warehousing.” A simpler way to think of SSIS is that it’s the solution for automating SQL Server. SSISprovides a way to build packages made up of tasks that can move data around from place to place and alter it on the way. There are visual designers (hosted within Business Intelligence Development Studio) to help you build these packages as well as an API for programming SSIS objects from other applications.

as an API for programming SSIS objects from other applications.

Though SSIS is almost infinitely customizable, Microsoft has produced a simple wizard to handle some of the most common ETL tasks: importing data to or exporting data from a SQL Server database. The Import and Export Wizard protects you from the complexity of SSIS while allowing you to move data between any of these data sources:

• SQL Server databases
• Flat files
• Microsoft Access databases
• Microsoft Excel worksheets
• Other OLE DB providers

SQL Server 2005 redesigned the way you design data transformation packages. It now includes much more capabilities, and because of that, it features a new tool. It separates the control of the package from the data transformation portion, so you can do much more. For instance, you have the ability to read information from WMIor a web service. There is also the ability to iterate through a loop of data stored in a variable, or from a result set.

Creating a Package

The Import and Export Wizard is easy to use, but it only taps a small part of the functionality of SSIS. To really appreciate the full power of SSIS, you’ll need to use BIDS to build an SSIS package. A package is a collection of SSIS objects including:

• Connections to data sources.
• Data flows, which include the sources and destinations that extract and load data, the transformations that modify and extend data, and the paths that link sources, transformations, and destinations.
• Control flows, which include tasks and containers that execute when the packageruns. You can organize tasks in sequences and in loops.
• Event handlers, which are workflows that runs in response to the events raised by a package, task, or container.

Step 1: Open SQL Server Business Intelligence Development Studio.

Step 2: Create a New Project

Step 3: Select Integration Services Project under Business Intelligence Projects and provide a name for the project.

Step 4: Add a new Data Source. Right Click on Data Sources and select New Data Source.

Step 5: Use the Data Source Wizard to add a new data source. Select ‘Create a data source based on an existing or new connection’ and click on ‘New’.

Step 6: Add the Server and Authentication information and click on Test Connection to test the connection. Then click OK.

Step 7: A default SSIS package is created under the solution called Package.dtsx. Rename this package with a meaningful name.

Step 8: Drag and drop Control Flow Items from the Toolbox on the left to the Control Flow diagram and create the package.

Step 9: Double Click on the Data Flow Task to edit each Data Flow and add data transformations.

Step 10: Save and Build the package.

Step 11: Run the package. On successful completion, the tasks will turn green.

Deploying a Package

Step 1: Save a copy of the package on any server.

Note: If the package is to be deployed on a different server, ensure that the Protection Level is selected as EncryptSensitiveWithPassword

Provide a Password for the package by clicking on the PackagePassword Item and enter the password.

Step 2: Select Package location as SQL Server, Server Name as destination server and Authentication Type as Windows Authentication. Click on Package Path to browse and save the package.

Step 3: Save the package under SSIS Packages.

Step 4: Open SQL Server Management Studio and connect to the Database Engine on the server where you have saved the Package.

Step 5: Go to SQL Server Agent -> Job. Right-click and select New Job.

Step 6: Provide a name for the Job.

Step 7: Go to Steps and click ‘New’.

Step 8: Provide a name for the Step and select the Type as SQL Server Integration Services Package.

Step 9: Select Package Source as SQL Server, Server as the destination server and click on Package to browse and select the package.

Step 10: Click on data Source tab. Provide a password when prompted (if saved with a password).

Step 11: Edit the Connection String to add password for OLE DB connections, or change location of Input/Output files if required. Click Ok to save the changes.

Step 12: Go to Schedules and click New to add a new schedule.

Step 13: Click Ok on the Job Schedule Properties window to save the schedule.

Step 14: Click Ok on the Job properties window to save the job.

refrence :http://technotes.towardsjob.com/sql-server/steps-to-create-and-deploy-ssis-package-as-a-sqlagent-job/

How to Edit Detailsview in asp.net aplplication

Using template Field you can edit datalist

Check the refrence link

http://www.asp.net/LEARN/data-access/tutorial-13-cs.aspx

System.Web.HttpException: Request timed out

Summery

executionTimeout parameter- indicates the maximum number of seconds that a request is allowed to execute before being automatically shut down by ASP.NET.

By default, the value of the executionTimeout attribute is set to 90 seconds in theMachine.config file. “Request timed out” error occurs when the processing time of request exceeds 90 seconds. In most cases an error occurs when you are uploading large files.

Solution

To work around this problem, increase the time-out value of request execution.

You can do that by following two ways:

Method 1:
EAUpload component provides a replacement of executionTimeout attribute of httpRuntime config section. If ExecutionTimeout parameter of EAUpload environment is defined then request have time-out that is specified by this parameter and"executionTimeout" parameter of httpRuntime configuration section is ignored. The specified value will take effect only for requests which are processed by EAUpload component. The value that is specified in executionTimeout attribute will be actually for other requests.

Set the ExecutionTimeout parameter value in the EAUpload configuration

• Open the Web.config file in Notepad.
• Increase the value of the ExecutionTimeout attribute to avoid time-out errors.
  

  "1.0" encoding="utf-8" ?>  ...            "3600"                     ...        />              ...       

• Save the Web.config file.

Method 2:
The executionTimeout attribute exists under httpRequest in the Machine.config file. You can change these settings either in the Web.Config file or in the Machine.config file. The default value for the time-out is 90 seconds. The executionTimeout attribute indicates the maximum number of seconds a request is permitted to run before being shut down by the ASP.NET Web application.

Figure A: Set the executionTimeout attribute value in the Web.config File

• Open the Web.config file in Notepad.
• Add the httpRuntime element in the system.web section as follows:
  

  "1.0" encoding="utf-8" ?>  ...      "90" maxRequestLength="4096" 	useFullyQualifiedRedirectUrl="false" 	minFreeThreads="8" 	minLocalRequestFreeThreads="4" 	appRequestQueueLimit="100" />   ...   

• Increase the value of the executionTimeout attribute to avoid time-out errors.
• Save the Web.config file.

Figure B: the executionTimeout attribute value in the Machine.config File

• Open the Machine.config file in Notepad. The Machine.config file is located in the %SystemRoot%\Microsoft.NET\Framework\%VersionNumber%\CONFIG\ directory.
• In the Machine.config file, locate the httpRuntime element.
  

  "90" maxRequestLength="4096" 	useFullyQualifiedRedirectUrl="false" 	minFreeThreads="8" 	minLocalRequestFreeThreads="4" 	appRequestQueueLimit="100" /> 

• Increase the value of the executionTimeout attribute to avoid time-out errors.
• Save the Web.config file.

References:

Configure ASP.NET HTTP runtime settings:
http://msdn2.microsoft.com/en-us/library/e1f13641(vs.71).aspx

http://www.easyalgo.com/knowledgeBase/system.web.httpexception-request-timed-out.aspx

AjaxToolkit: AutoCompleteExtender

<%@ Register Assembly="AjaxControlToolkit"Namespace="AjaxControlToolkit" tagprefix="ajaxToolkit"%>

Which says that the reference assembly "AjaxControlToolkit.dll" should be registered on the page by using above method. We should also have tagprefix="ajaxToolkit" which is similar to .

In this article I have very simple database table called as "Tbl_Countries" with fields as:

CountryId int primary key,
CountryName varchar(50)

I am using a web service called as "AutoComplete.asmx" whose code behind gets automatically added to the "App_Code" folder.

Note: Very important part is you need to give a reference of "AjaxControlToolkit.dll".

Here is complete code for "AutoComplete.asms.cs".

using System;

using System.Web;

using System.Collections;

using System.Web.Services;

using System.Web.Services.Protocols;

using System.Data;

using System.Data.SqlClient;

using System.Configuration;

///

/// Summary description for AutoComplete

///

[WebService(Namespace = "http://tempuri.org/")]

[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]

[System.Web.Script.Services.ScriptService]

public class AutoComplete : System.Web.Services.WebService

{

[WebMethod]

public string[] GetCountriesList(string prefixText)

{

DataSet dtst = new DataSet();

SqlConnection sqlCon = newSqlConnection(ConfigurationManager.AppSettings["ConnectionString"]);

string strSql = "SELECT CountryName FROM Tbl_Countries WHERE CountryName LIKE '" + prefixText + "%' ";

SqlCommand sqlComd = new SqlCommand(strSql, sqlCon);

sqlCon.Open();

SqlDataAdapter sqlAdpt = new SqlDataAdapter();

sqlAdpt.SelectCommand = sqlComd;

sqlAdpt.Fill(dtst);

string[] cntName = new string[dtst.Tables[0].Rows.Count];

int i = 0;

try

{

foreach (DataRow rdr in dtst.Tables[0].Rows)

{

cntName.SetValue(rdr["CountryName"].ToString(), i);

i++;

}

}

catch { }

finally

{

sqlCon.Close();

}

return cntName;

}

}

Let us take another page called as "default.aspx" in which I am having a tag and in which a tag in which you can specify path of webservices. You have already registered Assembly="AjaxControlToolkit" on this page so you can use that.

So my entire code will look something like this

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>

<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" tagprefix="ajaxToolkit"%>

DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head id="Head1" runat="server">

<title>Untitled Pagetitle>

head>

<body>

<form id="form1" runat="server">

<asp:ScriptManager ID="ScriptManager1" runat="server">

<Services>

<asp:ServiceReference Path="AutoComplete.asmx" />

Services>

asp:ScriptManager>

<div>

<asp:TextBox ID="txtCountry" runat="server">asp:TextBox>

<ajaxToolkit:AutoCompleteExtender runat="server" ID="autoComplete1" TargetControlID="txtCountry"ServicePath="AutoComplete.asmx" ServiceMethod="GetCountriesList" MinimumPrefixLength="1" EnableCaching="true" />

div>

form>

body>

html>

Following snapshot gives you clear idea as how the AutoCompleteExtender works.

http to https redirect in asp.net

write code on page load event

if(!Request.IsSecureConnection)

{

string redirectUrl = Request.Url.ToString().Replace("http:", "https:");
Response.Redirect(redirectUrl);

}