Symptom

The plug-in cannot generate/create the plug-in log or cannot update/write to the log or both.

The following actions have occurred in order to isolate the problem to a permission issue:

• A few test requests have been sent to the Web server to start the plug-in logging.
  
  
• Plug-in configuration with IIS web server has been reviewed based on the manual configuration steps documented in the information center.
  
  
• The ISAPI Web Service Extension is set to 'allow' (not 'prohibit' which also prevents the log from being written to).
  
  
• Plug-in was possibly logging but stopped after the last time stamp seen in the log and server administrators recently hardened permission's on the server to protect against vulnerability.
  
  
• The plugin-cfg.xml file can be edited to change the path to the plug-in log to a directory with "everyone" access (for test purposes) and this allows the plug-in to start logging after IIS restart and a few test requests. This test verifies the logging is a permission's issue.
  
  
• Setting IIS to use the IIS5 type Isolation Mode allows plug-in to start logging. This also points to permission's as the issue.