At CodeProject we spend an awful lot of time playing with room heaters, or as others like to call them, "servers". Over the years we've seen it all, some of it smoking, most of it usually working just nicely until something happens.
What that something is can be hard to find so we've created a quiet place for those battle scarred and frustrated to get a little help.
There's a secret error somewhere in your secret code. You need to fix that.
Seriously, how do you expect anyone to help you fix a problem in code we cannot see, running on a server we have no access to, when you haven't even bothered to check the Windows event logs for the details of the error?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I have a windows server with suspended processes. However, even with administrator privileges, I can't kill them. Everybody knows some idea without restart the server?
I used command taskkill but it doesn't work.
That's strange, because you can kill any process you own, even if it's suspended.
I didn't ask if is was a system process. I asked what account the process was running under. Go the Task Manager, Details tab, find the process that's suspended, and look under the "User name" column for the account that owns the process. If it shows your username, you can kill it.
I have installed a service in one of my new test server which is used for download or upload files from ftp server by calling an exe file, which will internally call cuteftp tool. Here my issue iswhen I am starting the windows service it not working the service is not even connecting to ftp server, and the service is logged on with local adminid.
when I am opening the exe file manually by clicking "run as different" user with the local admin the service is working perfectly and the upload/download is happening.
Please advice if any configuration changes in windows level is required or not