v20 Logfile Does Not Exist or Is Not Being Written To

If there are any problems during v20 installation and usage, it's always helpful to review the logfile.  If you receive a message that the logfile does not exist (using Shift+F9) or you view the logfile and nothing has been written into it (logfile has a 0 KB size), then you need to configure the logfile and activate the ability for entries to be made. 

To do this, follow the below steps:

1.  Navigate to the v20 program files (standard installation location is c:\inetpub\ungerboeck).

2.  Locate the EBMSlog.log file.  If the EBMSlog.log file does not exist, follow the below steps:

• Create a new text document by right-clicking in the folder where the v20 program files are located and selecting New -> Text Document.
• Rename the document by selecting the file, right-clicking and selecting Rename.  Update the name to EBMSlog.log.  A message appears confirming the file extension change.  Click Yes.

3.  Open IIS.

4.  In the Application Pools, verify Network Service is listed as the Application Pool Identity.

5.  Navigate back to the v20 program files from step 1.

6.  Select the program files folder, right-click and select Properties. The Properties screen opens.

7.  Select the Security tab.

8.  Verify that a Network Service Entry (the Application Pool Identity) exists.  If it does not, follow the below steps to add the entry:

• Click the Edit button. The Permissions screen opens.
• Click the Add button.
• Enter Network Service into the the text field.
• Click the Check Names button. NETWORK SERVICE populates.
• Click OK.

9.  In the Permissions section of the Permissions screen, check the Allow check box for the Modify option.

10.  Click OK.