asked on Windows 7 MFC Application - Faulting module name: MFC42.DLL
I have a MFC application that was installed for a user in Windows-7 and it works as intended; When another user logs into the Win-7 machine and tries to run the application, they get an "Unsupported operation was attempted" error and the MFC application fails to launch. I looked at event viewer and listed the error details below. It appears that only the user that installed this application can run this software successfully.
I've changed the security settings of the folder/application to ensure that all users have all the necessary rights, run as administrator, compatibility mode, etc, to no avail.
Any help is greatly appreciated.
Faulting module name: MFC42.DLL, version: 6.6.8064.0, time stamp: 0x4d79b238
Exception code: 0xc0000005
Fault offset: 0x0005ae34
Faulting process id: 0x18e4
Faulting application start time: 0x01cfc38989704101
Faulting application path: C:\Program Files (x86)\Test\Test.exe
Faulting module path: C:\windows\system32\MFC42.
I've changed the security settings of the folder/application to ensure that all users have all the necessary rights, run as administrator, compatibility mode, etc, to no avail.
Any help is greatly appreciated.
Faulting module name: MFC42.DLL, version: 6.6.8064.0, time stamp: 0x4d79b238
Exception code: 0xc0000005
Fault offset: 0x0005ae34
Faulting process id: 0x18e4
Faulting application start time: 0x01cfc38989704101
Faulting application path: C:\Program Files (x86)\Test\Test.exe
Faulting module path: C:\windows\system32\MFC42.
Windows 7C++
Last Comment
sarabande
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I wasn't implyig that some DLL is missing. The error message would tell that right away and not cause an exception, which can only occur in DLLs that are in fact there.
ASKER
Thanks for the suggestions, I will look into it more...
Question: If this MSI installer had the 'Install for all users', would this problem not have occurred?
I am trying to see if I can modify the MSI package through ORCA to see if I can turn on any flags for 'Install all users', but I can't seem to locate it. Any help in this area?
Thanks All!
Question: If this MSI installer had the 'Install for all users', would this problem not have occurred?
I am trying to see if I can modify the MSI package through ORCA to see if I can turn on any flags for 'Install all users', but I can't seem to locate it. Any help in this area?
Thanks All!
>>Question: If this MSI installer had the 'Install for all users', would this problem not have occurred?
Might be possible, but it's not sure at this stage. IF a module was missing, the app would not start in the 1st place. If a setting is missing, that could be the reason. But, with the above, you will at least be able to locate the faulting method and parameter, so this will definitely narrow down the issue.
Might be possible, but it's not sure at this stage. IF a module was missing, the app would not start in the 1st place. If a setting is missing, that could be the reason. But, with the above, you will at least be able to locate the faulting method and parameter, so this will definitely narrow down the issue.
try
your.msi ALLUSERS=2 /s /q
http://msdn.microsoft.com/en-us/library/aa367559.aspx talks about the ALLUSERS option.
I am not familiar with Orca but reading around I think Orca should have a "property" section under which you should find "ALLUSERS"
I mean when you open the msi the installer tables displayed by Orca,should show a "property" section or category
ASKER
I did look at ORCA property but there is no existing setting for all users and for some reason its opening my MSI as read-only.
just try running the installer as per my previous comment
your.msi ALLUSERS=2 /s /q
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
>>>> the 'AllUser' option at setup may not help for existing users as it would only provide the defaults for new users and the application itself must provide (or copy) the settings at first start for existing users.
@sara the above statement assumes that settings are changed from the defaults at startup.
Default values can be set for all users on an install so that an access violation does not result on app startup. It is not mandatory that user settings should be changed dynamically on app startup.
@sara the above statement assumes that settings are changed from the defaults at startup.
Default values can be set for all users on an install so that an access violation does not result on app startup. It is not mandatory that user settings should be changed dynamically on app startup.
It is not mandatory that user settings should be changed dynamically on app startup.it is the only way to get registry settings to the HKEY_CURRENT_USER section of windows registry when the account where the setup was done with was differently to the user account where the application was run at. HKEY_CURRENT_USER will not be updated from HKEY_USERS where only the defaults for new users could be stored. so, the alternative to let the application make its settings itself at start (for example by self registration via /Regserver) is to using HKEY_LOCAL_MACHINE section read-only or to have a separate "setup" which runs at user account or to using a configuration file from a public folder.
Sara
What did you end up doing? I have the exact same problem. Can I just uninstall and reinstall under the different user? The previous user is no longer with the firm. I have not deleted the old users profile. Please let me know.
Can I just uninstall and reinstall under the different user?yes. both the uninstall and the new setup should be done 'as administrator'.
Sara