I got this back when I had the error, but I think I also copied the patch files over the client ones and remade the releaseclient.zip by hand.
I trick posted by Jose Gomez or John Driggers was that you can change the version line on the server to anything that doesn't match the client like 700C and 700C force and the updater will run again when the client loads.
HTH
Greg Payne
Summary: Upgrade to E9.05.700C Client folder Issue
Book: Support Solutions
Page: 14728MPS
Upgrade to E9.05.700C Client folder Issue - EpicorPatchConfigUpdater needs 9.05.700.3 14728MPS
Upgrade to E9.05.700C Issue. The autoupdate process which updates the Epicor clients after upgrading to 700c does not transfer the c-patch files. The clients won't fully update until you either run a xcopy transfer manually (copy files from the server to the PC) or re-run the AutoUpdate after correcting the Updater. Once you correct the Updater, the AutoUpdate will re-execute from the client-side. Details shown below.
PROBLEM RESOLUTION:
1. Navigate to \Epicor905\Utilities\EpicorPatchConfigUpdater\ on
the Epicor server and launch EpicorPatchConfigUpdater.exe
2. In Path to Client Config Folder field, enter UNC patch to the
client\config folder on the server
3. Change the Customization Version to 9.05.700.3 and then click
Modify Configs button
4. Afterwards, launch a client from a workstation and it should
autoupdate (assuming that -skip isn't at the end of the target line)
Basically, the reason the EpicorPatchConfigUpdater.exe needs to be run is that the default.mfgsys file needs to contain the versional line that tells the Autoupdate where to get the C patch release files for the \Client folder - <customization name="Patch" directoryName="Patch"
version="9.05.700.3"... shown below. When AutoUpdate runs, it transfers the new files from Epicor905\Custom\Client\Patch folder via xcopy to the \Clients at 1st login after the update.
You will need to get the updater file fixed in order to properly update the Client folders on the PCs - otherwise, you would need to manually copy the content of the \Custom\Client\Patch folder to the PCs along with an updated 'default.mfgys' which resides in the PC's \Client\Config directory that contains the patch line, otherwise the client will go and retrieve an AutoUpdate.
at the very bottom of the default.mfgsys file you will see the added
line:
<customizations>
<customization name="Patch" directoryName="Patch"
version="9.05.700.3" deploymentType="XCOPY" />
</customizations>
</configuration>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of timlester67
Sent: Sunday, March 17, 2013 6:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Update to .700C error
Anyone have any further information on this, we did not have any issues with our test server; now we are upgrading the live server and this has hit us. We are upgraded to 700C.
Thanks.
Tim Lester
I trick posted by Jose Gomez or John Driggers was that you can change the version line on the server to anything that doesn't match the client like 700C and 700C force and the updater will run again when the client loads.
HTH
Greg Payne
Summary: Upgrade to E9.05.700C Client folder Issue
Book: Support Solutions
Page: 14728MPS
Upgrade to E9.05.700C Client folder Issue - EpicorPatchConfigUpdater needs 9.05.700.3 14728MPS
Upgrade to E9.05.700C Issue. The autoupdate process which updates the Epicor clients after upgrading to 700c does not transfer the c-patch files. The clients won't fully update until you either run a xcopy transfer manually (copy files from the server to the PC) or re-run the AutoUpdate after correcting the Updater. Once you correct the Updater, the AutoUpdate will re-execute from the client-side. Details shown below.
PROBLEM RESOLUTION:
1. Navigate to \Epicor905\Utilities\EpicorPatchConfigUpdater\ on
the Epicor server and launch EpicorPatchConfigUpdater.exe
2. In Path to Client Config Folder field, enter UNC patch to the
client\config folder on the server
3. Change the Customization Version to 9.05.700.3 and then click
Modify Configs button
4. Afterwards, launch a client from a workstation and it should
autoupdate (assuming that -skip isn't at the end of the target line)
Basically, the reason the EpicorPatchConfigUpdater.exe needs to be run is that the default.mfgsys file needs to contain the versional line that tells the Autoupdate where to get the C patch release files for the \Client folder - <customization name="Patch" directoryName="Patch"
version="9.05.700.3"... shown below. When AutoUpdate runs, it transfers the new files from Epicor905\Custom\Client\Patch folder via xcopy to the \Clients at 1st login after the update.
You will need to get the updater file fixed in order to properly update the Client folders on the PCs - otherwise, you would need to manually copy the content of the \Custom\Client\Patch folder to the PCs along with an updated 'default.mfgys' which resides in the PC's \Client\Config directory that contains the patch line, otherwise the client will go and retrieve an AutoUpdate.
at the very bottom of the default.mfgsys file you will see the added
line:
<customizations>
<customization name="Patch" directoryName="Patch"
version="9.05.700.3" deploymentType="XCOPY" />
</customizations>
</configuration>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of timlester67
Sent: Sunday, March 17, 2013 6:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Update to .700C error
Anyone have any further information on this, we did not have any issues with our test server; now we are upgrading the live server and this has hit us. We are upgraded to 700C.
Thanks.
Tim Lester
--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Greg Payne <gpayne@...<mailto:gpayne@...>> wrote:
>
> Do you have an SCR or call number that support can reference. They came up empty when I called in.
>
> Thanks
>
> Greg Payne
>
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of Stephen Booth
> Sent: Saturday, August 18, 2012 9:22 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: Re: [Vantage] Re: UPdate to .700C error
>
>
>
> This has been a common problem with 700C, and the main reason we're still on 700B2. There is a downloadable fix from epicor. I'm not sure if it is on epicweb, but I know you can get it if you call support.
>
> ________________________________
> From: Anon <epicor-team@...<mailto:epicor-team%40wisconsinconverting.com<mailto:epicor-team@...%3cmailto:epicor-team%40wisconsinconverting.com>>>
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> Sent: Saturday, August 18, 2012 1:24 PM
> Subject: [Vantage] Re: UPdate to .700C error
>
>
>
> I had the same issue going to 700B2. I reinstalled the client and created a new client release from scratch using the custom/patch folder. They release client stuff in 700 (admitted to me by epicor) is not working 100% there are sometimes some strange things that go on with it. If that doesn't work make sure to try logging in with multiple different users to ensure a personalization on the mainmenu is not broken.
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Ned <TechnoBabbly@<mailto:TechnoBabbly@>> wrote:
> >
> > I have not run into this before for any other updates I have done and
> > wondering if anyone is checking their mail on the weekend and could shed any
> > light on this? I get this error when I startup an Epicor Client, both on the
> > server and on a workstation. I had no problems with conversions, but this
> > one is puzzling me. I have done a few different .700 updates already and not
> > had this error pop up, so I am not sure where to start looking to solve it.
> > There don't appear to be any customizations in the .mfgsys file and rolling
> > the EpiClientLib file back to the previous version is even worse.
> >
> > Could not load file or assembly 'Epicor.Mfg.UI.EpiClientLib,
> > Version=2.5.607.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992' or one
> > of its dependencies. The located assembly's manifest definition does not
> > match the assembly reference. (Exception from HRESULT: 0x80131040)
> >
> > Stack Trace
> > ===========
> > at System.Reflection.Assembly._GetType(String name, Boolean throwOnError,
> > Boolean ignoreCase)
> > at System.Reflection.Assembly.CreateInstance(String typeName, Boolean
> > ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args,
> > CultureInfo culture, Object[] activationAttributes)
> > at Epicor.Mfg.UI.Startup.preLoadAssemblies()
> > at Epicor.Mfg.UI.Startup.PreStart(Session session, Boolean
> > initializeLanguage)
> > at Epicor.Mfg.UI.App.Launch.createInitialSession()
> > at Epicor.Mfg.UI.App.Launch.ShowMenuForm()
> > at Epicor.Mfg.UI.App.Launch.ShowDialog(String[] args)
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
> [Non-text portions of this message have been removed]
>
>
> ________________________________
> CONFIDENTIALITY NOTICE
>
> The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
>
> "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
>
>
> [Non-text portions of this message have been removed]
>
________________________________
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
[Non-text portions of this message have been removed]