Hi guys and gals!
I've run into a pickle of sorts. I'm trying to get a COM component (created with Vidual FoxPro 9), registered in the Component Services MMC to run under IIS6, Windows 2003 Std. Edition.
I've eliminated lots of possibilites but seem to be stuck on what looks like a permissions problem. I created a dedicated user who is to execute the COM Package, the Website and the ApplicationPool associated with that website. If this user is a member of the
Admin group, everything works fine. If he's anything less than an Admin it won't run. All I get in the borwser is a huge 'Service Unavailable' message.
Get this: If I access this COM component through a regular windows forms app (.exe) everything runs fine with this user NOT being an admin. He only needs the admin privilages in order to work with IIS6. btw. I'm using ASP1.1 here, no dotnet. After all, it's
just a createobject command and nothing more.
I know FoxPro is a rare dev tool, but maybe someone out there running W2k3 has some experience running other COM components and might me able to shed some light on this problem.
Any help would be appreciated. Thanks!
Matt
-
-
Hey Matt,
Since you can access it via Winforms, that means that the runtimes are on the machine and they are properly registered (at least for the interactive user you're running as when logged in running the winforms app).
This sounds like it's a COM+/IIS permissions issue (could also be double-hop issue - where the data the DLL accesses is on box #3). I'd suggest you call MSFT Support and start with COM+ support - they can call in the VFP support folks if needed - but I *think* you're better off starting with COM+.
yag
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.