This workaround is intended for connector versions bellow 7.0.5. In this section, you can replace the application name of RosettaStoneDaemon for the process you want to delay.Ĭaution: Connector version 7.0.5 and onward already implement a solution for this bug. Note: Rosetta Stone = RosettaStoneDaemon. Execute this command: sc.exe config RosettaStoneDaemon start= delayed-auto This configuration prevents the RosettaStoneDaemon service starts before the AMP connector.įor PowerShell/CMD, the next commands can be used. Tomcat, or web hosting consoles such as Plesk, CPanel, Helm, etc.) How to Test. Click on the dropdown menu and select Automatic (Delayed Start). installation of Java packages or similar web site components (i.e. The Startup type is configured as Automatic by default which means RossettaStoneDaemon starts automatically in the boot process. Right-click on RosettaStoneDaemon and click on Properties. Open services.msc, as shown in the image. This application is detected by SPP because it touches the lsass.exe process for authentication purposes. The Rosetta Stone application is taken as an example in this document. The workaround of this bug is to delay the Windows service that starts before the AMP service. When a Windows Service starts before the AMP connector (In versions below the 7.0.5) System Process exclusions are not honored and even if a process is excluded, the SPP engine stops the process and an event is created in the AMP Console, as shown in the image.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |