CODEWITHSUNDEEP
c#windowswindows-servicesevent-logwindows-7-x64
feenst
feenst

Reputation: 71

Windows Service output not showing up in Event Log

I am trying to follow this walkthrough.

I'm using Visual Studio 2010 Premium.

The only events I see in Server Explorer or in Event Viewer are "Service started successfully." and "Service stopped successfully."

Here is the service code:

namespace MyNewService
{
    public partial class MyNewService : ServiceBase
    {
        public MyNewService()
        {
            InitializeComponent();
            if (!EventLog.SourceExists("MySource"))
            {
                EventLog.CreateEventSource("MySource", "MyNewLog");
            }
            eventLog1.Source = "MySource";
            eventLog1.Log = "MyNewLog";
        }

        protected override void OnStart(string[] args)
        {
            eventLog1.WriteEntry("In OnStart");
        }

        protected override void OnStop()
        {
            eventLog1.WriteEntry("In onStop.");
        }
    }
}

Upvotes: 7

Views: 5254

Answers (3)

FumblesWithCode
FumblesWithCode

Reputation: 441

I had the same issue with Visual Studio 2010 Professional on Win 7 64. My newly compiled service was installed with InstallUtil.exe running as Administrator. It started and stopped correctly. No exceptions but no amount of refreshing the Event Viewer revealed a new event log. Fran71's suggestion worked for me: I closed the Event Viewer and reopened. Voilà, the newly created application log file appeared.

Upvotes: 3

Jordan
Jordan

Reputation: 659

FWIW, I ran into this problem in Win8 and found that Refreshing the Event Viewer did not cause my newly created Event Log to show up, but closing and reopening Event Viewer did. Was driving me insane since no exceptions were being thrown when Creating the Event source or writing a log entry.

Upvotes: 1

ScottBai
ScottBai

Reputation: 1511

Probably a permissions problem. Like the commenter said, try running VStudio or your compiled service as an Administrator.

Also, you can still debug a service - put a thread.Sleep(up to 20 seconds) as your first line (to give yourself time to attach the debugger), then put a break point on the line after that. Then go Tools --> Attach To Process and select your .exe. If you get that done before the end of your Thread.Sleep() then you should break.

Keep in mind that the service must complete the OnStart within IIRC 30 seconds or Windows will think it is not responding and kill your process, so move your code out of the service start if you are going to do much debugging. Just throw a timer in there or something.

To make it easier to debug, consider moving your functionality to a DLL and then keep your service to just enough code to call into your DLL - this will ease unit testing and debugging - but don't forget that lots of things change when you're actually running it as a service.

Upvotes: 0

Related Questions