WebTopics https://docs.microsoft.com/archive/blogs/webtopics/feed.xml IIS and ASP.NET Information and Tips from Microsoft Developer Support Thu, 16 Aug 2018 12:16:30 GMT en-US hourly 1 IIS on Nano server in a Hyper-V Virtual machine https://docs.microsoft.com/archive/blogs/webtopics/iis-on-nano-server-in-a-hyper-v-virtual-machine Thu, 16 Aug 2018 12:16:30 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1735 Nano Server:
  • Nano server is available with Windows Server 2016
  • This installation option is available for Standard and Datacenter editions of Server 2016.
  • It doesn't have the *FULL* .Net Framework installed.
  • It is similar to Windows Server Core, but significantly smaller, lighter, has no local logon capability, headless and only supports 64-bit applications and tools.
  • It is a remotely administered server operating system optimized for private clouds and datacenters.
  • It can be used as a DNS, File storage host, IIS web server to host the application which doesn't need full .net framework. It ideal to be used in a container or as a guest OS in virtual machine. It can also run on physical box.
  • It takes up far less disk space, sets up significantly faster, and requires far fewer updates and restarts than Windows Server.
  Difference between Server Core and Nano Server: Server Core:
  • Introduced with server 2008 R2
  • Has powershell / cmd to help us in the remote administrative management
  • GUI can be added if need be using install-windowsFeature
  • supports RDP
Nano Server:
  • This is not exactly same as server core. This is headless. Meaning there is no logon capability and No GUI option.
  • It can be only operated remotely.
  • It has fixed set of roles which can be installed.
  • It is best for a container / hyper V server. It doesn't support installing the full version of .Net framework. But only a subset of the .net Fx (.net core) which was written specifically for the cloud and cross platform.
Note: Both run on physical and VM. Both run on the container. The dotnet core application which run on nano can run on server core too.   Creating the nano VHD: I will be using a 180 day free trial ISO downloaded from the Evaluation Center site: https://www.microsoft.com/evalcenter/evaluate-windows-server-2016 Then follow the below steps in order: 1. Extract the ISO and you should be having it in your storage drive. I had it inside my F:\ drive 2. I created a sample folder C:\Nano\ and placed the NanoServerImageGenerator folder from the F:\NanoServer folder which we extracted in Step 1 3. Start Windows PowerShell as an administrator, Navigate to the folder C:\Nano\NanoServerImageGenerator\ and run the powershell command: Import-Module .\NanoServerImageGenerator.psm1 -Verbose 4. After this, you need to run the below command to create a nano server VHD which can be imported as a Guest OS in our Hyper V: PS C:\nano> New-NanoServerImage -edition Standard -MediaPath F:\ -BasePath C:\nano -targetPath C:\nano\nanodemo.vhdx -deploymentType Guest -Computername nanodemo -storage -Package Microsoft-NanoServer-IIS-Package This command copies the necessary files from media path F:\ drive into my base path C:\nano\. It converts the Nano Server .wim file into a .vhd file. It then moves the newly created standard edition of VHD to my target path. I have given my computer name as nanodemo and since I will be using it as a Guest OS, I have mentioned Guest in my deploymentType. I am installing the IIS role using the -package switch while creating the VHD. Note that you can also install the IIS feature later, I will be explaining it later in this blog. 5. It will also prompt you for providing the administrator password. Remember this password and you are expected to provide this password while you login to your nano server.   Setting up the VM: I have installed the Hyper-V role in my Host machine.
  1. Open the Hyper-V Manager, On the right-side Actions Pane, click on the Virtual Switch Manager and create a virtual switch. I am making use of an Internal virtual Switch in my demo.
  2. Click on Newà Virtual Machineà Give a name to Your Virtual machine à You can allocate some startup memory à Assign the Virtual switch connection which you created in Step 1.
  3. In the next step we can Use an existing Virtual hard disk à Point it to the Virtual hard disk ( vhd) which we created above.
  4. This will take some time to setup the Guest nano OS. After this, your Virtual machine will be up and running.
  5. You will be asked to login, use the same password which you had used while creating the vhd.

  Configuring the Nano Server:
  1. After your login, you will see Nano Server Recovery Console as shown below:

  1. You can enable the settings as per your requirement. Note: I have enabled the WinRM for remote management and enabled a few of the Inbound and outbound ports needed for my application.
  2. I have made a note of the IP address of my nano server from the Networking setting.
  3. Since I mentioned that the nano server is headless, we will be making use of the powershell to access the nano server remotely.
  Accessing nano server remotely:
  1. I am making use of the below powershell script to remotely login to the Nano server VM. Note: I have an entry in the C:\Windows\System32\drivers\etc\hosts file to map the nanodemo with the IP address found from Networking setting in my nano server.

    $server="nanodemo"

    Enter-PSSession  -VMName  $server -Credential administrator

  2. The above command will prompt you to enter the administrator credentials. On successful login, the powershell is ready to accept your commands:

    [nanodemo]: PS C:\Users\administrator\Documents>
  3. If you haven't used the switch -Package Microsoft-NanoServer-IIS-Package while creating the nano VHD, you can also install the IIS remotely using the below commands:

    Install-PackageProvider NanoServerPackage

    Import-PackageProvider NanoServerPackage

    Install-NanoServerPackage -Name Microsoft-NanoServer-IIS-Package

  4. To see all the available packages on Nano server, you can use the command: Find-NanoServerPackage

