Hi Sergey Zolotarev,
it seems that the set table location routine behaves a little different from before.
The set table location trows an exception that can be ignored (catched).
In our case it fixed that problem that was caused by this line:
crTable->Location = crTableLogOnInfo->TableName->Substring(crTableLogOnInfo->TableName->LastIndexOf(".") + 1);
May this helps you.
Kind Regards
Peter