RE: Extracting information from Exchange

  • From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 15 Mar 2005 11:58:03 -0500

Should have included this: 

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/e2k3/e2k3/_
exch2k_getting_well-known_mailbox_folder_urls.asp 

-----Original Message-----
From: Mulnick, Al 
Sent: Tuesday, March 15, 2005 11:56 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Extracting information from Exchange

http://www.MSExchange.org/

Sorry for the confusion. This particular code sample would run with Windows
Scripting Host (usually found on Windows 2000 and Windows XP workstations
but can be installed on NT4 workstations).  It would run on the individuals
workstation vs. on the server. 

To work on the server, you'd want to use a different method.  The problem is
that contacts in the mailbox exist in the mailbox itself.  To get to the
individual mailbox, you would typically go through the client to get there.
It is possible to use a different method, such as ExOLEDB which is what it
looks like you're trying and not having any luck with at the moment.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/e2k3/e2k3/_
clb_listing_contacts_using_ado_vbs.asp is a link to an example of using the
ExOLEDB provider to write information to a web page.

What error are you getting back from the attempt to connect from the SQL
server to exchange?




-----Original Message-----
From: Sonya [mailto:sonya.mcneal@xxxxxxxx]
Sent: Tuesday, March 15, 2005 11:23 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Extracting information from Exchange

http://www.MSExchange.org/

Thanks Al. This may be a dump question but what program/application are you
using to run this script?

Could I used this in any scripting tool to run?

Would I run this scripting on the physical Exchange Server for it to work
properly?

I wanted to use it in Activex SQL DTS but I would need to have the Exchange
and SQL server on the same computer and that is currently impossible. I
couldn't get the SQL Server to connect to the Exchange Server using
"ExOLEDB.DataSource".


------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
al.mulnick@xxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
al.mulnick@xxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx


Other related posts: