cancel
Showing results for 
Search instead for 
Did you mean: 

EarlyWatch Error(s)

Former Member
0 Kudos

Hi,

We are using Solution Manager 4.0 and getting an error messages when I use tr: DSWP and click R/3 system to view EarlyWatch...

I am sending screen shot to view that...

http://www.flickr.com/photos/25222280@N03/2570803640/sizes/o/

How to fix that please....

Thanks

J

Accepted Solutions (1)

Accepted Solutions (1)

former_member209604
Active Contributor
0 Kudos

I have recommended the following in similar problem. Please follow the steps.

Red flag means, no data collected or transferred yet.

Relevant for missing EWA data in SolMan is the RFC destination from Satellite System to SolMan.

Please check the following in the Satellite System:

  • RFC Destination (default name: SM_<SID>CLNT<client>_BACK ) to SAP Solution Manager exists and is functional.

  • Transaction SDCCN (Service Data Control Center) must have been activated.

  • RFC Destination (default name: SM_<SID>CLNT<client>_BACK ) is assigned in SDCCN: Goto -> Settings -> Task-Specific -> Session Data Collection -> RFC Destinations ->Settings.

  • Maintenance Package runs daily.

Check tasks (log) of SDCCN.

You should find a task "EarlyWatch Alert for Solution Manager" (or similar)

Ruediger

Former Member
0 Kudos

Thanks again for fast reply

ok I checked couple of thing

-


Relevant for missing EWA data in SolMan is the RFC destination from Satellite System to SolMan.

What does it mein that ?

-


Transaction SDCCN (Service Data Control Center) must have been activated.

YES its actived

-


RFC Destination (default name: SM_<SID>CLNT<client>_BACK ) to SAP Solution Manager exists and is functional.

Where may i found that is functional fine... ?

-


RFC Destination (default name: SM_<SID>CLNT<client>_BACK ) is assigned in SDCCN: Goto -> Settings -> Task-Specific -> Session Data Collection -> RFC Destinations ->Settings.

YES, its show there

-


Maintenance Package runs daily.

how may i check this one?

-


Check tasks (log) of SDCCN. You should find a task "EarlyWatch Alert for Solution Manager" (or similar)

I didn't see any like earlywatch alert or similar its show like (Tasklog)

========================================================

Type TaskID Message Text date user

========================================================

>> 0000000624 Maintenance Package completed solman

>> 0000000624 Maintenance Package started solman

>> Task processor started solman

something like that...

Thanks

Ruediger

former_member209604
Active Contributor
0 Kudos

>

> -


> Relevant for missing EWA data in SolMan is the RFC destination from Satellite System to SolMan.

>

> What does it mein that ?

> -


> RFC Destination (default name: SM_<SID>CLNT<client>_BACK ) to SAP Solution Manager exists and is functional.

>

> Where may i found that is functional fine... ?

>

> -


> Maintenance Package runs daily.

> how may i check this one?

>

> -


> Check tasks (log) of SDCCN. You should find a task "EarlyWatch Alert for Solution Manager" (or similar)

>

> I didn't see any like earlywatch alert or similar its show like (Tasklog)

> ========================================================

> Type TaskID Message Text date user

> ========================================================

> >> 0000000624 Maintenance Package completed solman

> >> 0000000624 Maintenance Package started solman

> >> Task processor started solman

>

> something like that...

See a nice picture of relevant RFC destinations on page 11 of

[Security Guide SAP Solution Manager 7.0|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000673252&_SCENARIO=01100035870000000112&_OBJECT=011000358700007187872005E]

Verify RFC destinations with transaction SM59 and perform an "Authorization Test" (available via menu). If no error appears, it's very likely that the destination is functional.

Task "Maintenance Package" should be visible for every day on tab "Done" in transaction SDCCN

Task "EarlyWatch Alert for Solution Manager" should be visible under tab "To do" or "Done" in transaction SDCCN

Former Member
0 Kudos

Hey buddy

You are right it was really nice screenshot

But still problem there, as you know that I tried to check couple of thing follow:-

The RFC connection for the SAP Solution Manager system

The 'Task Processor' background job

A periodic 'SDCC Maintenance Package' task has been scheduled

I am sending step by step screen shot please look it this

http://www.flickr.com/photos/25222280@N03/2573433646/sizes/o/

http://www.flickr.com/photos/25222280@N03/2572610147/sizes/o/

