This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- Due to marshalling?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 12, 2009
01:10 PM
COM Security and flex initialization
It appears that one of the flex publisher methods initializes DCOM security by calling CoInitializeSecurity.
The method fails if I call it after a call to lc_flexinit:
# for hex 0x80010119 / decimal -2147417831 :
RPC_E_TOO_LATE winerror.h
# Security must be initialized before any interfaces are
# marshalled or unmarshalled. It cannot be changed once
# initialized.
# 1 matches found for "0x80010119"
The call succeeds if I remove flex initialization. This is going to be a big problem for us. Why is flex breaking COM rules and calling CoInitializeSecurity inside a library? Can this functionality be modified?
Thanks in advance,
Paul
The method fails if I call it after a call to lc_flexinit:
# for hex 0x80010119 / decimal -2147417831 :
RPC_E_TOO_LATE winerror.h
# Security must be initialized before any interfaces are
# marshalled or unmarshalled. It cannot be changed once
# initialized.
# 1 matches found for "0x80010119"
The call succeeds if I remove flex initialization. This is going to be a big problem for us. Why is flex breaking COM rules and calling CoInitializeSecurity inside a library? Can this functionality be modified?
Thanks in advance,
Paul
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 27, 2009
09:37 AM
It appears that lc_flexinit may be causing a DCOM marshalling event, which would cause the default security to be used anyway. If your app needs to explicitly set security it should do so before the call to flex init.