A couple of things I'd add to this discussion: 1. Make sure the user rights of the folder in which your DLL resides are set correctly. 2. Component Services Package-level security tab (property sheet of the package): "Enforce access checks for this application". Uncheck this to see if the problem is security. 3. The Security tab at the Component level has a similar checkbox. 4. Your VFP support libraries may be in a different folder; if so, check the permissions on that folder. I usually put those files in the same folder as the MTDLL.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sietse Wijnker Sent: Wednesday, August 15, 2007 6:25 AM To: [EMAIL PROTECTED] Subject: RE: Running a batch file from VFP MTDLL What kind of OS is running your website? Can you instanciate the COM+ component using VFP? My guess is that the COM+ is securing the COM+ Application One extra step is needed: Go into the Roles section of your COM+ application. If there's a role present, edit it. If not create one. Then add the User/groups Everyone, ASPNET, IWAM_... to the Users section of the role Then try again from VFP and web-page Regards & GL, Sietse <snip> _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
