Problems with a Service. Servie is automatically stop

Most importantly: do you catch and handle each and every possible exception? Do you have an error logger in your service that writes to a log file or the eventlog when exceptions occur? If so, what does it say. If not, implement one as you're blind. Never use an empty catch unless you're absolutely ten-thousand percent sure that it does not make you blind.

You might have permission issues; e.g. if your service attempts to access network shares, it needs admin rights (you can configure a user somewhere in the properties of the service in the service manager); I'm not sure if the result is the error that you get. Or if the service tries to create a logfile or directory in a directory that it does not have permission on (e.g. C:\).

My approach is to log anything in the event log till the service is started completely. I also log in the eventlog when the service is stopped normally.

The start of a service has a time limit; if the onStart() is not finished within a certain time (I think one minute), the service will be considered as non-responding and stopped.

Did you develop a console application or windows application in parallel that was used to test / debug the main functionality of the service using exactly the same methods?
I use a conditional compilation flag to decide between console application and service. The console application will start a thread while the service will start service (onStart). The thread and the service will do exactly the same so it's easy to debug in the console application.