We had a scenario while working with one of the customers that  when we try to install IIS 8.5 and notice that it creates "inetpub" folder  in 2 Drives namely C: drive ( by default ) and additionally it creates on F: drive also.

when this happens we see WAS and WWW service throws below error when we try to start them.

Resolution

=====================================================

We noticed changes done in Registry : HKEY_LOCAL_MACHINE\Software\Microsoft\InetStp

we took registry backup and looked under HKEY_LOCAL_MACHINE\Software\Microsoft\InetStp

we found a FTPROOT config which was pointing to – F:/inetpub

- we changed it to C:/inetpub

and rebooted the box and installed IIS it worked fine

Web application on Visual studio 2013 on windows 7 64bit box

Customer had solution which was running is 32 bit and uses .net 2.0 uses IIS Express.

When we launch https://localhost:888/Login.aspx  in the background it contacts various Databases and does a

redirect to AT&T site which uses session State server ( internally ) and launch the login page for user to enter credentials.

When we have .net framework update 4.5.2 this breaks with following error:

Server Error in '/' Application.

--------------------------------------------------------------------------------

Unable to make the session state request to the session state server. Please ensure that the ASP.NET State service is started

and that the client and server ports are the same.  If the server is on a remote machine, please ensure that it accepts

remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters

\AllowRemoteConnection.  If the server is on the local machine, and if the before mentioned registry value does not exist or

is set to 0, then the state server connection string must use either 'localhost' or '127.0.0.1' as the server name.

  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace

for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Unable to make the session state request to the session state server. Please

ensure that the ASP.NET State service is started and that the client and server ports are the same.  If the server is on a

remote machine, please ensure that it accepts remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM

\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection.  If the server is on the local machine, and if the

before mentioned registry value does not exist or is set to 0, then the state server connection string must use either

'localhost' or '127.0.0.1' as the server name.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and

location of the exception can be identified using the exception stack trace below. 

Stack Trace:

[HttpException (0x80072749): Unable to make the session state request to the session state server. Please ensure that the

ASP.NET State service is started and that the client and server ports are the same.  If the server is on a remote machine,

please ensure that it accepts remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

\aspnet_state\Parameters\AllowRemoteConnection.  If the server is on the local machine, and if the before mentioned registry

value does not exist or is set to 0, then the state server connection string must use either 'localhost' or '127.0.0.1' as

the server name.]

   System.Web.SessionState.OutOfProcSessionStateStore.MakeRequest(StateProtocolVerb verb, String id, StateProtocolExclusive

exclusiveAccess, Int32 extraFlags, Int32 timeout, Int32 lockCookie, Byte[] buf, Int32 cb, Int32 networkTimeout,

SessionNDMakeRequestResults& results) +1835429

   System.Web.SessionState.OutOfProcSessionStateStore.SetAndReleaseItemExclusive(HttpContext context, String id,

SessionStateStoreData item, Object lockId, Boolean newItem) +191

   System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +560

   System.Web.SessionState.SessionStateModule.OnEndRequest(Object source, EventArgs eventArgs) +160

   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

  --------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:2.0.50727.5485; ASP.NET Version:2.0.50727.5483 

Note: Issue can be resolved by rolling back .net update 4.5.2 to 4.5.1.

Resolution :

==================================

Collected a network trace and we notice that there was a disconnect or Reset which was happening from back end Database.

When we looked deep into architecture of the Server we found it had a Firewall: “Hips”

HIPS stands for “Host-based Intrusion Prevention System“. We then asked customer to investigate why its rejecting the connection and we found that HIPS stores a hash for the aspnet_state.exe in the dynamically created firewall rule allowing it.

Even though you are using adaptive mode the install of the .NET 4.5.2 update which installs a newer aspnet_state.exe did not result in either this rule being replaced or updated. When you manually went into the rule configuration and used their wizard to drill down to the "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_state.exe" file it then updated the stored hash to a new value and the test solution is now back working.

More information on Hips : https://blog.malwarebytes.org/intelligence/2013/05/whatiships/

Hope this Helps !

Irfan

Recently I worked with one of our customer who was facing Thread abort exception and he was unable to login to his site. The exception showed up in Application logging which customer had set up.

we see there is a redirection issue when we enter values in text boxes and click on submit button on a URL

https://Custom-Site.Foo.com/Example/Summary.aspx

it redirects us to home.aspx which is not expected. we must see the data entered is submitted to DB and get a message on screen. this was customers requirement.

We see Error :

Thread was being aborted.

   at Com.D.Dt.Facts.D.EventD.SaveEvent()

   at EIGDefault.SaveEventAndReport(Boolean finishLatter)

EIGDefault.aspx.SaveEventAndReport

12/4/2014 12:00:00 AM 014373700

Thread was being aborted.

   at Com.De.Dt.Facts.D.EventD.GetParameters(String DBOperation)

   at Com.De.Dt.Facts.D.EventD.SaveEvent()

EventD.SaveEvent

12/4/2014 12:00:00 AM 014373700

Thread was being aborted.

   at System.Threading.Thread.AbortInternal()

   at System.Threading.Thread.Abort(Object stateInfo)

   at System.Web.HttpResponse.End()

   at System.Web.HttpServerUtility.Transfer(String path)

   at Com.D.Dt.Facts.D.EventD.GetParameters(String DBOperation)

EventD.GetParameters

Resolution or Work Around :

==============================

We found Thread Abort exception comes by default if we use Server.transfer.

