2007 May 22 6:09 PM
We have a custom .exe program that is working in our old R/3 46 system 32 bit system.
We are moving to ECC6 R/3 which is a 64 bit SAP system. We excute the same custom .exe executable via SXPG_COMMAND_EXECUTE and the program hangs.
We have tied various security setting and traps which indicate the parameter is passed and the .exe program starts but hungs
Any ideas
2007 May 22 7:02 PM
For the two questions about the program:
The program executes on the App server the program is written in C++
I assume that the underlying OS of the App Server is 64-bit as well then.
In which, you will need to re-compile the source code on a 64-bit C++ compiler
OR
Write a new program... why not create the program in ABAP and eliminate future headaches?
2007 May 22 6:30 PM
Is this .exe being executed on the App Server or on a local client?
2007 May 22 6:31 PM
2007 May 22 7:02 PM
For the two questions about the program:
The program executes on the App server the program is written in C++
2007 May 22 7:05 PM
I assume that the underlying OS of the App Server is 64-bit as well then.
In which, you will need to re-compile the source code on a 64-bit C++ compiler
OR
Write a new program... why not create the program in ABAP and eliminate future headaches?
2007 May 22 7:07 PM
OR
Speak to the OS vendor to see if they have a "translation utility" that will enable 32-bit apps to run in the new 64-bit environment.
2007 Aug 13 4:58 PM
I believe the problem is caused by the value of the operatingsystem on the SXPG_COMMAND_EXECUTE. We used the SY-OPSYS value which is all upper case. Once we set it to 'Windows NT' it worked! Thanks for the help........
| User | Count |
|---|---|
| 6 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |