https://docs.microsoft.com/archive/blogs/mayurpatankar/feed.xml Thu, 05 Apr 2018 07:45:57 GMT en-US hourly 1 https://docs.microsoft.com/archive/blogs/mayurpatankar/error-during-serialization-or-deserialization-using-the-json-javascriptserializer-the-length-of-the-string-exceeds-the-value-set-on-the-maxjsonlength-property Thu, 05 Apr 2018 12:44:05 GMT https://blogs.msdn.microsoft.com/mayurpatankar/?p=305 maxJsonLength : The maxJsonLength Gets or sets the maximum length that is accepted by the JavaScriptSerializer object for JavaScript Object Notation (JSON) strings. Syntax : [ConfigurationPropertyAttribute("maxJsonLength", DefaultValue = 102400)] public int MaxJsonLength { get; set; }   Property Value Type: System.Int32 An integer that represents the maximum length for JSON strings. The default is 102400 characters.   The value of the MaxJsonLength property applies only to the internal JavaScriptSerializer instance that is used by the asynchronous communication layer to  invoke Web services methods. Basically, the "internal" JavaScriptSerializer respects the value of maxJsonLength when called from a web method. Direct use of a JavaScriptSerializer (or use via an MVC action-method/Controller) does not respect the maxJsonLength property, at least not from the systemWebExtensions.scripting.webServices.jsonSerialization section which you define in the web.config file. You will get the below error if you exceed the above default value(DefaultValue = 102400) while serializing the JSON object and your Json string is too big Error(s): {"Message":"Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.","StackTrace":"   at System.Web.Script.Serialization.JavaScriptSerializer.Serialize(Object obj, StringBuilder output, SerializationFormat serializationFormat)\r\n   at System.Web.Script.Serialization.JavaScriptSerializer.Serialize(Object obj, SerializationFormat serializationFormat)\r\n   at System.Web.Script.Services.RestHandler.InvokeMethod(HttpContext context, WebServiceMethodData methodData, IDictionary`2 rawParams)\r\n   at System.Web.Script.Services.RestHandler.ExecuteWebServiceCall(HttpContext context, WebServiceMethodData methodData)","ExceptionType":"System.InvalidOperationException"}   Above error  “The length of the string exceeds the value set on the maxJsonLength property”  itself suggest that you have to increase the value for maxJsonLength property   Now the  question in your mind would be how to define the “safe” number or how to find out the “safe” number for the value of the maxJsonLength property so we it will not fail in the future if the web service is accessing more data than the defined value(or default value) for the maxJsonLength  property. The answer to the above question would be don’t pull huge data from the web service on a single request instead of that you can chunk the data and can access it , so it will not exceed the value you have set for the maxJsonLength. Also , if you are pulling huge records on a single request it will definitely going to hamper the performance of your application . In order to get the Safe number for the maxJsonLenght you have to perform some rigorous testing on your application and determine the same. There is no such default value which will be same for any amount of data or records you are pulling for the database which is invoked from the Web Service method call. If you are exceeding the default value for this property you have to update it in the web.config file as below :   <configuration>    <system.web.extensions>          <scripting>                     <webServices>                 <jsonSerialization maxJsonLength="....">                      </jsonSerialization>             </webServices>         </scripting>      </system.web.extensions> </configuration>   Or else you also can set the maxJsonLength in your controller like this JavaScriptSerializer jss = new JavaScriptSerializer(); jss.MaxJsonLength = Int32.MaxValue;   Hope this helps!!!! J]]> https://docs.microsoft.com/archive/blogs/mayurpatankar/iis-static-compression-the-directory-specified-for-caching-compressed-content-is-invalid-static-compression-is-disabled-warnings-in-event-viewer2264 Fri, 16 Feb 2018 07:55:56 GMT https://blogs.msdn.microsoft.com/mayurpatankar/?p=295 <httpCompression> element specifies the HTTP compression settings for Internet Information Services (IIS) 7. HTTP compression can provide faster transmission times between IIS and client browsers that can accept compressed files. More about httpcompression When a user requests for a page, the IIS worker process creates a folder specific to the application pool on the configured IIS Cache directory (One time i.e. under C:\inetpub\temp\IIS Temporary Compressed Files\appPoolName). The folder is getting created but we are getting a warning on the Eventvwr for IIS-W3SVC-WP source. “The directory specified for caching compressed content <folder location> is invalid. Static compression is disabled. Log Name:     Application Source:       Microsoft-Windows-IIS-W3SVC-WP Date:         9/1/2017 3:07:58 PM Event ID:     2264 Task Category: None Level:         Warning Keywords:     Classic User:         N/A Computer: Description: The directory specified for caching compressed content C:\inetpub\temp\IIS Temporary Compressed Files\appPoolName is invalid. Static compression is being disabled. Event Xml: <Event xmlns="https://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" /> <EventID Qualifiers="32768">2264</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-09-01T22:07:58.000000000Z" /> <EventRecordID>1063103</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer> </Computer> <Security /> </System> <EventData> <Data Name="Directory">C:\inetpub\temp\IIS Temporary Compressed Files\appPoolName</Data> <Binary>05000000</Binary> </EventData> </Event> Whenever we delete the subfolders under ' C:\inetpub\temp\IIS Temporary Compressed Files', the folder recreates with 'IUSRS' as the owner and we were not getting these warning logged again . But after sometime if we delete the app pool folder and  recycled the application pool the same warnings were getting logged on the event viewer for the first request . Before troubleshooting this issue , make sure you have checked the below things :

