Hi Terry, 

We have clients/partners that have applied the fix and not experiencing the issue.. I did though just have another partner report that they were getting the log in error after applying the hot fix and it turned out the reason was that in the BXDATA\SQL folder in the shared data there were multiple renamed and backed up alchemex.svd files. 

Once those backed up and fixed Alchemex files were removed from the BXDATA\SQL folder, the error went away with the Hot Fix applied. 

Can you check if this may be the case for your client? 

Regards,

DCrampton

Hi Terry, 

We have clients/partners that have applied the fix and not experiencing the issue.. I did though just have another partner report that they were getting the log in error after applying the hot fix and it turned out the reason was that in the BXDATA\SQL folder in the shared data there were multiple renamed and backed up alchemex.svd files. 

Once those backed up and fixed Alchemex files were removed from the BXDATA\SQL folder, the error went away with the Hot Fix applied. 

Can you check if this may be the case for your client? 

Regards,

DCrampton

I just checked and there is only one alchemex.svd file.  I did have a BXDATA_old in the shared data folder which I have deleted so we will see what happens.