Q:
Transport problem
Hi!
Here the history of problem. Some time ago we had a following landscape: server1 with system SANDBOX and server2 with system TEST. We moved system TEST to server1. Now we have two systems – SANDBOX and TEST – on server1. Server2 has now the system PRODUCTION.
The problem is that we can’t start up systems SANDBOX and TEST simultaneously. We get in log:
“WARNING: Background job RDDIMPDP could not be started or terminated abnormally. Please check that the R/3 system is running. Please check the system. Use transactions SM21, SM37, SM50. WARNING: (This warning is harmless if no further warnings follow.)”
And transport requests from TEST to PRODUCTION hang. I think we need to reconfigure transport from SANDBOX to TEST with saving transport between TEST and PRODUCTION. But how? What to see, what to change? Please help.
Here the history of problem. Some time ago we had a following landscape: server1 with system SANDBOX and server2 with system TEST. We moved system TEST to server1. Now we have two systems – SANDBOX and TEST – on server1. Server2 has now the system PRODUCTION.
The problem is that we can’t start up systems SANDBOX and TEST simultaneously. We get in log:
“WARNING: Background job RDDIMPDP could not be started or terminated abnormally. Please check that the R/3 system is running. Please check the system. Use transactions SM21, SM37, SM50. WARNING: (This warning is harmless if no further warnings follow.)”
And transport requests from TEST to PRODUCTION hang. I think we need to reconfigure transport from SANDBOX to TEST with saving transport between TEST and PRODUCTION. But how? What to see, what to change? Please help.
ASKED:
Jan 12 2009 3:56 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
