Hello Lee,

This is probably indeed a permission problem. Your configuration file looks file. It may be that when you don't run the service on your development machine, that the service/user doesn't have the required permissions to open/write the log file.

You can check for such errors by registering an event handler to the SmartInspect Error event as explained in the SmartInspect manual (press F1 in the Console, then go Working with SmartInspect | Library Error Handling).

It basically works as follows:

public class ErrorHandling
{
   public static void EventHandler(object sender, ErrorEventArgs args)
   {
      System.Console.WriteLine(args.Exception);
   }

   public static void Main(string[] args)
   {
      // Register our event handler for the error event.
      SiAuto.Si.Error += new ErrorEventHandler(EventHandler);

      // And force a connection error
      SiAuto.Si.Connections = @"file(filename=c:\)";
      SiAuto.Si.Enabled = true;
   }
}

It is not recommended to use SmartInspect in the error event, so it's best to log an error with a third-party logging mechanism. In the example, I simply write the message with System.Console, but in a service you could use the Windows event log (with the System.Diagnostics.EventLog class). This should help you find the issue/permission problem. Please let me know in case you have any further questions.

Regards,
Tobias