Re: Running FOP using shell command yields Permission Problems
Sash Wiener wrote: Hi, Running FOP Successfully for years on Windows servers using Shell Command to execute from client side ie. shell(fopString) However according to hosting company the new security updates in Windows Server 2005 are causing this error message. To better isolate the problem, I would create a simple.bat file that just has this command: "dir". Then try to run simple.bat instead of fopString. If you get a directory listing, we know the problem is with "fopString"; but if simple.bat fails with the same security error, then this is a Microsoft security question best asked on one of their mailing lists. Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Running FOP using shell command yields Permission Problems
Hi, Running FOP Successfully for years on Windows servers using Shell Command to execute from client side ie. shell(fopString) However according to hosting company the new security updates in Windows Server 2005 are causing this error message. --System.Security.SecurityException: Request for the permission of type System.Security.Permissions.SecurityPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed.-- I have tried different commands which obviously do not work. I have read that you can Demand() access but this does not seem to work... Any Suggestions please I am desperate SASH