• Ensured that static compression is enabled on the IIS configuration
• Provided the application pool service account/ IIS_IUSRS  required access on the IIS Cache directory
• Do not change the Default location of this directory

In order to troubleshoot this issue further we ran the procmon and saw who is owning the compression folder

• We found that the compression folder is being created (and owned by) IUSR
• The compression folder must be owned by the AppPool Identity.
• IUSR is the default identity used by IIS when 'Anonymous Authentication' is used

To resolve this issue we followed the below steps : Right click 'Anonymous Authentication' in IIS -> Set to 'AppPool Identity' -> Delete compression folder -> restart IIS website -> When new compression folder is created it will be owned  by the AppPool identity and no Events 2264 will occur. Note: The new owner will be 'Administrators' if the AppPool Identity is in the local administrators group.   Hope this helps !!!  😊  ]]> https://docs.microsoft.com/archive/blogs/mayurpatankar/sha-256-self-signed-certificate-for-windows-server-2012-r2 Fri, 01 Sep 2017 23:00:29 GMT https://blogs.msdn.microsoft.com/mayurpatankar/?p=45 Signature hash algorithm as sha1 . The SHA-1 hashing algorithm for the Microsoft Root Certificate Program is being decommissioned. https://blogs.msdn.microsoft.com/spses/2014/10/21/sha-1-decommissioning/   If you want your self-signed certificate should use the sha256 Signature hash algorithm, we have to generate the certificate from the mmc console   You can follow below steps to create and use a Self-Signed Certificate with the Signature hash algorithm as sha256. 1.Open the mmc console >> go to Run >>>type mmc >>>OK 2. You will get the below Window (mmc console). Click on Add/Remove Snap-in 3. Select Certificates >> Add 4. Select Computer Account and Click on Next   5.Click on Finish 6. The Certificates will be added in your snap-in   7. Expand Certificates (Local Computer) >>>Personal >>>>>Certificates >>>>>All Tasks>>>>>Advanced Operations>>>>>Create Custom Request   8. Click on Next     9.Select Proceed without enrollment policy>>>>>>>Next   10. Click on Next   11.Click on Details >>>>>Properties >>>>Next     12.Add the Friendly for your certificate as per your choice     13. Click on Subject >>>>>>Subject Name >>>>Type >>>>>>>Select Common Name (Common Name should be your host name with which you are browsing your site) >>>Add  Alternative Name >>>>Type >>>>DNS>>>>>Add your DNS (domain name here)>>>>Add     14. Click on Extensions tab>>>>>>>>>>>>>>Extended Key Usage (application policies)     15.Click Basic Constraints >>>>>>>Select Enable this extension   16. Go to Private Key tab>>>>>>>>>>>>>>>>Key Options >>>>>>>>>>>>>Select Make private key exportable   17. Go to Private Key tab>>>>>>>>Select Hash Algorithm >>>>>>>>>>>Hash Algorithm >>>>>>>>>>>>>>>>>sha256(Here you will select the Signature hash algorithm )   18. Click on Apply >>>Ok     19. Click Next   20. Click on Browse and give the certificate with CertName.cer and click on Finish     21. Click on Certificate Enrollment Requests >>>>>>>Right click on Certificates >>>>>>>>>>All Tasks >>>>>>>>>>Import   22. Click on Next   23. Specify the file name and the location     24. Click on Next   25. Click on Finish 26. Click on OK   27. You will see your certificate here under Certificate Enrollment Requests >>>>>>> Certificates     28. Double click on the certificate >>go to Details >>>>Click on Copy to File >>>>>>>Next >>>>>>>>Select the Format you want to use >>>give the file name and the import it to the desktop>>>>>>Finish   29. Import the certificate in Personal Store   Now, check the Certificate go to Details tab check for the Signature hash algorithm >>>>it will be sha256   Import the Certificate to the IIS and add the http binding for the site select the cert.   You have to add this certificate on every client machine from where you want to access the site. On the Client Machines: Run >>>>>mmc >>>>>file>>>>>>Add/Remove Snap in >>> add the Certificates >>>>>select Computer Account >>>>import the certificate under Trusted Root Certification Authorities   Hope this helps !!!!!..]]>