Based on NT login name, I want to get user's email address.  I wrote a 

small DLL (below) that gets the email address from Outlook based on the 

Exchange Server Name and the Mailbox (also the NT login name).



I can reference this DLL from another VB project and it works beautifully.



I've registered it on the IIS server in c:\winnt\system32.  The CDO.DLL is 

also registered and my compiled DLL includes a reference to CDO.DLL.



When I try to use the function in an ASP page, however, I get the 

following:

   Collaboration Data Objects error '8004010f' 

[Collaboration Data Objects - [MAPI_E_NOT_FOUND(8004010F)]] 







Public Function GetEmailAddr(sServer As String, sMailbox As String) As 

String

Dim oSession As Session ' MAPI.Session

'Dim sServer As String

'Dim sMailbox As String

Dim sProfileInfo As String

Dim oGAL As AddressList

Dim oAddEntryColl As AddressEntries

Dim oAddEntry As AddressEntry

Dim oEmail As Field

    

    sProfileInfo = sServer & vbLf & sMailbox

    Set oSession = New Session 'MAPI.Session

    oSession.Logon "", "", False, True, 0, True, sProfileInfo

    Set oGAL = oSession.AddressLists("Global Address List")

    

    Set oAddEntryColl = oGAL.AddressEntries

    For Each oAddEntry In oAddEntryColl

        If oAddEntry.Name = oSession.CurrentUser Then

            Set oEmail = oAddEntry.Fields(972947486) 'FieldID for field 

that holds SMTP mail address

            GetEmailAddr = oEmail.Value

            Exit For

        End If

    Next

End Function

Tell us how you did "The CDO.DLL is also registered". As you might know,

the only supported way to get CDO 1.21 (which is CDO.DLL) installed is

installing one of the following products:



Outlook 98  (Note that Microsoft claims to support CDO 1.21

only in CW mode here)

Outlook 2000  (Note that Microsoft claims to support CDO 1.21

only in CW mode here)

Outlook 2002



Also note that CDO 1.21 isn't installed by default installed with

Outlook 2000 and 2002.



On the server-side you can install:



Exchange 5.5 Server

Exchange 2000 Server



So how did you install CDO 1.21 on your Webserver to make sure it works

properly?



<Siegfried />



> -----Original Message-----

> From: Romas V Petrelis [mailto:rpetrelis@b...]

> Sent: Tuesday, August 28, 2001 10:22 PM

> To: ASP CDO

> Subject: [asp_cdo] CDO MAPI_E_NOT_FOUND(8004010F)]

>

> Based on NT login name, I want to get user's email address.  I wrote a

> small DLL (below) that gets the email address from Outlook based on

the

> Exchange Server Name and the Mailbox (also the NT login name).

>

> I can reference this DLL from another VB project and it works

beautifully.

>

> I've registered it on the IIS server in c:\winnt\system32.  The

CDO.DLL is

> also registered and my compiled DLL includes a reference to CDO.DLL.

>

> When I try to use the function in an ASP page, however, I get the

> following:

>    Collaboration Data Objects error '8004010f'

> [Collaboration Data Objects - [MAPI_E_NOT_FOUND(8004010F)]]

>

>

>

> Public Function GetEmailAddr(sServer As String, sMailbox As String) As

> String

> Dim oSession As Session ' MAPI.Session

> 'Dim sServer As String

> 'Dim sMailbox As String

> Dim sProfileInfo As String

> Dim oGAL As AddressList

> Dim oAddEntryColl As AddressEntries

> Dim oAddEntry As AddressEntry

> Dim oEmail As Field

>

>     sProfileInfo =3D sServer & vbLf & sMailbox

>     Set oSession =3D New Session 'MAPI.Session

>     oSession.Logon "", "", False, True, 0, True, sProfileInfo

>     Set oGAL =3D oSession.AddressLists("Global Address List")

>

>     Set oAddEntryColl =3D oGAL.AddressEntries

>     For Each oAddEntry In oAddEntryColl

>         If oAddEntry.Name =3D oSession.CurrentUser Then

>             Set oEmail =3D oAddEntry.Fields(972947486) 'FieldID for

field

> that holds SMTP mail address

>             GetEmailAddr =3D oEmail.Value

>             Exit For

>         End If

>     Next

> End Function

> 

CDO 1.21 (the mapi version), CDO 2.0 (aka CDOSYS, aka CDO for Windows 2000),

and CDOEX (for exchange) all ship with Windows 2000 as well.



-- Tomm



> -----Original Message-----

> From: Siegfried Weber [mailto:sweber@c...]

> Sent: Tuesday, August 28, 2001 5:09 PM

> To: ASP CDO

> Subject: [asp_cdo] RE: CDO MAPI_E_NOT_FOUND(8004010F)]

>

>

> Tell us how you did "The CDO.DLL is also registered". As you might know,

> the only supported way to get CDO 1.21 (which is CDO.DLL) installed is

> installing one of the following products:

>

> Outlook 98  (Note that Microsoft claims to support CDO 1.21

> only in CW mode here)

> Outlook 2000  (Note that Microsoft claims to support CDO 1.21

> only in CW mode here)

> Outlook 2002

>

> Also note that CDO 1.21 isn't installed by default installed with

> Outlook 2000 and 2002.

>

> On the server-side you can install:

>

> Exchange 5.5 Server

> Exchange 2000 Server

>

> So how did you install CDO 1.21 on your Webserver to make sure it works

> properly?

>

> <Siegfried />

>

Some notes:



CDO 1.21 (CDO.DLL) never shipped with any Microsoft OS. It is *only*

part of the products I mentioned in one of my previous replies and there

is neither a supported nor legal way to install it without those

