Thanks for that additional information and yes, it turns out there's a compatibility issue with those versions of R and Rlabkey with old versions of LabKey (including 22.11) causing this exact error. I'm able to reproduce this locally against 23.7 and didn't go back any farther. I'm not certain exactly what the issue is here, and it's possible that downgrading to using R version 3.x.x might resolve it, but that could add other issues so I didn't try this option myself.

Better yet, I can confirm that it is fixed/compatible in LabKey Server version 23.11, and will work with your versions of R, RStudio, Rlabkey, etc as detailed above. Since we recommend staying current with the latest LabKey Server release anyway, that's the best way forward.

You can find the latest release of LabKey Server 23.11 on our website here:

• Download LabKey Server Community Edition.

Note that to use an API key to authenticate against LabKey Server 23.11, you also need to have a system default domain set. It can be left set to the default "labkey.com" or set to your own domain. All this does is allow "users" (including the APIkey) to authenticate without also including an email account domain. If you try your executeSql after the upgrade using a newly generated API key and receive an authentication error, this would be the first thing to check.

Hope that helps,

--Molly