There was a confusion on why the redirection was happening. later we found that BIG F5 which was load balancer had a update which caused this “Redirection and updating Load balancer Firmeware it fixed issue of redirection.

But, the reason for Thread Abort exception was not load balancer instead the use of  Server.transfer in code.

Which According to this article will cause Thread Abort Exception.

https://support.microsoft.com/en-us/kb/312629

From the article : If you use the Response.End, Response.Redirect, or Server.Transfer method, a ThreadAbortException exception occurs.

Work around this problem, use one of the following methods:
For Response.End, call the HttpContext.Current.ApplicationInstance.CompleteRequest method instead of Response.End to bypass the code execution to the Application_EndRequest event.
For Response.Redirect, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. For example:

  Response.Redirect ("nextpage.aspx", false);
If you use this workaround, the code that follows Response.Redirect is executed.

---> For Server.Transfer, use the Server.Execute method instead.

Cheers,

Irfan

This is my first blog and please feel free to comment if you need additional info on the below content :)

So on this post we will be focusing on issues that occur with NAS devices when we deploy using Webdeploy API

The deployment done from Web Deploy APIs to a file share which is on NAS device fails to write or update existing files.

it first "Deletes" the File share content and then Updates the new content which was not expected.

Note :  We have a -enableRule:DoNotDeleteRule  switch available with Msdeploy but for our case that customer was also deleting some folders through the code and it did not help us.

More information on DoNotDeleteRule is here.

===================================================================================

In one of customer scenario similar to this we found that we have file share on  NAS device known ( NetAppStorage Systems). We use webdeploy APIs to deploy content to NAS device.

Also we have console application which uses WEB DEPLOY APIs & it is internally called using another asp.net website which has the User interface to Deploy the content of one server to a file share.

 ( it was a custom built application to deploy the content via asp.net code to file share directly )

Note : This will also fail if we are deploying using Visual studio or by command line using web deploy tool to a file share ( NAS) device.

We see now with NAS device when we deploy the content first " Deletes the content existing on file share and then Freshly copies new information "

 and in 2003 file share or any windows file share it was working fine & not deleting the content and it was running as expected.

The problem started when they Upgraded to use a NAS device and decommissioned windows boxes.

Fix for this Issue :

====================================================================================

If the file system is NTFS, then Web Deploy will rely on the system to keep things sorted.  If it isn’t, then Web Deploy will sort it first. 

However if the system is not NTFS and for some reason it can’t discover this, then it will assume it’s NTFS. 

We figured out from Dev team of webdeploy that  connecting to windows files share by default windows file shares will be sorted and content will be upgraded easily but NAS device file structure will not be sorted by

default we need to enable a Registry to force webdeploy to sort before it upgrades the files on NAS share.

By doing a run “dir” from a command line on the NAS to see if everything is in alphabetical order.  If it isn’t, then you need to force Web Deploy to do the sorting. 

Before the Registry changes we see :

09/25/2014  03:00 PM    <DIR>          .
09/25/2014  03:00 PM    <DIR>          ..
09/25/2014  03:00 PM               829 About.aspx
09/25/2014  03:00 PM               171 ApplicationError.htm
09/25/2014  03:00 PM             1,072 Bundle.config
09/25/2014  03:00 PM               545 CheckSite.aspx
09/25/2014  03:00 PM             2,270 Default.aspx
09/25/2014  03:00 PM            32,038 favicon.ico
09/25/2014  03:00 PM               122 Global.asax
09/25/2014  03:00 PM             2,026 packages.config
09/25/2014  03:00 PM             3,507 Site.Master
09/25/2014  03:00 PM             4,632 Web.config
09/25/2014  03:00 PM             1,304 Web.Debug.config
09/25/2014  03:00 PM             1,365 Web.Release.config
09/25/2014  03:00 PM    <DIR>          bin
09/25/2014  03:00 PM    <DIR>          Content
09/25/2014  03:00 PM    <DIR>          Images
09/25/2014  03:00 PM    <DIR>          Scripts
              12 File(s)         49,881 bytes
              

 To do this, you can create a DWORD called “AlwaysSortDirectories” and set it to 1 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\3 in the registry

on Source machine ( on server from where the deployment is happening) in our case IIS server .

 By doing the above resolved the issue. 

We see After the Registry setting done and restarted the box we see behaviors of files sorting on NAS.

09/25/2014  04:15 PM    <DIR>          .
09/25/2014  04:15 PM    <DIR>          ..
09/25/2014  03:00 PM               829 About.aspx
09/25/2014  03:00 PM               171 ApplicationError.htm
09/25/2014  04:15 PM    <DIR>          bin
09/25/2014  03:00 PM             1,072 Bundle.config
09/25/2014  03:00 PM               545 CheckSite.aspx
09/25/2014  04:15 PM    <DIR>          Content
09/25/2014  03:00 PM             2,270 Default.aspx
09/25/2014  03:00 PM            32,038 favicon.ico
09/25/2014  03:00 PM               122 Global.asax
09/25/2014  04:15 PM    <DIR>          Images
09/25/2014  03:00 PM             2,026 packages.config
09/25/2014  04:15 PM    <DIR>          Scripts
09/25/2014  03:00 PM             3,507 Site.Master
09/25/2014  03:00 PM             4,632 Web.config
09/25/2014  03:00 PM             1,304 Web.Debug.config
09/25/2014  03:00 PM             1,365 Web.Release.config
              12 File(s)         49,881 bytes
              

-- The Dword registry change has fixed the issue of sorting by Web deploy before the content is copied to NAS device.

I hope this helps :)

Irfank