Can't open MfgSys.exe but can open MfgSys64.exe

Again to reiterate for a third time... THE COMPATIBILITY MODE TRICK DID NOT WORK! I had to use another method which I posted a few days ago. It required deleting some files related to .NET.



Joshua Giese

CTO

920.437.6400 Ext. 337

Site ID: 27450-E905700B2-SQL64

----- Original Message -----

From: "adamnoffie" <ygroups.adamleer@...>
To: vantage@yahoogroups.com
Sent: Monday, April 1, 2013 10:16:41 AM
Subject: [Vantage] Re: Can't open MfgSys.exe but can open MfgSys64.exe





I agree with Ned. I have even seen this work for a specific user on a Windows 2003 (XP) terminal server. The one user would be unable to launch 32-bit Epicor... it would just crash immediately and give the System.Security.XmlSyntaxException even message in event log.

Logged in as this user, I turned on compatibility mode for her shortcut to Epicor Prod - set it to Windows XP. Now Epicor starts fine! I then turn compatibility mode off again and Epicor will still start up fine. It's like it clears some setting or corrupt configuration file somewhere.

--- In vantage@yahoogroups.com , Ned <TechnoBabbly@...> wrote:
>
> That's a compatibility mode error.
>
> Set all users to run it as is its XP SP3 and run it as administrator.
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto: vantage@yahoogroups.com ] On Behalf Of
> jgiese1988
> Sent: Thursday, March 28, 2013 12:55 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe
>
> Very strange issue on Windows 8. Can't open the 32 bit client. No login
> screen or anything. Immediately after opening it throws "MfgSys.exe Has
> Stopped Working". I uninstalled, removed all Epicor folders from
> ProgramData, removed all Epicor folders from Program Files, removed USER
> hive registry keys for Epicor, tried compatibility modes, removed the
> compatibility mode keys from registry, and still same result can open 64 bit
> client but not 32 bit. Ran debug on Mfgsys.exe and got the following. What
> precipitated this was a "Communication Layer" error in Epicor. After I
> killed the session to re-open it 32 bit started throwing a fit.
>
>
> System.Security.XmlSyntaxException was unhandled
> Message=Invalid syntax.
> Source=mscorlib
> StackTrace:
> at System.Security.SecurityDocument.InternalGetElement(Int32&
> position, Boolean bCreate)
> at System.Security.SecurityDocument.InternalGetElement(Int32&
> position, Boolean bCreate)
> at
> System.Security.SecurityDocument.GetChildrenPositionForElement(Int32
> position)
> at System.Security.Policy.PolicyStatement.FromXml(SecurityDocument
> doc, Int32 position, PolicyLevel level, Boolean allowInternalOnly)
> at System.Security.Policy.PolicyLevel.CheckCache(Int32 count, Char[]
> serializedEvidence)
> at System.Security.Policy.PolicyLevel.Resolve(Evidence evidence,
> Int32 count, Char[] serializedEvidence)
> at System.Security.PolicyManager.CodeGroupResolve(Evidence evidence,
> Boolean systemPolicy)
> at System.Security.PolicyManager.ResolveHelper(Evidence evidence)
> at System.Security.HostSecurityManager.ResolvePolicy(Evidence
> evidence)
> at System.Security.PolicyManager.Resolve(Evidence evidence)
> at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
> PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
> PermissionSet& denied, Boolean checkExecutionPermission)
> at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
> PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
> PermissionSet& denied, Int32& securitySpecialFlags, Boolean
> checkExecutionPermission)
> InnerException:
>
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
> already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and
> Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo ! Groups Links
>





[Non-text portions of this message have been removed]
Very strange issue on Windows 8. Can't open the 32 bit client. No login screen or anything. Immediately after opening it throws "MfgSys.exe Has Stopped Working". I uninstalled, removed all Epicor folders from ProgramData, removed all Epicor folders from Program Files, removed USER hive registry keys for Epicor, tried compatibility modes, removed the compatibility mode keys from registry, and still same result can open 64 bit client but not 32 bit. Ran debug on Mfgsys.exe and got the following. What precipitated this was a "Communication Layer" error in Epicor. After I killed the session to re-open it 32 bit started throwing a fit.


