SolarWinds Log Forwarder will NOT stay started on w2k8

Hello everyone.

I am new to the site and I am not sure if this is post in the correct place. If not, please help move me to the correct area, thanks.

In my environment, we run W2K8 R2 SP1 servers. We installed SolarWinds Log Forwarder on all of our servers, but somehow, the SolarWinds Log Forwarder will NOT stay started on couple of our servers. It just said it has nothing to do and stopped the service. We have about 15 servers running the OS patch level, but 2 refused to work correctly. I have tried re-install, repair and nothing works. Can someone please help? Thank you in advance for your assistant.

Sincerely,

Mike

Find more posts tagged with

Accepted answers

All comments

byrona

While I can't help you get the SolarWinds Event Log Forwarder running, I can suggest a different application that does almost exactly the same thing. We run a lot of W2K8 R2 as well and we have found NTsyslog to be a much lighter application to accomplish the same goal. Just download and run the executable and you will have it up and running in seconds. You can find a copy of it HERE.

Hope this helps!

FormerMember

Hi Byrona, thank you for the information. I will take a look, but I am still hoping someone has a fix for this. ;-)

dwiggy

I am running into the same problem on 2k8 R2 x64. After extensive trouble shooting I have been able to produce two errors.

1. When running the logforwarderclient I receive this error:

"Could not initialize license manager", and "The default algorithm could not be instantiated."

2. After loading License Manager I am showing that the log forwarder is not activated. The instructions to activate the product are not correct. Additionally, the log forwarder is supposed to be free and unlicensed, according to the sales representitive.

Additional support for this product would be appreciated.

danielleh

Hi Mike--

I moved this to the NPM forum to get better visibility.

FormerMember

Thanks Danielle

andy.p

Mike

I know this post is getting old but as I have just come accross the same problem and eventually found a solution I thought I would offer it to the wider group.

I had the exact same error as dwiggy states. The problem for me was caused by a local security policy on my server:

Security Settings/Local Policies/Security Options/System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.

This was set to enabled and seemed to cause the error. When I disabled it Log Manager worked fine. Obviously you may not be able to just change this depending on your organisations security policy.

Hope this helps anyone else who runs into it.