Incorrect distribution -Error while distributing GOA to R3 Backend system

Hi,
We have installed SRM server 5.5 and implementing contract Management
scenario with backend system R/3 4.6B.
In this scenario we are creating a Global Outline Agreement in SRM
system and distributing it to the back-end ERP system.
In SRM5.0 GOA (Trans.type GCTR) that are distributed at Header level
are failing to distribute to R/3 system v4.6b
We are getting this error message in SRM transaction SLG1: -
The error ocurred by processing event RELEASED_NEWLY with GUID
DCA7101B320134F1949F000347DE470F and object_id= 5600000054 " RECEPIENT
NOT FOUND"
The purchasing org , the plant has been mapped .Also vendor & material is maintained for the company & Plant .
The condition types are mapped in SRM
Pls suggest.
Regards,
Avinash

Hi Avinash,
In reference to your query about GOA, the distribution error might be beacause of the issues in BADI implementation.
By using the BADI you can define which document to be created in the backend.
BBP_CTR_BE_CREATE BADI can be used in SRM and BBP_CTR BADI can be used in back end R/3 for this purpose.
Check for the transaction types (GCTR) and the number ranges for the transaction types.
The GOA will either create a contract or a Scheduling agreement in R/3 back end after distribution.
Also refer the below SDN thread in this regard :
Re: Scheduling Agreement from GOA
Any further clarifications are welcome.
Award points for suitable answers.
Rgds,
Teja