System.Security.XmlSyntaxException was unhandled
Message=Invalid syntax.
Source=mscorlib
StackTrace:
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.GetChildrenPositionForElement(Int32 position)
at System.Security.Policy.PolicyStatement.FromXml(SecurityDocument doc, Int32 position, PolicyLevel level, Boolean allowInternalOnly)
at System.Security.Policy.PolicyLevel.CheckCache(Int32 count, Char[] serializedEvidence)
at System.Security.Policy.PolicyLevel.Resolve(Evidence evidence, Int32 count, Char[] serializedEvidence)
at System.Security.PolicyManager.CodeGroupResolve(Evidence evidence, Boolean systemPolicy)
at System.Security.PolicyManager.ResolveHelper(Evidence evidence)
at System.Security.HostSecurityManager.ResolvePolicy(Evidence evidence)
at System.Security.PolicyManager.Resolve(Evidence evidence)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission)
InnerException:
Not familiar with win 8..what is compatibility mode, I know I had similar issues once in a great while on 7... right clicking on icon and going thru troubleshoot compatibility always fixed it..long shot I'm sure..



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jgiese1988
Sent: Thursday, March 28, 2013 11:55 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe



Very strange issue on Windows 8. Can't open the 32 bit client. No login screen or anything. Immediately after opening it throws "MfgSys.exe Has Stopped Working". I uninstalled, removed all Epicor folders from ProgramData, removed all Epicor folders from Program Files, removed USER hive registry keys for Epicor, tried compatibility modes, removed the compatibility mode keys from registry, and still same result can open 64 bit client but not 32 bit. Ran debug on Mfgsys.exe and got the following. What precipitated this was a "Communication Layer" error in Epicor. After I killed the session to re-open it 32 bit started throwing a fit.

System.Security.XmlSyntaxException was unhandled
Message=Invalid syntax.
Source=mscorlib
StackTrace:
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.GetChildrenPositionForElement(Int32 position)
at System.Security.Policy.PolicyStatement.FromXml(SecurityDocument doc, Int32 position, PolicyLevel level, Boolean allowInternalOnly)
at System.Security.Policy.PolicyLevel.CheckCache(Int32 count, Char[] serializedEvidence)
at System.Security.Policy.PolicyLevel.Resolve(Evidence evidence, Int32 count, Char[] serializedEvidence)
at System.Security.PolicyManager.CodeGroupResolve(Evidence evidence, Boolean systemPolicy)
at System.Security.PolicyManager.ResolveHelper(Evidence evidence)
at System.Security.HostSecurityManager.ResolvePolicy(Evidence evidence)
at System.Security.PolicyManager.Resolve(Evidence evidence)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission)
InnerException:



[Non-text portions of this message have been removed]
That's a compatibility mode error.

Set all users to run it as is its XP SP3 and run it as administrator.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
jgiese1988
Sent: Thursday, March 28, 2013 12:55 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe

Very strange issue on Windows 8. Can't open the 32 bit client. No login
screen or anything. Immediately after opening it throws "MfgSys.exe Has
Stopped Working". I uninstalled, removed all Epicor folders from
ProgramData, removed all Epicor folders from Program Files, removed USER
hive registry keys for Epicor, tried compatibility modes, removed the
compatibility mode keys from registry, and still same result can open 64 bit
client but not 32 bit. Ran debug on Mfgsys.exe and got the following. What
precipitated this was a "Communication Layer" error in Epicor. After I
killed the session to re-open it 32 bit started throwing a fit.


System.Security.XmlSyntaxException was unhandled
Message=Invalid syntax.
Source=mscorlib
StackTrace:
at System.Security.SecurityDocument.InternalGetElement(Int32&
position, Boolean bCreate)
at System.Security.SecurityDocument.InternalGetElement(Int32&
position, Boolean bCreate)
at
System.Security.SecurityDocument.GetChildrenPositionForElement(Int32
position)
at System.Security.Policy.PolicyStatement.FromXml(SecurityDocument
doc, Int32 position, PolicyLevel level, Boolean allowInternalOnly)
at System.Security.Policy.PolicyLevel.CheckCache(Int32 count, Char[]
serializedEvidence)
at System.Security.Policy.PolicyLevel.Resolve(Evidence evidence,
Int32 count, Char[] serializedEvidence)
at System.Security.PolicyManager.CodeGroupResolve(Evidence evidence,
Boolean systemPolicy)
at System.Security.PolicyManager.ResolveHelper(Evidence evidence)
at System.Security.HostSecurityManager.ResolvePolicy(Evidence
evidence)
at System.Security.PolicyManager.Resolve(Evidence evidence)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
PermissionSet& denied, Int32& securitySpecialFlags, Boolean
checkExecutionPermission)
InnerException:




