Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Windows Event Log Forwarder - service failed to start on Windows 2003 SP2

Hi,

We have many servers that after installing and configuring Windows Event Log Forwarder the service is not able to start reporting following error message:

Service Control Manager
Event ID: 7000

The SolarWinds Windows Event Syslogger service failed to start due to the following error:
The service did not respond to the start or control request is a timely fashion.

Version of the Orion Windows Event Forwarder: 1.0.2055.28085.

I tried to reinstall the product and / or start the service manually - that did not resolve the issue for all of the servers (Windows 2003 SP2) but only for some.

Please help.

Kris

Find more posts tagged with

Accepted answers

All comments

duelunds

Hi All,

Im am getting this exact same message, windows 2003 ENT, SP2.

I have tried reinstalling the addon a few times and seaching for another solution with no luck.

anyone found a solution to this or is able to help?

duelunds

Ok doing some testing:

Windows 2003 SP2 - no good

Windows 2003 SP1 - installed and running.

Windows 2000 server SP4 - installed and running.

Windows XP SP2 - installed and recieving alerts

There is no port blocking enabled so its no that, i have full admin rights on all services so its not that...

Tested it on several different Windows SP 2 machines and they worked! meaning its down to these few servers... all having similar properties, they are all web servers with SQL installed.

could be somethign using that port already... going to check using the TCP port viewer from microsoft and will update post.

grantsewell

I have this running on several 2003 SP2 machines... no problems. The TCP port conflict sounds like a viable possiblity. Are these boxes 32-bit or x64?

Qwiati

all Windows 2003 SP2 - 32bit

smcdonald

Are you guys running with an Internet proxy?
I had similar issues - the following seemed to work for me to fix the issues -
Add the following to your local hosts file in c:\windows\system32\drivers\etc\hosts

127.0.0.1 wpad
127.0.0.1 CRL.THAWTE.COM

if you're running Windows 2000/2003 run -
"proxycfg -u"
from a CMD prompt to ensure your Internet proxy settings are copied correctly from IE into the WINHTTP proxy settings - the solarwinds forwarder seems to want to check it's .Net certificate or something - doing these changes has made the forwarder work reliably. This was for the older version - I havn't noticed if the newer version still has this issue...

Additionally I noticed on some boxes the service would fail after reboot - these settings helped fix that too - although these days I use the Application monitor to ensure the forwarder service is running on all out boxes... I also would set the service to restart if it fails.

Hope this helps!