Windows服务仅在调试模式下运行异常排查求助

Hey there, let's break down why your Windows Service runs flawlessly in debug mode but doesn't even log "Starting it" when installed—even though it shows as "running" in the Services console. These are the most common culprits to investigate:

1. Permission Mismatches (The Top Suspect) #

When debugging, your service runs under your user account (with all your file, network, and resource permissions). But installed services typically default to the Local System account (or a limited service account), which might lack access to:

• The directory you're writing logs to (especially if using relative paths or user-specific folders like Documents)
• Resources your initialization class depends on (databases, network shares, registry keys, etc.)

Quick Checks:

• Switch your service's logon account temporarily to your own user (Services > Right-click your service > Properties > Log On tab) to test if permissions are the issue.
• Use an absolute path for logs (e.g., @"C:\Windows\Temp\MyServiceLogs.txt"—Local System has write access here by default).

2. Uncaught Exceptions in Initialization #

Your initialization class might be throwing a silent exception during startup. In debug mode, Visual Studio catches these errors, but installed services swallow unhandled exceptions in OnStart—Windows marks the service as "running" even though your code stops executing before the log line.

Fix: Wrap your entire OnStart logic in a try-catch block that logs every detail to an absolute path:

protected override void OnStart(string[] args)
{
    try
    {
        // Log immediately to confirm OnStart is firing
        File.AppendAllText(@"C:\Windows\Temp\MyServiceLogs.txt", $"[{DateTime.Now:yyyy-MM-dd HH:mm:ss}] Starting it\n");
        
        // Initialize your class and call core functions
        var initClass = new YourInitializationClass();
        initClass.Setup();
        
        // Execute your three core functions here
    }
    catch (Exception ex)
    {
        // Log full exception (including stack trace!)
        File.AppendAllText(@"C:\Windows\Temp\MyServiceLogs.txt", $"[{DateTime.Now:yyyy-MM-dd HH:mm:ss}] ERROR in OnStart: {ex.ToString()}\n");
        // Optional: Write to Windows Event Log for easier access
        EventLog.WriteEntry("MyServiceName", $"Startup failed: {ex.ToString()}", EventLogEntryType.Error);
    }
}

This will reveal exactly what's breaking before your startup log line runs.

3. Blocking Code in OnStart #

Windows requires the OnStart method to return within ~30 seconds. If your three functions run synchronously and take time, the service might appear to start successfully, but Windows could kill the underlying process or your code might never finish initializing. Debug mode doesn't enforce this timeout strictly.

Fix: Move core logic to a background thread so OnStart can return quickly:

private Thread _workerThread;

protected override void OnStart(string[] args)
{
    try
    {
        File.AppendAllText(@"C:\Windows\Temp\MyServiceLogs.txt", $"[{DateTime.Now}] Starting it\n");
        
        // Spin up a background thread for long-running work
        _workerThread = new Thread(RunCoreLogic);
        _workerThread.IsBackground = true;
        _workerThread.Start();
    }
    catch (Exception ex)
    {
        // Log exception as before
    }
}

private void RunCoreLogic()
{
    // Call initialization class and three core functions here
}

4. Missing Dependencies #

When debugging, Visual Studio copies all required DLLs to your output folder. But when installing the service, you might have forgotten to include dependencies (like third-party libraries or your initialization class's DLL) in the service's installation directory. If the service can't load these files, it fails silently during initialization.

Fix:

• Navigate to your service's installation folder (usually C:\Program Files\<YourService>)
• Verify every referenced DLL (including your initialization class assembly) is present.

5. Relative Path Confusion #

Installed services use C:\Windows\System32 as their default working directory—not your installation folder. If your logs or initialization files use relative paths, the "Starting it" log might be writing to System32 instead of where you expect, making you think it's missing.

Fix: Always use absolute paths for files, logs, or resources in your service.

内容的提问来源于stack exchange，提问作者PyDeveloper