This OCX may be requiring permissions that it no longer has on Windows
Server 2003, for security reasons. So, the fact that it worked on prior
Windows version really doesn't mean much -- it may have been working because
it required a security vulnerability to work.
You have to first verify that the OCX is even loading -- I would remove the
ASP.Net application and the file creation stuff from the picture by using a
test ASP.Net page which just instantiates the OCX with the same settings as
the real page. See if this works, and check of the OCX file is loaded in
memory (Process Explorer from
www.sysinternals.com and TLIST.EXE from
Microsoft Debugging Tools at
http://www.microsoft.com/whdc/devtools/debugging/default.mspx is what I'd
use to verify the OCX file is loaded in memory).
Please report whether the OCX is loaded in memory and doesn't cause
problems.
My suspicion right now is that the OCX requires some extraneous
permission(s) which is no longer allowed by default on Windows Server 2003
for security reasons. For example, users over the WEB cannot access CMD.EXE,
nor can the IIS6 process identity create any UI. OCX may be trying to do
these illegal things and getting denied, and the only work-around to allow
these programs to function is to enable the security vulnerabilities that
they require. Of course, Microsoft recommends that you notify the vendor to
provide you with secure code instead of requiring you to open security
vulnerabilities to use their program.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Scott" <scottbuzan.RemoveThis@msn.com> wrote in message
news:54d101c4741c$9f978470$a501280a@phx.gbl...
We are using Windows 2003 Server, and we are unable to
generate mp3 files from our web application. The web
application calls an ocx dll which generates mp3 files
from text. It appears that the ocx is not loading at
all, although we aren't 100% sure of this. Our ASPNET
user account has sufficient privileges to create/modify
files directly to the target folder. Also, when the ocx
dll is called from a winform application, the files are
created. How do we configure permissions for the aspnet
process to create/modify files through a 3rd party dll?
This process works for Windows xp, Windows 2000, and
Windows 2000 Server.
Thanks