RUNUBE

I am trying to do a RUNUBE command in Windows on the Enterprise server. I have read the Server and Workstation Administration guide. I am running the command from the bin32 folder and directly on the console. I have my command and log below. Any ideas why I am getting this error? My system is E1 9.0 TR 8.98.2.1.CPU.

Command:

D:\JDEdwards\E900\DDP\system\bin32>RUNUBE JDE JDE DV900 R0006P XJDE0001

Log:

3212/3156 MAIN_THREAD Tue Jan 19 10:49:30.063000 ipcmisc.c299
IPC1200009 - lockIPCInit couldn't create mutex Global\~JDEIni~6000, err 5.

3212/3156 MAIN_THREAD Tue Jan 19 10:49:30.063001 ipcmisc.c299
IPC1400001 - IPC routine called without successful IPC initialization.

3212/3156 MAIN_THREAD Tue Jan 19 10:49:30.064000 ipcmisc.c299
IPC1400001 - IPC routine called without successful IPC initialization.

3212/3156 MAIN_THREAD Tue Jan 19 10:49:30.064001 ipcmisc.c299
ipcSawInit: Error: ipcCreateResource 27

3212/3156 MAIN_THREAD Tue Jan 19 10:49:30.065000 ipcmisc.c299
IPC1400001 - IPC routine called without successful IPC initialization.

3212/3156 MAIN_THREAD Tue Jan 19 10:49:30.066000 ipcmisc.c299
Error: ipcLockResource 27

3212/3156 MAIN_THREAD Tue Jan 19 10:49:30.066001 Runube.c454
process <---

Do I need to be signed in with the same user that is running the E1 service? Currently the E1 service is running as Local System and I am signed directly onto the machine with JDE. Should I change the service to use the JDE domain account?

Is that correct syntax for the RUNUBE command ? I thought with TR 8.97 (or application release 8.12) and above the password had to be supplied in a text file , and the file location was one of the arguments passed to the command.

I presume you are able to successfully run UBE's on this server from BV..?

Also try the runubexml command. It is a lot more flexible and also returns the job number after submission which runube does not

I have only tried running the command signed on as the windows user that runs the JDE services. But if your environment variables are defined properly (under system variables and not user), I think it should still work ,since you are calling the command from the bin32 directory it self

Hi,

With your tools release level the syntax may be incorrect. You can either user an operator to promt -p that will promt for a user name and password or -f to pass it via a txt file.

Try and use the following syntax

First you need to create a txt file for the password. In my example I have created PWD.TXT. Make sure the user id and password are on different lines.

runube -f D:\JDEdwards\E812\DDP\BATFILE\PWD.txt PY812 *ALL R0010P XJDE0001 QBATCH BATCH HOLD SAVE

I am able to submit UBEs successfully in BV. I am referencing the 8.98 Server and Workstation Administration Guide and its example is:

runube KL5595218 KL5595218 PROD R0006P XJDE0001 QBATCH Interactive Print Delete printer_1

Joel, I did try your command and got the same exact results in the log.

Command:

runube -f D:\JDEdwards\E812\DDP\batfile\pwd.txt DV900 *ALL R0010P XJDE0001 QBATCH BATCH HOLD SAVE

Log:

5956/2448 MAIN_THREAD Tue Jan 19 12:42:04.184000 ipcmisc.c299
IPC1200009 - lockIPCInit couldn't create mutex Global\~JDEIni~6000, err 5.

5956/2448 MAIN_THREAD Tue Jan 19 12:42:04.184001 ipcmisc.c299
IPC1400001 - IPC routine called without successful IPC initialization.

5956/2448 MAIN_THREAD Tue Jan 19 12:42:04.185000 ipcmisc.c299
IPC1400001 - IPC routine called without successful IPC initialization.

5956/2448 MAIN_THREAD Tue Jan 19 12:42:04.186000 ipcmisc.c299
ipcSawInit: Error: ipcCreateResource 27

5956/2448 MAIN_THREAD Tue Jan 19 12:42:04.186001 ipcmisc.c299
IPC1400001 - IPC routine called without successful IPC initialization.

5956/2448 MAIN_THREAD Tue Jan 19 12:42:04.187000 ipcmisc.c299
Error: ipcLockResource 27

5956/2448 MAIN_THREAD Tue Jan 19 12:42:04.187001 Runube.c454
process <---

I will try the runubexml command and see if I can get some more info from the system. I am not seeing anything in the Tools 8.98 Server and Workstation Administration Guide on this command. Does anyone have an example of the command?

Also, I will change the E1 service owner to JDE instead of Local System and try that.

Screen capture from my 9.0 server running 8.98.1.4:

E:\JDEdwards\E900\DDP\system\bin32>runube
Using User/Password information on the command line has been deprecated. Although it will continue to work in this release, it will no longer be available as an option in a future release. Please switch to using one of the -p -f or -d options instead.

New Usage: runube <[-p|-P] [-f|-F|-d|-D FilePath] [user password]>
<Environment>
<Role>
<ReportName>
<VersionName>
<JobQueue>
<"Interactive"|"Batch">
<"Print"|"Hold">
<"Save"|"Delete">
[Printer]

-p|-P Prompts for user/password information

-f|-f FilePath Reads user/password information from the plain text file that is specified in FilePath.

-d|-D FilePath Reads user/password information from the plain text file, and indicates the automatic removal of the file.

How are you connecting to the Windows Enterprise Server..? If you connect thru an RDP connection , it will use separate IPC resources than those used by the E1 services. Check SOLUTION ID: 201006370

To start with I would change the services to run with the JDE domain user and then log on to the box with the same credentials either using Netmeeting Remote Desktop sharing , or do a telnet session, or a VNC like program

For runubexml you need to run a few commands.

If you have never used runubexml before , the first command to run is

runubexml G CREATE_XML <template.xml>

This creates a file called template.xml in your bin32 directory. In the above command you can call the file name what ever you want.

Once the file is created open this XML file , and edit it to populate user id , env , role , password , report name , version etc.

Then run this command

runubexml S <template.xml> <report_version.xml>

template.xml is the file you just edited , and report_version.xml will be the name of the new file created

report_version.xml is basically the main input file for your runubexml submission. If you open this file you will actually be able to see the versions specs in terms of data selection and PO values etc.

Next to submit the ube run the below command

runubexml S <report_version.xml> <report_output.xml>

Here report_output.xml is the file that will created after the submission of the job. The file will contain the submission status and also the job number returned by the Queue Kernel.

We figured out that the issue was that you have to be logged onto the machine with the same user that is running the JDE E1 service. We had Local System running the JDE E1 service. Once we changed this to use JDE and we logged onto the box with JDE it worked fine. Even worked using RDP.

Thanks everyone!

[ QUOTE ]
I am trying to do a RUNUBE command in Windows on the Enterprise server. I have read the Server and Workstation Administration guide. I am running the command from the bin32 folder and directly on the console. I have my command and log below. Any ideas why I am getting this error? My system is E1 9.0 TR 8.98.2.1.CPU.


[/ QUOTE ]


My standard RUNUBE reply template:


"In order to execute RUNUBE from the Enterprise Server it is necessary that you be logged on to
the server console using the same NT username that is running the OneWorld services

OneWorld processes use IPC (memory) resources that cannot be modified by users other
than the owner of the process"

Please check you are not connected through Terminal Services, use the actual console display to exec RUNUBE.

There is a tip in Metalink3 which was solved by "Setting SHMMIN=1 and adding DB server to host file " , but it was a Sun box.