Faulting module name: secman.dll

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

Faulting module name: secman.dll
Periodic error using secman.dll 
Mads




Posts: 28
 Joined: 2010-10-22
Hi

Using:
Windows Terminal Server 2008 R2
Outlook 2007
Security Manager 2010 for Microsoft Outlook, .NET 6.1.3.3016

Some times secman fails to remove the security box. If I install on a normal windows machine everything works. I found this in the event log:

Faulting application name: OUTLOOK.EXE, version: 12.0.6423.1000, time stamp: 0x49b08185
Faulting module name: secman.dll, version: 3.0.3.0, time stamp: 0x4cceadb3
Exception code: 0xc0000005
Fault offset: 0x0000305c
Faulting process id: 0xffc
Faulting application start time: 0x01cc69315d7557d1
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Outlook Security Manager\secman.dll
Report Id: b4d6c3f1-d527-11e0-8d65-000c29ff28e2

Any idea why?

/Mads
Posted 13 Sep, 2011 04:00:36 Top
Renat Tlebaldziyeu


Add-in Express team


Posts: 132
 Joined: 2010-02-15
Hi Mads,

There's a test build available at
http://www.add-in-express.com/files/support/osmnet-v601-b3017.zip
Can you please check if it fixes the problem on your side?
Posted 13 Sep, 2011 04:13:57 Top
Mads




Posts: 28
 Joined: 2010-10-22
Since this is a newer version (3017), does this mean there´s a known issue with Terminal Server? Or what is changed in the beta?

Mads
Posted 13 Sep, 2011 08:31:54 Top
Renat Tlebaldziyeu


Add-in Express team


Posts: 132
 Joined: 2010-02-15
We were reported about the temperamental issue on a terminal server some months ago. And it was fixed in this test build. Could you please check if it fixes the issue on your side?
Posted 13 Sep, 2011 08:48:05 Top
Mads




Posts: 28
 Joined: 2010-10-22
Hi

I uninstalled the 3016 and installed the 3017b on my development machine. But now Outlook crashes almost everytime OSM is used. Sometimes it works.
The project i´m working on is quite old and have been using OSM in the last 5 years.
There is no difference in Debug or Release mode.

Visual Studio debugger stops at: sm = new Outlook.SecurityManager
Context 0x6fa040' is disconnected.
Releasing the interfaces from the current context (context 0x6f9b38).
This may cause corruption or data loss.
To avoid this problem, please ensure that all contexts/apartments stay alive until the applicationis completely done with the RuntimeCallableWrappers that represent COM components that liveinside them.
Posted 14 Sep, 2011 07:48:25 Top
Renat Tlebaldziyeu


Add-in Express team


Posts: 132
 Joined: 2010-02-15
Hi Mads,

There is no difference in Debug or Release mode.

Do you mean that you also get this exception when you run your application in the Release mode?

Could you please show me the code you use to disable security warnings?
Posted 14 Sep, 2011 08:00:15 Top
Mads




Posts: 28
 Joined: 2010-10-22
Yes the error is in both Debug and Release mode. But when in Release mode Outlook just stops responding.

Dim sm as new Outlook.SecurityManager (this is where the error is thrown)

try
sm.disableOOWarnings = true
...
finally
sm.disableOOWarnings = false
end try
Posted 14 Sep, 2011 08:06:49 Top
Renat Tlebaldziyeu


Add-in Express team


Posts: 132
 Joined: 2010-02-15
I'm sorry, I wasn't able to reproduce the issue on my PC.
Could you please create and send me a sample project for testing which reproduces the issue (please see readme.txt for the support e-mail address and make sure your e-mail contains a link to this topic)?
Posted 14 Sep, 2011 08:11:47 Top