I am currently testing KAV Administration Server Kit 6.0 for my company on an isolated part of my network before rolling it out for the whole company. Immediately after installing the server, things went swimmingly, allowing me access through the console, setting up groups and policies, remote install, the works. Everything was great.

However, I come back from the long weekend to find that at some point the server reset itself. Now, none of the admin consoles can connect, not even the one on the localhost of the server. After doing some digging into a message I ignored at first, it turns out that klserver.exe wasn't running, because the service failed at start up. Checking the Event Viewer, in the logs CSAdminServer threw an error, stating "The service process could not connect to the service controller." That means nothing to me at all.

I assumed maybe I had installed everything incorrectly. So, I wiped everything (the beauty of having a spare server I can do that too) and started from scratch.

Same problem.

Now, it seems the server service will only start if I manually go into Services and start it myself. Hardly something I want to do every time the system reboots. Especially because I'd like to know WHY this is a problem more than anything else.

So, anyone have any ideas? Btw, yes I installed as an admin with rights to add services and the like. And the server is plugged in. But any other bonehead moves that could be causing the problem are more than welcome suggestions.

Do you have more info in Eventlog?

Which OS and DB you are using?

Did you try an another account for this service?

To answer your questions, the Eventlog didn't give me anymore information beyond the user the error occured with, the name of the server, and the time.

The OS is Windows 2003 Server, and the DB is MSDE.

I will say though, I solved the problem on my own, and I'll tell you how in case any other users come across the same problem.

Remember how I said the Eventlog gave me a username? I decided that was pretty odd, since it should be a system process. Turns out, I was right and that's were the problem occured. Every working system service Kaspersky installed was installed to run with the "Log On As" set to Local System, with the exception of the Admin Server, which was set to run with the "Log On As" set to the administrator. Shouldn't in theory be a problem, but I went ahead and changed it to Local System just to be sure.

Sure enough, problem solved.

So, thanks for taking the time to listen, but I'm all set with this issue.

Ok, that didn't work. Well, it did, but not in a helpful way. Allow me to explain.

By changing the log on as setting, I now have the service running as if it is the local system's service. However, this prevents the Server from having admin privileges across the entire domain. So, the immediate problem is, I can't remote install the Network Agent without the KAV Server service running loged in as an admin, and the KAV Server service won't run at start up without being logged as coming from the Local System.

A dizzying problem, hopefully I can find the solution soon.