Creating IIS website:
  1. We will be making use of the newly introduced iisadministration module.
  2. Remotely create the folder structure needed for your website and place your application code in nano server. Note: If you want to make use of the SMB ( \\nanodemo\ ) to access the nano server files remotely, ensure that the File and Remote sharing Firewall setting is enabled on nano server.

    Import-Module  iisadministration

      New-IISSite -Name samplesite -BindingInformation "*:80:" -PhysicalPath C:\inetpub\samplesite

     3. After this you can access the website:

References: https://docs.microsoft.com/en-us/windows-server/get-started/nano-server-quick-start https://docs.microsoft.com/en-us/windows-server/get-started/getting-started-with-nano-server https://docs.microsoft.com/en-us/windows-server/get-started/iis-on-nano-server Hope this helps]]> Securing the ARRAffinity Cookie https://docs.microsoft.com/archive/blogs/webtopics/securing-the-arraffinity-cookie Mon, 14 May 2018 13:56:42 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1635 Usually when we talk about COOKIES the primary reason would be to manage state, handle logins etc. So, it would be a quintessential property to keep it safe and to prevent any breach of security. Just like how we have a safe version of HTTP by encrypting over SSL, we can do the same for a cookie through the SECURE tag. When we think of using the ARR module in IIS for load balancing and enable server affinity , an additional tag(cookie) called ARR affinity will be assigned by the ARR to the first request of a new user session so that till all subsequent requests are served, the client talks to the same back-end server until the session gets expired. This “technique” is aptly called as the Cookie Insertion Method where the ARR acts like a proxy between the client and the server to intercept the requests so that it will attach/stick the session to a specific server addressed by the RESPONSE_SERVER_NAME. While troubleshooting on an issue, I came across a vulnerability in which the penetration test read “Missing Secure Attribute In SSL Session Cookie” that basically means that we need to plug the RESPONSE_SET_COOKIE with a “secure” tag. Out of the different Fields that we can modify in the RESPONSE, our primary concern here would be to change the outgoing content (cookie) from the server back to the client but with the ARRAffinity set to secure. After pondering over the many options we have in IIS, a very feasible option would be to use the URL REWRITE Module in IIS to Modify the Response Section through an Outbound Rule. This would need you to add a simple rule (mentioned below) in the outbound section. 
<rewrite>

 <allowedServerVariables>

    <add name="REMOTE_USER" />

    </allowedServerVariables>

    <globalRules>

           <rule name="ADD YOUR RULE NAME" enabled="true" patternSyntax="Wildcard" stopProcessing="true">

           <match url="*" />

           <action type="Rewrite" url="http://SERVERFARMNAME/{R:0}" />

           </rule>
     </globalRules>

           <outboundRules>

           <rule name=”ADD YOUR RULE NAME">

           <match serverVariable="RESPONSE_Set_Cookie" pattern="ARRAffinity=(.*)" />

           <action type="Rewrite" value="{R:0};secure" />

           </rule>

           </outboundRules>

