Question

SSRS Report error


Userlevel 4
Badge +9

IFS 9 supports which version of SSRS Report ?

Kindly help to resolve this error ?


Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> Ifs.Fnd.FndSystemException: Unexpected error while calling server method PrintReport/ReportFormatRequest ---> Ifs.Fnd.FndServerFaultException: PluginExecute Failed. PluginException:SSRS:Error Executing plugin ifs.application.printagentservice.impl.extendedformatter.PluginException: PluginException:SSRS:rs.render com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DataSet1'. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors Please see the server log to find more detail regarding exact cause of the failure.
   at Ifs.Fnd.AccessProvider.FndConnection.ParseErrorHeader(FndBuffer buffer, FndManualDecisionCollection decisions)
   at Ifs.Fnd.AccessProvider.FndConnection.UnMarshalResponseHeader(Stream responseStream, FndManualDecisionCollection decisions)
   at Ifs.Fnd.AccessProvider.FndConnection.HandleHttpSuccessResult(HttpWebResponse result, FndManualDecisionCollection decisions, String operation, FndBodyType responseBodyType, Object responseBody)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync)
   --- End of inner exception stack trace ---
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync)
   at Ifs.Fnd.AccessProvider.Activity.FndActivityContext.Invoke(String intface, String operation, Object request, Object response)
   at Ifs.Fnd.AccessProvider.Activity.FndActivityCommand.ExecuteNonQuery(Object body)
   at Ifs.Application.InfoServicesFramework.ServerInterface.Ifs.Application.InfoServicesFramework.IPrintReport.ReportFormatRequest(Double resultKey, String formatRequest, String langCode, String& pdfFile, Byte[]& pdf)
   at Ifs.Application.InfoServicesFramework.PrintDialog.ReportFormatRequest(PrintInstance instance, String& filename, Byte[]& pdfData)
   at Ifs.Application.InfoServicesFramework.PrintDialog.PreviewReport(PrintInstance instance)
   at Ifs.Application.InfoServicesFramework.PrintDialog.cmdPreview_Execute(Object sender, FndCommandExecuteEventArgs e)
   at Ifs.Fnd.Windows.Forms.FndCommand.OnExecute(Component component)
   at Ifs.Fnd.Windows.Forms.FndCommandButton.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   --- End of inner exception stack trace ---


12 replies

Userlevel 6
Badge +14

Hi @proharikg,

 

Could you please check if the SSRS Report Server URL(configured using IFS Installer) is in the correct format. The URL should look like this,

 

http://<ssrs-host>/ReportServer/reportexecution2005.asmx

 

Hope this helps!

Userlevel 5
Badge +10

This instance can be of MSSQLServer 2008R2, MSSQLServer2012 or MSSQLServer2014.

1. At what point you came across the mentioned error?
2. SSRS Extension installation was successful?

These extensions can be installed using the IFS – MS SQL Server Extensions Installer. The installer can be accessed from

 <Build_Home>/Win32Server/SQL Server Extensions/Install/IFSBISSExtInstaller.exe

Userlevel 1
Badge +4

Hi Himasha/Charith,

Good Day.

Thanks for your information.

We are facing this issue in customer invoice report. All other reports are working fine.

Previously this report is working fine. after a adding one text box in layout design and we didn’t modify the SQL query.

Kindly find the below mentioned url in System parameters in IFS app 9 our environment.

Please check and get back us if possible kindly contact us in infanteena13@gmail.com .

Regards,

Magnus Infan teena

Userlevel 1
Badge +4

Good Day.

Thanks for your information.

We are facing this issue in customer invoice report. All other reports are working fine.

Previously this report is working fine. after a adding one text box in layout design and we didn’t modify the SQL query.

Kindly find the attached  System parameters url in IFS app 9 our environment.

Please check and get back us if possible kindly contact us in infanteena13@gmail.com .

Regards,

Magnus Infan teena

Userlevel 6
Badge +11

I’m assuming that this is an Operational Report of SSRS.

If so, it looks like that the Dataset you have pointed in the published report in the SSRS server is incorrect. Check if the correct dataset is  'DataSet1' and if so, check if  'DataSet1' correctly configured.

 

Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DataSet1'. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors Please see the server log to find more detail regarding exact cause of the failure.
   at Ifs.Fnd.AccessProvider.FndConnection.ParseErrorHeader(FndBuffer buffer, FndManualDecisionCollection decisions)

Userlevel 1
Badge +4

@ChanakaAmarasekara Thanks for the reply.

 

Query is running fine. please tell how to check dataset1 configured properly.

Please.

Userlevel 6
Badge +11

@ProMagnus Have a look at the following video

https://wit.ifsworld.com/technology/recordings/content/SSRS%20_Development.mp4

 

This shows how to design a SSRS Operational Report.

Userlevel 1
Badge +4

@ChanakaAmarasekara After modification in ssrs layout, for few reports while preview it displays blank. So, I did again overwite existing rdl in reporting service.

 

But not uploaded rpl. And I run the report in ifs. I think so only I m getting this error. Correct?

 

 

Userlevel 1
Badge +4

@ChanakaAmarasekara can please tell me that when upload the RDL file in reporting service, we need to upload this file in somewhere or we need to modify in some location. because we are getting same error in ifs. after modification also it is not changed.

 

Please help.

Userlevel 6
Badge +11

@ProMagnusIf the RPL is not changed then you don’t have to import it. If the RDL is changed then you need to publish the layout in the server again. Also, when designing you need to make sure that you have the same dataextention installed in the design machine and the SSRS server.

If this doesn’t help. It’s good if you have a look at the logs as the error message says and contact support for further help.

Userlevel 1
Badge +4

@ChanakaAmarasekara 

we are using is MS sql Server 2012 report builder 3.0.

on the first day of error, in report log I m getting the error as

e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot read the next data row for the dataset DataSet1. ---> System.Threading.ThreadAbortException: Thread was being aborted.

 

above error message received just for one day. Later days, I m not getting this error. But in IFS application 9, it showing same error  Query execution failed for dataset “Dataset1”.

 

 

 

Userlevel 6
Badge +11

@ProMagnus It looks like that you have an issue with you database connection or dataset, This needs more troubleshooting therefore I suggest that you contact LCS Support for this matter.

Reply