Exception while generating Plugin Output Caused by: Error while rendering the report

Hi @AndersSvensson63,

Try solution mentioned in KBA-KB0053192
------------------------------------------------
Perform a mtctl stop and start on the namespace.


If this doesn't work, tell us the SU version? It seems that the issue for the error mentioned in the snapshot has been fixed in SU versions 22R2 SU23, 23R1 SU16, 23R2 SU09 and 24R1 SU03.

Hi @AndersSvensson63,

Better if you can provide the ifsapp-reporting & ifsapp-reporting-ren pod logs. That will help us to find the root cause of the issue.

We have a similar error occurring in print manager:

We are running cloud version 23.2.7.  This occurs when attempting to use the email function from the print dialog window.  It happens with any SSRS report.  The same SSRS report will run perfectly when attempting to preview it.  Restarting the pods seemed to have no effect.  I found the same error in the logs, but it didn’t seem to provide any more details.  I have attached the log and the errors are at the bottom.

​@ashen_malaka_ranasinghe and ​@Dharmendra  do you have any update on this question?

We are having the same issue as ​@jlandon296 above. 

​@jlandon296  ​@PhillBronson 

In the rpl, there is a section for <default-output-reference>

Have you tried adding the following in that section?

<file-sender></file-sender>

The sample doesn’t have it, but you could try adding it to see if that gets rid of the error.

https://docs.ifs.com/techdocs/23r2/060_development/025_operational_reporting/190_using_report_plugins/plugin_layout/

​@Tracy Norwillo yes I did add this with no difference in the given error. 

The logs posted above do seem very similar to mine

Errors from both [BatchProcessor] and [Application]

As well as the same error posted above

PhillBronson wrote:

​@Tracy Norwillo yes I did add this with no difference in the given error. 

The logs posted above do seem very similar to mine

Errors from both [BatchProcessor] and [Application]

As well as the same error posted above

 

Hi ​@PhillBronson ,

Could you please attach the .RPL layout file? Seems like there is a syntax issue within the .RPL file according to this error message.

​@ashen_malaka_ranasinghe yes I will do that. However, I do think we are glossing over one important point. These reports can be previewed through the same exact print dialog.

It is when they are emailed that this error occurs.

​@PhillBronson  If I had to guess, trying to email the SSRS reports invokes some IFS logic to check the rpl for the email defaults in the  <default-output-reference> section of the .rpl.  Trouble is the sample SSRS rpl does not have the file-sender tag.  

https://docs.ifs.com/techdocs/23r2/060_development/025_operational_reporting/210_ssrs_as_operationalreport/211_example__operationalreport/#plug-in_data

​@Tracy Norwillo I turned on more Server Logging and the errors above are accompanied by this error:

ORA-20105: Login.FUSRNULL: The directory id UNAUTHENTICATED is not allowed to run the application….

It looks like this error comes from `Login_SYS.Init_Fnd_Session___`
 

When running Fnd_Session_API.Get_Directory_Id in the database as the IFSAPP, I return NULL. However, when `Login_SYS.Init_Fnd_Session___` is called in production I have to assume `directory_id_` input is not null or we would fall into this error

IF (directory_id_ IS NULL) THEN
      Error_SYS.Appl_General(service_, 'DIRIDNULL: Directory id must have a value, can not be NULL.',
                             upper_directory_id_);
   END IF;

We don’t fall into the previous error we fall into one of the next errors

IF Fnd_Session_API.Get_Directory_Id IS NULL OR Fnd_Session_API.Get_Fnd_User IS NULL OR Fnd_Session_API.Get_Directory_Id <> upper_directory_id_ THEN
      fnd_user_ := Fnd_User_API.Get_Web_User_Identity_(upper_directory_id_);
      IF (fnd_user_ IS NULL) THEN
         Error_SYS.Appl_General(service_, 'FUSRNULL: The directory id :P1 is not allowed to run the application.',
                                upper_directory_id_);
      END IF;

…

I have not found where the directory id “UNAUTHENTICATED” is set...

Is there any difference in the authenticating user between Previewing the report vs Printing or Emailing the report?

Does IFSPRINT execute SSRS reports and impersonate the end user when previewing? Or does this behavior change between Previewing the report vs Printing or Emailing the report?

I can still upload the .rpl but I don’t think that is where the issue is based on this error

Turns out this is what our issue was.  I had previously tested this with an empty file-sender tag.  However, this time I had the idea to insert our mail sender as the value of tag.  To my shock it actually worked.  NO WHERE is it documented that this is necessary in Cloud.  We utilized the same layouts in Apps10 and this was never required.  IFS really needs to do a better job with documenting what is required.  Thanks to those that contributed with the clues to figure it out!