Problem with Office 2003 PIA in ASP.Net

[tigerjade]

I'm trying to display some Outlook data (current appts, tasks & number of unread in inbox) for users on an intranet. There's no problem if I view the site via Cassini, but if I open it in IIS, I get the following error:

Retrieving the COM class factory for component with CLSID {0006F03A-0000-0000-C000-000000000046} failed due to the following error: 80070005.

I've given ASPNET read/execute permissions to darn near everything. The one thing I haven't been able to give permissions to is the Windows/assembly/ folder, 'cause for some reason it's locked down from security editing. I can give permissions to Windows, but I'm not certain that it's propagating permissions to assembly.

Googling gives me no useful info (can't find the COM in dcomcnfg, so no help there), and I can't get responses on any of the posts I've made on any forums, not even MSDN.

Help!

"Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live." -- Martin Golding

 

[bboffin]

Have you installed the .NET Programmability Support feature for Outlook on your PC?

If not go into Control Panel/Add/Remove Programs and select Micosoft Outlook 2003 (or whatever) and drill down until you find the feature and install it.

Without this you don't get any programmatic access to the later versions of Outlook.

What's even worse is that if you're on XP SP2 you'll find that you keep getting security warnings when accessing Outlook messages etc. The fix for this can be found at

http://www.mapilab.com

and is called 'Advanced Security for Outlook' and the last time I looked it was free!



Bob Boffin

 

[ca8msm]

can't find the COM in dcomcnfg, so no help there

I think this is where the problem lies (although I'm not sure which entry it is either). I know for Excel tasks, you have to set the Launch and Execute permissions for the ASPNET user in the DCOM so it will most likely be the same for Outlook (an article that descibes these steps can be found at

http://blog.crowe.co.nz/archive/2006/03/02/589.aspx).

You may also want to look at this article (

http://msdn2.microsoft.com/en-us/library/kh3965hw.aspx)

as:

You must install the Microsoft Office 2003 primary interop assemblies in the global assembly cache (GAC) before you can create or run a Microsoft Visual Studio 2005 Tools for the Microsoft Office System solution. The interop assemblies enable managed code to interact with an Office application's COM-based object model.

I'd suggest asking this question in either the Windows XP (forum779) or the Email forum (forum605) and see if anyone there has any other suggestions if the above doesn't work for you.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[tigerjade]

Thanks for the responses!

Oh my yes; the .Net programmability support has been installed and re-installed. I've also gotten the same errors on my test box that has a new install of Office 2003 with all the goodies. That one is Win2k3 standard.

The PIAs are in the GAC like they're s'posed to be, and like I said, it works fine with Cassini. (That's the part that gets me!) I'm almost certain it's some sort of permissions issue, but I just can't find it. At least, based on it being error 80070005, I'm assuming it's a permissions error.

I've read that post about DCOM & Excel too, but I can't find any confirmation ANYWHERE (dang it!) that Outlook should be there too. I thought the same as you, ca8msm, that it should be there & that that's the problem, but if it's not showing up in dcomcnfg on ANY machine that has this installed, should it indeed be there? Or is it a different beast 'cause it's Outlook?

Do you know of ANYONE who has ever done this sort of thing successfully? It shouldn't be that unusual a request, but I swear I can't find anything on the web about something like this. Makes me feel like I'm losing my mind!

I'll check on the Office forum & see if anyone has ever done anything like this.

Thanks!

"Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live." -- Martin Golding