Click OK to return to the Properties dialog box. In the Select Users dialog box, change 'From this location', if necessary, to the location of the ArcGIS Web services account, and type the account in the lower box (or browse to it with the Advanced button).In the Security dialog box, click Add.In the Properties dialog box, click the Security tab. Right-click C:\Windows\Temp and click Properties.Open Windows Explorer and navigate to the C:\Windows\Temp directory.Grant modify permissions to the ArcGISWebServices user for the C:\Windows\Temp directory.NET command prompt by typing 'exit' and pressing the Enter key. Type the following command at the prompt, substituting the ArcGIS Web services account name as appropriate:.NET Framework SDK v2.0 > SDK Command Prompt. NET command prompt with Start > (All) Programs > Microsoft. Grant the ArcGIS Web services user account permissions to the IIS metabase.Add or modify the userName and password attributes inside the processModel element as follows: Locate the section shown below (found below the element: ). Back up and open, in Visual Studio or a text editor, the following file: C:\WINDOWS\Microsoft.NET\Framework\v7\CONFIG\nfig.Modify this account name as appropriate for the system being used. The following instructions assume that the ArcGIS Web services account is called ArcGISWebServices (the default specified in the ArcGIS Server post installation utility). Applications and services can still be configured to run as a specific user by setting impersonation in their web.config files. NET Web applications using default impersonation running on the server are running as the ArcGIS Web services user. It is important to realize that all other. The steps below outline how to configure the ASP.NET worker process to run with the identity of the ArcGIS Web services user and how to disable per request impersonation for the ArcGIS Server services and REST Web services. The burden on the lsass.exe process can be alleviated by altering the configuration of the aspnet worker process and the Web services or applications that are under heavy load. When a Web service or application that is impersonating is under heavy load (more than 25 simultaneous connections per second) for extended periods of time, the per request authentication operations begin to severely affect the memory and processing footprint of the lsass.exe process. Under normal load conditions, this authentication operation is insignificant. By default, these components impersonate the ArcGIS Web services account.Įvery time a Web service or application that uses impersonation handles a request, the underlying ASP.NET worker process must use the Local Security Authority Subsystem Service process (lsass.exe) to authenticate. The components of ArcGIS Server that handle Internet service requests, such as and are, themselves, Web services. By default, this is accomplished by configuring a Web service or application to impersonate with a specified identity, when handled by the aspnet worker process. NET must run as users in the AGSUSERS and/or AGSADMIN operating system group. Web applications and services that work with ArcGIS Server. This can cause system performance degradation and, in extreme cases, such as a heavy load over periods of 12 hours or more, machine shutdown. NET Web applications and Internet services are under heavy load (more than 25 concurrent requests per second), the Local Security Authority Subsystem Service (lsass.exe) system process can become overtaxed. Please feel free to contact our support team if you have any questions or require further assistance.Problem: On Windows XP, the Local Security Authority Subsystem Service (lsass.exe) grows in CPU usage and memory utilization under heavy load Description Microsoft has a hotfix for this issue that can be downloaded here: The main symptom is a decrease in performance when an application is running for a long time. The high memory usage is attributed to a Microsoft memory leak “defect” in Windows Service Pack 3 and is further explained in Microsoft’s Knowledge Base. After some investigation, we found that this issue may occur on Windows XP machines running Microsoft’s Service Pack 3 and usually takes place during extended remote sessions. Users on either end of the remote session may potentially find that the Techinline application uses an unusually large amount of computer memory. Our support team recently discovered that Techinline may in some cases be effected by a Microsoft memory leak issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |