Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
ServletExec Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 60
Product ServletExec
Category Admin Username and Password, Administration, Miscellaneous, Registration
Question I used the ServletExec Admin UI to make some configurations but after I restart ServletExec, the settings I entered are gone. What is wrong? Is this normal behavior?

This FAQ only applies to SE ISAPI. If you are using SE AS this FAQ does NOT apply.

It is not considered normal behavior for ServletExec to forget any of its configuration data (such as License Key, or Session settings, or Configured Servlet settings, etc...) after a restart.
When you enter a setting via the ServletExec Admin UI, and then click the appropriate Submit button, ServletExec attempts to write that information into the appropriate configuration file. For example, when you enter your license key and then click the Register button, SE tries to write that info to:
...\ServletExec Data\servletexec.xml (for SE 5.0 and newer)
...\ServletExec Data\ (for SE 4.x and older)
so that the next time ServletExec starts up it can read that info back in from the file and use it. If your instance of ServletExec is forgetting its settings after a restart, most likely this is a file permissions issue in which ServletExec does not have access to write to the appropriate file. Another indication of this sort of problem would be if you were to enter your license key (or any other configuration change via the ServletExec Admin UI) and then click the appropriate submit button, and saw in your browser a message sort of like this:

! ERROR - Settings Save failed. Check ServletExec.log for error messages.

When a problem like this occurs most likely you will find IOExceptions in ServletExec.log, and "access is denied" messages. You would also see these messages in DBMON if running ISAPI or NSAPI on windows. This normally happens when ServletExec doesn't have read/write access to the ServletExec Data directory and all of its subdirectories and subcontents. Make sure that ServletExec has permission to read/write to this directory and all of its subdirectories and subcontents. This problem commonly occurs with SE ISAPI on Windows due to the fact that SE ISAPI runs inside the IIS process and the IIS process runs as different users at different times.

A very quick way to test if this is in fact a file permissions problem is to give the group named Everyone, Full Control over the ServletExec ISAPI directory and all of its subdirectories and subcontents.
Here is how you do that:
  1. Right click on the appropriate folder
  2. select Properties, and choose the Security tab
  3. Select the group named 'Everyone' (add that group if it is not listed) and then give it Full Control permission (check the checkbox labeled "Full Control")
  4. Click the 'Apply' button
  5. Click the 'Advanced...' button
  6. Select the group named 'Everyone'
  7. Check the radio button that is labeled "Reset permissions on all child objects and enable propagation of inheritable permissions."
  8. Click the 'Apply' button so that the new permission settings will propagate downward

If this solves the problem then you will know if was a file permissions issue. At that time you may go back and use more fine-grained security settings if you wish. With IIS you would need to make sure that the following user accounts have read/write access to this directory and all of its subdirectories and subcontents:
  • Beginning with IIS 6 on Windows 2003:
    • The user specified as the application pool identity for ServletExec. Typically this is the user named "Network Service". See SE FAQ #7 (step #6) for more information about which user we're talking about)
    • The ServletExec Admin User Account (SE 4.x and older only)
  • With versions of IIS, prior to IIS 6:
    • SYSTEM
    • IUSR_<server name>
    • The ServletExec Admin User Account (SE 4.x and older only)

Section 2.7 of the ServletExec Installation Guides for SE 4.1, 4.1.1, 4.2, & 5.0, all discuss this in greater detail.

If this does not work then try setting these permissions on the top level JVM folder and all of its subfolders and subcontents.

company media information terms of use privacy policy contact us