The Creation of Export DataSource Failed Error while transporting ODS Cube

Hi  All,
I am facing this issue from last 1 week.. i had developed an ODS cube in APO-DP BW which will fetch data from SAP R/3 and its working fine in APO Dev Server.  But when i transport this cube into APO PAC(Prodn Server) the below error i am getting..
   Start of the after-import method RS_ODSO_AFTER_IMPORT for object type(s) ODSO (Activation Mode)
   The creation of the export DataSource failed
   Password logon no longer possible - too many failed attempts
   Password logon no longer possible - too many failed attempts
   Error when creating the export DataSource and dependent Objects
   Error when activating DataStore Object ZANAUTSL
I also updated the transport conversion tables but still problem not resolved.
Immediate help is hightly appreciated.
Thanx
AJ

Hi AJ,
Looking at your error, it seems that the RFC user's password is locked and hence connectivity from R/3 towards APO BW is broken.
You know the name of your export datasource (from R/3 to APO BW). Find out the name of your R/3 source system e.g. PACCLT000, by scrolling to the right against teh export data source.
Take help of your Basis or EAI team to identify the RFC destination corresponding to the connectivity from the R/3 source system (PACCLT000) to your APO BW system. (If needed ask for help from your BW team, I am not very sure how connectivity would be set up from R/3 to APO BW, I guess this would be independent from CIF connectivity)
For this RFC connection from R/3 to APO BW, see which RFC user is maintained in SM59 in APO and ask your security team to reset (or unlock) the password of this RFC user in R/3, and then if required update the user password details in SM59 in APO also.
After this, your issue should get resolved.
Thanks - Pawan

