SEP 12 Causes rundll32.exe - Application Error
New installation of SEP 12.1.1000.157 RU1, on Windows XP SP3. Our mapping application generates an error when printing:
rundll32.exe - Application Error
The exception unknown software exception (0xc0000417) occurred in the application at location 0x60a052e4.
If you click OK, the rundll box goes away, and you get this:
Run a DLL as an App has encountered a problem and needs to close. We are sorry for the inconvenience.
If you click the "Debug" button, the print then completes.
The messages are intermittent, but are only seen with non-administrator accounts on Windows XP. No problem with Administrator accounts
on Windows XP, or Windows 7 machines (so far).
The problem occurred immeditately after installing SEP on several machines. (Generally speaking there is no problem with Rundll32 on these machines.)
Questions:
- Can anyone suggest how to located the exact DLL that is having a conflict? I might be able to exclude it in policy once I know what it is.
- Is there a way to locate the DLL based on the "location" shown in the error message?
- Is there some standard magic incantation that avoids this issue?
- Where should I exclude the application?
Comments
no easy solution
Hello,
you can review SEP logs to identify possible detections or other activities that can be related to your software, after that you can see for something like an exclusion.
If nothing is in the product logs, you need to get the memory dump for analysis. After that, it will possible to know which product is the real culprit and what to do (being the last installed is not a technical evidence that SEP is the real culprit).
Regards,
Giuseppe
SEP 12.1.1000 is the cause
I've run into this problem on a few laptops as well. It seems to only occur on the Dell D-series line of laptops (in our office at least) running Win XP SP3. If the laptop is running Windows 7 this problem does not occur. But it ALWAYS occurs right after the SEP upgrade on affected laptops. The user will actually see application error pop-ups for almost all services that are attempting to start up on login.
I'm still searching for a solution and there are a few other forum posts regarding this issue that have been yet resolved. So far I've been clean wiping the few XP laptops we have and reverting them to SEP 11.
Application & Device Control
I've had this issue on 3 of 3400+ endpoints. My "fix" was to uninstall the Application & Device Control component of SEP. You may find that you cannot access Add / Remove programs regardless of the account used to login to the troubled device. I had to "run as" administrator to access it, even though I was logged in as the local administrator. I haven't been able to isolate the cause of the issue, or what is different between the failing endpoints and the working endpoints. So far it is only Windows XP SP3, but that is still the majority OS in our enterprise. I hope this helps, or at least points you in the right direction.
Would you like to reply?
Login or Register to post your comment.