I have an application which needs to talk to an MYOB data file. The ASP page uses an ODBC connection. After research and talks with MYOB the only way we have found that works is MYOB needs to be running on the server.
Yesterday hours were spent identifying how to get this done. The following post is what I found most useful:
http://www.tek-tips.com/viewthread.cfm?qid=1181274&page=1
After:
Ø registering the aspexec.dll
Ø Changing security in Premier12 folder to have Network Service, Local Service, Users to have Full Control
Ø Changing security for system32\ntdll.dll for all users to have Full Control
Ø Changing WWW Service to Interact with Desktop
And running this code:

Dim Executor
Dim strResult
Set Executor = Server.CreateObject("ASPExec.Execute")
'Executor.Application = "C:\Windows\system32\Calc.exe"
Executor.Application = "C:\Premier12\myobp.exe"

Executor.Parameters = "\\melbdcsql02\company\myob\MYOB Premier\Premier 2008_09 Test.MYO"
Executor.ShowWindow = True
Executor.TimeOut = 120
strResult = Executor.ExecuteWinApp
Response.Write(strResult & "<BR>")

It fails to run the application. If we try to run the calc.exe or notepad.exe they appear in the processors tab in task manager but we do not see them. Any idea how we can get an application to run on the server initiated by ASP code on the client?
Is this to big of an issue? If we get it done can we close it? Or can MYOB run permanently on the server which may or may not be a good idea. We have top level access to the server and can change any settings
TYIA

__________________
Wind is your friend
Matt

ASPExec is a pretty ancient component, created in the days of IIS 2 and IIS 3. Whether it still works with current versions of IIS is anybody's guess.

You'd probably be better off just using the MS WSH shell.

Something like this:

Code:

Or you might need to prefix the call to the .exe with %ComSpec%

But I wouldn't expect any window to appear. Modern web servers don't want to allow apps to open windows on the server machine, for good reason.

Aftenoon...Trial and error has seems to tell me the MS WSH shell works on XP but seesm to fail on 2003 server. Or I should say running the code on XP makes it apear on the process tab in task manager however it does not on the 2003 server. Any suggesetions why? The 2003 server is the production environement.

Thanking you

__________________
Wind is your friend
Matt

Permissions?? You have to allow "out of process" components from IIS for WSH to work. It does *NOT* run in the same process as the web server. I've never worked with Win2003 Server, directly, so not sure. But that's the likely culprit. Just an IIS setting. Look in the docs for "out of process".