Help Center>
CodeArts Deploy>
FAQs>
Custom Application Actions>
Running PowerShell Commands>
Parameters Contain Backslashes (\)
Updated on 2023-05-26 GMT+08:00
Parameters Contain Backslashes (\)
Symptoms
When a host-related application is deployed, an error message is displayed.
The following takes a path as an example.
- The deployment fails due to the \b characters.
Figure 1 Log information
- The deployment fails due to the \f characters.
Figure 2 Log information
- The deployment fails due to the \r characters.
Figure 3 Log information
- The deployment fails due to the \t characters.
Figure 4 Log information
- The deployment fails due to the \n characters.
Figure 5 Log information
Cause Analysis
The deployment failure is caused by the use of escape characters that have special meanings.
Solution
- Method 1: Avoid using special escape characters.
- Method 2: Use forward slashes (/) instead of backslashes (\).
Parent topic: Running PowerShell Commands
Running PowerShell Commands FAQs
- Deployment of the Action Run PowerShell Commands Times Out
- Unidentified PowerShell Commands Are Used
- PowerShell Command References a File or Folder That Does Not Exist
- How Does a PowerShell Command Reference Parameters?
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore