UNSPECIFIED ERROR

Add-in Express™ Support Service
That's what is more important than anything else

UNSPECIFIED ERROR
 
favk




Posts: 5
 Joined: 2006-12-21
Hi,

Got your application installed just now and we are testing.
If I run your SendMail sample and press the SEND button the first time everything works. The second time, however we get an unspecified error. Those errors kinda make me nervous....

Unhandled Exception: System.Runtime.InteropServices.COMException (0x80004005): Unspecified error

And after that a orphaned OUTLOOK.EXE process continues to run.

Any ideas?

Regards, Frank
Posted 21 Dec, 2006 13:49:51 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
 Joined: 2004-07-05
Hi Frank.

Thank you for the bug report. There is a little issue in the SendMail example. I will try to fix it as soon as possible.
Do other examples work properly?

P.S. Note that we take up your forum requests in the order we receive them.
Besides, it may take us some time to investigate your issue. Please be sure we will let you know as soon as the best possible solution is found.
Posted 23 Dec, 2006 06:31:56 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
 Joined: 2004-07-05
Frank, please change the finally block as shown below. Let me know if the issue still exists.
.........
finally
{
if (recipients != null)
Marshal.ReleaseComObject(recipients);
if (newMail != null)
Marshal.ReleaseComObject(newMail);
if (tbtnMode.Pushed)
{
securityManager1.DisableOOMWarnings = false;
securityManager1.Disconnect(outlookApp);
}
if (outlookApp != null)
{
if (canQuit) outlookApp.Quit();
Marshal.ReleaseComObject(outlookApp);
}
}
Posted 23 Dec, 2006 08:57:31 Top
favk




Posts: 5
 Joined: 2006-12-21
Hi Sergey,

Thank you for your response, but I ran the VB sample. I can't tell the difference between your code and the current code in the VB sample. (I'm not a C# expert though, so correct me if I'm wrong) 

            Finally
              If Not (Recipients Is Nothing) Then
                Marshal.ReleaseComObject(Recipients)
              End If
              If Not (NewMail Is Nothing) Then
                Marshal.ReleaseComObject(NewMail)
              End If
              If (TBtnMode.Pushed = True) Then
                SecurityManager1.DisableOOMWarnings = False
                SecurityManager1.Disconnect(OutlookApp)
              End If
              If Not (OutlookApp Is Nothing) Then
                If (CanQuit) Then OutlookApp.Quit()
                Marshal.ReleaseComObject(OutlookApp)
              End If
            End Try


Regards, Frank
Posted 27 Dec, 2006 09:11:58 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
 Joined: 2004-07-05
Hi Frank.

A bit strange situation. The C# code works fine on my PC. I will test the VB code and will let you know about results.
Posted 28 Dec, 2006 06:15:25 Top
favk




Posts: 5
 Joined: 2006-12-21
Hi Sergey,

The error does only occurs when Outlook is running before starting the VB demo.
Furthermore I discovered that leaving out 

SecurityManager1.Disconnect(OutlookApp)


Seems to solve the problem. (Bad housekeeping probably)
I thought you might like to know

Regards, Frank
Posted 28 Dec, 2006 10:03:30 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
 Joined: 2004-07-05
Hi Frank.

Yes, right. Please remove the code above from your application. I will investigate the issue with the Disconnect method and will fix it ASAP.
Posted 29 Dec, 2006 06:53:45 Top