Hi
Raised a support case already, but wondering if anybody else has run into the following error whilst trying to perform Extension Schema Syncronize on 2025.2.5 after installation of UK CSF pack..? @MikeGross maybe..? 
The log file gives nothing away, last few lines are just references to the scrips that have been run and I can run them manually without error.
Cheers
We ran into issues with Epicor Education Databases with Kinetic 2025.2 versions where the Vendor table contained a field named ElecRemittanceBuyerRef defined as nvarchar(20). However, the default constraint for this field was incorrectly set to an integer value (0) instead of a string.
Below is what we have been using as a temporary fix/workaround until a new Epicor update comes out with a fix.
ALTER TABLE [Erp].[Vendor] DROP CONSTRAINT [DF_Vendor_ElecRemittanceBuyerRef];
GO
ALTER TABLE [Erp].[Vendor]
ADD CONSTRAINT [DF_Vendor_ElecRemittanceBuyerRef] DEFAULT ('') FOR [ElecRemittanceBuyerRef];
GO
Perfect, thanks for the quick reply - confirm that this worked perfectly. Did you troubleshoot and find this yourself or was it from support? If you did find it, I’m intrigued in how you did so as the logs didn’t really give anything away from what I could see.
Many Thanks.
One of our Senior Developers (Meharban Singh) troubleshooted the issue and found it and the solution. I believe that the issue was found by manually executing the relevant extension sync SQL scripts within SQL Management Studio (or similar) until error(s) were reported, then reviewing the details to find the cause and prepare the workaround/fix.
It would definitely be better if the extension sync logs did provide more details but so far when we have run into extension sync challenges, we have generally been able to identify the issue and figure out a solution fairly quickly via the above method.
Glad you got the solution - not sure I had that answer 