Help Center>
CodeArts Deploy>
FAQs>
Custom Application Actions>
Stopping a Service>
Action Stop Service Deployed Successfully, But the Service Is Still in Started State
Updated on 2023-11-28 GMT+08:00
Action Stop Service Deployed Successfully, But the Service Is Still in Started State
Symptoms
On a Windows host, the result shows that the action Stop Service is successfully deployed, but the service is still detected in Started state.
Figure 1 Log information
Cause Analysis
The service is registered as a Windows service, with the startup mode set to automatic startup.
Solution
Change the startup mode of this Windows service, or stop this service in other ways.
Parent topic: Stopping a Service
Stopping a Service FAQs
- Incorrect Port Number
- Action Stop Service Deployed Successfully, But the Service Is Still in Started State
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
more