Similar Messages

  • Error while posting return delivery to backend system

    Hi All,
    We are facing problem when we are posting return delivery. Currently we are in ECS implementation. Our SRM is 7.0 EHP3.
    Scenario goes as, SC is created then PO is created then further confirmation is created and on creating return delivery of this confirmation, this return delivery goes error in process.
    Now on further analyzing, I found out that outbound IDoc in SRM is getting posted successfully but when ECC receives this IDoc it is saying please enter reason for movement 122. This reason for return is already entered while creating the return delivery. But this reason is not flowing in IDoc (Message Type MBGMCR and Basic Type MBGMCR01) in SRM and further to ECC. This field MOVE_REAS in IDoc is populating blank.
    Can anybody help me resolving this problem? Any pointers or SAP notes related to can also be suggested.
    Thanks
    Siddarth

    Hi Siddarth,
    Please implement the note below, which is included in SP05.
    2007628 - Return delivery cannot be posted in backend system as reason for return delivery is empty
    Regards,
    Wendy

  • Error while distributing the ALE distribution model through BD64

    Hi,
    I am getting the error while distributing the distribution model through BD64. The error is as follows:
    "Model view DVGDVH has not been updated
    Reason: the following ALE connection already exists in model view TESTMOD".
    What does this means?
    Regards,
    Soumya.

    Dear Sapera,
    I faced the same problem last night.
    We just manually deleted the distribution model from receiving system.
    Log on to receiving system => BD64 => change/dispay => edit => delete => Save.
    Once deleted log in to sender system and then select model and distribute again.
    by performing this we were able to resolve this issue.
    Warm regards,

  • Error while reading ID of own business system from the SLD

    HI guys when trying to send Idoc from my R/3 system to SUS i am getting the following error in XI
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
      <SAP:P1>DSM</SAP:P1>
      <SAP:P2>900</SAP:P2>
      <SAP:Stack>Error while reading ID of own business system from the SLD for system DSM and client 900</SAP:Stack>
    I checked in sxmb_adm on both the ends on Xi as well as on my SUS server in Xi the role is the Integration server and on the SUS it is Application server also checked SLDAPICUST which is configured rite. Plz help me to come out of the problem.
    Regards,
    Anand

    Hi Anand,
      check the two thing's in XI.
    1. First created technical system in XI to identify your XI server (Web as ABAP and Web AS Java)
    2. Create the business system based on above technical system and select the role of business system is Integration server.
      URL : http://<hostname>:<ICM Port>/sap/xi/engine?type=entry.
    3. Create the technical system based on your SAP R/3 system.
    4. Create the business system based on your SAP R/3 system.
    here you need to select role of business system : Application system.
      related integration server is : <XI System SID has to come>
    and try to refresh the initical cache once ...
    http://<hostname>:<j2ee stack port>/CPACache/refresh?mode=full
    after all the things post what is the problem you are faceing.
    Regards,
    Venu.

  • Error while reading ID of own business system from the SLD for system D18

    Dear guru's,
    I have almost completed a file2proxy scenario but I'm stuk on the following.
    When sending a message the outbound adapter says:
    <b>Error while reading ID of own business system from the SLD for system D18 and client 200</b>
    What's the problem? I'm using a HTTP connection in the comm. channel. In this http connection a user with SAP_ALL is defined.
    Any suggestions?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
      <SAP:P1>D18</SAP:P1>
      <SAP:P2>200</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading ID of own business system from the SLD for system D18 and client 200</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Login to system D18 and client 200 and check the TC SLDCHECK and also as per my pervious message check the entries in the SLDAPICUST, it should point to the Server on which SLD is present usually XI server https.
    Actually what happens in this error is when you are done with the configuration part in the ID, you are trying to eceute the scenario File to proxy, when it comes to identify the receiver system which is D18 clnt 200, it goes to SLD to check it and SLD is trying to ping to the machine D18 this connection is set from the TC SLDAPICUST on the machine D18.
    here the problem is that either the D18 is not able to ping to the SLD and also try refreshing the SLD cache.
    Hope you problem is fixed

  • Error while reading ID of own business system from the SLD for system DPI

    Hi All,
    My sceanrio is Proxy to JDBC. and its B2B. am sending the data from BI system and based on the country field from the source, table is decided and value is updated in the table.
    In RWB->Component Monitoring->Adapter Engine->Test Message, I have given the Sender component,Receiver Party,Receiver component,Interface,Interface Namespace,userid and password,Quality of Service and pasted the payload.
    Now I am getting the error :Error While Sending Message: Error stack from response: Error while reading ID of own business system from the SLD for system DPI and client 001 Internal error in Landscape Directory
    Please help me out.
    Thanks
    Kiruthi
    Edited by: kiruthiga balusamy on Nov 24, 2009 4:02 PM

    Hi,
    Check transaction SLDAPICUST for correct SLD configuration.
    http://help.sap.com/saphelp_nw70/helpdata/EN/0b/8512417301ee6fe10000000a1550b0/content.htm
    ~Sanv...

  • SLD Error in IE:Error while reading ID of own business system from the SLD

    Dear Champs,
    Scenario : JDBC to Proxy(APO system)
    We are getting below error in MONI UAT Box. All other interface are working fine but we are facing issue for a particular Bussiness System also logical system are maintained properly.the same interface is working fine in other UAT box.
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
      <SAP:P1>R/3 Sys ID</SAP:P1>
      <SAP:P2>"Client"</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading ID of own business system from the SLD for system "R/3 Sys ID"and client "Clnt no"</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    Regards,
    Manikandan

    Hi Mani,
    Solution 1:
    Check if the techncal system has associated Business system. I think there is something wrong in your SLD configuration and try to correct it.
    Solution 2:
    Create a Business system in the ID, and create the communication channel do the respective changes in ID ( I.e Receiver agreement, Receiver determination & Interface).

  • Distribution of GOA to the backend system

    Dear Experts,
    I am working in Extended classic scenario (SRM 5.0). We are planing to configure GOA.
    Can any one give me the steps required to configure GOA and distribute the contracts to the back end system.
    When I create the GOA as of now GOA is getting created but not distributed.
    Regards,
    B.N.Karthikeyan

    Hi,
    Here are the main configuration steps needed:
    1: Make sure you have done the following in customizing:                 
       When you go to define transaction type  and you                       
       choose the entry with BUS2000113, then you click Transaction type     
       go to DETAIL screen of GCTR and choose Global Outline                 
       agreement as a specification.                                                                               
    2: You can follow these steps.                                           
       1. Go to the transaction WEDI                                         
       2. Goto IDoc menu and select Partner Profile (or F6)                  
       3. In Partner Profile, Goto PartnerType LS                            
       4. Click on the client eg. ABCCLNT300                                 
       5. In "Inbound parmtrs" make an entry for BLAORD.Enter the client as  
       Partner number. BLAO as Process Code.                                                                               
    3: In the R3 backend system,                                             
       maintain BLAORD as inbound message type, and maintain                 
       BLAREL as outbound message type                                                                               
    4: One of the requirements for setting up GOA is:                        
       Mapping of the appropriate products,product categories, condition     
       types, document IDs, transaction types and text iDs in the BAdis:     
       *IN EBP  > BBP_CTR_BE_CREATE                                          
    IN the backend system: BBP_CTR                                      
    Any GOA contract in EBP has to be mapped in R/3 with the corresponding   
    entry for conditions i.e 01CT to synchronise the two systems.            
    If the conditions are not mapped, the idocs will not be created.         
    Hence, please map the conditions and check for the distribution.         
    It is also an option to try:                                           
    Please run the function module 'BBP_PD_CTR_TRANSFER', this FM posts the
    IDOC in R/3 and add an entry in BBP_DOCUMENT_TAB,                      
    afterwards call report 'CLEAN_REQREQ_UP' which updates the status.                                                                               
    Kindly ensure all customizing and settings are correct in both SRM and 
    R/3 backend in order for the GOA to pass from systems without issues.  
    I hope this helps,
    Kind Regards,
    Lisa

  • Error while transporting database index into quality system

    Hello,
    I am getting an error while transporting a new index in quality system.
    I have created a new index for table VBFA in TRD and activity the object without errors. I even adjusted the database table using database utility.
    While transporting the request there was a strange error "R3TRTABLVBFA was repaired in this system".
    I retransported the objects using a new request. However I still got the same error.
    Please help.

    Navin,
    No idea about the error you have mentioned but check the SAP Notes 185530 and see if you can avoid creating an index.In this Notes it is clearly mentioned on how to use VBFA table without any performance issues.
    K.Kiran.

  • FJS-00012 ERROR while executing script in start SAP system

    Hi experts,
    I am getting error in the Oracle preload actions while installing the SAP 4.7 using the ORacle 9.2.0.1..
    FJS-00012  Error when executing script in start SAP system(post processing)
    My comp configuration is as follows:
    160 gb hard disk
    RAM 1GB
    OS: win 2003 server enterprise edition
    oracle 8.1.7
    During the Database Load (post processing) section of the
    installation, i get an error and the installation fails.
    I am giving all the logs here including the trace log and the
    Sapview.log file ans sapinst.
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: START OF LOG: 20070511002459
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#5 $ SAP
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe -ctf I E:\db3\EXPORT3/DATA/SAPVIEW.STR C:\SAPinst ORACLE KERNEL/DDLORA.TPL C:\SAPinst ORACLE KERNEL/SAPVIEW.TSK ORA -l C:\SAPinst ORACLE KERNEL/SAPVIEW.log -o D
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: job completed
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: END OF LOG: 20070511002500
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: START OF LOG: 20070511070423
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#5 $ SAP
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: version R6.20/V1.2
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE KERNEL/SAPVIEW.cmd -l C:\SAPinst ORACLE KERNEL/SAPVIEW.log -stop_on_error
    DbSl Trace: Got ORACLE_HOME=D:\oracle\ora81 from environment
    DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Logon as OPS$-user to get SAPESA's password
    DbSl Trace: Connecting as /@ESA on connection 0 ...
    DbSl Trace: Attaching to DB Server ESA (con_hdl=0,svchp=002BD418,svrhp=002BD224)
    DbSl Trace: Starting user session (con_hdl=0,svchp=002BD418,srvhp=002BD224,usrhp=00304E94)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=002BD418,usrhp=00304E94)
    DbSl Trace: Now I'm disconnected from ORACLE
    DbSl Trace: Try to connect with default password
    DbSl Trace: Connecting as SAPESA/<pwd>@ESA on connection 0 ...
    DbSl Trace: Starting user session (con_hdl=0,svchp=002BD418,srvhp=002BD224,usrhp=00304E94)
    DbSl Trace: Now I'm connected to ORACLE
    DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
    DbSl Trace: Database instance esa is running on MALTI with ORACLE version 8.1.7.4.1 since 20070511
    (DB) INFO: connected to DB
    (DB) INFO: /SAPTRX/A_CONDF4 created
    (DB) INFO: /SAPTRX/VDASFEV created
    (DB) INFO: /SAPTRX/VDASFPAR created
    (DB) INFO: /SAPTRX/VD_AOMIL created
    (DB) INFO: /SAPTRX/VD_AOPAC created
    (DB) INFO: /SAPTRX/VD_AOPAE created
    (DB) INFO: /SAPTRX/VD_AOPAI created
    (DB) INFO: /SAPTRX/VD_AOPAR created
    (DB) INFO: /SAPTRX/VD_AOTD1 created
    (DB) INFO: /SAPTRX/VD_AOTD2 created
    (DB) INFO: /SAPTRX/VD_AOTDD created
    (DB) INFO: /SAPTRX/VD_AOTYP created
    (DB) INFO: /SAPTRX/VD_ASPAR created
    (DB) INFO: /SAPTRX/VD_CONDL created
    (DB) INFO: /SAPTRX/V_AODD02 created
    (DB) INFO: /SAPTRX/V_DD03 created
    (DB) INFO: /SAPTRX/V_DD03X created
    (DB) INFO: /SDF/SMODICOMP created
    (DB) INFO: /SDF/SMODIDEVC created
    (DB) INFO: /SDF/UMOD_COMP created
    (DB) INFO: ACEPSOIT_UPD created
    (DB) INFO: ADJV_TRANS_DIF created
    (DB) INFO: AFFWV0 created
    (DB) INFO: AFKO_LAUFN created
    (DB) INFO: AFSPLIT created
    (DB) INFO: AFVCP created
    (DB) INFO: ALM_ME_T003O_IS created
    (DB) INFO: ALM_ME_T350I created
    (DB) INFO: ALM_ME_TQ80_T created
    (DB) INFO: ANEKPV created
    (DB) INFO: APOUPD created
    (DB) INFO: APPL_DEVC created
    (DB) INFO: APPL_DIAL created
    (DB) INFO: APPL_DOMA created
    (DB) INFO: APPL_DTEL created
    (DB) INFO: APPL_ENQU created
    (DB) INFO: APPL_FUGR created
    (DB) INFO: APPL_FUGRG created
    (DB) INFO: APPL_FUNC created
    (DB) INFO: APPL_INDX created
    (DB) INFO: APPL_MCOB created
    (DB) INFO: APPL_MENU created
    (DB) ERROR: DDL statement failed
    (CREATE VIEW "APPL_MODS" ( "NAME" , "TYP" , "MEMBER" , "DEVCLASS"  ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X')
    DbSlExecute: rc = 103
      (SQL error 942)
      error message returned by DbSl:
    ORA-00942: table or view does not exist
    DbSl Trace: Disconnecting from connection 0 ...
    DbSl Trace: Closing user session (con_hdl=0,svchp=002BD418,usrhp=00304E94)
    DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=002BD418,srvhp=002BD224)
    DbSl Trace: Now I'm disconnected from ORACLE
    (DB) INFO: disconnected from DB
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    D:\usr\sap\ESA\SYS\exe\run/R3load.exe: END OF LOG: 20070511070433
    SAPINST
    INFO 2007-05-10 23:59:05
    Processing of host operation t_HostInfo_SHARED succeeded.
    INFO 2007-05-10 23:59:16
    The 'saploc' share exists at directory 'D:\usr\sap'. Choosing drive D: as SAP System drive.
    INFO 2007-05-10 23:59:21
    Copying file E:/KERNEL/NT/COMMON/OraVolatileDatabaseParameters.xml to: OraVolatileDatabaseParameters.xml.
    INFO 2007-05-10 23:59:21
    Creating file C:\SAPinst ORACLE KERNEL\OraVolatileDatabaseParameters.xml.
    INFO 2007-05-11 00:01:52
    Copying file E:/db1/EXPORT1/DB/ORA/DBSIZE.XML to: DBSIZE.XML.
    INFO 2007-05-11 00:01:52
    Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.XML.
    INFO 2007-05-11 00:01:52
    Copying file system node E:\db1\EXPORT1/DB/ORA/DBSIZE.XML with type NODE to DBSIZE.XML succeeded.
    INFO 2007-05-11 00:01:52
    Processing of all file system node operations of table tORA_filecopy succeeded.
    INFO 2007-05-11 00:01:52
    Copying file E:/db1/EXPORT1/DB/DDLORA.TPL to: DDLORA.TPL.
    INFO 2007-05-11 00:01:52
    Creating file C:\SAPinst ORACLE KERNEL\DDLORA.TPL.
    INFO 2007-05-11 00:01:52
    Copying file system node E:\db1\EXPORT1/DB/DDLORA.TPL with type NODE to DDLORA.TPL succeeded.
    INFO 2007-05-11 00:01:52
    Processing of all file system node operations of table tORA_filecopy succeeded.
    INFO 2007-05-11 00:01:57
    Moving file C:/SAPinst ORACLE KERNEL/DDLORA.TPL to: orig_ddl_ora_tmp.tpl.
    INFO 2007-05-11 00:01:57
    Moving file C:/SAPinst ORACLE KERNEL/changed_ddl_ora_tmp.tpl to: DDLORA.TPL.
    INFO 2007-05-11 00:01:57
    Removing file C:/SAPinst ORACLE KERNEL/orig_ddl_ora_tmp.tpl.
    INFO 2007-05-11 00:03:00
    Package table created
    PHASE 2007-05-11 00:04:15
    SAP R/3 Enterprise 4.70 for Oracle
    PHASE 2007-05-11 00:04:15
    SAP Web Application Server
    PHASE 2007-05-11 00:04:15
    Request common parameters of SAP System
    PHASE 2007-05-11 00:04:15
    Create operating system accounts
    INFO 2007-05-11 00:04:15
    Copying file C:/SAPinst ORACLE KERNEL/keydb.xml to: C:/SAPinst ORACLE KERNEL/keydb.1.xml.
    INFO 2007-05-11 00:04:15
    Creating file C:\SAPinst ORACLE KERNEL\keydb.1.xml.
    INFO 2007-05-11 00:04:15
    Copying file C:/SAPinst ORACLE KERNEL/OraVolatileDatabaseParameters.xml to: C:/SAPinst ORACLE KERNEL/OraVolatileDatabaseParameters.1.xml.
    INFO 2007-05-11 00:04:15
    Creating file C:\SAPinst ORACLE KERNEL\OraVolatileDatabaseParameters.1.xml.
    INFO 2007-05-11 00:04:15
    Copying file C:/SAPinst ORACLE KERNEL/DBSIZE.XML to: C:/SAPinst ORACLE KERNEL/DBSIZE.1.XML.
    INFO 2007-05-11 00:04:15
    Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.1.XML.
    INFO 2007-05-11 00:04:15
    Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1004 ACCOUNTNAME=malti\SAP_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2007-05-11 00:04:15
    Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1005 ACCOUNTNAME=malti\SAP_ESA_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2007-05-11 00:04:15
    Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1006 ACCOUNTNAME=malti\SAP_ESA_GlobalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Global Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2007-05-11 00:04:15
    Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1007 ACCOUNTNAME=ORA_ESA_DBA ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Operator Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2007-05-11 00:04:15
    Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1008 ACCOUNTNAME=ORA_ESA_OPER ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2007-05-11 00:04:15
    Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
    INFO 2007-05-11 00:04:18
    Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1009 ACCOUNTNAME=malti\esaadm ACCOUNTTYPE=USER DESCRIPTION=SAP System Administrator MEMBERSHIP=malti\SAP_ESA_GlobalAdmin,malti\Users,Administrators,ORA_ESA_DBA,ORA_ESA_OPER,malti\SAP_LocalAdmin,malti\SAP_ESA_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*...  succeeded.
    INFO 2007-05-11 00:04:18
    Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1010 ACCOUNTNAME=malti\SAPServiceESA ACCOUNTTYPE=USER CONDITION=YES DESCRIPTION=SAP System Service Administrator MEMBERSHIP=malti\SAP_ESA_GlobalAdmin,Administrators,ORA_ESA_DBA,ORA_ESA_OPER,malti\SAP_LocalAdmin,malti\SAP_ESA_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*...  succeeded.
    INFO 2007-05-11 00:04:18
    Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
    PHASE 2007-05-11 00:04:18
    Request operating system user information
    PHASE 2007-05-11 00:04:18
    Request operating system user information
    PHASE 2007-05-11 00:04:18
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    PHASE 2007-05-11 00:04:19
    Request operating system user information
    INFO 2007-05-11 00:04:20
    Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1488183395-3813774055-1856681103-500' on host 'malti'!
    INFO 2007-05-11 00:04:20
    Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1488183395-3813774055-1856681103-500' on host 'malti'!
    INFO 2007-05-11 00:04:20
    Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1488183395-3813774055-1856681103-500' on host 'malti'!
    INFO 2007-05-11 00:04:20
    Evaluating all 'tNT_RegistryEntries' table rows succeeded.
    INFO 2007-05-11 00:04:21
    Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
    INFO 2007-05-11 00:04:22
    Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata6\esa_16 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata1\esa620_1.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata1\esa620_1 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata2\esa620_2.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata2\esa620_2 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata3\esa620_3.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata3\esa620_3 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata4\esa620_4.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata4\esa620_4 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata4\esa620_5.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata4\esa620_5 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata5\esa620_6.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata5\esa620_6 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata5\esa620_7.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata5\esa620_7 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata6\esa620_8.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata6\esa620_8 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata6\esa620_9.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata6\esa620_9 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata6\esausr_1.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata6\esausr_1 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata2\roll_1.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata2\roll_1 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata3\temp_1.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata3\temp_1 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Creating directory D:\oracle\ESA\sapdata1\system_1.
    INFO 2007-05-11 00:05:39
    Creating file system node D:\oracle\ESA/sapdata1\system_1 with type DIRECTORY succeeded.
    INFO 2007-05-11 00:05:39
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2007-05-11 00:05:40
    Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
    INFO 2007-05-11 00:05:40
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2007-05-11 00:05:41
    Creating file D:\oracle\ora81\database\initESA.ora.
    INFO 2007-05-11 00:05:42
    Creating file D:\oracle\ora81\database\initESA.sap.
    INFO 2007-05-11 00:05:43
    Copying file E:/KERNEL/NT/COMMON/INSTALL/INITSID.DBA to: D:\oracle\ora81/database/initESA.dba.
    INFO 2007-05-11 00:05:43
    Creating file D:\oracle\ora81\database\initESA.dba.
    INFO 2007-05-11 00:05:44
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:05:45
    Moving file D:/oracle/ora81/database/initESA.ora to: orig_init_ora_tmp.txt.
    INFO 2007-05-11 00:05:45
    Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\oracle\ora81\database\initESA.ora.
    INFO 2007-05-11 00:05:45
    Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2007-05-11 00:05:46
    Creating file C:\SAPinst ORACLE KERNEL\oradim.log.
    INFO 2007-05-11 00:05:51
    See 'D:\oracle\ora81/bin/oradim -new -sid ESA -STARTMODE auto' output in 'C:\SAPinst ORACLE KERNEL\oradim.log'.
    INFO 2007-05-11 00:05:51
    'D:\oracle\ora81/bin/oradim -new -sid ESA -STARTMODE auto' returned with '0'.
    INFO 2007-05-11 00:05:52
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:05:57
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:06:02
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:06:27
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:06:29
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:06:51
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:06:54
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:07:21
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:07:24
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:07:27
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:07:29
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:07:31
    Moving file D:/oracle/ora81/database/initESA.ora to: orig_init_ora_tmp.txt.
    INFO 2007-05-11 00:07:31
    Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\oracle\ora81\database\initESA.ora.
    INFO 2007-05-11 00:07:31
    Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2007-05-11 00:07:32
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:07:34
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:08:09
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:08:12
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:08:48
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:08:50
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:09:26
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:09:29
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:10:04
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:10:06
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:10:42
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:10:44
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:11:20
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:11:22
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:11:57
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:12:00
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:12:35
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:12:37
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:13:13
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:13:15
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:13:51
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:13:53
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:14:29
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:14:31
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:15:09
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:15:11
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:15:48
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:15:50
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:16:26
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:16:28
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:17:04
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:17:07
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:17:43
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:17:45
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:18:22
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:18:24
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:19:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:19:03
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:19:39
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:19:42
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:20:21
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:20:24
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:21:02
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:21:05
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:21:43
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:21:45
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:22:24
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:22:27
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:23:06
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:23:08
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:23:47
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:23:50
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:23:54
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:23:56
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:12
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:15
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:41
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:43
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:46
    Moving file D:/oracle/ora81/database/initESA.ora to: orig_init_ora_tmp.txt.
    INFO 2007-05-11 00:24:46
    Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\oracle\ora81\database\initESA.ora.
    INFO 2007-05-11 00:24:46
    Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2007-05-11 00:24:46
    Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
    INFO 2007-05-11 00:24:47
    See 'D:\oracle\ora81/bin/lsnrctl stat' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
    INFO 2007-05-11 00:24:47
    'D:\oracle\ora81/bin/lsnrctl stat' returned with '3'.
    INFO 2007-05-11 00:24:47
    Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
    INFO 2007-05-11 00:24:48
    See 'D:\oracle\ora81/bin/lsnrctl start' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
    INFO 2007-05-11 00:24:48
    'D:\oracle\ora81/bin/lsnrctl start' returned with '0'.
    INFO 2007-05-11 00:24:49
    Copying file E:/KERNEL/NT/COMMON/INSTALL/ORADBUSR.SQL to: ./oradbusr.sql.
    INFO 2007-05-11 00:24:49
    Creating file C:\SAPinst ORACLE KERNEL\oradbusr.sql.
    INFO 2007-05-11 00:24:49
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:52
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    PHASE 2007-05-11 00:24:54
    Database Load
    INFO 2007-05-11 00:24:56
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:57
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:57
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:58
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:58
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:24:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:25:00
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:25:00
    Task files created
    INFO 2007-05-11 00:25:00
    Command files created
    INFO 2007-05-11 00:25:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:25:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 00:25:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    ERROR 2007-05-11 02:18:03
    MSC-01015  Process finished with error(s), check log file C:\SAPinst ORACLE KERNEL/SAPAPPL1.log
    INFO 2007-05-11 02:18:03
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    ERROR 2007-05-11 02:44:07
    MSC-01015  Process finished with error(s), check log file C:\SAPinst ORACLE KERNEL/SAPSSEX2.log
    INFO 2007-05-11 02:44:07
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 03:55:07
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 04:25:07
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 04:42:08
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 04:47:08
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 04:55:22
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 04:57:22
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 04:59:22
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 05:01:22
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 05:03:22
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 05:04:23
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 05:05:23
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-05-11 07:04:33
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    ERROR 2007-05-11 07:04:33
    MSC-01015  Process finished with error(s), check log file C:\SAPinst ORACLE KERNEL/SAPVIEW.log
    ERROR 2007-05-11 07:04:33
    FJS-00012  Error when executing script.
    THANKS ALLL IN ADVANCE,
    Regards,
    Malti

    no space left on devices...
    ==> "<b>MOS-01109 Needed space on mountpoint F:/ is 5.248e07 KB, but got only 4.26433e07 KB.</b>"
    and others...
    -> provide more space and restart
    GreetZ, AH

  • Getting Runtime Error while Activating Characteristics in BW sandbox system

    Hi, i m getting  runtime error while activating Characteristics. Error as All InfoObjects Already Saved(locked)
    Short Text
    SQL error 1691 occurred when accessing program "GP4H8Z73D1WOGH7XBIZ54N5GXEG "
       Runtime Errors         DBIF_REPO_SQL_ERROR
    even if creating a new Characteristics same error is comming.
    Key Figures are getting created successfully but problems is comming only with Characteristics. Please Help...
    Edited by: kush kumar on Mar 23, 2010 11:56 AM

    Hi,
    Follow bellow steps:
    a) Once check the Lock entries by useing SM13.
    Goto SM13--> Select your object lock entries --> Select delete.
    b). Acitvate the Infoobject.
    Regards.

  • SAP NAME FILE lock error while creating the TR in development system.

    Hi All,
    I am getting an error message while saving the changes in my SAP Script that 'SAP names file for <UserId> locked by another process'
    The name of the lock file is "/usr/sap/trans/tmp/<UserId>.LOS".
    Can any body help me, how to resolve this problem ?
    Thanks,

    Hi Kamlesh,
    did you find any solution? I'm getting the same error while a saving the changes in a Dynpro in the ABAP Development Workbench.
    Thanks,
    Viktor

  • Error while configuring TMS in SAP (3 system Landscape)

    Hi,
    We need to replace our quality server with a new one.While configuring TMS,with the new replacement of our quality server,we are facing an error.
    Our development server is the domain controller and we have added our new QA and then deleted the old system and previous TMS configuration.But after deleting the configuration in our Production also,we get an error while adding it in the landscape.
    Password should contain atleast 2 numericals(0-9) for TMSADM.We changed and tried but of no use.
    Our password is welcome@01 which goes as per the password exception table.
    Can anyone help us in resolving this issue.Do we need to change the parameters and restart the system?Or is there any resolution like unlocking any table etc.
    Please help.Early response would be of great help as our landscape is affected.
    Regards,
    Sudheer.

    Hi Sudheer,
    Make sure the client id open
    in client other than 000 open table TMSCROUTE using SE11 and create following entry.
    sysname = ,ADMPWD
    Routestring=USER
    save the entry then try to configure STMS in 000.
    Try to add the Entry in All 3 Systems.
    Also Refer Note 1568362 - TMSADM password change
    Regards,
    Vaibhav

  • Error while extracting data from a remote system

    Hi,
    I am facing problem while extracting data from a remote system. The connection is alright I can extract the table required from the remote system,but when I deploy it I get this error
    ORA-04052: error occurred when looking up remote object [email protected]@ORACLE_UBN_15_LOCATION1
    ORA-00604: error occurred at recursive SQL level 1
    ORA-28000: the account is locked
    ORA-02063: preceding line from UBNDW@ORACLE_UBN_15_LOCATION1
    here Scott.demo1 is the table and UBNDW is the sid of the remote system and ORACLE_UBN_15_LOCATION1 is the location. Please help me out with this
    Thanks

    Hi,
    IDOC's need to be processed manually either in OLTp or in BW depending on the failure. Error msg in monitor status will take u to either BW or OLTP whernever there is a prob. Process IDOC's , this will start the left over packets and will finish the load.
    we hav to check IDOC in WE05(t-code) and know the status these are WE51,WE52,WE53 AND GOTO WE19 there we hav to execute the exist Idoc will succesfully loaded Idoc
    Goto St22 see the short dump error msg..
    post if there any inf..
    Thanks,
    Shreya

  • Error while applying J2EE SP14 for 640 system

    Hi,
    I am facing issue while applying J2EE SP14 for 640 system. The current level is SP9. Below is the error. Can you recommand any resolution for the same.
    ERROR 2005-03-04 14:23:47
    CJS-20076  Error while retrieving the mode of the J2EE Engine. See output of logfile C:\Program Files\sapinst_instdir\PATCH\MSS/getEngineMode.log: 'Error while loading BatchConfig C:\Program Files\sapinst_instdir\PATCH\MSS/getSafeMode.xml definition file.
    java.lang.Exception: Unknown Task information
         at com.sap.engine.configtool.batch.descriptor.BatchConfigDescriptorDocument.readDescriptorFromDocument(BatchConfigDescriptorDocument.java:121)
         at com.sap.engine.configtool.batch.descriptor.BatchConfigDescriptorDocument.readDescriptorFromDocument(BatchConfigDescriptorDocument.java:94)
         at com.sap.engine.configtool.batch.descriptor.BatchConfigDescriptor.loadFromFile(BatchConfigDescriptor.java:66)
         at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:74)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:78)
    WARNING 2005-03-04 14:23:47
    The step checkIfSafeModeIsEnabled with step key ApplySupportPackage|ind|ind|ind|J2EE_Engine|6.30|0|PatchJ2eeEngine|ind|ind|ind|J2EE_Engine|6.30|0|checkIfSafeModeIsEnabled was executed with status ERROR.

    hi Atul,
    Welcome to SDN!
    This problem occurs due to unexpectedly high CPU usage. Check the SAP OSS Notes (from Service Market Place) <a href="https://websmp203.sap-ag.de/form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000309362004">743207</a> and <a href="https://websmp203.sap-ag.de/form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000300342004">742395</a>
    They will help you to solve the problem.
    Regards
    ak

Maybe you are looking for

  • SRM - MDM query

    Hi all, We are integrating SRM & MDM via XI/PI. Kindly let me know what services should be run in MDM import server so that the xml file transferred from XI/PI replicates the data( product categories, products etc.) in MDM repository. Thanks Nikhil

  • SourceSet is empty

    Hello, I've been struggling with this issue for several days. I've read just about every piece of information I can find on google- document object models, xfa/xdp specifications, video tutorials, etc. I'm not exactly a beginner programmer, either. I

  • Pl2java

    I am trying to compile a simple java class to call a database procedure. I have built my wrapper class OK and placed it in the same location as my main java files. I cannot get my java code to compile because the java wrapper class gives me an two er

  • Just upgraded to the new mac operating system and Illustrator CS5 crashes upon launching. All other applications open fine

    Any helpful ideas?

  • Interative report Charts Javascript error

    Hi All, I have a interactive report, when I generate a chart from the drop down action menu, it throws javascript error "null is null or not an object". Also I was wondering if I could include onclick event to this chart like the other normal apex ch