Client Variables - Database creation failed on MSSQL

"solved" issue following suggestion (see above), this fix does not really solve the issue, you will still have a exception, but the exception should now report in more details, why this issue happening. for example because the user used has no right to create the necessary table.

https://github.com/lucee/Lucee/commit/89d15a09c06f73f606d0c0b9070a7eb97ff27bac

FYI as you can see next to the Ansi92 class is a MSSQL and MySQL class. it was planned to make an independent implementation for this datasource types. wanted to implement them ...

Yes, I've already noticed it & i agree with it. Surely we need to show the original error which happened in the first try/catch. But the first error may not relevant to the issue in some cases. each try/catch is related to a specific set of DBMS like MSSQL, MySql, Oracle & MS Access( with different versions). Better we can check what error is happening at the moment, if the error is a permission issue, then we can just throw the error. Otherwise we can proceed with next try/catch. This is the correct way to fix this issue, I think.

I've uploaded a sample test file(test.cfm) to explain the scenario in a better way. But for producing the error, we need to create a sql login/user with lack of permission, as i explained in my previous comment. Also please look at the Error.png image file. If we're experiencing permission issue on a try/catch, There should be no reason to proceed with next try/catch.

Did you see my last comment on this ticket where I explained what was happening? This basically happens when you have incorrect permissions, but the way we're catching and discarding errors causes the real issue to be obfuscated. Minimally, the code needs improved to let the user know when there is a permissions error. Ideally the code needs rewritten to better detect the database and not just start throwing code at it until something doesn't error. The way it is now, there's no good way to tell the difference between an error caused by trying SQL that doesn't work on a given engine and an error caused by an actual mis-configuration. In the case of this ticket, the issue was a misconfiguration, but the error messages masked that fact.