Merge pull request #59 from telerik/new-kb-login-issues-telerik-website-1f33a09b99524d46b6af3495e375347f

Added new kb article login-issues-telerik-website

Author: tsvetkoe

docs/knowledge-base/getting-out-of-memory-exception-errors.md

@@ -3,27 +3,27 @@ title: Getting Out of Memory Exception Errors
 page_title: System Out of Memory Exception Errors
 description: Getting Out of Memory Exception (OutOfMemory or System.OutOfMemoryException) Errors when scheduling tests to run on remote machine. Remote test list execution is failing because of OutOfMemory exceptions. Fix OutOfMemory Exception OOM exception. Open results crashes with System.OutOfMemory.
 previous_url: /user-guide/knowledge-base/oom.aspx
-position: 1
+position: 20
 ---
-#Dealing with OutOfMemoryException Errors#
+# Dealing with `OutOfMemoryException` Errors
 
-##Problem##
+## Problem
 
 When working with very large Test Studio test projects (350+ tests) or very large result sets you may get out of memory errors. Test Studio does not have any built-in hard limits on project size or results size. Naturally the larger the project or the larger the result set the more memory it will require. Test Studio, being a 32-bit Windows application, has an address space limitation of 2GB put upon it by the OS, no matter how much physical memory you actually have.
 
 When a Windows application asks the OS for a block of memory, Windows will attempt to satisfy that memory request with a contiguous block of memory. If you ask for a 40MB block of memory, it means a single 40MB block of memory (not a piece from here and a piece from there). If Windows cannot find a contiguous block of memory large enough to satisfy the request and make it fit within the 2GB address space for the application, i.e. fit along with all the other memory the application is already using, you will get an OutOfMemoryException error from the OS and the application usually will be terminated by the OS.
 
-##Solution##
+## Solution
 
-###Option 1###
+### Option 1 
 
 The most obvious option is to break up your test project or your tests into multiple smaller pieces. This way the memory being used will not be as great. Our experience shows that you will start to get out of memory errors with projects larger than about 350 tests total or with tests that have over 800 steps in them.
 
-###Option 2###
+### Option 2
 
 Another option that sometimes helps is to use a 64-bit version of Windows. This version of Windows can handle more physical memory which allows it to better manage the memory it has and may more easily be able to satisfy requests for large blocks of memory.
 
-###Option 3###
+### Option 3
 
 This last option is more experimental, but has been shown to work in a few cases. There is a flag called "LARGEADDRESSAWARE" that can be turned on for 32-bit executables like Test Studio. When this flag is set Windows will let the application use 3GB of address space instead of 2GB of address space. This flag only works when you're using a 64-bit version of Windows. It also requires Visual Studio to be installed before you can set this flag. To turn on this flag follow these 3 steps:
 

docs/knowledge-base/login-issues-telerik-website.md

@@ -0,0 +1,40 @@
+---
+title: Troubleshooting Login Issues on Telerik Website
+description: Users experiencing difficulties signing into their Telerik accounts can follow these steps to troubleshoot the common causes.
+type: troubleshooting
+page_title: How to Resolve Login Problems on Telerik.com
+slug: login-issues-telerik-website
+tags: progress, telerik, test studio, login, troubleshooting
+res_type: kb
+ticketid: 1661389
+position: 19
+---
+
+## Description
+
+When attempting to sign into the Telerik website, several errors may appear in the browser console. The issue persists across different browsers and devices. Clearing the browser's cache or using incognito mode might temporarily allow for successful login, but the problem reoccurs.
+
+## Cause
+
+This issue can arise from various browser-related problems including outdated browser versions, stored cache and cookies, disabled JavaScript or cookies, active browser extensions, or network restrictions.
+
+## Solution
+
+To troubleshoot and potentially resolve login issues on the Telerik website, follow these steps:
+
+1. Ensure the used browser is up-to-date. Check the browser's official website for information on the latest version and update if necessary.
+2. Clear the browser's cache and cookies. This step removes saved website data that might be causing the issue.
+3. Disable all browser extensions including Test Studio Extension. Extensions can interfere with website functionality, including login processes.
+4. Confirm that JavaScript is enabled in the browser settings. JavaScript is essential for many website interactions.
+5. Ensure that cookies are enabled. Cookies are necessary for maintaining a login session.
+6. Try accessing the website again using incognito or private browsing mode. This mode uses a fresh session without saved cookies or cache.
+7. Test the login process with a different browser or device to rule out browser-specific issues.
+8. Attempt to access the website from a different network. Some networks may have restrictions that impact website functionality.
+
+
+
+## See Also
+
+- [Test Studio Documentation](https://docs.telerik.com/teststudio/)
+- [How to Enable JavaScript in Your Browser](https://www.enable-javascript.com/)
+- [How to Clear Cache and Cookies in Major Browsers](https://www.pcworld.com/article/242939/how-to-delete-cookies.html)