/MT debugging option problem.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi all,
I have built an ISAPI filter that is working correctly in debug mode, both
in my development (XP. IIS 5.1) environment and in the test environment
(W2K3, IIS6). When I switch to the release build however, the filter wont
even start in the test environment. It works good on the development machine
though (XP).

After a lot of testing I have come to the conclusion that if I remove /MT
and replace it with /MTd in the release build, it works on the W2K3 machine.

It is really strange, the filter wont even initiate, It does not even seem
to call GetFilterVersion or even DLLMain before the error arises.

The error I Recieve in the eventviewer is :
Faulting application w3wp.exe, version 6.0.3790.1830, faulting module
ssofiltr.dll, version 1.0.0.1, fault address 0x0002f331.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 33 77 ure w3w
0018: 70 2e 65 78 65 20 36 2e p.exe 6.
0020: 30 2e 33 37 39 30 2e 31 0.3790.1
0028: 38 33 30 20 69 6e 20 73 830 in s
0030: 73 6f 66 69 6c 74 72 2e sofiltr.
0038: 64 6c 6c 20 31 2e 30 2e dll 1.0.
0040: 30 2e 31 20 61 74 20 6f 0.1 at o
0048: 66 66 73 65 74 20 30 30 ffset 00
0050: 30 32 66 33 33 31 02f331

I would apprciate it if someone could point me in the right direction.



Regards,

Tobias


.



Relevant Pages

  • /MT /MTd debugging problems
    ... I have built an ISAPI filter that is working correctly in debug mode, ... IIS 5.1) environment and in the test environment ... It works good on the development machine ... Faulting application w3wp.exe, version 6.0.3790.1830, faulting module ...
    (microsoft.public.vc.debugger)
  • domain trust
    ... I have a test environment with nt 4.0 pdc and a w2k3 dc. ... I establish a two trust relationship between the two domain and was able to ...
    (microsoft.public.windows.server.general)