http://www.flickr.com/photos/25222280@N03/2573433690/sizes/o/

http://www.flickr.com/photos/25222280@N03/2573433712/sizes/o/

http://www.flickr.com/photos/25222280@N03/2572610213/sizes/o/

http://www.flickr.com/photos/25222280@N03/2572610245/

http://www.flickr.com/photos/25222280@N03/2573433810/sizes/o/

http://www.flickr.com/photos/25222280@N03/2572610303/sizes/o/

http://www.flickr.com/photos/25222280@N03/2573433860/

O yes, I wanna give you more reward points how may i gonna do that ?

Please advised

Thanks a lot in advanced

former_member209604
Active Contributor
0 Kudos

This screen shot [SDCCN - task log empty|http://www.flickr.com/photos/25222280@N03/2573433810/sizes/o/] is the relevant one.

"SDCCN Activated means": SDCCN is functional. I you case SDCCN can be called, but nothing is performed by SDCCN.

Please do the following:

- call SDCCN

- choose in the menu for "Activate SDCCN" or similar (probably under Utilities)

- this action will perform some activies, which can be found afterwards in the Task Log.

Best regards,

Ruediger

former_member209604
Active Contributor
0 Kudos

>

> O yes, I wanna give you more reward points how may i gonna do that ?

See [Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] how to reward useful answers with points.

(I am not very familar with this.)

Former Member
0 Kudos

Hi,

I perform that action and it bring some data (screenshot blow) :-

http://www.flickr.com/photos/25222280@N03/2572877093/sizes/o/

Thanks a lot again, could you please tell me what is the next step, I know you have very busy time, if you would like to add me in yahoo messanger maamir_awan @ yahoo . com

Where you live buddy? i am in canada

former_member209604
Active Contributor
0 Kudos

Hi,

I live in Walldorf. Sorry, but I do not use any messenger.

Communicating through SDN or customer messages is fine.

Send me a screen of tab "To do" and "Done".

Ruediger

Former Member
0 Kudos

Thanks again

http://www.flickr.com/photos/25222280@N03/2573027197/sizes/l/

Last screenshot is tr: smsy goto system R/3 NQA --> client tab --> RFC connection push button and TEST again... it asking me user name and password for NQA system provided it then I got last screen with errors

one more thing about "To do" and Tasklog when I apply tr: sdccn its direct goto service data control center screen, which is i belive solution manager if I want to see other system "task log" then ?

Thanks

former_member209604
Active Contributor
0 Kudos

Goto tab "To do" and click on log item on task 640.

Please post the complete log.

In general SDCCN in System NSM looks fine.

By the way, why are posting information from NSM ?

NQA was the system having problem (indicated by the red flag in your SAP Solution Manager - EWA).

RFCs in SMSY are not relevant for EWA processing.

Only the "Back" destination pointing from connected system (for example NQA, NSM) to SolMan is required.

>

> one more thing about "To do" and Tasklog when I apply tr: sdccn its direct goto service data control center screen, which is i belive solution manager if I want to see other system "task log" then ?

Transactions

- SDCCN = Service Data Control Center

- DSMOP, DSWP, SOLUTION_MANAGER = SAP Solution Manager

SDCCN is handling service data collection requests (for EarlyWatch Alert, or Service Sessions delivered by SAP for example SAP GoingLive Functional Upgrade Check, ...)

If you want to check easily the task log of SDCCN of all systems connected to your SolMan system. You can navigate through SMSY and call SDCCN.

A good method to check operating of EWAs is to look at the Self-Diagnosis in SolMan.

It includes check routines for RFCs, SDCCN, ...

Former Member
0 Kudos

Thanks for great infromation

you know what? when I apply tr: sdccn it direct goto task log it never asking me for user name and password for NQA

and screen log is like that... there is no 620 i can double click on there...

http://www.flickr.com/photos/25222280@N03/2574696409/sizes/o/

NSM system is solution manager

=========================================================================

after we fix this issue, our company wants to control CCMS in solution manager, any system like NQA, NPR or NDV just configure to CCMS MTE alerts such as CPU utilization...

my question is should I have to create RFC connection for that or use same RFC connection which is i am using for EWA

Thanks again

former_member209604
Active Contributor
0 Kudos

>

> you know what? when I apply tr: sdccn it direct goto task log it never asking me for user name and password for NQA

>

> and screen log is like that... there is no 620 i can double click on there...

>

> http://www.flickr.com/photos/25222280@N03/2574696409/sizes/o/

>

> NSM system is solution manager

Sorry, I did not understand the last posting.

Are the issues with EWA processing in SolMan solved?

SDCCN should never prompt for a user name and password.

In case of further questions, please list the involved systems and describe the steps with used system.

For CCMS, please open a new Thread.

Former Member
0 Kudos

Hi,

SDCCN issue still there, EWA still not generate report for others 2 server such as NQA

about CCMS forget about it right now...only EWA report I am warry about that...

I alerady send "ToDo" report, did you found any clue

Thanks

Former Member
former_member209604
Active Contributor
0 Kudos

Please summarize the issues, list the systems . In case of Screen Shots, display the system id in the right lower corner of the screen.

Please post the log of task 640

http://www.flickr.com/photos/25222280@N03/2573027197/sizes/l/

former_member209604
Active Contributor
0 Kudos

As NQA shows red flag in SolMan. You need to verify the mentioned SDCCN in NQA

Red flag means, no data collected or transferred yet.

Relevant for missing EWA data in SolMan is the RFC destination from NQA to SolMan.

Please check the following in NQA

- RFC Destination (default name: SM_NSMCLNT<client>_BACK ) to SAP Solution Manager exists and is functional.

- Transaction SDCCN (Service Data Control Center) must have been activated. You might send screen shots of "Todo", "Done", "Task Log"

- RFC Destination (default name: SM_NSMCLNT<client>_BACK ) is assigned in SDCCN: Goto -> Settings -> Task-Specific -> Session Data Collection -> RFC Destinations ->Settings.

- Maintenance Package runs daily.

- Check tasks (log) of SDCCN.

You should find a task "EarlyWatch Alert for Solution Manager" (or similar) at Done.

Post the log

former_member209604
Active Contributor
0 Kudos

>

> ok i am sending all posible screenshot I am still confouse why and where is that problem everying is seem to be look fine...

> Thanks

.....many screen shots of less (in this case no) relevance.

I asked for SDCCN information of system NQA (the system

which causes the Red Flag in your SolMan), not your SolMan System NSM.

I assume an error in NQA.

Regards, Ruediger

Former Member
0 Kudos

I really appriciated your time, to look at screenshot, I do understand what are you asking about NQA system log... but again when I goto SDCCN it always show NSM system log not NQA

how may I check NQA tasklog or todo log....

I pretty much check all options in menu, but unfortunately, I could't found that out, can you please let me know couple of steps how may I check NQA log

Thanks

former_member209604
Active Contributor
0 Kudos

>

> I really appriciated your time, to look at screenshot, I do understand what are you asking about NQA system log... but again when I goto SDCCN it always show NSM system log not NQA

> how may I check NQA tasklog or todo log....

>

> I pretty much check all options in menu, but unfortunately, I could't found that out, can you please let me know couple of steps how may I check NQA log

Sorry, for "shouting". It was a long day for me.

- logon to system NQA via SAP Logon (not via SMSY of SolMan, you might have a wrong RFC destination assigned). You should see NQA in the lower right corner.

- run transaction SDCCN (in NQA) and collect the required information

Former Member
0 Kudos

Hi, with thanks

I got you, now I loged in NQA and sending screenshot of ToDo, Done, Tasklog, pretty much empty...

I done screenshot after active

http://www.flickr.com/photos/25222280@N03/2576292786/sizes/o/

Thanks

former_member209604
Active Contributor
0 Kudos

Great.

"SDCCN Activated means": SDCCN is functional. I you case SDCCN can be called, but nothing is performed by SDCCN.

Please do the following in NQA:

  • call SDCCN

  • choose in the menu for "Activate SDCCN" or similar (probably under Utilities)

  • this action will perform some activies, which can be found afterwards in the Task Log.

Best regards,

Ruediger

Former Member
0 Kudos

yes, sure

in NQA, I goto Utilities and actived then nothing happend

but when I apply tr: smt2 I got that screen

http://www.flickr.com/photos/25222280@N03/2576335472/sizes/o/

its funny when when apply sm59 its show all connection without trusted but when i apply smt2 its show trusted connection... where thease connection from ?

please guide

Thanks

former_member209604
Active Contributor
0 Kudos

>

> in NQA, I goto Utilities and actived then nothing happend

Open a message on SV-SMG-SDD and let my colleagues (or may be I) help you. Without access to the system, we might spend weeks to get it done.

or perhaps, other SDN members can talk you through better. Calling for Markus.

>

> but when I apply tr: smt2 I got that screen

http://www.flickr.com/photos/25222280@N03/2576335472/sizes/o/

>

> its funny when when apply sm59 its show all connection without trusted but when i apply smt2 its show trusted connection... where thease connection from ?

I don't know about your connection in SMT2, but they are of no value regarding the EWA topic.

You should see in SM59 in system NQA a destination (with a communication user in SolMan System) pointing to SolMan system.

Former Member
0 Kudos

Hi,

This is travis again

any luck ?

Thanks

Former Member
0 Kudos

Hi, dear

I already sent this message again, I am sending to you as well, now its more clear picture

R/3 landscape (NDV,NQA,NPR)

NDV and NPR does works fine and getting EWA everyweek which is schedule every week

NQA does not work at all

Screenshot here:

http://www.flickr.com/photos/25222280@N03/2586790185/sizes/o/

-


1. I check RFC connection in solution manager (sdccn)

Selected NQA, and click RFC button

Login NQA tr: sdccn --> taskLog --> from menu GOTO --> setting --> Processor task

Checkhosts then double click (RFC destination) I got error: "no host fulfils the requirements of service data control center"

Is there any problem please let me know

Screenshot here:

http://www.flickr.com/photos/25222280@N03/2586794197/sizes/o/

-


2. Goto SM59 --> under R/3 connection --> check connection "SM_NSMCLIENT100_BACK" does works fine...

screenshot here:

http://www.flickr.com/photos/25222280@N03/2586794219/sizes/o/

-


Question: please let me know where and what i am missing or wrong ?

Thanks in Advanced

former_member209604
Active Contributor
0 Kudos

>

> -


> 1. I check RFC connection in solution manager (sdccn)

> Selected NQA, and click RFC button

> Login NQA tr: sdccn --> taskLog --> from menu GOTO --> setting --> Processor task

> Checkhosts then double click (RFC destination) I got error: "no host fulfils the requirements of service data control center"

> Is there any problem please let me know

> Screenshot here:

> http://www.flickr.com/photos/25222280@N03/2586794197/sizes/o/

>

>

The screen shot shows transaction SMSY in your Solution Manager sytem NSM. For EWA processing, it's of no relevance.

>

> 2. Goto SM59 --> under R/3 connection --> check connection "SM_NSMCLIENT100_BACK" does works fine...

> screenshot here:

http://www.flickr.com/photos/25222280@N03/2586794219/sizes/o/

Please perform an authorization check as well. This is also accessible through SM59

According to screen shot. Connection test was OK.

Ruediger

Former Member
0 Kudos

Hi,

I put authz. S_RFCACL in NQA system and now there is no errors as screen shot here:

http://www.flickr.com/photos/25222280@N03/2590143794/sizes/o/

first screen is NQA now all of green, and 2nd screen is NPR still red but NPR getting EWA report, and NQA still not getting EWA report thats really strange

can you please tell me what process/job running when EWA report create, i would like to re-create again

thanks

former_member209604
Active Contributor
0 Kudos

Perform the following:

- logon to system NQA

- choose SM59 --> under ABAP connection --> "SM_NSMCLIENT100_BACK"

Perform Authorization Test via Utilities -> Test -> Authorization Test".

SolMan System: Job SM:EXEC SERVICES is processing the EWA data in SolMan.

Additional authorizations in NQA are nice, but of no relevance for EWA processing problem.

Former Member
0 Kudos

Thanks you

But I didn't see any other connection under ABAP

please check screen shot

http://www.flickr.com/photos/25222280@N03/2590180614/sizes/o/

Thanks

former_member209604
Active Contributor
0 Kudos

There is no need for further RFC connections. Which connection is missing?

Perform authorization tests for SM_NSMCLIENT100_BACK"

Former Member
0 Kudos

sorry for that last post... i was follow as per

Perform the following:

logon to system NQA

choose SM59 --> under ABAP connection --> "SM_NSMCLIENT100_BACK"

Perform Authorization Test via Utilities -> Test -> Authorization Test".

anyway! where is SM_NSMCLIENT100_BACK connection it sould be in solman or sdccn ? and what authorization is most impoartant for that

last time i just add roles S_RFCACL

please advised.... i belive so we done mostaly 70% workd please stay with me

Former Member
0 Kudos

This screen shot first NQA and NPR

sdccn --> Goto --> setting --> task processor

then click "check hosts"

selected "RFC destination SM_NSMCLNT100_BACK NSM 0020186334

and same procedure i apply to NQA as well

2nd screen is sdccn --> goto --> setting --> task specific

RFC destination setting

RFC destination SM_NSMCLNT100_BACK NSM 0020186334

then test rfc desc.

http://www.flickr.com/photos/25222280@N03/2589392731/sizes/o/

former_member209604
Active Contributor
0 Kudos

>

> logon to system NQA

> choose SM59 --> under ABAP connection --> "SM_NSMCLIENT100_BACK"

> Perform Authorization Test via Utilities -> Test -> Authorization Test".

What's the result of the authorization test?

>

> anyway! where is SM_NSMCLIENT100_BACK connection it sould be in solman or sdccn ? and what authorization is most impoartant for that last time i just add roles S_RFCACL

SM_NSMCLIENT100_BACK is created (visible via SM59) in satellite system NQA and pointing to SolMan System NSM.

SM_NSMCLIENT100_BACK is assigned in system NQA in transaction SDCCN

In which system, did you made this picture from SDCCN?

http://www.flickr.com/photos/25222280@N03/2589392731/sizes/o/

Ruediger

Former Member
0 Kudos

screen shot from NQA system

former_member209604
Active Contributor
0 Kudos

Screen Shot shows, that RFC destination SM_NSMCLIENT100_BACK is not functional in NQA.

Perform authorization test as recommended above, I assume problems with logon data.

Former Member
0 Kudos

Hi,

In NQA I have Roles defined

S_RFCACL

Z:BC_AUTHORIZATION_ADMIN

Z:BC_BASIS_USER

Z:BC_ENDUSER_GLOBAL

Z:BC_USER_ADMINISTRATOR

Is any thing else i have to add please advised

thanks

former_member209604
Active Contributor
0 Kudos

>

> In NQA I have Roles defined

> S_RFCACL

> Z:BC_AUTHORIZATION_ADMIN

> Z:BC_BASIS_USER

> Z:BC_ENDUSER_GLOBAL

> Z:BC_USER_ADMINISTRATOR

Roles in NQA are of no relevance.

RFC SM_NSMCLIENT100_BACK points from NQA to NSM.

The user assigned in the RFC is defined in NSM.

Please, please, please: Perform authorization test of destination RFC SM_NSMCLIENT100_BACK in system NQA as recommended above so many times.

Afterwards, you might need to fix the destination (may be reset password, check whether a user is defined at all in the destination).

Ruediger

Former Member
0 Kudos

first of all I am sorry, I didn't miss that point you was saying, I know you keep saying in NQA check authroz. for SM_NSMCLNt100_BACK, my question is how may i check that...

I tried sm59 double click on RFC SM_NSMCLINT100_Back... test connection, but i dind't found any authrozation option there...

in RFC under SM_NSMCLNT100_TRUSTED & SM_NSMCLNT100_BACK Remote login does not working in NQA... so now I know thats the problem... but how to setup authrozation ???

Thanks a lot your time...

former_member209604
Active Contributor
0 Kudos

>

>I know you keep saying in NQA check authroz. for >SM_NSMCLNt100_BACK, my question is how may i check that...

> I tried sm59 double click on RFC SM_NSMCLINT100_Back... test connection, but i dind't found any authrozation option there...

>

What's the release of SAP_BASIS of NQA?

The authorization check in SM59 is for example not available in 4.6c.

>

> in RFC under SM_NSMCLNT100_TRUSTED & SM_NSMCLNT100_BACK Remote login does not working in NQA... so now I know thats the problem... but how to setup authrozation

Remote login for SM_NSMCLNT100_BACK will not work if setup correctly. The assigned user in the RFC destination is usually a "Communication User", which does not a allow login in dialog.

Find out the assigned user name in the RFC destination. Verify the user exits in NSM, you might reset the password of the user in NSM and apply the new password in the RFC destination.

Don't know exact authorization, because I have currently no access to a system.

You should still evaluate the option to create a customer message on SV-SMG-SDD (provide logon data in secure area, open the connection). With system access, it's done in less than 15 minutes.

Ruediger

Best regards,

Ruediger

Former Member
0 Kudos

Yes, we are using 4.6c and there is no authroz. button, anyway!

about user type: i check su01 my user is dialog in NQA and also samething in NDV as well, as you know that NDV does works fine...

-


Find out the assigned user name in the RFC destination. Verify the user exits in NSM, you might reset the password of the user in NSM and apply the new password in the RFC destination.

-


When I check sm59 SM_NSMCLNT100_BACK screen bring all setting also logon: client 100 and user solman

is that you talking about assigned user name in the RFC destination ?

I checked SOLMAN user both system NDV, and NQA both are user type: dialog

both system roles define: Z:BC_SOLMAN

check user NQA user is not locked

check user NDV user is locked

Remember: NDV EWA works fine..

please advised

former_member209604
Active Contributor
0 Kudos

>

> -


> Find out the assigned user name in the RFC destination. Verify the user exits in NSM, you might reset the password of the user in NSM and apply the new password in the RFC destination.

> -


>

> When I check sm59 SM_NSMCLNT100_BACK screen bring all setting also logon: client 100 and user solman

> is that you talking about assigned user name in the RFC destination ?

Logon screen indicates, that password is wrong defined in RFC destination. Could you set the correct password.

Ideally, for every satellite system you have defined a specific user id in SolMan System NSM (see [Security Guide|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000673252&_SCENARIO=01100035870000000112&_OBJECT=011000358700007187872005E])

(for example as copy of user SOLMAN).

Going to bed now (and not really motivated to talk you through, it's too time consuming through SDN).

Use in NQA, in transaction SDCCN the Check RFC functionality to verify functional RFC connection with appropiate authorizations.

Ruediger

Answers (2)

Answers (2)

Former Member
0 Kudos

ok

former_member209604
Active Contributor
0 Kudos

>

> ok

Hi issue2008,

You have roughly opened 20 threads about your problems with activating EWA, trusted RFCs, SDCCN, ...

Now, you close all these threads with the reply "OK".

Many members (including me) have tried to help you, but this was quite difficult.

Have you been successful?

If yes, what has helped you?

If not, have you tried to contact SAP Support to receive help or requested support by a Consultant or friend?

Best regards,

Ruediger

Former Member
0 Kudos

It looks like something changed between your systems to cause the RFC failure. Can you re-establish these connections in SMSY?

Former Member
0 Kudos

Thanks you!!!

I tried SMT2 and double click RFC failer connection to change application server name, but its not allowed to changed mode....

how we change or edit RFC connection

and what is solman user, should I have to login that user ?

Thanks

Former Member
0 Kudos

You should be able to update (or add) RFC connections for each of the systems in transaction SMSY. Note that it is not necessary to use trusted RFC connections in order to login and run SDCCN remotely.

In SMSY, you will have to navigate down to each of the systems in order to edit the RFC connections. On my system the path is: Systems > SAP ECC > [system ID] > 'SAP ECC Server'

Does that help?

Former Member
0 Kudos

Thanks for reply!

I double check some RFC connection are working and someone does not, forexample XDV which is exchange infrastructure development does not working truested RFC fail..

ok so we consider that truested RFC connection is not working, but I am little bit confoused....

In solution Manager Overview we have the following entries:

BW landscape solution (with red flag)

R/3 Landscape solution (with red flag)

XI landscape solution (there is no red flag)

When I click on R/3 landscape solution

-


NDV sap earlywatch alert works fine

NPR sap earlywatch alert works fine

NQA sap earlywatch alert with red flag

So I check both NPR and NQA differences and I found out (which is has red flag) then I got this messages:

====================================================

The data for this session is overdue. Data has not yet been transferred from the associated satellite system.

Go to the Service Data Control Center (transaction SDCCN) in the satellite system and check why the data has not been sent.

Typical sources of errors are:

The RFC connection for the SAP Solution Manager system is not working.

The 'Task Processor' background job, which collects the session data, has been changed.

Problems arose while data was being collected (see the detail log for the task that collects the session data).

A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data.

Session number: 1000000001684

Back Call Service Data Control Center

=========================================

When I click on call service data control center I got messages line.... said

"Unable to reach remote system. No authorization to log on as a trusted system"

What does it mein that and how to resolved that problem is that RFC problem or someting else...

Please advised