J
Jay Kappel
OK, Here's the latest...
I have an activex dll that does what I need it to do. I have created an
ASP page that uses that dll. On my windows XP Professional machine I have
registered the dll and used my local web server to browse the asp page. The
good news is that it works GREAT! The page completes in 3-4 seconds.
However when I transfer the dll and the ASP page to a Windows Web 2003
server it jumps up to a whopping 54 seconds!
I am wondering if this could have something to do with the enhanced
browsing security implemented by default on the Web Server 2003? It appears
that this enhanced setting is profile based, so setting it back to a normal
level for my admin account does not help the IUSR_MachineName account. Does
anyone know how I can change this setting for the IUSR account? And is
there a registry key or something that I can have my com object change and
then flip back when it's done. Will the com object have the appropriate
security rights to perform this action? And lastly am I barking up the
wrong tree?
Thanks, Jay Kappel
I have an activex dll that does what I need it to do. I have created an
ASP page that uses that dll. On my windows XP Professional machine I have
registered the dll and used my local web server to browse the asp page. The
good news is that it works GREAT! The page completes in 3-4 seconds.
However when I transfer the dll and the ASP page to a Windows Web 2003
server it jumps up to a whopping 54 seconds!
I am wondering if this could have something to do with the enhanced
browsing security implemented by default on the Web Server 2003? It appears
that this enhanced setting is profile based, so setting it back to a normal
level for my admin account does not help the IUSR_MachineName account. Does
anyone know how I can change this setting for the IUSR account? And is
there a registry key or something that I can have my com object change and
then flip back when it's done. Will the com object have the appropriate
security rights to perform this action? And lastly am I barking up the
wrong tree?
Thanks, Jay Kappel