Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For some reason service crashes with message in the event viewer saying “Faulting module name: MSVCR100.dll” no any other useful information. It kills the whole process. We can not find what causes this problem and can’t catch this exception. We are not referencing this module in our source.
Service is running on Windows 7 64 bit .NET 4.
A quick Google search shows this to be a common error for a variety of applications. It also reveals this is a common underlying library.
I have a couple of potential suggestions, as a quick search revealed no firm answer that matches your issue exactly.
One possibility is this library is unregistered in Windows. This assumes it is COM based, of course. I don’t think this is the first approach, but it is a possibility.
Another is a 64 bit issue. The most likely cause here would be a 32 bit service on a 64 bit OS. One potential method is to set up the service as 64 bit; the other would be ensure the DLL in question is being usable by WOW. This would most likely be plopping a copy of the DLL in SysWOW64.