The SolarWinds NetFlow Service service hung on starting

Orion 9.5 SP4

NetFlow Traffic Analyzer 3.5 SP2

(and Network Configuration Manager 5.5.1)

running on a virtual Windows Server 2003 R2 SP2 server.

I'm getting the error "NetFlow Service service hung on starting" on bootup. However the service does start a minute of two later (its set to automatically restart on error).

It looks like its trying to start to soon (for example before the Network Connections service starts, which seems foolish for something that looks at network traffic!).

I've noticed a couple of other posts on this subject but they didn't have answers that worked for me

Any thoughts?

Thanks

Andrew

Find more posts tagged with

Accepted answers

All comments

MarieB

Hi Andrew--

If you don't get an answer and the problem continues, consider opening a support ticket.

Donald_Francis

If you do not want to go through support you could always run the config wizard and reinstall the netflow service.

Hi,

we've already investigated this problem, and we found out that service is ok and it doesn't crush. We are just too slow in same cases and start up operation is not finished on time. That's why system notify you about start up delay. Service has only limited time to finish start up sequence during system boot up, otherwise system display warning. On start up we check SQL connection, and some other things, which can caused this delay.

Are you sure that the service crushed? Can you see message in resource Last 25 Messages about it?

Regards

MarieB

Awesome response guys, thanks!!

AndrewShine

I can't see any message in the Events resource.

I didn't say the service crashes, merely that (according to the system event log) it hangs. I do see an event log message about a minute later saying that the service has entered the running state. A such everything works, however after a reboot, I get the annoying popup on the servers console telling me that 'at least one service or driver failed to start etc etc'. This forces me to check the server out since I can't be sure that the popup is in response to the Netflow service having a problem or if there's something additional going wrong.

I'd like to fix the Netflow startup so I that it doesn't generate the error and I get a clean boot up. I'm thinking in terms of modifying the service start order or creating a dependency so that the Netflow doesn't start before everything it depends on is running (which it should have anyway?!) eg: Netflow service should depend on the Network Connections service (?)