</rewrite>
 ]]> An error occurred : Failed to find any azure subscriptions for the current user https://docs.microsoft.com/archive/blogs/webtopics/an-error-occurred-failed-to-find-any-azure-subscriptions-for-the-current-user Thu, 11 Jan 2018 16:00:14 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1545   This error occurs if the website , dev.botframework.com , is logged in with an account which do not have any Azure subscription .   To overcome this issue , we can follow the below steps. In the portal, dev.botframework.com, 1.Open My Bots   2.Click on the bot that has to be migrated. 3.Navigate to settings tab. In settings, under the Admin section we see owners.   4.Add the owner/account which has Azure subscription in here. 5.Login back with the new owner , now you will be able to migrate the bot  to azure bot services without any issues.  ]]> Deploy the ASPNET Core App on Linux and Capture Perfview traces https://docs.microsoft.com/archive/blogs/webtopics/deploy-the-aspnet-core-app-on-linux-and-capture-perfview-traces Thu, 28 Dec 2017 14:30:09 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1535 My previous blog was specifically to capture the perfview traces for aspnet core MVC application on a Windows box.

The current blog targets capturing the perfview traces for aspnet core MVC application on a LINUX box.

Pre-requisites: 1. On the Windows Development Box ensure that you have the below components:
  • putty.exe: This is used to connect to your Guest LINUX box
  • pscp.exe: This is a command line application to securely transfer the files.
2. Have a LINUX Operating system with most recent release. I am making use of Ubuntu 17.04 release for my demo. 3. The ASPNET Core application with the logging enabled. More Info on enabling logging can be found here in my previous blog.   Let's get started. Step 1: Installing the Dotnet Core SDK on Linux 1. Install the Dotnet Core SDK for Linux from this article Then run the commands mentioned in the above article. Note that you need to run the command as per the product version. If you are not sure of the version, you can simply run the below command:

navba@CoreLinuxDemo:~$ lsb_release -a

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 17.04

Release: 17.04

Codename: zesty
  2. Post adding dotnet product feed and installing dotnet SDK, you can test the installation by simply creating a sample .NET     MVC application using the dotnet CLI. We are creating the app within the myapp directory.       navba@CoreLinuxDemo:~$ dotnet new mvc -o myapp To see the contents / files the above command gave you, run the below commands:

navba@CoreLinuxDemo:~$ cd myapp

navba@CoreLinuxDemo:~/myapp$ ls

appsettings.Development.json appsettings.json bower.json bundleconfig.json Controllers Models myapp.csproj obj Program.cs Startup.cs Views wwwroot
  3. To restore the dependencies of your application, you can run the below command:

navba@CoreLinuxDemo:~/myapp$dotnet restore

Restore completed in 39.36 ms for /home/navba/myapp/myapp.csproj.

Restore completed in 27.37 ms for /home/navba/myapp/myapp.csproj.

To run the application, you can run the below command:

navba@CoreLinuxDemo:~/myapp$ dotnet run

warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]

No XML encryptor configured. Key {79a1ec79-a634-4707-936e-a91a85576f75} may be persisted to storage in unencrypted form.

Hosting environment: Production

Content root path: /home/navba/myapp

Now listening on: http://localhost:5000

Application started. Press Ctrl+C to shut down.

Note: dotnet run command will internally run the dotnet restore / dotnet build commands. 4.  To test the application, you can launch another instance of the putty and connect to your LINUX box and try accessing             the  http://localhost:5000 using curl as shown below:     navba@CoreLinuxDemo:~$ curl http://localhost:5000 You should be getting the html response of the application. Alternatively, you can also try accessing the app using wget as shown below:

navba@CoreLinuxDemo:~$ wget http://localhost:5000

--2017-12-21 12:11:50-- http://localhost:5000/

Resolving localhost (localhost)... 127.0.0.1

Connecting to localhost (localhost)|127.0.0.1|:5000... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/html]

Saving to: 'index.html'

index.html [ <=> ] 8.62K --.-KB/s in 0s

2017-12-21 12:11:50 (162 MB/s) - 'index.html' saved [8827]

Once we confirm that we get the expected response from the application we can confirm that the .NET Core SDK is installed fine, and our application is functioning right.

  Step 2: Install Nginx server 1. We install the nginx server using the below command:       navba@CoreLinuxDemo:~/myapp$ sudo apt-get install nginx 2. Once it is installed, try to access your nginx server using your external IP address of the LINUX box. If you see the nginx HOME page then your nginx server installation did succeed and its functioning fine.

Welcome to nginx!