------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
I've had success with that in the past as well, but not in this instance. In this case it appears to have been an issue with the .NET install on my computer, something corrupted it. I was sent instructions on how to clear the corrupt files (they regenerate if not in existence) and now all is well. Below was the fix.

Open the command prompt and do the following:


cd C:\Users\%USERNAME%\AppData\Roaming\Microsoft\CLR Security Config\v2.0.50727.312

del security.config.cch

cd C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG

del *.cch


Joshua Giese


CTO

920.437.6400 Ext. 337

Site ID: 27450-E905700B2-SQL64

----- Original Message -----

From: "Rob Bucek" <rbucek@...>
To: vantage@yahoogroups.com
Sent: Thursday, March 28, 2013 1:06:17 PM
Subject: RE: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe



Not familiar with win 8..what is compatibility mode, I know I had similar issues once in a great while on 7... right clicking on icon and going thru troubleshoot compatibility always fixed it..long shot I'm sure..

From: vantage@yahoogroups.com [mailto: vantage@yahoogroups.com ] On Behalf Of jgiese1988
Sent: Thursday, March 28, 2013 11:55 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe

Very strange issue on Windows 8. Can't open the 32 bit client. No login screen or anything. Immediately after opening it throws "MfgSys.exe Has Stopped Working". I uninstalled, removed all Epicor folders from ProgramData, removed all Epicor folders from Program Files, removed USER hive registry keys for Epicor, tried compatibility modes, removed the compatibility mode keys from registry, and still same result can open 64 bit client but not 32 bit. Ran debug on Mfgsys.exe and got the following. What precipitated this was a "Communication Layer" error in Epicor. After I killed the session to re-open it 32 bit started throwing a fit.

System.Security.XmlSyntaxException was unhandled
Message=Invalid syntax.
Source=mscorlib
StackTrace:
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.GetChildrenPositionForElement(Int32 position)
at System.Security.Policy.PolicyStatement.FromXml(SecurityDocument doc, Int32 position, PolicyLevel level, Boolean allowInternalOnly)
at System.Security.Policy.PolicyLevel.CheckCache(Int32 count, Char[] serializedEvidence)
at System.Security.Policy.PolicyLevel.Resolve(Evidence evidence, Int32 count, Char[] serializedEvidence)
at System.Security.PolicyManager.CodeGroupResolve(Evidence evidence, Boolean systemPolicy)
at System.Security.PolicyManager.ResolveHelper(Evidence evidence)
at System.Security.HostSecurityManager.ResolvePolicy(Evidence evidence)
at System.Security.PolicyManager.Resolve(Evidence evidence)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission)
InnerException:

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
Joshua, nice! My Vantage 8.03.409C client on Win 7 64 stopped working about 1.5 weeks ago. Same symptoms as you previously listed. Couldn't get it working. This fixed it.



Thanks for posting!





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Thursday, March 28, 2013 3:17 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe





I've had success with that in the past as well, but not in this instance. In this case it appears to have been an issue with the .NET install on my computer, something corrupted it. I was sent instructions on how to clear the corrupt files (they regenerate if not in existence) and now all is well. Below was the fix.

Open the command prompt and do the following:

cd C:\Users\%USERNAME%\AppData\Roaming\Microsoft\CLR Security Config\v2.0.50727.312

del security.config.cch

cd C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG

del *.cch

Joshua Giese

CTO

920.437.6400 Ext. 337

Site ID: 27450-E905700B2-SQL64

----- Original Message -----

From: "Rob Bucek" <rbucek@... <mailto:rbucek%40dsmfg.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Thursday, March 28, 2013 1:06:17 PM
Subject: RE: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe

Not familiar with win 8..what is compatibility mode, I know I had similar issues once in a great while on 7... right clicking on icon and going thru troubleshoot compatibility always fixed it..long shot I'm sure..

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf Of jgiese1988
Sent: Thursday, March 28, 2013 11:55 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe

Very strange issue on Windows 8. Can't open the 32 bit client. No login screen or anything. Immediately after opening it throws "MfgSys.exe Has Stopped Working". I uninstalled, removed all Epicor folders from ProgramData, removed all Epicor folders from Program Files, removed USER hive registry keys for Epicor, tried compatibility modes, removed the compatibility mode keys from registry, and still same result can open 64 bit client but not 32 bit. Ran debug on Mfgsys.exe and got the following. What precipitated this was a "Communication Layer" error in Epicor. After I killed the session to re-open it 32 bit started throwing a fit.

