Accessing Exchange/Outlook information

[crystalvictim]

Hi,

we're using CR/CE8.5. We'd like to report on our exchange server's public folders. We have installed outlook 2000 on our ce-server and basically the data access works. Our problem is, that we're only able to access folders on which the 'user' who is running the outlook-process has the according rights. As we'd like to avoid giving access to ALL relevant folders to one single user we would like to know, if there's a possibility to schedule the report with the logon-information of other users. If this is a valid option, what has to be done and how?
We tried using user & password as well as domain & user & password and have checked this with both outlook and exchange as datasource but the reports fail with either 'cannot open sql server' or 'abort by user request' (which definitely isn't true ;-)).

Help's appreciated!

 

[crystalvictim]

After reinstalling our CE-Server, we tried something that should be easier for crystal: We have created a user under whose account all the processes (i.e. the different servers) are running and who has an email-account. Now we wanted to create a report that is based on this user's mailbox (incoming emails). As usual with CR there's no problem at all, no matter if trying on a separate client or on the CE-Server's CR-Installation.
Alas, trying to schedule or simply run this report from the CE-Server via CMC or ePortfolio, there's again a f****** error message ('not enough memory' - which obviously isn't true...
I can't believe that such a primitive task can be so complicated or even impossible :-(
And as for us this does not seem to be a very 'exotic' issue, we still hope, that there's somebody out there who has made similar experiences and finally found out the trick.

 

[crystalvictim]

Finally we've been able to do some digging on this topic again and managed to find out at least how to use "Exchange" as a datasource: Our Outlook client on the CE-server was obviously lacking the (standard-)profile used by our developers and therefore wasn't able to connect.
Although there's still an error message when trying to access the "Outlook"-datasource, I think we'll get along with Exchange quite well as it seems to provide more accessible information (fields).