Closed benoit-aa closed 2 years ago
Seems to me like that is causing this escaping issue as the base for the task is PowerShell. Is it possible to change the \
in the password? Or use a (new) dedicated user/password combination without any special character?
This is a bug. We deployed hundred of customers with passwords always containing special characters, we cannot change this easily without huge impact to our whole landscape and configuration.
This is only happening since the recent updates (with which we already had lots of issues and losing our in-line scripts, connection services several times).
Btw, is there a way to use the version before 1.5.x until this is fixed ?
I have updated the task (v1.5.6) to escape the SQL Password value.
Hello after v1.5.6 we are getting an error: Unrecognized escape sequence. If our password contains '#' mark it is converted like 'test#' -> 'test#' and does not work, means raises an error: Unrecognized escape sequence.
FYI, we tried it today and it worked for the password containing \ (version used was 1.5.7). We did not test with other special characters (I see some still have issues in the other thread).
Hi,
Since recently, I get the following error (it was working before). Not sure if related but the password contains the character \
Benoit