Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
I fixed my issue by assigning a target server to both RDDIMPDP jobs (normally you do not need to do that, but now helped for me)
| | | ---------------Original Message---------------
From: carrieBgraham
Sent: Wednesday, November 29, 2006 9:45 AM
Subject: Can anyone help with hung transport - Windows MSSQL SAP ECC 6.0
Transport remains in status 'import running'.
Initially had the following error the SLOG:
WARNING: System QAS. Warning. 20061129134211 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=QAS
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings
follow.)
Ran RDDNEWPP in as DDIC in 000 to reschedule RDDIMPDP job.
Following error found in dev_evt:
Wed Nov 29 22:43:09 2006
Trace File of External Event Raiser (Level=0, Append=1)
EventID: SAP_TRIGGER_RDDIMPDP
*** ERROR ***: Cannot determine mshost
Found that IP address and host name for QAS where missing from the hosts
file on the QAS server. Added this entry and restarted server.
Also implemented note 449270 by adding the following entry in the
TP_DOMAIN_DEV.PFL file:
QAS/SYSTEM_PF = E:\usr\sap\QAS\SYS\profile\DEFAULT.PFL
This solved the above two problems. However, transport is still in status
'import running'.
Removed the following entry from TRBAT in QAS:
HEADER P B 20061127092322
Still no change to the status of the QAS import queue.
Any help appreciated.
Regards,
Carolyn |
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Popular White Papers
In the Spotlight  _.____.__ |