Similar Messages

  • The creation of export datasource failed.

    Hi everyone! This is Chong Tao from Central Michigan University and I got one problem recently when I was doing my set-up of the BW course. I actually wanna copy the infocube but when I click the "Generate export datasource", it automatically comes up one error message "The creation of export Datasource failed". What should I do to overcome this problem? Thanks for paying attention to this problem and I need your valuable advice as soon as possible since it is for the student in this SAP BW course.

    Hi,
    I guess your objective is to copy an existing infocube. Right ?
    In that case, Right Click Infocube and use 'copy'. This will create another Infocube with the same structure, but with no data. You can then fill this copy Infocube by cerating transformation between the two infocubes and scheduling through DTP.
    'Generate export datasource'  can normally be done when there are two separate BW systems and you want an Infocube to be a source of data to another Infocube in a different BW system( though it can be used in the same BW system as well).
    Best Regards

  • Creation of export datasource failed

    Hi All.
    i copied a bussiness content data source object (DSO) and tried to activate it. it is giving error that
    "The creation of the export DataSource failed"
    Why ??? where m i going wrong.
    Thanks & Regards,
    Mo

    Hello,
         This is the problem becos the system is unable to create DATAMART for DSO object.  The following reasons might be hindering the creation of DSO.  Please check whether
    1)  You have proper authorization to create Datasource/Datamarts.
    2)  If so then, check whether DATAMART for the BW Self Source System is properly Installed from Business Content.  (I hope you are working on the version 3.5 or later.. here we need to manually install Aplication Component related to Datamart from Business Content so that Datamart creation never fails after that)
    3)  Also check BW Self Source System is properly functioning.
    Thanks
    Kishore Kusupati
    Edited by: Kishore Kumar K on Jul 28, 2008 5:35 AM

  • Error while transporting standard cube

    Hi
    We are facing errors while transporting a standard cube and all relevant objects.
    While collection it throws errors saying certain routines are not active, whilst unable to find those routines.
    If we ignore and transport the same, transformations es are not being transported.
    How to resolve this., please provide inputs.
    regards
    Lavanya

    Hi Lavanya
    The error log says these objects are in repair mode in this system. I searched the system for the trnsformations, but they are not present. How do we resolve these
    This only means that the objects were changed directly in the target system (could be QA or prod) and are captured in some request. You need to find the relevant request on the target system and take the appropriate action. You could chose to delete the request or transport it from QA to Prod.
    Find the requests on the target system and you will see the tranaformations collected. However, it is not going to be an easy taskl for you to find as the TR will be with the technical name. But this is definitely the reason for the error.
    Cheers
    Umesh

  • The installation of this package failed" error while installing Nov 2013 CU (KB 2889944) for SharePoint 2013

    Hi,
    I'm currently installing Nov CU on my Sharepoint 2013 farm, I have 2 APPS and 2 WFE. I successfully installed the patch in 3 servers however, I got this error "The installation of this package failed” in one of my server.
    Now i cant run the configuration wizard because it of this error.
    Any advise how on to solve this issue? it's giving me headache the whole day already.
    thanks!
    JD

    Hi Trevor,
    Thank you for your reply, I just want to share with you what i found in the msi logs.
    DEBUG: Error 2746:  Transform 9010F70000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10F7-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010F70000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010F70000100015.0.4420.1017
    1: 2746 2: 9010F70000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-10F7-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010F70000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10F7-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010F70000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010FB0000100015.0.4454.1510
    1: 2746 2: 9010F70000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-10F7-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010FB0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10FB-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010FB0000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010FB0000100015.0.4420.1017
    1: 2746 2: 9010FB0000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-10FB-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010FB0000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10FB-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010FB0000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 90107F0000100015.0.4454.1510
    1: 2746 2: 9010FB0000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-10FB-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 90107F0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-107F-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:482]: Skipping validation for patch transform #90107F0000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:482]: Looking for patch transform: 90107F0000100015.0.4420.1017
    1: 2746 2: 90107F0000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-107F-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 90107F0000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-107F-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:482]: Skipping validation for patch transform #90107F0000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:482]: Looking for patch transform: 90104B0000100015.0.4454.1510
    1: 2746 2: 90107F0000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-107F-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2749:  Transform 90104B0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product version == 15.0.4454.1510, found product version 15.0.4420.1017.
    I hope you can help me shed light on this.
    Regards,
    JD

  • Error while transporting ODS setting's.

    Hi Experts,
    I am trying to enable the "BeX Reporting" checkbox for one of the ODS's  in Development and then transport the change to QA.I have just enabled the Check Box and then activated the ODS,saved the changes in a request and then tried transporting it.
    But I got an error saying "Value # for characteristic 0REF_KEY1 is invalid" and so "Error in Activating the ODS object".
    Can you please shed some light on what may be wrong with this?
    Thanks a Lot!

    Hi Sarma,
    Thanks for your explanation. I am expecting it to be ''Hash'' here. ODS Data Activation complains against the value which exists in the new data table. There must be some transaction data extracted with '#' for that characteristic.
    ODS activation should not be complaining about the values that does not exist in the ODS new data table. I think, If you just delete the ODS data and activate with the same settings it will ignore all the values from the master data. In that case it doesn't matter what values exist in the master data table for the info-objects used in ODS.
    Hence there are two ways of getting around the issue.
    1) Delete ODS data and switch on the setting and activate it.
    2) Maintain the character in RSKC and activate.
    If it is just a blank value in the characteristic then it should never complain about activation.
    Hope it helps.
    Thanks
    Soumya
    Soumya Mishra

  • Transport Error-The creation of the export DataSource failed

    Hi Experts,
    I am transporting a DSO from DEV to QA in 7.0 system.While transporting the DSo i am getting the below mentioned error.
    The creation of the export DataSource failed
    Reading the Metadata of APMD0009 ...
    Creating DataSource 8APMD0009 ...
    Password logon no longer possible - too many failed attempts
    Password logon no longer possible - too many failed attempts
    Error when creating the export DataSource and dependent Objects
    Error when activating DataStore Object APMD0009
    the request conatins just the DSO and not the Export datsource.i have also tried exporting both together still it failed.
    I have referred OSS note No.597326 for the same.But it didnt helped in resolving the issue.
    Has any one come across this kind of an issue.
    Thanks in advance!!!!!
    Regards,
    Umesh.

    No it didnt seem to work still got the same password error..                                                                               
    Start of the after-import method RS_ODSO_AFTER_IMPORT for object type(s) ODSO (Activation Mode)              
    /     The creation of the export DataSource failed                                                                 
          Name or password is incorrect (repeat lo gon)                                                                
          Name or password is incorrect (repeat lo gon)                                                                
          Error when creating the export DataSource and dependent Objects                                              
          Error when activating DataStore Object 0BBP_BID                                                              
    /     The creation of the export DataSource failed                                                                 
          Name or password is incorrect (repeat lo gon)                                                                
          Name or password is incorrect (repeat lo gon)                                                                
          Error when creating the export DataSource and dependent Objects                                              
          Error when activating DataStore Object 0BBP_QUO                                                              
    /     The creation of the export DataSource failed                                                                 
          User not authorized. Session terminated                                                                      
          User not authorized. Session terminated                                                                      
          Error when creating the export DataSource and dependent Objects                                              
          Error when activating DataStore Object 0PUR_DS03                                                             
    /     The creation of the export DataSource failed                                                                 
          Name or password is incorrect (repeat lo gon)                                                                
          Name or password is incorrect (repeat lo gon)

  • ODS activation error( The creation of the export DataSource failed

    Hi Friends,
             i have a problem activating the ODS. after defining the ODS, when i try to activate the following error is occured
    1.The creation of the export DataSource failed
    2.RFC connection to source system BWD100 is damaged ==> no Metadata upload
    3.Error when creating the export DataSource and dependent Objects     
    Any help would be appreciated
    Thanks

    Seems that there are one or more characteristics in the ODS for which one or more attributes may be new or inactive.
    Please see SAP Note 597326..Pasting the content below..Solution steps are also given..
    Symptom
    When you activate or transport ODS objects, the following errors appear in the log:
    "The creation of the export DataSource failed". Message number RSBM 035
    "Error &1 in function module &2". Message number RSBM 006
    "Error when creating the export DataSource and dependent Objects". Message number RSDODSO 169
    "Error when activating the ODS object &1". Message number RSDODSO 168
    Other terms
    RSBM 035, RSBM 006, RSDODSO 169, RSDODSO 168
    Reason and Prerequisites
    A characteristic involved is active but it is using new or inactive attributes.
    Characteristics involved are all characteristics used in the ODS object.
    Solution
    Check all characteristics involved as described in the following:
    Check the Compounding and Attributes tabs in the characteristics maintenance.
    All characteristics here must be active. This is displayed by a green icon.
    If this is not the case for a characteristic involved (a gray icon is displayed on one of the two tabs), activate the characteristic involved. This also activates the inactive dependent characteristics.
    After you have checked and repaired all the characteristics involved as described above, the loading/maintenance of master data should work again.
    cheers,
    Vishvesh

  • DSO activation failed due to creation of the export datasource failed

    hi experts,
    i am activating DSO, but failed. Cause is "The creation of the export DataSource failed"
    there are many threads in the forum saying restoring the BI myself source system can address it, I tried many times, but failed.
    I used program RSDG_ODSO_ACTIVATE to activate an already activated DSO, it returned same error and the original activated DSO turned into inactivated. So I guess there must be something wrong with the setting.
    please advise, thanks!
    attach error info:
    The creation of the export DataSource failed
    Message no. RSBM035
    Diagnosis
    The system could not create DataSource .
    System Response
    The metadata for a DataSource must be created while the export InfoSouce is being generated. An error occurred at that time.
    Procedure
    Consult the appropriate developer (function module: RSA1_OLTPSOURCE_GENERATE).
    The delta process ODS does not exist
    Error when creating the export DataSource and dependent Objects
    Error when activating DataStore Object ZFIM_D09

    Hi,
    As I read the system RESTORE option should resolve your issue. From RSA1 try to restore your source system and try to active your DSO again.
    Regards,
    Durgesh.

  • The creation of the export DataSource failed

    Dear All,
    Can u give me the some information to fix the following error which i got while moving Multicube from Dev sys to Prod. sys. multi cube consits of lot of ODS object as dependent objects.
    Error FYI.
    The creation of the export DataSource failed
    RFC connection to source system PBWCLNT300 is damaged ==> no Metadata upload
    RFC connection to source system PBWCLNT300 is damaged ==> no Metadata upload
    Error when creating the export DataSource and dependent Objects
    Error when activating ODS Object 0CRM_CN2P
    Regards,
    Veeru.

    Hi Srinivas,
    If itz SS problem i can able to transport the other objects like cubes, Info Obj.. etc. only while transporting the ODS obj it is showing
    can u help me on this.
    any way i wil chk with basis team and ask to reset PWD.
    Regards,
    Veeru.

  • The creation of the export DataSource failed 0FIGL_O06, 0FIGL_O02

    Hello Expert,
    I have an issue with the export data source creation,
    This is the detail,
    Thank you very much in advance for your kind help,
    The creation of the export DataSource failed
    Message no. RSBM035
    Diagnosis
    The creation of the DataSource &v1& was unsuccessful.
    System Response
    Whilst generating the export InfoSource, the metadata for a DataSource must be generated. An error arose when doing this.
    Procedure
    Consult the appropriate developer (function module: RSB1_OLTPSOURCE_GENERATE).

    Niurka,
    Is this datasource for a hierarchy? See if note - 403092 is relevant.
    Viren

  • Configuration Failed Error while running the Shareoint 2010 Products and Configuration wizard in windows 7

    Hi Techys,
    Kindly help me to resolve the below issue
    "Configuration Failed Error while running the Shareoint 2010 Products and Configuration wizard in windows 7"
    Many Thanks,
    Madhu

    Hi,
    Follow this link for smooth installation for SP 2010 on Win 7.
    http://msdn.microsoft.com/en-us/library/office/ee554869(v=office.14).aspx
    Murugesa Pandian.,MCTS|App.Development|Configure

  • Error While Transporting the DSOs

    Hi Experts,
    I am transporting a DSO from DEV to QA in 7.0 system.While transporting the DSO, i am getting the below mentioned error.
    The creation of the export DataSource failed
    Reading the Metadata of APMD0009 ...
    Creating DataSource 8APMD0009 ...
    Password logon no longer possible - too many failed attempts
    Password logon no longer possible - too many failed attempts
    Error when creating the export DataSource and dependent Objects
    Error when activating DataStore Object APMD0009
    The transport request contains just the DSO and not the Export datsource.I have also tried exporting both together still it failed.
    I have referred OSS note No.597326 for the same.But it didnt helped in resolving the issue.
    Can anyone please help me out with this problem.
    Thanks,
    Shalaka.

    Hai shalaka,
    jus check some points in u r transportation.
    check the collection mode,grouping option - whether it is in dataflow before and after ,in data flow  after,or in data flow before ,might be u have selected the in data flow before ,so the datasource  error is happening here
    check the datasource is from the same sap system or non sap system ,might be the system is having the password .so these are the problems check out and let me know the status of it and if it is solved by other means let me know
    Suri..

  • Error while transporting custom datasource

    Hi All,
    Below is the scenario that was carried out in my project.
    1. Created OHD to load data from a CUBE to Data base Table /BIC/ABC.
    2. Created a custom Datasource ZABC_TEST with the above table.
    3. Activated the DataSource and loaded the data. (Data load successfull. It works fine).
    4. Tried transporting the above. But trows error while transporting the data source.
    Error -- InfoSource ZABC_TEST is not available in source system BITST.
    Let me know what can be done to solve the above error. Please suggest if i have missed out something.
    Thanks in advance.
    Maddy

    HI,
    The problem seems to be occuring since you are transporting both OHD and DS in the same TR request.
    Transport first the DS in a request, then in another request transport the OHD.
    This should resolve the issue.
    hope this helps.
    thanks,
    rahul

  • Connection Failed Error while Importing tables in 11.1.1.6 on Windows 7

    Hi,
    Can you please help me in resolving the connection failed error while importing the tables from the database.
    I am using OBI 11.1.1.6 on Windows 7
    You help is highly appreciated. I have followed all the below blogs but still i was not able to resolve the issue.
    http://123obi.com/2011/03/error-the-connection-has-failed-in-obiee-11g/
    http://obieedeveloper.blogspot.in/2012/03/connection-failed-error-in-obiee-11-g.html
    http://iadviseblog.wordpress.com/2011/05/29/obiee-11g-error-in-importing-metadata/
    http://www.obieefans.com/%E2%80%9Cthe-connection-has-failed%E2%80%9D-error-in-obiee-11g-admin-tool/
    Thanks in Advance
    Siva

    It would be nice if you put your issues instead of asking to look those many urls.
    try using tns entry in connection pool or follow this thread
    Connection failed in OBIEE 11g

Maybe you are looking for

  • Reading data from a file which is in portal KM

    HI, Iam trying read a file which is in portal KM if u have any sample code with u plz share with me

  • Re: Help needed in passing values from workflow to Approve Forms

    Dear Experts, how do I pass values from a workflow to a step (Form) - approve form? I am using a customized table structure as my data source (FORMCONTAINERELEMENT) but am stuck on how to access the data when i get to to the screen painter's flow log

  • GSR 12000 Router and Router 7609S

    Hi all, GSR 12816 supports 40GB/slot. How can I check this information ? I tried to using Dynamic Configuration Tool to build 04 SPA-1X10GE-L-V2 on 12000-SIP-601 but It does not support. Please answer as soon as possible. Thanks

  • Fetching only part of an attribute which is a collection of the candidate

    Given is a pc A with an A.b collection 1:n relation to B. B contains a combination of other attributes. Is it possible to query for A and optain not all A.b but only a subset in A.b which fulfills some criteria (containing relations to a joined pc C)

  • Adding an HP 7310 Printer

    Im having sugnificant issues adding an HP 7310 printer. HP have done all they can over the past 10 days and have now drawn a black because the printer driver seems to load for a 'brief' second in the Setup Utility before disapearing. They have theref