cancel
Showing results for 
Search instead for 
Did you mean: 

Information Broadcasting Error!

Former Member
0 Kudos

Dear Experts,

I have scheduled a job through Information broadcasting to distribute a Report to certain set of recepients. I have maitained a distribution list too..

I noticed that, in SM37 the job status seems to be finished but the email has not distributed.

Its showing the following error in rsrd_log

Error occurred during processing of framework class

"CL_RSRD_PRODUCER_EXCEL, type PROD"

I am not sure what the problem is.. Can one anyone help me out to fix this?

I am in BW 3.5 with service pack 17.

Thanks in advance,

Suraj

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Check in Transaction SCOT it will show you why it hasn't executed and will contain more information.

former_member205400
Active Participant
0 Kudos

Exactly,

Trans SCOT, on the top menu click on View | Nodes.

Make sure SMTP and RML are setup as nodes in trans SCOT.

Also, even after this was setup successfully on SU01 the Comm Method. It should be blank and you should be able to send mail to another address manually.

Answers (2)

Answers (2)

Former Member
0 Kudos

This message is attributed to a variety of different errors, but most, e.g. gateway problems, would effect all workbooks not jsut one. As mentioned check OSS Notes for that message.

You should also review the log files, tran RSRD_LOG and and SLG1, which usually has more info than RSRD_LOG.

There should also be a log file in the \Windows\Temp folder on the precalc server -named something like BEprecalcllog.txt or similar which should have detail about what happened on the precalc server, e.g. some sort of .Net Framework or resource problem. I beleive there is also an Environment variable that can be set on the precalc server to generate a trace file. See the How To on Troubleshooting Information Broadcasting.

Former Member
0 Kudos

A quick check of SAP Notes shows that this error is indicative of problems with the precalculation server. In particular, SAP Note 965221 seems to be relevant, and suggests that you upgrade to SP 19 to fix the problem.

Hope this helps...

Bob