OK, here is the situation
We have a development server, GENESIS, which is an NT box with CF 5.0 Server installed. On this box, CFEXECUTE runs fine. The CFEXECUTE calls wscript.exe which runs a VBScript to convert uploaded Word and Excel documents to HTML.
We also a test server, ODYSSEY, which is an NT box with CF 5.0 Server installed. On this box, CFEXECUTE will not execute.
Here is the entire code of the template:
<cfoutput>
<cfexecute
name="C:\WinNT\System32\wscript.exe" arguments="e:\inetpub\ acf13.doc e:\inetpub\</cfexecute>
</cfoutput>
(Note, the CFOUTPUTs are there because the arguments are normally dynamically generated. We hardcoded them for debugging purposes.)
OK, here is where it gets weird. I can run the above code from the command prompt on ODYSSEY:
c:>wscript.exe e:\inetpub\ acf13.doc e:\inetpub\ and it runs fine.
But, if I run it by calling the CF template, the VBScript is never executed. I have messageboxes that pop up in three places in the script if it runs, which is how I monitor whether the VBScript runs.
Both GENESIS's and ODYSSEY's CF App Server are currently set to run as an account, CFService. When I set ODYSSEY to run as the system account and check the box to allow interaction with the desktop, the page still does not execute. BUT, when it is running as the system account, if I remove those two CFOUTPUT tags, then the page executes the VBScript??!!??$^%$#
Our gut feeling is that this is a permissions problem, but we cannot figure out where, what, how, when, or who.
When I posted this problem yesterday, I got some great suggestions for editing the page to make it work, but my boss and I are way too fixated on this problem for that. We want this to work on ODYSSEY just like it does on GENESIS.
I have read the thread in the Support Forum on the Macromedia/Allaire site about this bug, and we have tried everything mentioned there. As a matter of fact, that is how I found out that the page would execute without the CFOUTPUTs when the Service was running under the system account.
Any ideas, resources, or references would be greatly appreciated.
Kathryn
We have a development server, GENESIS, which is an NT box with CF 5.0 Server installed. On this box, CFEXECUTE runs fine. The CFEXECUTE calls wscript.exe which runs a VBScript to convert uploaded Word and Excel documents to HTML.
We also a test server, ODYSSEY, which is an NT box with CF 5.0 Server installed. On this box, CFEXECUTE will not execute.
Here is the entire code of the template:
<cfoutput>
<cfexecute
name="C:\WinNT\System32\wscript.exe" arguments="e:\inetpub\ acf13.doc e:\inetpub\</cfexecute>
</cfoutput>
(Note, the CFOUTPUTs are there because the arguments are normally dynamically generated. We hardcoded them for debugging purposes.)
OK, here is where it gets weird. I can run the above code from the command prompt on ODYSSEY:
c:>wscript.exe e:\inetpub\ acf13.doc e:\inetpub\ and it runs fine.
But, if I run it by calling the CF template, the VBScript is never executed. I have messageboxes that pop up in three places in the script if it runs, which is how I monitor whether the VBScript runs.
Both GENESIS's and ODYSSEY's CF App Server are currently set to run as an account, CFService. When I set ODYSSEY to run as the system account and check the box to allow interaction with the desktop, the page still does not execute. BUT, when it is running as the system account, if I remove those two CFOUTPUT tags, then the page executes the VBScript??!!??$^%$#
Our gut feeling is that this is a permissions problem, but we cannot figure out where, what, how, when, or who.
When I posted this problem yesterday, I got some great suggestions for editing the page to make it work, but my boss and I are way too fixated on this problem for that. We want this to work on ODYSSEY just like it does on GENESIS.
I have read the thread in the Support Forum on the Macromedia/Allaire site about this bug, and we have tried everything mentioned there. As a matter of fact, that is how I found out that the page would execute without the CFOUTPUTs when the Service was running under the system account.
Any ideas, resources, or references would be greatly appreciated.
Kathryn