none
microsoft office word requires the file msointl.dll error on 2 Terminal servers - 2008 sp2

    Question

  • Hi there,

    I have 2 terminal servers (one freshly built) that are coming up with this error. I am running office 2007 pro plus. Also on both servers I am unable to remove office, I have to use a microsoft mr fixit in order to remove and re-install. After that, the problem still comes back even if i clear office from the registry.

    Please assist.

    thanks,
    Matt

     

    Tuesday, May 24, 2011 3:23 AM

Answers

  • Hi Matt,

    Msointl.dll errors are caused by situations that lead to the removal or corruption of the msointl DLL file.

    In some cases, msointl.dll errors could indicate a registry problem, a virus or malware issue or even a hardware failure.

    How to Fix Msointl.dll Errors

    Important: Do not download msointl.dll from a "DLL download" website. There are many reasons why downloading a DLL file is a bad idea. If you need a copy of msointl.dll, it's best to obtain it from its original, legitimate source.

    Note: Start Windows in Safe Mode to complete any of the following steps if you're unable to access Windows normally due to the msointl.dll error.

    1. Restore msointl.dll from the Recycle Bin. The easiest possible cause of a "missing" msointl.dll file is that you've mistakenly deleted it.

    If you suspect that you've accidentally deleted msointl.dll but you've already emptied the Recycle Bin, you may be able to recover msointl.dll with a free file recovery program.

    Important: Recovering a deleted copy of msointl.dll with a file recovery program is a smart idea only if you're confident you've deleted the file yourself and that it was working properly before you did that.

    2. Run a virus/malware scan of your entire system. Some msointl.dll errors could be related to a virus or other malware infection on your computer that has damaged the DLL file. It's even possible that the msointl.dll error you're seeing is related to a hostile program that's masquerading as the file.

    3. Use System Restore to undo recent system changes. If you suspect that the msointl.dll error was caused by a change made to an important file or configuration, a System Restore could solve the problem.

    4. Reinstall the program that uses the msointl.dll file. If the msointl.dll DLL error occurs when you use a particular program, reinstalling the program should replace the file.

    Important: Try your best to complete this step. Reinstalling the program that provides the msointl.dll file, if possible, is a likely solution to this DLL error.

    If the issue still persists, let’s refer to the following link:

    http://pcsupport.about.com/od/findbyerrormessage/a/msointl-dll-not-found-missing-error.htm

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
     
    Best Regards,

    Nick Wan

    • Marked as answer by Nick Wan Tuesday, June 7, 2011 8:30 AM
    Wednesday, June 1, 2011 7:19 AM

All replies

  • Please note I also get an error when I try and uninstall that says: 'the language of this installation package is not supported by your system'

     

     

    Tuesday, May 24, 2011 5:08 AM
  • I have also completely uninstalled, removed office from HKLM\software and re-installed using a different directory - again it worked for a while then corrupted.

    I have run sfc /SCANNOW and there were no integrity violations

     

    Tuesday, May 24, 2011 6:59 AM
  • I have not recieved any reply on this, the issue is very critical and needs to be resolved. Please reply soon.

     

     

    Tuesday, May 24, 2011 11:14 PM
  • Hi Matt,

    Msointl.dll errors are caused by situations that lead to the removal or corruption of the msointl DLL file.

    In some cases, msointl.dll errors could indicate a registry problem, a virus or malware issue or even a hardware failure.

    How to Fix Msointl.dll Errors

    Important: Do not download msointl.dll from a "DLL download" website. There are many reasons why downloading a DLL file is a bad idea. If you need a copy of msointl.dll, it's best to obtain it from its original, legitimate source.

    Note: Start Windows in Safe Mode to complete any of the following steps if you're unable to access Windows normally due to the msointl.dll error.

    1. Restore msointl.dll from the Recycle Bin. The easiest possible cause of a "missing" msointl.dll file is that you've mistakenly deleted it.

    If you suspect that you've accidentally deleted msointl.dll but you've already emptied the Recycle Bin, you may be able to recover msointl.dll with a free file recovery program.

    Important: Recovering a deleted copy of msointl.dll with a file recovery program is a smart idea only if you're confident you've deleted the file yourself and that it was working properly before you did that.

    2. Run a virus/malware scan of your entire system. Some msointl.dll errors could be related to a virus or other malware infection on your computer that has damaged the DLL file. It's even possible that the msointl.dll error you're seeing is related to a hostile program that's masquerading as the file.

    3. Use System Restore to undo recent system changes. If you suspect that the msointl.dll error was caused by a change made to an important file or configuration, a System Restore could solve the problem.

    4. Reinstall the program that uses the msointl.dll file. If the msointl.dll DLL error occurs when you use a particular program, reinstalling the program should replace the file.

    Important: Try your best to complete this step. Reinstalling the program that provides the msointl.dll file, if possible, is a likely solution to this DLL error.

    If the issue still persists, let’s refer to the following link:

    http://pcsupport.about.com/od/findbyerrormessage/a/msointl-dll-not-found-missing-error.htm

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
     
    Best Regards,

    Nick Wan

    • Marked as answer by Nick Wan Tuesday, June 7, 2011 8:30 AM
    Wednesday, June 1, 2011 7:19 AM
  • Hi Nick and All

    Are you copying Tim Fisher from pcsupport.about.com or it's my imagination.

    Realy...in the busy environment I have here with MS Office 2010 being deployed via SCCM I would not go for such time wasting solution that even cannot guarantee the resolution of the case (on about 60000 machines).

    As of now none of the proposed solution helped.

    Thanks anyway (at least for copy & paste :D)

    Greetings!

    Muzzy


    • Edited by cranky27 Thursday, March 22, 2012 5:07 PM
    Thursday, March 22, 2012 5:06 PM