Zum Hauptinhalt gehen

REST Manager keeps logging out

Kommentare

8 Kommentare

  • Stefan Schweigert

    Hello Berend,

    This issue sounds related to Application Services misbehaving; is there any information provided in the REST or Manager log files?

    By any chance, is your Essentials instance installed using load balacing? 

    Thanks,  Stefan.

    0
  • Berend Veldkamp

    The REST logfiles did show some file permission issues, but when I corrected these, the issue is still there, and nothing is added to the logfile (level is set to DEBUG).

     

    The IIS log has a warning that occurs every time I get logged out:

    A process serving application pool 'EssentialsAdministrationAppPool4' suffered a fatal communication error with the Windows Process Activation Service. The process id was '5588'. The data field contains the error number.

    Details:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="32768">5011</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-05-21T08:01:24.000000000Z" /> <EventRecordID>5381</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>NLBLTA06.grontmij.net</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">EssentialsAdministrationAppPool4</Data> <Data Name="ProcessID">4476</Data> <Binary>6D000780</Binary> </EventData> </Event>

     

    This seems to be a quite common issue, but I haven't found a solution yet. I changed the recycling settings from every 1740 minutes to every midnight, set Enable 32-Bit applications to True, and Maximum failures to 100.

     

    0
  • Berend Veldkamp

    I overlooked permissions on the SiteCache folder. There wasn't anything in the logs, but Process Monitor came up with it.

    Now that I've added write permission to NetworkService and IIS_IUSRS things seem to work properly.

     

    This made me think: What are the implications when running the application pool as NetworkService as opposed to EssentialsAdmin? Would it be an idea if the post install let me choose an identity, and then set the correct permissions?

    0
  • Permanently deleted user

    Have you considered using the default 2008 R2 user to ApplicationPoolIdentity? This of course means how ACLs are set changes too. A great blog entry on this from:

    http://blogs.iis.net/webdevelopertips/archive/2009/10/02/tip-98-did-you-know-the-default-application-pool-identity-in-iis-7-5-windows-7-changed-from-networkservice-to-apppoolidentity.aspx

    Shawn.

    0
  • Berend Veldkamp

    Yes, that would even be better. In this case it's 'only' a development server, so it's not very important.

    Is there a fundamental difference between using the ApplicationpoolIdentity or EssentialsAdmin?

    0
  • Permanently deleted user

    Latitude creates the EssentialsUser account, which is a standard local windows user account on the machine which the product was installed. The other is an account setup by Microsoft and already configured into the core of Windows, so should be more "stable" in nonstandard windows configurations or where problems are popping up.

    0
  • James Brink

    I'm getting logged off also. I didn't have this problem till we upgraded to Essentials 3.14 and Silverlight 1.9. Example of the logout problem: I maded modifications to a layer in one Chrome window in Manager. I then refreshed the viewer to see the changes in another Chrome Window. I then went back to Manager and it was logged out. This has happened many times, the logout  doesn't happen everytime I move off of the Manager window.

    Jimmy Brink

    0
  • Berend Veldkamp

    Sounds like the same problem I had. The easiest way to debug these kind of problems IMO is to use Process Monitor, you can download it (http://technet.microsoft.com/en-us/sysinternals/bb795533.aspx) here .

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.