RE: Executing a program on a Windows 2003 server

["Shannon O'Donnell" <shannon.odonnell@xxxxxxxxxxxxxx>]

The RUNRMTCMD is passing a user id and password to W2003 yes? 

And it's the actual VB program that is being called via RUNRMTCMD that
is failing?  That is, you're not calling the VB app from RUNRMTCMD and
it's calling another process and it's this other process that is
failing?

We have no problems using RUNRMTCMD with Win2003 Server as long as the
profile we are using to logon with has enough authority to the files,
directories and commands we want to access.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Fisher, Don
Sent: Thursday, October 26, 2006 11:46 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Executing a program on a Windows 2003 server

I have a Visual Basic application that resides on a Windows 2003 server
with iSeries Access version 5.3 installed.  Using RUNRMTCMD, the server
either rejects the request to execute the application or just doesn't
execute the command specified.  I have the "Interact with desktop" of
the iSeries Remote Command service activated.  

Furthur examination of the archives revealed the option to use the rexec
a.p.i.  All of our user i.d.s are specified in a domain so I took Scott
Klements rexec example and specified "OURDOMAIN\SERVERUSER" as the user
i.d.  However, the server claims either the user i.d. or the password is
invalid.

If anyone has a clue what I might be doing wrong, I would appreciate
some assistance because I ran out of ideas a while ago.  I didn't have
these problems on our old Windows NT server.

Thank you in advance.

Donald R. Fisher, III
Project Manager
RoomStore, Inc.
(804) 784-7600 ext. 2124
dfisher@xxxxxxxxxxxxx