Check on source system failing

My info package is failing
When i check the connection with my source system it says
"Result of the destination check:Password logon no longer possible - too many failed attempts"
How can this be fixed??

Hi,
This problem comes whenever the background user password changes or resets, so contact Ur basis Team for restoring the connection
The password for ALEREMOTE has been locked
Try to Schedule Info Package once the password has been reset. It will be successful.
T.codes : SM59 Source system Connection
RSCUSTV* * 1,2,3,4,5,6,7 Back ground user ID Setup
Regards
Hari

Similar Messages

Create SAP Source System Failed

Hi all,
We are using NetWeaver 2004s BI and try to connect to ECC 5.0. I tried to create SAP source system but got error message saying "RFC user logon failed". When I check RFC destination in ECC 5.0 for BI, the test connection is ok, but the remote logon will pop up another logon screen asking for id and password. I am pretty sure that the id and password in RFC destination is correct. The RFC destination in BI is ok. Can you help me out with this? Thanks a lot in advance.

Hi,
Check the Default Logon <b>Client</b> for ECC 5.0
and verifiy that the User is in the Same Client
Each RFC destination has a mapped user for specific Client..Check the Client and User in the same client
regards
Happy Tony
Message was edited by: Happy Tony

HELP!! Create source system failed in BW ( ORA-01403: no data found)

Hi,
I cannot create Oracle DB as a source system in my BW (7.01).
In system log, I got the following information.
============================
Database error 1403 at CON
> ORA-01403: no data found
============================
How can I fix this issue?
It's kind of urgent.
Thanks!
Regards,
Steven
Edited by: Wen Steven on Sep 30, 2011 6:09 PM

Hi Steven,
Please check the below thread
SQL/Buffer trace RC=1403
Regards,
Venkatesh

Delete source system fails

I've got a flat file source system definition which I deleted via rsa1 --> source system --> right-click --> delete. it deleted all the dependant objects (transfer rules, psa, EDI config, etc), but the system still shows up in RSA1. There's an entry in table RSBASIDOC referencing this source system (field SLOGSYS), because we manually tried creating a basic idoc type for it (which we now can't delete with tcode WE20 since it's been generated).
Does anyone know off hand how to get rid of the source system in the RSA1 list?
Thanks!
Rich

Hi Rich -
I guess the SAP Note (967999) applies in your case. I've pasted it below for your reference.
Symptom
In the source system tree of the Administrator Workbench (AWB), you use the 'Delete' function in the context menu (right mouse button) for a connected source system.
Even though the system displays success message RSAR 262:
Source system & deleted
at the end in the status line, the source system connection is visible again after the AWB has been updated and the source system connection has not been deleted.
Other terms
Context menu, source system tree, right mouse button, delete source system, RSAR, 262, 620, SLG1, RSAR262, RSAR620, AdminWorkbench
Reason and Prerequisites
This problem is caused by a program error.
An error occurs during the deletion, however the system does not inform you correctly of this at the end, after the deletion process has terminated.
Solution
BW 3.0B
Import Support Package 33 for 3.0B (BW 3.0B Patch 33 or SAPKW30B33) into your BW system. The Support Package is available onceNote 914950 "SAPBWNews BW 3.0B Support Package 33", which describes this Support Package in more detail, has been released for customers.
BW 3.10 Content
Import Support Package 27 for 3.10 (BW 3.10 Patch 27 or SAPKW31027) into your BW system. The Support Package is available onceNote 935963 "SAPBWNews BW 3.1 Content Support Package 27", which describes this Support Package in more detail, has been released for customers.
BW 3.50
Import Support Package 19 for 3.5 (BW3.50 Patch 19 or SAPKW35019) into your BW system. The Support Package is available once Note 928662 "SAPBWNews BW Support Package19 NetWeaver'04 Stack 19", which describes this Support Package in more detail, has been released for customers.
BW 7.0
Import Support Package 10 for 7.0 (BW7.0 Patch10 or SAPKW70010) into your BW system. The Support Package is available once Note 914304 "SAPBWNews BW 7.0 Support Package 10", which describes this Support Package in more detail, has been released for customers.
To provide information in advance, the note(s) mentioned above may already be available before the Support Package(s) is/are released. In this case, the short text of the note still contains the words "Preliminary version".
Pls assign points if helpful.

[SOLVED] check pacman source sign failed on sh4 CPU