System.Security.XmlSyntaxException was unhandled
Message=Invalid syntax.
Source=mscorlib
StackTrace:
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.InternalGetElement(Int32& position, Boolean bCreate)
at System.Security.SecurityDocument.GetChildrenPositionForElement(Int32 position)
at System.Security.Policy.PolicyStatement.FromXml(SecurityDocument doc, Int32 position, PolicyLevel level, Boolean allowInternalOnly)
at System.Security.Policy.PolicyLevel.CheckCache(Int32 count, Char[] serializedEvidence)
at System.Security.Policy.PolicyLevel.Resolve(Evidence evidence, Int32 count, Char[] serializedEvidence)
at System.Security.PolicyManager.CodeGroupResolve(Evidence evidence, Boolean systemPolicy)
at System.Security.PolicyManager.ResolveHelper(Evidence evidence)
at System.Security.HostSecurityManager.ResolvePolicy(Evidence evidence)
at System.Security.PolicyManager.Resolve(Evidence evidence)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission)
InnerException:

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3267 / Virus Database: 3161/6210 - Release Date: 03/28/13




-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3267 / Virus Database: 3161/6210 - Release Date: 03/28/13


[Non-text portions of this message have been removed]
I agree with Ned. I have even seen this work for a specific user on a Windows 2003 (XP) terminal server. The one user would be unable to launch 32-bit Epicor... it would just crash immediately and give the System.Security.XmlSyntaxException even message in event log.

Logged in as this user, I turned on compatibility mode for her shortcut to Epicor Prod - set it to Windows XP. Now Epicor starts fine! I then turn compatibility mode off again and Epicor will still start up fine. It's like it clears some setting or corrupt configuration file somewhere.

--- In vantage@yahoogroups.com, Ned <TechnoBabbly@...> wrote:
>
> That's a compatibility mode error.
>
> Set all users to run it as is its XP SP3 and run it as administrator.
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> jgiese1988
> Sent: Thursday, March 28, 2013 12:55 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Can't open MfgSys.exe but can open MfgSys64.exe
>
> Very strange issue on Windows 8. Can't open the 32 bit client. No login
> screen or anything. Immediately after opening it throws "MfgSys.exe Has
> Stopped Working". I uninstalled, removed all Epicor folders from
> ProgramData, removed all Epicor folders from Program Files, removed USER
> hive registry keys for Epicor, tried compatibility modes, removed the
> compatibility mode keys from registry, and still same result can open 64 bit
> client but not 32 bit. Ran debug on Mfgsys.exe and got the following. What
> precipitated this was a "Communication Layer" error in Epicor. After I
> killed the session to re-open it 32 bit started throwing a fit.
>
>
> System.Security.XmlSyntaxException was unhandled
> Message=Invalid syntax.
> Source=mscorlib
> StackTrace:
> at System.Security.SecurityDocument.InternalGetElement(Int32&
> position, Boolean bCreate)
> at System.Security.SecurityDocument.InternalGetElement(Int32&
> position, Boolean bCreate)
> at
> System.Security.SecurityDocument.GetChildrenPositionForElement(Int32
> position)
> at System.Security.Policy.PolicyStatement.FromXml(SecurityDocument
> doc, Int32 position, PolicyLevel level, Boolean allowInternalOnly)
> at System.Security.Policy.PolicyLevel.CheckCache(Int32 count, Char[]
> serializedEvidence)
> at System.Security.Policy.PolicyLevel.Resolve(Evidence evidence,
> Int32 count, Char[] serializedEvidence)
> at System.Security.PolicyManager.CodeGroupResolve(Evidence evidence,
> Boolean systemPolicy)
> at System.Security.PolicyManager.ResolveHelper(Evidence evidence)
> at System.Security.HostSecurityManager.ResolvePolicy(Evidence
> evidence)
> at System.Security.PolicyManager.Resolve(Evidence evidence)
> at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
> PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
> PermissionSet& denied, Boolean checkExecutionPermission)
> at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
> PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
> PermissionSet& denied, Int32& securitySpecialFlags, Boolean
> checkExecutionPermission)
> InnerException:
>
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
> already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and
> Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>