Outlook Interop Exception

后端 未结 10 1314
故里飘歌
故里飘歌 2021-01-25 07:49

Trying to automate Outlook as

Microsoft.Office.Interop.Outlook.Application myApp = new Microsoft.Office.Interop.Outlook.ApplicationClass();    
Microsoft.Office         


        
相关标签:
10条回答
  • 2021-01-25 08:00

    I've been stumped by this problem for days. This worked for me:

    I just realized that Outlook 2013 is 64 bit... And my C# app had in Project Properties -> Build "Any CPU" as platform target and a check-mark in "Prefer 32-bit".

    I changed the Platform target to x64 and it worked!

    0 讨论(0)
  • 2021-01-25 08:00
       //DECLARE
        Microsoft.Office.Interop.Outlook.Application app = null;
        Microsoft.Office.Interop.Outlook.NameSpace ns = null;
    
      //INITIALISE
        app = new Microsoft.Office.Interop.Outlook.Application();
        ns = app.Session;
    
    0 讨论(0)
  • 2021-01-25 08:01

    Same error exactly in the same place:

    Outlook.NameSpace ns = application.GetNamespace("MAPI");
    

    I have a Win 10 and Office 365 - both 64 bits - with no previous Office installation; I tried several solutions above and did too Office quick repair, to no avail.
    After running a Office online repair it functions like a charm.

    0 讨论(0)
  • 2021-01-25 08:08

    For me removing 9.5 entry from this registry works:

    HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}

    0 讨论(0)
  • 2021-01-25 08:11

    The exception looks quite obvious, this should work

        var myApp = new Microsoft.Office.Interop.Outlook.Application();
    

    you just can't get a cast exception with that line above.

    0 讨论(0)
  • 2021-01-25 08:11

    The fix of the 9.5 version didn't work for me, as there was no excessive 9.5 field.

    In my case, the problem was that when I downgraded to Outlook 2010 I have modified the installation location (i.e. not in the default ProgramFiles folder). However, windows didn’t update accordingly the value in ‘HKEY_CLASSES_ROOT\TypeLib{00062FFF-0000-0000-C000-000000000046}\9.4\0\win64’.

    After manually updating the value and pointing it to the right location, the problem was resolved.

    0 讨论(0)
提交回复
热议问题