• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 190
  • Last Modified:

Trying to launch a program on 2012 Server from web page hosted on IIS

I'm trying to run an executable on our server when a visitor (authenticated Windows User) hits a webpage.
I have the authenticated access to the page figured out.
I have the asp page written that will be launched.    The asp page displays the message "Processing Job".   However, the part of the page where the batch file is launched doesn't work.     The batch file never launches and the .exe in a folder on the c drive, not within the IIS web files never runs     I know this must be a permission problem but I can't figure out where to set it.     I had this working on my 2003 server, but upgrades have forced me to get this working on a 2012 Server.  

----------------------------------------------------------
<html>
<%
Dim WSHell
Set WSHell = Server.CreateObject("Wscript.Shell")
WShell.Run "C:Jobs\doit.bat"
Set WShell = Nothing
%>
<body>
<p align="Left" style="margin-top: 0; margin-bottom: 0"><font size="6">Processing Job.</font></p>
</body>
</html>

-----------------------------------------

Doit.bat is nothing more than a reference to an executable in the same directory.   I have no problem launching the executable in the batch file running the batch file from the Server 2012 command prompt.

Any suggestions would be greatly appreciated.

Thanks

Gary
0
Gary Fuqua, CISSP
Asked:
Gary Fuqua, CISSP
  • 6
  • 2
1 Solution
 
Dan McFaddenSystems EngineerCommented:
The only issue I see in the script is the WShell.Run command has a bad path reference in it.  You have:


WShell.Run "C:Jobs\doit.bat"

When it should be:

WShell.Run "C:\Jobs\doit.bat"

You are missing the slash between "C:" and "Jobs\doit.bat"

Dan
0
 
Gary Fuqua, CISSPOwnerAuthor Commented:
Good eye.   Unfortunately, that is just a typo in the post.    The real code actually accesses a different file.   I was trying to simplify things for the post.
0
 
Dan McFaddenSystems EngineerCommented:
OK, then... you might want to grant IIS_IUSRS read and execute on the location of the batch file.

And make sure the identity of the Application Pool used by this web site is a member of the above group.

Dan
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Gary Fuqua, CISSPOwnerAuthor Commented:
Nope.  

I changed the the code slightly to try and debug

WShell.Run ("C:\Jobs\doit.bat",3,true)

Parameter "3" should open up a maximized window on server?   True should wait until the command is executed to proceed.

After making this change, I get

500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
0
 
Gary Fuqua, CISSPOwnerAuthor Commented:
I tried changing the identity of the app pool to local system....nothing.
0
 
David Johnson, CD, MVPOwnerCommented:
Did you also "grant IIS_IUSRS read and execute" permissions on that directory?
0
 
Gary Fuqua, CISSPOwnerAuthor Commented:
Thanks for the reply.   Yes. That has been done already.   No luck.
0
 
Gary Fuqua, CISSPOwnerAuthor Commented:
I have determined that my batch file is executing by putting a simple pipe operation in the file.

dir > c:\jobs\dir.txt

The problem that I have remaining is getting the executable referenced inside the batch file, in the same directory as the batch file to execute.     I wish I could echo the batch file to the screen, but that doesn't seem to work.
0
 
Gary Fuqua, CISSPOwnerAuthor Commented:
Getting closer...

I used the pipe option to output the results of my batch file execution

WShell.Run "C:Jobs\doit.bat >> c:\Jobs\doitresults.txt"

The results showed the the executable is running,   The parameters that I am passing to it are bad.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now