Support Forums

We are taking time during the holiday to perform our annual site maintenance from Dec. 21, 2018, 9:00 a.m. to Dec. 22, 2018, 9:00 a.m. (PST).All SAPIEN services will be offline during this maintenance period, including the SAPIEN website, Community Support Forums, Premium Support Ticketing, SAPIEN Blog, SAPIEN Store, and License Activation. We appreciate your patience and understanding.

"i build the service.
if get some error, the service look is running but it is not work."

I am sorry, but that is not enough information to determine what your problem might be.
"i build the service": I am assuming that means you packaged a script as a service? If so, with what options? For what platform?
"Some error": What exactly does that mean?
"it is not work": That can mean anything from doing nothing over rebooting your computer to causing a blackout in Singapore. Can you be more specific?

Maybe you can explain what your service does and WHERE it counters an error.

You need to catch errors inside your script and handle them accordingly.
It is imperative that your script does not exit until a stop service command is issued. It is your responsibility to handle any errors in your script.
Just because your script stopped or crashed does not make the outer service wrapper stop or change its status.

A service runs under a different account. Usually defaulting to the system account. Files or folder may not be accessible to that account, drives not mapped, network shares not available etc.
Without any information it is impossible to tell.