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@...>
To: vantage@yahoogroups.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, Ned <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]
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]
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, Ned <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]
>