products. Hence the reason why I am asking.



CDOEX ships only with Exchange 2000 and Office XP and is only supported

locally on the Exchange 2000 server.



Leaves only CDOSYS as shipping with Windows 2000 itself.



Just my $.02 US



<Siegfried />



> -----Original Message-----

> From: Tomm Matthis [mailto:matthis@b...]

> Sent: Wednesday, August 29, 2001 12:37 PM

> To: ASP CDO

> Subject: [asp_cdo] RE: CDO MAPI_E_NOT_FOUND(8004010F)]

>

> CDO 1.21 (the mapi version), CDO 2.0 (aka CDOSYS, aka CDO for Windows

> 2000),

> and CDOEX (for exchange) all ship with Windows 2000 as well.

>

> -- Tomm

>

> > -----Original Message-----

> > From: Siegfried Weber [mailto:sweber@c...]

> > Sent: Tuesday, August 28, 2001 5:09 PM

> > To: ASP CDO

> > Subject: [asp_cdo] RE: CDO MAPI_E_NOT_FOUND(8004010F)]

> >

> >

> > Tell us how you did "The CDO.DLL is also registered". As you might

know,

> > the only supported way to get CDO 1.21 (which is CDO.DLL) installed

is

> > installing one of the following products:

> >

> > Outlook 98  (Note that Microsoft claims to support CDO 1.21

> > only in CW mode here)

> > Outlook 2000  (Note that Microsoft claims to support CDO 1.21

> > only in CW mode here)

> > Outlook 2002

> >

> > Also note that CDO 1.21 isn't installed by default installed with

> > Outlook 2000 and 2002.

> >

> > On the server-side you can install:

> >

> > Exchange 5.5 Server

> > Exchange 2000 Server

> >

> > So how did you install CDO 1.21 on your Webserver to make sure it

works

> > properly?

> >

> > <Siegfried />

> >

>

Thanks to both of you for responding.



As far as CDO on the server is concerned, Exchange Server 5.5 is installed 

on the server.





> Some notes:

> 

> CDO 1.21 (CDO.DLL) never shipped with any Microsoft OS. It is *only*

> part of the products I mentioned in one of my previous replies and there

> is neither a supported nor legal way to install it without those

> products. Hence the reason why I am asking.

> 

> CDOEX ships only with Exchange 2000 and Office XP and is only supported

> locally on the Exchange 2000 server.

> 

> Leaves only CDOSYS as shipping with Windows 2000 itself.

> 

> Just my $.02 US

> 

> <Siegfried />

> 

> > -----Original Message-----

> > From: Tomm Matthis [mailto:matthis@b...]

> > Sent: Wednesday, August 29, 2001 12:37 PM

> > To: ASP CDO

> > Subject: [asp_cdo] RE: CDO MAPI_E_NOT_FOUND(8004010F)]

> >

> > CDO 1.21 (the mapi version), CDO 2.0 (aka CDOSYS, aka CDO for Windows

> > 2000),

> > and CDOEX (for exchange) all ship with Windows 2000 as well.

> >

> > -- Tomm

> >

> > > -----Original Message-----

> > > From: Siegfried Weber [mailto:sweber@c...]

> > > Sent: Tuesday, August 28, 2001 5:09 PM

> > > To: ASP CDO

> > > Subject: [asp_cdo] RE: CDO MAPI_E_NOT_FOUND(8004010F)]

> > >

> > >

> > > Tell us how you did "The CDO.DLL is also registered". As you might

> know,

> > > the only supported way to get CDO 1.21 (which is CDO.DLL) installed

> is

> > > installing one of the following products:

> > >

> > > Outlook 98  (Note that Microsoft claims to support CDO 1.21

> > > only in CW mode here)

> > > Outlook 2000  (Note that Microsoft claims to support CDO 1.21

> > > only in CW mode here)

> > > Outlook 2002

> > >

> > > Also note that CDO 1.21 isn't installed by default installed with

> > > Outlook 2000 and 2002.

> > >

> > > On the server-side you can install:

> > >

> > > Exchange 5.5 Server

> > > Exchange 2000 Server

> > >

> > > So how did you install CDO 1.21 on your Webserver to make sure it

> works

> > > properly?

> > >

> > > <Siegfried />

> > >

> >

Okay. Now that we know what you installed CDO 1.21 using a supported

way, I'd check that your custom application (COM component) runs within

a security context which can access the global address list to retrieve

the information it is supposed to.



Also you might want to check if you can login as administrator with

Outlook Web Access on the Exchange 5.5 Server computer locally.



And finally make sure you have the latest Exchange 5.5 service pack

installed and in case you have SP4 installed then go and install the

postSP4 CDO hotfixes as available on the Microsoft download Website.



<Siegfried />



> -----Original Message-----

> From: Romas V Petrelis [mailto:rpetrelis@b...]

> Sent: Wednesday, August 29, 2001 4:43 PM

> To: ASP CDO

> Subject: [asp_cdo] RE: CDO MAPI_E_NOT_FOUND(8004010F)]

>

> Thanks to both of you for responding.

>

> As far as CDO on the server is concerned, Exchange Server 5.5 is

installed

> on the server.

>

>

> > Some notes:

> >

> > CDO 1.21 (CDO.DLL) never shipped with any Microsoft OS. It is *only*

> > part of the products I mentioned in one of my previous replies and

there

> > is neither a supported nor legal way to install it without those

> > products. Hence the reason why I am asking.

> >

> > CDOEX ships only with Exchange 2000 and Office XP and is only

supported

> > locally on the Exchange 2000 server.

> >

> > Leaves only CDOSYS as shipping with Windows 2000 itself.

> >

> > Just my $.02 US

> >

> > <Siegfried />