If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org. Commercial support is available at nginx.com. Thank you for using nginx.
Note: Remember to open PORT 80 in the external firewall (if any). See my configurations below:   Step 3: Configuring Nginx as reverse proxy to dotnet core application: 1. We will clear the default configuration using the below command:     navba@CoreLinuxDemo:~/myapp$ sudo truncate -s 0 /etc/nginx/sites-available/default 2. Modify the nginx config using the below command:     navba@CoreLinuxDemo:~/myapp$ sudo nano /etc/nginx/sites-available/default The editor opens, and you need to manually enter the below to avoid any syntactical errors:
server {     listen 80;     location / {         proxy_pass http://localhost:5000;         proxy_http_version 1.1;         proxy_set_header Upgrade $http_upgrade;         proxy_set_header Connection keep-alive;         proxy_set_header Host $host;         proxy_cache_bypass $http_upgrade;     } }
Note: The port which dotnet.exe process will be listening to can be different, ensure that you place a correct one in the nginx config file. 3. To ensure that you have the syntax placed right in the configuration file you can run the below command:

navba@CoreLinuxDemo:~/myapp$ sudo nginx -t

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful
  4. If the above command throws any syntactical errors, you need to verify the nginx configuration and manually type the above entry again. 5. The below command should reload the new configuration settings.    navba@CoreLinuxDemo:~/myapp$ sudo nginx -s reload 6. Then you run the dotnet run command again to spawn up the dotnet.exe process.    navba@CoreLinuxDemo:~/myapp$ dotnet run 7. Now try to access the application externally. You should see that the Home/Index page of your MVC application. Our nginx server successfully proxied the request to dotnet application. Note: If you are having trouble in getting this page, please follow the above steps again. Now that the application is up and running on Linux via nginx you can try capturing perfview traces. Note that you can do custom logging so that it gets logged within the perfview using this article.   Step 4: Deploying your concerned Core application to Linux: If you need help in moving your own application from windows environment to Linux before capturing the Perfview traces, you can use pscp.exe 1. On your Dev box, Open the CMD prompt in admin mode. 2. Navigate to the location where you placed your application. 3. From this folder place the path to your pscp.exe and run the below command to place your application contents within the myapp folder within your profile.   E:\dotnet\CoreDemo> C:\temp\pscp.exe -r * navba@52.170.94.20:/home/navba/myapp 4. Post this go back to you linux files and you can run the ls  command to ensure that your files have been placed right. 5. Run the dotnet run command to launch the dotnet.exe and note the port number it is listening on. Then you modify the nginx configuration file by following the steps from Step 3 section mentioned above.   Step 5: Capturing Perfview traces for your application 1. Launch a different instance of PUTTY and connect to your LINUX box. 2. The below command will download the perfview tool:    navba@CoreLinuxDemo:~$curl -OL http://aka.ms/perfcollect 3.  You can confirm it again by using ls command.

navba@CoreLinuxDemo:~$ ls

index.html myapp perfcollect
4. You can try giving it JUST executable permissions. I simply gave it FULL Control for all groups to avoid any issues.   navba@CoreLinuxDemo:~$chmod 777 perfcollect 5. Install the perfview using the below command:   navba@CoreLinuxDemo:~$ sudo ./perfcollect install 6. Add the below environment variable before you start collecting the trace:   navba@CoreLinuxDemo:~$ export COMPlus_PerfMapEnabled=1 7. Then you run the below command to start collecting it. Ensure that your dotnet.exe process is running and try accessing your application. 8. Once you are sure that you have captured the issue, you can stop the perfview by clicking Ctrl + C as shown below: navba@CoreLinuxDemo:~$ sudo ./perfcollect collect MyPerfviewFile Collection started. Press CTRL+C to stop. ^C ...STOPPED. Starting post-processing. This may take some time. Generating native image symbol files ...SKIPPED Crossgen not found. Framework symbols will be unavailable. See https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/lin ux-performance-tracing.md#resolving-framework-symbols for details. Saving native symbols ...FINISHED Exporting perf.data file ...FINISHED Compressing trace files ...FINISHED Cleaning up artifacts ...FINISHED Trace saved to MyPerfviewFile.trace.zip 8. You can run the ls command to see the collected trace:
navba@CoreLinuxDemo:~$ ls index.html lttng-traces myapp MyPerfviewFile.trace.zip perfcollect
  More Info about the analysis of perfview trace on Linux you can see this: https://blogs.msdn.microsoft.com/vancem/2016/02/20/analyzing-cpu-traces-from-linux-with-perfview/   Hope this helps :)]]> Capturing Perfview traces for ASPNET Core application https://docs.microsoft.com/archive/blogs/webtopics/capturing-perfview-traces-for-aspnet-core-application Wed, 27 Dec 2017 17:43:22 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1507 perfview traces for aspnet core web application. So, I decided to blog on this topic and explain how to enable the logging, capture and analyze perfview trace. I am making use of a simple ASPNET Core MVC application here to explain this. I have the below lines in my Program.cs file:
static void Main(string[] args) {     BuildWebHost(args).Run(); } public static IWebHost BuildWebHost(string[] args) => WebHost.CreateDefaultBuilder(args) .CaptureStartupErrors(true) // THE ABOVE LINE IS FOR THE STARTUP RELATED ISSUES .UseSetting(WebHostDefaults.DetailedErrorsKey,"true") //THE ABOVE LINE WILL GIVE A DETAILED ERROR PAGE IN CASE OF ANY FAILURE .UseStartup<Startup>() .UseKestrel() .ConfigureLogging((hostingContext,logging)=> {    logging.AddConfiguration(hostingContext.Configuration.GetSection("Logging"));    logging.AddConsole();    //THE ABOVE LINE WILL DISPLAY THE LOGS IN CONSOLE WHILE RUNNING THE APP FROM THE CMD LINE    logging.AddDebug();    //THE ABOVE LINE WILL DISPLAY THE LOGS IN DEBUG OUTPUT WINDOW    logging.AddEventSourceLogger();    //THE ABOVE LINE IS FOR THE PERFVIEW }) .Build();
  Ensure that you have placed the below namespaces within your Program.cs    using Microsoft.AspNetCore.Hosting;    using Microsoft.Extensions.Logging;    using Microsoft.AspNetCore; You can make use of the Nuget PM to install the Microsoft.Extensions.Logging component. Go to your concerned Controller and ensure that you have referenced the logging component
public class HomeController : Controller {     // GET: /<controller>/     private readonly ILogger _logger;     public HomeController(ILogger<HomeController> logger)     {        _logger = logger;     }     public IActionResult Index()     {        // This code specifies the loglevel.        // Ex: LogInformation, LogWarning, LogCritical, LogDebug etc        _logger.LogInformation(1000, "In Index method..............");        return View();     } }
  Ensure that you have placed the below namespaces within your Controller:    using Microsoft.AspNetCore.Mvc;    using Microsoft.Extensions.Logging; After doing the above changes, you will see the Logging information within your Debug Output window and the CMD console.   In the Debug window:
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 GET http://localhost:5761/home/index Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 GET http://localhost:5761/home/index ------------------------------------ Demo.Controllers.HomeController:Information: In Index method.............. Demo.Controllers.HomeController:Information: In Index method..............
  In the CMD console:
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[1] Request starting HTTP/1.1 GET http://localhost:5762/home/index info: Microsoft.AspNetCore.Hosting.Internal.WebHost[1] Request starting HTTP/1.1 GET http://localhost:5762/home/index info: Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker[1] Executing action method Demo.Controllers.HomeController.Index (Demo) with arguments ((null)) - ModelState is Valid info: Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker[1] Executing action method Demo.Controllers.HomeController.Index (Demo) with arguments ((null)) - ModelState is Valid infoinfo: Demo.Controllers.HomeController[1000] In Index method.............. : Demo.Controllers.HomeController[1000] In Index method.............. info: Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ViewResultExecutor[1] Executing ViewResult, running view at path /Views/Home/Index.cshtml. info: Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ViewResultExecutor[1] Executing ViewResult, running view at path /Views/Home/Index.cshtml. info: Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker[2] Executed action Demo.Controllers.HomeController.Index (Demo) in 4628.1449ms info: Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker[2] Executed action Demo.Controllers.HomeController.Index (Demo) in 4628.1449ms info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2] Request finished in 4686.3757ms 200 text/html; charset=utf-8 info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2] Request finished in 4686.3757ms 200 text/html; charset=utf-8
  Perfview Data Collection: Download the Perfview from the below location and place it on the machine where you have the ASPNET Core app running: https://www.microsoft.com/en-us/download/details.aspx?id=28567 Data Capture:
  • Open Perfview.
  • Go to Collect and select Collect option as shown below:
  • Expand the Advanced Options.
  • Enable the Thread Time and IIS providers. (This will help us give some additional Information while troubleshooting) Note: IIS provider is needed if the app is hosted on IIS. Else you can skip it. This provider can be used only if the IIS Tracing feature is installed.
  • Place the *Microsoft-Extensions-Logging section within Additional Providers section as shown below:
  Perfview Analysis: After we open the perfview ETL trace we see our logging information being logged:
Event Name                                    Time MSec Process Name   Rest  
Microsoft-Extensions-Logging/FormattedMessage 39,706.201 dotnet (25292) ThreadID="285,016" Level="2" FactoryID="1" LoggerName="Demo.Controllers.HomeController" EventId="1000" FormattedMessage="In Index method.............." ActivityID="//1/3/1/"
Microsoft-Extensions-Logging/Message          39,708.668 dotnet (25292) ThreadID="285,016" Level="2" FactoryID="1" LoggerName="Demo.Controllers.HomeController" EventId="1000" Exception="{ TypeName="", Message="", HResult=0, VerboseMessage="" }" Arguments="[{ Key="{OriginalFormat}", Value="In Index method.............." }]" ActivityID="//1/3/1/"
Microsoft-Extensions-Logging/MessageJson      39,708.700 dotnet (25292) ThreadID="285,016" Level="2" FactoryID="1" LoggerName="Demo.Controllers.HomeController" EventId="1000" ExceptionJson="{}" ArgumentsJson="{"{OriginalFormat}": "In Index method.............."}" ActivityID="//1/3/1/"
  Hope this helps :)]]> IIS FTP with ASP.NET membership authentication https://docs.microsoft.com/archive/blogs/webtopics/iis-ftp-with-asp-net-membership-authentication Wed, 27 Dec 2017 17:21:14 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1496 this. This blog specifically explains how to address the below error which most of them have encountered while setting up the ASP.NET SQL membership authentication with FTP site:

Response:       220 Microsoft FTP Service

Command:        USER test

Response:       331 Password required

Command:        PASS *********

Response:       530-User cannot log in.

Response:       Win32 error:

Response:       Error details: System.Web: Default Membership Provider could not be found.

Response:       530 End

Error:          Critical error: Could not connect to server

You can follow this blog to configure the authentication with SQL membership for the FTP site on IIS. Post this if you still run into the above issue then you need to ensure that the following steps are followed: Steps 1: Have the below setting within the web.config within the <configuration> tag. (depending on the framework and the bitness your application pool is using) Example: If your AppPool is 64 bit running under .NET 4.0. You should be using the location C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\web.config
<location path="GlobalFtpSite/ftpsvc">   <connectionStrings>     <add connectionString="server=localhost;database=aspnetdb;Integrated Security=SSPI" name="FtpLocalSQLServer" />    </connectionStrings> <system.web>    <membership defaultProvider="FtpSqlMembershipProvider">      <providers>         <add name="FtpSqlMembershipProvider"            type="System.Web.Security.SqlMembershipProvider,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a"            connectionStringName="FtpLocalSQLServer"            enablePasswordRetrieval="false"            enablePasswordReset="false"            requiresQuestionAndAnswer="false"           applicationName="/"            requiresUniqueEmail="false"            passwordFormat="Clear" />       </providers>    </membership>    <roleManager defaultProvider="FtpSqlRoleProvider" enabled="true">       <providers>         <add name="FtpSqlRoleProvider"            type="System.Web.Security.SqlRoleProvider,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a"            connectionStringName="FtpLocalSQLServer"            applicationName="/" />          </providers>       </roleManager>    </system.web> </location> </configuration>
Note: If you are making use AppPool which is on .NET version 2.0 with 64 bit, then you need to modify the web.config in the location C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG. Also ensure that you have modified the above highlighted section to 2.0.0.0. Steps 2: Grant the permissions to the Network Service Account Write / Modify permissions to the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\ folder. Note: depending on your AppPool framework and bitness the above path can differ. Steps 3: Remember You don't need to have any settings at the FTP website level for the .NET Roles, .NET Users etc, Because the root web.config setting should apply to all the applications which run on that version of framework and bitness. Hope this helps :)]]> Session State Is Lost in Web Farm If You Use SqlServer or StateServer Session Mode https://docs.microsoft.com/archive/blogs/webtopics/session-state-is-lost-in-web-farm-if-you-use-sqlserver-or-stateserver-session-mode Wed, 21 Jun 2017 21:02:48 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1455 unexpected loss of session state”. We face these issues when we store the session information inproc, especially when we don’t set client affinity in the load balancer level. This is one of the main reasons why users opt for an outproc session storage technique (like a SQL server or State Server). But, when you are configuring a state server across a web farm, maintaining the session state across multiple servers and applications is a matter of challenge for which you must take care of a little configuration piece while setting your sites. Let me give you a brief idea on what we can do and why we are supposed to concentrate on such configuration settings while setting up our sites in a webfarm environment.
  • When we make a request, a worker process will be spawned which is always associated with a site ID.
  • The user is assigned with a unique session ID when the session begins. The user will then send that session ID to the server for every request.
  • When the session information is stored in the SQL Server or state server, to uniquely identify the session information for each user specific to each application, it is associated with a primary key.
  • That primary key is a combination of the session ID assigned to the user (that you might see in the request header) and the application ID.
For example, the value looks like: ’13clw2vlrjio0d45opi0qg4500000002’ where 2 is site id You should ensure that your website is associated with the same site ID in all the web servers which are behind a load balancer to avoid unexpected session state losses.When we are configuring the application in multiple servers and when the site ID’s are different in different servers, this primary key will become different for different servers. That will produce a behavior similar to storing the session inproc. Conclusion: Maintaining same site ID for the same application across all the servers in the webfarm is important and will help in maintaining the session state when going with out-of-proc approach in a multi-server environment Please leave your comments if you have any questions around this or need any clarification.]]> Data Collection for Deadlock Detected issue of a IIS based web application https://docs.microsoft.com/archive/blogs/webtopics/data-collection-for-deadlock-detected-issue-of-a-iis-based-web-application Tue, 05 Apr 2016 13:25:47 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1441 Defining a w3wp deadlock detected issue:

Sometimes we might see that the website hosted on IIS became unresponsive for some time and we see any of the below event log entry

1) ISAPI 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.

2) ISAPI’C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll’ reported itself as unhealthy for the following reason: ‘Deadlock detected’”

3) Description: ISAPI 'C:\Windows\system32\inetsrv\asp.dll' reported itself as unhealthy for the following reason: 'ASP unhealthy because 100% of executing requests are hung and 0% of the request queue is full.'

