OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Joakim Karlsson (joakim.karlssonCELLNETWORK.COM)
Date: Thu Jan 17 2002 - 05:27:02 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    This problem may appear on NT4 installations as well unfortunately.

    In ATL's registration code there is a workaround to a bug in CreateProcess concerning long filenames. ATL automatically converts the filename to the 8.3 format while, as it says in Keith Brown's faq, still retains the long filename in the rgs-file.

    If the server is launched with the short filename, the corresponding key is searched for under the HKLM\AppID key, but it will not be found. Therefore the AppID cannot be found.

    Well... something like that. Assuming you used ATL to develop your server.

    Does your server have a name longer than eight characters?

    Regards,
    Joakim

    -----Original Message-----
    From: Mark Freeman [mailto:mark.freemanJEMMAC.COM]
    Sent: den 17 januari 2002 09:48
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: 0x80070005 (accessdenied) on W2K

    Thanks Owen, Zlatko, Joakim for taking the trouble to respond, I appreciate
    it!!

    It looks like Joakim was correct (a big thankyou for the pointer to the
    FAQ), I added a key HKCR\AppID\<exename> that contained a string value
    (APPID) containing the apps AppID (bit of a mouthful) and it all started
    working!! I wasn't aware this was a requirement? I've been happily plodding
    along on NT for years without including this key and everything worked just
    fine. Migrate to W2K and the problems start!

    Unfortunately, in the production system I can not include the
    HKCR\AppID\<exename> instead I must call CoInitializeSecurity (the other
    option in the FAQ Joakim pointed me at) because a given machine may run
    multiple instances of the same executable albeit in different contexts. This
    is fine except CoInitializeSecurity does not like the Launch and Access
    permissions I have generated (created programmatically, and not via
    dcomcnfg). Again, these are fine on NT4 and only pose problems on W2K.
    Still, made some progress :-)

    Is it just me or has anyone else had problems migrating from NT4 to W2K?

    Thanks again for your help.

    cheers,

    Mark.

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM