<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Open Software Solutions &#187; ASP &#8211; Code</title>
	<atom:link href="http://ossmall.info/category/programing-and-coding/asp-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://ossmall.info</link>
	<description>Open Software Solutions</description>
	<lastBuildDate>Thu, 09 Feb 2012 14:59:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How to repair IIS mapping after you remove and reinstall IIS</title>
		<link>http://ossmall.info/how-to-repair-iis-mapping-after-you-remove-and-reinstall-iis/</link>
		<comments>http://ossmall.info/how-to-repair-iis-mapping-after-you-remove-and-reinstall-iis/#comments</comments>
		<pubDate>Sat, 04 Feb 2012 17:03:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ASP - Code]]></category>

		<guid isPermaLink="false">http://ossmall.info/how-to-repair-iis-mapping-after-you-remove-and-reinstall-iis/</guid>
		<description><![CDATA[After you install the Microsoft .NET Framework Software Development Kit (SDK), Microsoft Visual Studio .NET 2002, Visual Studio .NET 2003, or Visual Studio 2005, Microsoft Internet Information Service (IIS) mappings are created to associate the new file extensions and settings for ASP.NET. If you did not have IIS installed when you ran the SDK or [...]]]></description>
			<content:encoded><![CDATA[<p>After you install the Microsoft .NET Framework Software Development Kit (SDK), Microsoft Visual Studio .NET 2002, Visual Studio .NET 2003, or Visual Studio 2005, Microsoft Internet Information Service (IIS) mappings are created to associate the new file extensions and settings for ASP.NET. If you did not have IIS installed when you ran the SDK or Visual Studio Setup, or if you uninstalled and reinstalled IIS after you ran the SDK or Visual Studio Setup, those settings will not be in place. You experience unexpected behavior when you try to view ASP.NET pages.</p>
<p>When you try to create a new ASP.NET Web application in Visual Studio .NET 2003, you receive the following error message:</p>
<p>Visual Studio .NET has detected that the specified Web server is not running ASP.NET version 1.1. You will be unable to run ASP.NET Web applications or services.</p>
<h2>MORE INFORMATION</h2>
<p>To fix IIS mappings for ASP.NET, run the Aspnet_regiis.exe utility:</p>
<table border="0" cellpadding="0">
<tr>
<td>1.</td>
<td>Click <strong>Start</strong>, and then click <strong>Run</strong>.</td>
</tr>
<tr>
<td>2.</td>
<td>In the <strong>Open</strong> text box, type cmd, and then press ENTER.</td>
</tr>
<tr>
<td>3.</td>
<td>At the command prompt, type the following, and then press   ENTER:</p>
<p>&#8220;%windir%\Microsoft.NET\Framework\<var>version</var>\aspnet_regiis.exe&#8221; -i</p>
<p>In this path, <var>version</var> represents the version   number of the .NET Framework that you installed on your server. You must   replace this placeholder with the actual version number when you type the   command.</td>
</tr>
</table>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<h5>Microsoft Knowledge Base Article</h5>
<p class="MsoNormal">This article contents is Microsoft Copyrighted material.<br />
Microsoft Corporation. All rights reserved. <a href="http://support.microsoft.com/tou/">Terms of Use</a> | <a href="http://support.microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx">Trademarks</a></p>
<div class="aizatto_related_posts"><span class="aizatto_related_posts_header" >Related Articles or Pages</span><ul></ul></div>]]></content:encoded>
			<wfw:commentRss>http://ossmall.info/how-to-repair-iis-mapping-after-you-remove-and-reinstall-iis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ASP.NET pages exhibit unexpected behavior because the server-side code is not processed</title>
		<link>http://ossmall.info/aspnet-pages-exhibit-unexpected-behavior-because-the-server-side-code-is-not-processed/</link>
		<comments>http://ossmall.info/aspnet-pages-exhibit-unexpected-behavior-because-the-server-side-code-is-not-processed/#comments</comments>
		<pubDate>Mon, 19 Dec 2011 17:06:03 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ASP - Code]]></category>

		<guid isPermaLink="false">http://ossmall.info/aspnet-pages-exhibit-unexpected-behavior-because-the-server-side-code-is-not-processed/</guid>
		<description><![CDATA[Symptoms that are exhibited at run time When you view an .aspx page in a Microsoft ASP.NET Web application, you may experience the following symptoms: A blank page may appear in the browser. You may receive an instruction to download the .aspx page. The typical behavior is that the server-side code for the .aspx page [...]]]></description>
			<content:encoded><![CDATA[<h3>Symptoms that are exhibited at run time</h3>
<p>When you view an .aspx page in a Microsoft ASP.NET Web application, you may experience the following symptoms:</p>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>A blank page may appear in the browser.</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>You may receive an instruction to download the .aspx page.</td>
</tr>
</table>
<p>The typical behavior is that the server-side code for the .aspx page is processed, and then the code is not sent to the Web browser in its raw form.</p>
<h3>Symptoms that are exhibited when you use Visual Studio .NET to debug ASP.NET</h3>
<p>When you debug an ASP.NET application in Microsoft Visual Studio .NET, you may receive the following error message in the IDE:</p>
<p>Error while trying to run project: Unable to start debugging on the Web server. The server does not support debugging of ASP.NET or ATL Server applications. Run setup to install the Visual Studio .NET server components. If setup has been run, verify that a valid URL has been specified.</p>
<p>You may also want to refer to the ASP.NET and ATL Server debugging topic in the online documentation. Would you like to disable future attempts to debug ASP.NET pages for this project?</p>
<h2>CAUSE</h2>
<p>After you install the Microsoft .NET Framework Software Development Kit (SDK) or Microsoft Visual Studio .NET, Microsoft Internet Information Services (IIS) mappings are created to associate new file name extensions and new settings for ASP.NET.</p>
<p>The new settings are not in place if either of the following statements applies to your situation:</p>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>IIS was not installed when you ran the .NET Framework SDK   or Visual Studio .NET Setup.</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>You removed and then reinstalled IIS after you ran the   .NET Framework SDK Setup or the Visual Studio .NET Setup.</td>
</tr>
</table>
<h2>RESOLUTION</h2>
<p>To resolve this issue, repair the IIS mappings so that the file name extensions for ASP.NET are properly associated. There are two ways to fix IIS mappings for ASP.NET.</p>
<p>To repair IIS mappings for ASP.NET, run the Aspnet_regiis.exe utlity. To do so, follow these steps:</p>
<table border="0" cellpadding="0">
<tr>
<td>1.</td>
<td>Click <strong>Start</strong>, and then click <strong>Run</strong>.</td>
</tr>
<tr>
<td>2.</td>
<td>Type cmd, and then click <strong>OK</strong>.</td>
</tr>
<tr>
<td>3.</td>
<td>At the command prompt, type the following command, and   then press ENTER:</p>
<p>&#8220;\<var>WindowsFolder</var>\Microsoft.NET\Framework\<var>VersionNumber</var>&gt;\aspnet_regiis.exe&#8221; -i</p>
<p><strong>Note</strong> Replace <var>WindowsFolder</var> with the name   of the directory where the operating system is installed. Replace <var>VersionNumber</var>   with the .NET Framework version installed on your computer.</td>
</tr>
</table>
<p>To repair IIS mappings for ASP.NET, you must register Aspnet_isapi.dll. To do so, follow these steps:</p>
<table border="0" cellpadding="0">
<tr>
<td>1.</td>
<td>Click <strong>Start</strong>, and then click <strong>Run</strong>.</td>
</tr>
<tr>
<td>2.</td>
<td>Type regsvr32 <var>WindowsFolder</var>\Microsoft.NET\Framework\<var>VersionNumber</var>\aspnet_isapi.dll, and then click <strong>OK</strong>.   Regsvr32 returns the results of the registration.</td>
</tr>
</table>
<h2>STATUS</h2>
<p>This behavior is by design.</p>
<h2>MORE INFORMATION</h2>
<h3 id="tocHeadRef">Steps to reproduce the behavior</h3>
<p>Follow these steps to verify whether or not you see the issue described in this article. This test checks for the typical symptoms that are related to the issue. If you are already familiar with how IIS application mappings work, you can also follow the steps in the &#8220;How To Verify Your IIS Application Mappings&#8221; section of this article to verify the configuration of your Web server.</p>
<table border="0" cellpadding="0">
<tr>
<td>1.</td>
<td>To create an ASP.NET Web application, use Visual Studio   .NET. To do so, follow these steps:</p>
<table border="0" cellpadding="0">
<tr>
<td>a.</td>
<td>Start Microsoft Visual Studio .NET.</td>
</tr>
<tr>
<td>b.</td>
<td>On the <strong>File</strong> menu, point to <strong>New</strong>,     and then click <strong>Project</strong>.</td>
</tr>
<tr>
<td>c.</td>
<td>In the <strong>New Project</strong> dialog box, click     either <strong>Visual C# Projects</strong> or <strong>Visual Basic Projects</strong>     under <strong>Project Types</strong>, and then click <strong>ASP.NET Web     Application</strong> under <strong>Templates</strong>.</td>
</tr>
<tr>
<td>d.</td>
<td>In the <strong>Location</strong> box, replace the <strong>WebApplication</strong><var><strong>#</strong></var>     default name with MyWebApp. If you use the     local server, you can leave the server name as <strong>http://localhost</strong>.     The resulting <strong>Location</strong> box appears as follows:</p>
<p><strong>http://localhost/MyWebApp</strong></td>
</tr>
</table>
</td>
</tr>
<tr>
<td>2.</td>
<td>In Solution Explorer right-click the project node, point   to <strong>Add</strong>, and then click <strong>Add Web Form</strong>. Name   the Web Form MappingsTest.aspx, and then click <strong>Open</strong>.</td>
</tr>
<tr>
<td>3.</td>
<td>Right-click the .aspx page in the editor, and then click <strong>View   Code</strong>. Add the following code to the <strong>Page_Load</strong> event handler:</p>
<p>Visual C# .NET</p>
<pre>private void Page_Load(object sender, System.EventArgs e)</pre>
<pre>{</pre>
<pre>        Response.Write("This code was executed");</pre>
<pre>}</pre>
<pre></pre>
<p>Visual Basic .NET</p>
<pre>Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load</pre>
<pre>    Response.Write("This code was executed")</pre>
<pre>End Sub</pre>
<pre></pre>
</td>
</tr>
<tr>
<td>4.</td>
<td>On the <strong>File</strong> menu, click <strong>Save All</strong>   to save the Web Form and other associated project files.</td>
</tr>
<tr>
<td>5.</td>
<td>On the <strong>Build</strong> menu in the Visual Studio   .NET IDE, click <strong>Build Solution</strong>.</td>
</tr>
<tr>
<td>6.</td>
<td>Right-click the .aspx page, and then click <strong>View in   Browser</strong>.</td>
</tr>
<tr>
<td>7.</td>
<td>If the mappings are correct, the &#8220;This code was   executed&#8221; message appears in the browser. If the mappings are not   correct, one of the following behaviors occurs:</p>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>A blank page appears in the browser.</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>You receive a prompt to download the .aspx page.</td>
</tr>
</table>
<p>This behavior occurs because server-side code is not   processed or executed in the expected manner. In either case you receive the   unprocessed source code. For the blank page scenario, if you right-click the   page in the browser and then click <strong>View Source</strong>, you notice   that the server-side code appears in its unprocessed form. For example, in a   Visual C# ASP.NET Web Form, the <strong>@ Page</strong> directive appears similar to   the following:</p>
<pre>&lt;%@ Page language="c#" Codebehind="MappingsTest.aspx.cs" AutoEventWireup="false" Inherits="MyWebApp.MappingsTest" %&gt;</pre>
<pre></pre>
</td>
</tr>
</table>
<h3>How to verify your IIS application mappings</h3>
<p>To verify that the application mappings are correct, follow these steps:</p>
<table border="0" cellpadding="0">
<tr>
<td>1.</td>
<td>Click <strong>Start</strong>, point to <strong>Programs</strong>,   point to <strong>Administrative Tools</strong>, and then click <strong>Internet   Services Manager</strong>.</td>
</tr>
<tr>
<td>2.</td>
<td>Expand the node that corresponds to the local host   (computer name), and then expand the <strong>Default Web Site</strong> node.</td>
</tr>
<tr>
<td>3.</td>
<td>Right-click your Web application directory, and then click   <strong>Properties</strong>.</td>
</tr>
<tr>
<td>4.</td>
<td>On the <strong>Directory</strong> tab, under <strong>Application   Settings</strong>, click <strong>Configuration</strong>.</td>
</tr>
<tr>
<td>5.</td>
<td>Click the <strong>App Mappings</strong> tab.</td>
</tr>
<tr>
<td>6.</td>
<td>On the <strong>App Mappings</strong> tab, under <strong>Application   Mappings</strong>, check whether the .aspx extension is mapped to the   following DLL:</p>
<p>C:\<var>WindowsFolder</var>\Microsoft.Net\Framework\<var>VersionNumber</var>\aspnet_isapi.dll</p>
<p><strong>Note</strong> Replace <var>WindowsFolder</var> with the name   of the directory where the operating system is installed. Replace <var>VersionNumber</var>   with the .NET Framework version that is installed on your computer.</td>
</tr>
<tr>
<td>7.</td>
<td>If you cannot find the application mapping entry, follow   the steps in the &#8220;Resolution&#8221; section of this article.</td>
</tr>
</table>
<hr align="center" size="2" width="100%" />
<h5>APPLIES TO</h5>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft ASP.NET 1.1</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft ASP.NET 1.0</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2003 Professional Edition</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2003 Enterprise Architect</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2003 Enterprise Developer</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2003 Academic Edition</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2002 Professional Edition</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2002 Enterprise Architect</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2002 Enterprise Developer</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Visual Studio .NET 2002 Academic Edition</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Internet Information Services 6.0</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Internet Information Services 5.1</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft Internet Information Services 5.0</td>
</tr>
</table>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<h5>Microsoft Knowledge Base Article</h5>
<p>This article contents is Microsoft Copyrighted material.<br />
Microsoft Corporation. All rights reserved. <a href="http://support.microsoft.com/tou/">Terms of Use</a> | <a href="http://support.microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx">Trademarks</a></p>
<div class="aizatto_related_posts"><span class="aizatto_related_posts_header" >Related Articles or Pages</span><ul></ul></div>]]></content:encoded>
			<wfw:commentRss>http://ossmall.info/aspnet-pages-exhibit-unexpected-behavior-because-the-server-side-code-is-not-processed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ASP : &#8220;Operation must use an updateable query&#8221; error</title>
		<link>http://ossmall.info/asp-operation-must-use-an-updateable-query-error/</link>
		<comments>http://ossmall.info/asp-operation-must-use-an-updateable-query-error/#comments</comments>
		<pubDate>Fri, 19 Aug 2011 04:15:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ASP - Code]]></category>

		<guid isPermaLink="false">http://ossmall.info/asp-operation-must-use-an-updateable-query-error/</guid>
		<description><![CDATA[You may encounter the following common error when you use ActiveX Data Objects (ADO) with Active Server Pages (ASP): Microsoft OLE DB Provider for ODBC Drivers error &#8217;80004005&#8242; [Microsoft][ODBC Microsoft Access 97 Driver] Operation must use an updateable query. CAUSE This article explains the four primary causes of this error and the corresponding workarounds. Although [...]]]></description>
			<content:encoded><![CDATA[<p>You may encounter the following common error when you use ActiveX Data Objects (ADO) with Active Server Pages (ASP):</p>
<p>Microsoft OLE DB Provider for ODBC Drivers error &#8217;80004005&#8242;<br />
[Microsoft][ODBC Microsoft Access 97 Driver] Operation must use an updateable query.</p>
<h2>CAUSE</h2>
<p><script type="text/javascript"> loadTOCNode(1, 'cause'); </script>This article explains the four primary causes of this error and the corresponding workarounds. Although this article refers to Microsoft Access databases, the information provided here also applies to other types of databases.</p>
<h2>RESOLUTION</h2>
<p><script type="text/javascript"> loadTOCNode(1, 'resolution'); </script>This error is typically encountered when your script attempts to perform an UPDATE or some other action that alters the information in the database. This error occurs because ADO is unable to write to the database for one of the following reasons:</p>
<table border="0" cellpadding="0">
<tr>
<td>1.</td>
<td>The most common reason is that the Internet Guest account   (IUSR_MACHINE), which is by default part of the &#8220;Everyone&#8221; group,   does not have Write permissions on the database file (.mdb). To fix this   problem, use the Security tab in Explorer to adjust the properties for this   file so that the Internet Guest account has the correct permissions.</p>
<p><strong>NOTE</strong>: When using Microsoft Access databases with ADO, it is also necessary to give the   Internet Guest account Write permissions on the directory containing the .mdb   file. This is because Jet creates an .ldb file to handle database locking.   You may also need to give read/write permission on the &#8220;Temp&#8221;   folder because Jet may create temporary files in this directory.</td>
</tr>
<tr>
<td>2.</td>
<td>A second cause of this error is that the database was not   opened with the correct MODE for writing. If you perform the Open on the   Connection object, you use the Mode property to indicate the permissions on   the connection as shown here:</p>
<pre></pre>
<pre>      SQL = "UPDATE Products Set UnitPrice = 2;"</pre>
<pre>      Set Conn = Server.CreateObject("ADODB.Connection")</pre>
<pre>      Conn.Mode = 3      '3 = adModeReadWrite</pre>
<pre>      Conn.Open "myDSN"</pre>
<pre>      Conn.Execute(SQL)</pre>
<pre>      Conn.Close</pre>
<pre></pre>
<pre></pre>
<p><strong>NOTE</strong>: By default, the MODE is set to   0(adModeUnknown), which generally allows updates.</td>
</tr>
<tr>
<td>3.</td>
<td>Another cause of this error is that the &#8220;Read   Only&#8221; setting may be checked in the Options page for this DSN in the   ODBC Manager.</td>
</tr>
<tr>
<td>4.</td>
<td>The last issue and work around pertains to any SQL data   source. The error can be caused by SQL statements that violate referential   integrity of the database. Here are a few of the most common queries that   fail:</p>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>The simplest groups to deal     with are those you cannot change: crosstab, SQL pass-through, union, or     update (or make-table) action queries that have UniqueValue properties set     to Yes.</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>Another very common cause     is when the join includes linked ODBC tables that do not have unique     indexes. In this case, there is no way for SQL to guarantee that records     are unique in a table that has fields whose value will change with the     query.</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>One cause does have a robust workaround. If you try to     update a join field on the &#8220;one&#8221; side of a     &#8220;one-to-many&#8221; query it will fail unless you turn on cascading     updates. This way, you delegate referential integrity to the JET engine.</td>
</tr>
</table>
</td>
</tr>
</table>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<h3>Microsoft Knowledge Base Article</h3>
<p>This article contents is Microsoft Copyrighted material.<br />
Microsoft Corporation. All rights reserved. <a href="http://support.microsoft.com/tou/">Terms of Use</a> | <a href="http://support.microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx">Trademarks</a></p>
<div class="aizatto_related_posts"><span class="aizatto_related_posts_header" >Related Articles or Pages</span><ul></ul></div>]]></content:encoded>
			<wfw:commentRss>http://ossmall.info/asp-operation-must-use-an-updateable-query-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ASP.NET 2.0 Web application does not send actual values to the parameters of the Update method of the data source</title>
		<link>http://ossmall.info/aspnet-20-web-application-does-not-send-actual-values-to-the-parameters-of-the-update-method-of-the-data-source/</link>
		<comments>http://ossmall.info/aspnet-20-web-application-does-not-send-actual-values-to-the-parameters-of-the-update-method-of-the-data-source/#comments</comments>
		<pubDate>Thu, 05 May 2011 16:01:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ASP - Code]]></category>

		<guid isPermaLink="false">http://ossmall.info/aspnet-20-web-application-does-not-send-actual-values-to-the-parameters-of-the-update-method-of-the-data-source/</guid>
		<description><![CDATA[In an ASP.NET 2.0 Web application, you use data binding to update data. However, the application does not send actual values to the parameters of the data source Update method. Instead, the application sends 0 values or null values to the data source. This problem occurs if the following conditions are true: The control that [...]]]></description>
			<content:encoded><![CDATA[<p>In an ASP.NET 2.0 Web application, you use data binding to update data. However, the application does not send actual values to the parameters of the data source <strong>Update</strong> method. Instead, the application sends 0 values or null values to the data source.</p>
<p>This problem occurs if the following conditions are true:</p>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>The control that is used to update data is nested in   another control.</td>
</tr>
<tr>
<td>
<ul></ul>
</td>
<td>These two controls are in a templated control.</td>
</tr>
</table>
<p><strong>Note</strong> This problem does not occur when you use data binding to view data.</p>
<h2>CAUSE</h2>
<p>This problem occurs because of a limitation of ASP.NET 2.0. If the two conditions that the &#8220;Symptoms&#8221; section mentions are true when you use data binding to update data, ASP.NET 2.0 cannot parse the control tree. The operation stops when ASP.NET 2.0 is parsing the first complex control.</p>
<h2>RESOLUTION</h2>
<p>To resolve this problem, do not use nested ASP.NET controls in templated controls.</p>
<hr align="center" size="2" width="100%" />
<h5>APPLIES TO</h5>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft ASP.NET 2.0</td>
</tr>
</table>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<h5>Microsoft Knowledge Base Article</h5>
<p>This article contents is Microsoft Copyrighted material.<br />
Microsoft Corporation. All rights reserved. <a href="http://support.microsoft.com/tou/">Terms of Use</a> | <a href="http://support.microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx">Trademarks</a></p>
<div class="aizatto_related_posts"><span class="aizatto_related_posts_header" >Related Articles or Pages</span><ul></ul></div>]]></content:encoded>
			<wfw:commentRss>http://ossmall.info/aspnet-20-web-application-does-not-send-actual-values-to-the-parameters-of-the-update-method-of-the-data-source/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Error message when you run an ASP.NET 2.0 application on a Windows Server 2003: &#8220;Server unavailable&#8221;</title>
		<link>http://ossmall.info/error-message-when-you-run-an-aspnet-20-application-on-a-windows-server-2003-server-unavailable/</link>
		<comments>http://ossmall.info/error-message-when-you-run-an-aspnet-20-application-on-a-windows-server-2003-server-unavailable/#comments</comments>
		<pubDate>Tue, 07 Dec 2010 16:57:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ASP - Code]]></category>

		<guid isPermaLink="false">http://ossmall.info/error-message-when-you-run-an-aspnet-20-application-on-a-windows-server-2003-server-unavailable/</guid>
		<description><![CDATA[When you try to run a Microsoft ASP.NET 2.0 application on a Microsoft Windows Server 2003-based computer, you may receive the following error message: Server Unavailable Additionally, an error message that resembles following is logged in the Application log: Event Type: Error Event Source: ASP.NET 2.0 Event Category: None Event ID: 1088 Date: Date Time: [...]]]></description>
			<content:encoded><![CDATA[<p>When you try to run a Microsoft ASP.NET 2.0 application on a Microsoft Windows Server 2003-based computer, you may receive the following error message:</p>
<p><font color="#ff0000">Server Unavailable</font></p>
<p>Additionally, an error message that resembles following is logged in the Application log:<br />
Event Type: Error<br />
Event Source: ASP.NET 2.0<br />
Event Category: None<br />
Event ID: 1088<br />
Date: <var>Date</var><br />
Time: <var>Time</var><br />
User: N/A<br />
Computer: <var>ComputerName</var><br />
Description: Failed to execute request because the App-Domain could not be created. Error: 0&#215;80070005 Access is denied.</p>
<h2>CAUSE</h2>
<p>This issue may occur if you try to run the ASP.NET 2.0 application after you perform an in-place upgrade of the existing Windows Server 2003 installation by using a Windows Server 2003 CD that is integrated with Windows Server 2003 Service Pack 2 (SP2).</p>
<p>When you perform an in-place upgrade, the upgrade process resets the permissions on the Microsoft Internet Information Services (IIS) metabase and on other folders that are used by ASP.NET. Therefore, the custom service account will not have permissions to access these folders, and you receive the error message that is mentioned in the &#8220;Symptoms&#8221; section.</p>
<p><strong>Note</strong> An in-place upgrade is also known as a &#8220;repair installation.&#8221;</p>
<h2>RESOLUTION</h2>
<p>To resolve this issue, configure the custom service account by using the Aspnet_regiis.exe utility. At a command prompt, run the Aspnet_regiis.exe utility from ASP.NET 2.0 by using the <strong>-ga</strong> switch:</p>
<p><strong>Aspnet_regiis -ga <var>AccountName</var></strong></p>
<p><strong>Note</strong> In this command, <var>AccountName</var> represents the custom service account.</p>
<p>For example, you can run the following command to grant permissions to the NT AUTHORITY\NETWORK SERVICE account:</p>
<p><strong>aspnet_regiis -ga &#8220;NT AUTHORITY\NETWORK SERVICE&#8221;</strong></p>
<p>.</p>
<hr align="center" size="2" width="100%" />
<h5>APPLIES TO</h5>
<table border="0" cellpadding="0">
<tr>
<td>
<ul></ul>
</td>
<td>Microsoft ASP.NET 2.0, when used with:</td>
</tr>
<tr>
<td colspan="2">
<table border="0" cellpadding="0">
<tr>
<td></td>
<td></td>
<td>Microsoft Windows Server 2003, Enterprise Edition     (32-bit x86)</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Microsoft Windows Server 2003, Standard Edition (32-bit     x86)</td>
</tr>
</table>
</td>
</tr>
</table>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<h5>Microsoft Knowledge Base Article</h5>
<p>This article contents is Microsoft Copyrighted material.<br />
Microsoft Corporation. All rights reserved. <a href="http://support.microsoft.com/tou/">Terms of Use</a> | <a href="http://support.microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx">Trademarks</a></p>
<div class="aizatto_related_posts"><span class="aizatto_related_posts_header" >Related Articles or Pages</span><ul></ul></div>]]></content:encoded>
			<wfw:commentRss>http://ossmall.info/error-message-when-you-run-an-aspnet-20-application-on-a-windows-server-2003-server-unavailable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