When a Web application is busy, there may be instances when the maximum number of threads has been spawned and some of the threads are unresponsive, resulting in degraded performance. IIS has the ability to solve the problem of unresponsive threads by recycling the worker process that hosts that particular instance of the ISAPI. When threads are unresponsive the appropriate ISAPI i.e ASP.dll or aspnet_isapi.dll calls the ISAPI server support function HSE_REQ_REPORT_UNHEALTHY, and the WAS (in IIS 7) or WWW service(in IIS 6) will recycle the worker process and make an entry in the event log.

https://msdn.microsoft.com/en-us/library/ms524715(VS.90).aspx

So when we see a deadlock there might not be an actual deadlock for any resource and it might just be that all the threads are busy doing some task.

Steps to Create Debug Diag Rule:

1. We will use Debug Diagnostic 2.0 update 2 version to troubleshoot this issue further. Please install the Debug Diagnostic 2.0 update 2 tool from https://www.microsoft.com/en-us/download/details.aspx?id=49924 (Please un-install all other versions of Debug Diagnostic tool before installing the latest version)

2. Before proceeding with the rule creation we need to download the symbols needed for the automated rule creation. Take the below steps to download the symbols for your w3wp process.

a. Download PDBDownloader.exe from https://github.com/rajkumar-rangaraj/PDB-Downloader/releasesb. Run the PDBDownloader.exe and click on open files

c. If it is a IIS 6 machine, Navigate to the path C:\Windows\System32\inetsrv\ and select w3isapi.dll. Click on Start

d. If it is a IIS 7 or higher machine, Navigate to the path C:\Windows\System32\inetsrv\ and select isapi.dll. Click on Start

e. If it is a 32 bit application on a 64 bit IIS 6 machine, Navigate to the path C:\Windows\SysWow64\inetsrv\ and select w3isapi.dll. Click on Start

