With the release of Epicor ERP 10? there was a big shift in the entire Epicor architecture. As we all know, the days of ABL are long gone and Epicor 10 is running on a Microsoft stack. After being involved in many implementations and upgrades we’ve come to realize that a lot of customers and even some consultants don’t fully understand the way in which the new Epicor 10 client is deployed and how to modify that deployment as needed to push out and/or publish additional files and customizations.
More often than not, we come across installations where the deployment client has been corrupted and everyone gets that dreaded version mismatch error when launching Epicor.
Many customers resort to manually copying dlls into the ReleaseClient.zip like they used to do in Epicor 9 to fix these issues but this can cause further problems. Hopefully with this post we can shed a little light into this aspect of Epicor 10.
When Epicor ERP 10 is installed a deployment folder is created and shared.
\\MYSERVER\ERP10.0.700Deployment\
This network share contains several folders:
When you install an Epicor patch (10.0.700.3, 10.0.700.4 … etc) a new zip file is created and placed in the Custom folder (outlined above).
These zip files are used to update the clients with the changes to the dlls. These patches are incremental and as you can see by their sizes, they do not include ALL the client files, but rather only those files that have changed. These zip files should not be touched either. Any customization you want to deploy should be placed in their own zip file and deployed according to the instructions outlined next. If by any chance you or your consultant has changed these zip files, you can get a fresh copy of these by getting the original ReleaseClient.zip from the Patch specific folder located at:
Drive:\[Epicor_Location]\ERP10\ERP10.0.700\Updates\ERP10.0.700.XXX\ClientDeployment\ReleaseClient.zip
Copy the new ReleaseClient.zip from above to the \ClientDeployment\Custom\Client\Update folder. Delete the corrupted zip [ERP10.0.XXX.X] file and rename the ReleaseClient.zip to the original name of the corrupted file.
How to Deploy your Custom Files
The next time you (or anyone else) launches this Epicor client an Automatic Update will be triggered and your new files will be copied down to the client folder.
Last Words
We hope that you find this post useful and that it helps to clarify some of the “Black Magic” that goes on behind the curtain within the Epicor environment.
At TriGem, we strive to make your life just a tad easier. Feel free to contact us with any questions or suggestions and please let us know if there is anything we can help you with.
Subscribe to our email updates here
联系客服