I've build 'base' packages on sh4 CPU. (Some base library still use the original linux distributions. eg. gcc,glibc,...)
I followed Pacman-key to setup key rings.
pacman-key --init
pacman-key --populate archlinux
pacman-key --refresh-keys
I run previous commands through ssh. I tried to build haveged, but it occurs following messages, I guess it is caused by old kernel and my hardware haven't realtime clock. So I forgive it.
gcc -Wall -I.. -O2 -pipe -o haveged haveged.o havege.o havegetune.o havegecollect.o havegetest.o
havegecollect.o: In function `havege_gather':
havegecollect.c:(.text+0x264): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0x6a0): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0x9d0): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0xd8c): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0x1208): undefined reference to `HARDCLOCK'
havegecollect.o:havegecollect.c:(.text+0x1684): more undefined references to `HARDCLOCK' follow
collect2: ld returned 1 exit status
And rerun makepkg on pacman.
==> Validating source files with md5sums...
pacman-4.0.3.tar.gz ... Passed
pacman-4.0.3.tar.gz.sig ... Passed
0001-Add-conflict-for-replacing-owned-empty-directory.patch ... Passed
0002-Check-empty-subdirectory-ownership.patch ... Passed
0003-Ensure-pre_upgrade-scriptlet-gets-old-package-version.patch ... Passed
pacman.conf ... Passed
pacman.conf.x86_64 ... Passed
pacman.conf.sh4 ... Passed
makepkg.conf ... Passed
==> Verifying source file signatures with gpg...
pacman-4.0.3.tar.gz ... FAILED (unknown public key 5C2E46A0F53A76ED)
==> WARNING: Warnings have occurred while verifying the signatures.
Please make sure you really trust them.
Even I manual add the key on message, it is still failed.
$ sudo pacman-key -r 5C2E46A0F53A76ED
gpg: requesting key F53A76ED from hkp server pool.sks-keyservers.net
gpg: key F53A76ED: "Dan McGee <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
==> Updating trust database...
gpg: next trustdb check due at 2014-01-22
$ makepkg
==> Verifying source file signatures with gpg...
pacman-4.0.3.tar.gz ... FAILED (unknown public key 5C2E46A0F53A76ED)
BTW, in the process of building gpgme, I can not build pinentry successful, so I pass and use fedora's.
fedora9 pinentry 0.7.4-5.fc9.sh4
Solved, I guess wrong direction, that's cause I forgot to read Makepkg again.
gpg --list-keys
echo 'keyring /etc/pacman.d/gnupg/pubring.gpg' >> ~/.gnupg/gpg.conf
Last edited by dlin (2013-02-07 01:42:56)

I've build 'base' packages on sh4 CPU. (Some base library still use the original linux distributions. eg. gcc,glibc,...)
I followed Pacman-key to setup key rings.
pacman-key --init
pacman-key --populate archlinux
pacman-key --refresh-keys
I run previous commands through ssh. I tried to build haveged, but it occurs following messages, I guess it is caused by old kernel and my hardware haven't realtime clock. So I forgive it.
gcc -Wall -I.. -O2 -pipe -o haveged haveged.o havege.o havegetune.o havegecollect.o havegetest.o
havegecollect.o: In function `havege_gather':
havegecollect.c:(.text+0x264): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0x6a0): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0x9d0): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0xd8c): undefined reference to `HARDCLOCK'
havegecollect.c:(.text+0x1208): undefined reference to `HARDCLOCK'
havegecollect.o:havegecollect.c:(.text+0x1684): more undefined references to `HARDCLOCK' follow
collect2: ld returned 1 exit status
And rerun makepkg on pacman.
==> Validating source files with md5sums...
pacman-4.0.3.tar.gz ... Passed
pacman-4.0.3.tar.gz.sig ... Passed
0001-Add-conflict-for-replacing-owned-empty-directory.patch ... Passed
0002-Check-empty-subdirectory-ownership.patch ... Passed
0003-Ensure-pre_upgrade-scriptlet-gets-old-package-version.patch ... Passed
pacman.conf ... Passed
pacman.conf.x86_64 ... Passed
pacman.conf.sh4 ... Passed
makepkg.conf ... Passed
==> Verifying source file signatures with gpg...
pacman-4.0.3.tar.gz ... FAILED (unknown public key 5C2E46A0F53A76ED)
==> WARNING: Warnings have occurred while verifying the signatures.
Please make sure you really trust them.
Even I manual add the key on message, it is still failed.
$ sudo pacman-key -r 5C2E46A0F53A76ED
gpg: requesting key F53A76ED from hkp server pool.sks-keyservers.net
gpg: key F53A76ED: "Dan McGee <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
==> Updating trust database...
gpg: next trustdb check due at 2014-01-22
$ makepkg
==> Verifying source file signatures with gpg...
pacman-4.0.3.tar.gz ... FAILED (unknown public key 5C2E46A0F53A76ED)
BTW, in the process of building gpgme, I can not build pinentry successful, so I pass and use fedora's.
fedora9 pinentry 0.7.4-5.fc9.sh4
Solved, I guess wrong direction, that's cause I forgot to read Makepkg again.
gpg --list-keys
echo 'keyring /etc/pacman.d/gnupg/pubring.gpg' >> ~/.gnupg/gpg.conf
Last edited by dlin (2013-02-07 01:42:56)

Error RSAR 371 when checking source system in BI

This was mentioned in 1 forum but not really answered to my understanding.
Message - BI IDOC type ZSBB003 not the same as source system IDOC type ZSBC005
RSAR 371
This is when checking a source system from BI 7.0 to ECC 6.0 after a refresh and running BDLS with many patches.
thanks

Hi Bradley,
I believe you have to run BDLS using option 1 - Conversion of Client Dependent and Client-Independent Tables. This is to ensure that you have a correct conversion to a new logical system.
You can refer to these notes too:
886102, 184754, 325470
These notes help but rather confusing to read it at first. Hope this helps.
Regards,
Andrew

R/3 Source System Check in BW

Hi ,
We had a BW client Copy from Production to QA and DEV system. Last week, When I am trying to restore source system connection to R/3 after client copy by creating PORT and PARTNERPROFILES in BW system. I could restore connection in BW Dev but not in QA.When I tried to check the source system in RSA1 then I am getting an error that USER IS LOCKED. The remote logon test is going sucessful and when I replicate I could replicate every thing successful. I checked the user(ALEREMOTE) in R/3 and the status of the user is not locked.
Thanks in Advance,
Varma.

Hi,
Did you check the ALEREMOTE in your BW QA? The best to test out is to go into SM59 of both the system (BW and R3) and try the logon.
Hope this helps,
Cheers,
Gimmo

Checking source system

Hai,
I am seriouslu suffering from a problem with my source system. I am not able to connect to load data, transfer structure not getting activated. Can some body please tell me all the ways I could check a source system, infosource and datasource.
I know the following:
1. AWB>source system> (rt.click on sourcesystem)> check
How can I check on both BW and R/3ides?
Any help is highly appreciated.
thanks a lot.

Hi,
Please follow the steps,
1) TransactionSM59 --> Run the RFC destination for your R3 system and it should show 'success' message. Check with Basis team
2) Transaction RSA1 --> Tools --> Mapping of the source system names & Assignment of source system to source system ID.
Please make sure this settings are made and test the data load.
Thank you
Arun

Function module to check source system

Hello
Can some one help me by providing the name of the function module to check the Source system connection?
I know that in the source system we can right click and check.
But i want to know the function module to check the status.
Thanks in advance
Kind regards
M.A
Edited by: M.A on Aug 19, 2008 12:42 PM

Hi shasank,
Thanks for the info.
I had given the tech name of the source system as an input to the function module.
But it raises an exception that destination does not exists.
But the source system connection is ok.
Regards
M.A

Error is data loading from 3rd party source system with DBCONNECT

Hi,
We have just finished an upgrade of SAP BW 3.10 to SAP NW 7.0 EHP1.
After the upgrade, we are facing a problem with data loads from a third party Oracle source system using DBConnect.
The connection is working OK and we can see the tables in the source system. But we cannot load the data.
The error in the monitor is as follows:
'Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.'
But, unfortunately, the error message has no further information.
If we look at the job log in sm37, the job finished with the following log -
27.10.2009 12:14:19 Job started                                                                                00           516          S
27.10.2009 12:14:19 Step 001 started (program RSBATCH1, variant &0000000000119, user ID RXSAHA)                    00           550          S
27.10.2009 12:14:23 Start InfoPackage ZPAK_4FMNJ2ZHNNXC6HT3A2TYAAFXG                                              RSM1          797          S
27.10.2009 12:14:24 Element NOAUTHORITYCHECK is not available in the container                                     OL           356          S
27.10.2009 12:14:24 InfoPackage ZPAK_4FMNJ2ZHNNXC6HT3A2TYAAFXG created request REQU_4FMXSQ6TLSK5CYLXPBOGKF31G     RSM1          796          S
27.10.2009 12:14:24 Job finished                                                                                00           517          S
In a BW 3.10 system, there is no message related to element NOAUTHORITYCHECK. So, I am wondering if this is something new in NW 7.0.
Thanks in advance,
Rajib

There will be three things to get the errors like this
1.RFC CONNECTION FAILED
2.CHECK THE SOURCE SYSTEM
3.CHECK IT OUT WITH Oracle Consultants WEATHER THEY ARE FILLING UP THE LOADS.TELL THEM TO STOP
4.CHECK I DOC PROCESSING
5.FINALLY MEMORY ISSUES.
6.CATCH THE DATA SOURCE FIRST CHANGE IT AND THEN ACTIVATE AND RUN THE LOAD
7.LAST IS MEMORY ISSUE.
and also Check the RFC connection in SM59 If it is ok then
check the SAP note : 692195 for authorization
Santosh

DYNPRO_SEND_IN_BACKGROUND errors in source system

Hi All,
Yesterday night we kicked DELTA Process Chain.
The PC failed While loading the 0GL_ACCOUNT Attributes, and showing the message Errors in Source System.
and also Failed at Cost Element Attributes but both the error messages are same.
Checked the source system connections and repeated the process, but it was failed again. and tried to load manually and again failed.
When we check the DUMP in Source system (ECC) in ST22 showing the message as below:
"DYNPRO_SEND_IN_BACKGROUND" Current screen: "SAPLSTRD " 0351
Note: We ran FULL load day before yesterday and Ran INITIAL yesterday, We are running DELTA TODAY.
one thing is we just deleted the GL attirbutes Requests manually and loaded INIT , we are able to do INIT load perfectly. but while trying DELTA only this problem is causing.
Thanks in Advance,
Teena

Hello ,
Sometimes the problem happens because the background users do not have the correct authorization. Please check the information in the SAP note 150315.
Kind Regards,
Des

Prod source system issue

Dear All,
I have an issue in production system.
We applied a patch in BI prod and r3 prod for data lineage...but after that all process chains failed when i checked in source system connection ...there was no connection..
Now i want to restore my r3 prod source system in BI system Please tell me how to do that.
regards
shweta

Hello,
First check in SM59 whether the connection for the source system exits. If it does not then contact the BASIS team for connection.
If the connection is fine, then you can right click on the source system in BI and choose restore option.
But beware restoring with set the timestamp for all the datasources for that source system.
It will take time as it will replicate and activate all the datasources.
Regards,
Shashank

Question about source system copy for BW

Dear all,
I have a quick question about copying a source system for BW.
We have two clients in the source ERP:
100 Customizing
200 Testing
Our BW is only linked to client 200, so when we now delete client 200 and make a copy from 100 to 200, are we then still able to restore the source system connection so that our extraction will work, or will it fail, as in client 100 I have no BW related (except the cross-client-objects like datasource) information, that can be used for a possible restore of this connection.
What is the procedure in this case?
Thanks,
Andreas

Unfortunately, you will lose your source connection and need to create a new one in R/3. You can use the same source system name in BW, but check the source system connection after the copy (SM59). Also, I would "Restore" the source system (in BW, right-click on Source system in RSA1, and click "Restore") to insure the datasources get replicated from R/3 to BW.
Depending on how much you want your BW and R/3 systems to be in synch, you will need to rebuild all your data providers (cubes/ODS's) from your R/3 system. This means deleting all the data and running the initializations from scratch. At the very least, you will need to rebuild the delta queues.
Curious, if 100 is just for customizing, is there any data in it? Are you just creating a new blank client 200?

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

Error in source system while extracting the data from R/3!

Hi,
i had created FM and extract strcucture in R/3 .
using the above two, i had created data source using RSO2 T code.
when i checked the extractor ( RSA3 T code) in R/3 it was working fine .
(status messege displayed as 1000 records selected).
then i assigned this data source to infocurce and creted info cube using the same info source.
but when i schedule the info package it is syaing in the monitor screen "error in source system".
what could be the problem?
Thanks,
Ravi

Hi
trhese are the possiblies
1.first check the source system connection and find if there is any error in it.
2.Go to sm37 and find whether the request is completed or not if its terminated find out the time. how long does it takes to complete the process.
3.once again relicate the data source and find whether is it again extract data.

Check on source system failing

Similar Messages

Maybe you are looking for