f. If it is a 32 bit application on a 64 bit IIS 7 or higher machine, Navigate to the path C:\Windows\System32\inetsrv\ and select isapi.dll. Click on Start

g. The tool will download the public symbols of w3isapi.dll or isapi.dll to C:\Symbols folder and we are good to proceed with the rule creation

 

Debug Diag 2.0 Update 2 uses the symbol folder as C:\Symbols. Debug Diag 1.2 or Debug Diag 2.0 Update 1 uses the symbol folder as C:\symcache. If you have Debug Diag 1.2 or Debug Diag 2.0 Update 1 then change the file location in PDBDownloader.exe to C:\symcache. If folder does not exist please create it.

 

Note: The executable requires internet connection to download the symbols. If you don’t have internet connection on the server, then copy the C:\Windows\System32\inetsrv\w3isapi.dll or C:\Windows\System32\inetsrv\isapi.dll to the machine which has internet connection and run the tool over there. Once you have the symbols downloaded, copy PDB file to the server’s symbol folder. In case of Debug Diag 1.2 or Debug Diag 2.0 Update 1 copy it to C:\Symcache, else use C:\Symbols

 

3. Create a Crash Rule in Debug Diagnostic 2.0 with the following steps:

a. Open Debug Diag (Start -> Programs -> Debug Diagnostic Tool 2.0 Collection)

b. Select "Crash" and click Next

c. Choose the option “A specific IIS application pool” and click Next and choose the application pool that is crashing from the list and click Next. (Note: The Application pool list may be empty if the IIS 6 Metabase Compatibility is not installed. In such a case you can always type the name of the application pool and click Next)

d. Click Next in Advanced Configuration (Optional), click on Breakpoints and then click on Add Breakpoint

e. If it is a IIS 7 or higher machine then add isapi!SSFReportUnhealthy and change the Action Type to Full User Dump and Action Limit to 5 and click on Ok.

(OR)

If it is a IIS 6 machine then Add w3isapi!SSFReportUnhealthy and change the Action Type to Full User Dump and Action Limit to 5 and click on Ok.

f. Click on Save and Close

g. Click Next for "Rule Name". The "User dump Location" can be changed here.

h. Select "Activate the rule now" and click Finish

4. Notice the Status is Active. The User dump Count will increase each time a dump file is created.

5. Wait for the issue to happen.

Once the issue occurs

1. The user dump count field in the Crash Rule will increment whenever the tool generates a dump. The dump will be generated in the User Dump Path

2. You can also analyze the Dump by running Debug Diag Analysis Tool and clicking Add Data Files. When the .dmp is added, select the Crash/Hang Analyzers script and click Start Analysis. When finished, a report (.mht) will be created in C:\Program Files\DebugDiag\Reports and displayed in Internet Explorer with the results and recommendations. If using custom DLL’s, the Symbol path (Tools menu -> Options and Settings -> Symbol Search Path) to the custom PDB files can be added.

 

Hope this helps Smile

]]> Session Loss due to Application Domain Recycle-Advanced https://docs.microsoft.com/archive/blogs/webtopics/session-loss-due-to-application-domain-recycle-advanced Tue, 05 Apr 2016 12:08:03 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1421 In the previous blog we had discussed regarding the basics of application domain recycling and how to identify if the session loss is because of app domain recycling. Over here in the below article we will discuss further on the data that we can capture to find out the root cause of application domain recycle and also how to debug the data that we have collected.

https://blogs.msdn.microsoft.com/chiranth/2015/12/14/session-loss-due-to-application-domain-recycle-advanced/

Hope this helps Smile

]]> Session Loss due to Application Domain recycle- Basics https://docs.microsoft.com/archive/blogs/webtopics/session-loss-due-to-application-domain-recycle-basics Tue, 05 Apr 2016 12:05:40 GMT https://blogs.msdn.microsoft.com/webtopics/?p=1403 One of the very tricky issues i have seen in the recent past are session loss issues due to application domain recycle. The issue becomes tricky in terms of data collection and how to further look into it. In the below link i have provided more information on what is application domain recycle and how you can determine if the session loss is happening because of application domain recycling. Also i have discussed the common reasons for application domain recyling and the precautionary measures to be taken so that we don’t end up facing app domain recycling issues.

https://blogs.msdn.microsoft.com/chiranth/2015/12/14/session-loss-due-to-application-domain-recycle-basics/

Hope this helps Smile

]]>