Home » Developer & Programmer » Reports & Discoverer » FRM-41214: Unable to run report (Oracle Reports 12.2.1.3.0)
FRM-41214: Unable to run report [message #677863] Wed, 16 October 2019 13:06 Go to next message
Goldaxe
Messages: 31
Registered: September 2019
Member
Hi, I have reinstalled weblogic12c over other Linux machine, but I am not able to run a report:

* Report Server is RUNNING:

[oracle@dachserwls2 ~]$ sh /opt/oracle/Oracle/Middleware/Oracle_Home/user_projects/domains/base_domain/reports/bin/rwdiag.sh -findAll

Reading the rwnetwork.conf from :/opt/oracle/Oracle/Middleware/Oracle_Home/user_projects/domains/base_domain/config/fmwconfig/components/ReportsToolsComponent/reptoo ls1/rwnetwork.conf
Broadcast mechanism used to locate servers
------------------------------------------
Channel address = 228.5.6.7
Channel port = 14021

(1) Name = rep_wls_reports_dachserwls2 : Type = server : Host = dachserwls2


* But when I call a report from my fmx, through:
ReportServerJob := run_report_object(Report_id,PL_ID);

I get the error:
FRM-41214: Unable to run report

I attach you procedure Lanza_report


.rep and .fmx are on then same path.
The .env file contains REPORTS_PATH and FORMS_PATH variables with the correct path.
report has execution permissions


* If I execute:
http://172.24.47.103:9002/reports/rwservlet/showjobs?
I access to the reports console. I have no reports executed, but it is running.


*One doubt in my fmb:
SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_SERVER, 'WLS_REPORTS');
WLS_REPORTS is the name I see in my console, but then rep_wls_reports_dachserwls2 is up. Should I change WLS_REPORTS to rep_wls_reports_dachserwls2?

Thanks
Re: FRM-41214: Unable to run report [message #677984 is a reply to message #677863] Mon, 28 October 2019 08:40 Go to previous messageGo to next message
ranamirfan
Messages: 534
Registered: January 2006
Location: Pakistan / Saudi Arabia
Senior Member

Hi,

Could you Please login in Enterprise Manager.
http://localhost:7001/em
Check the Reports Server Status. See the screenshot.

/foru/forum/fa/14210/0/

Regards,
Muhammad Irfan


[EDITED by LF: removed unnecessary quote of the WHOLE previous message]

[Updated on: Fri, 08 November 2019 16:18] by Moderator

Report message to a moderator

Re: FRM-41214: Unable to run report [message #677987 is a reply to message #677984] Tue, 29 October 2019 03:14 Go to previous messageGo to next message
Goldaxe
Messages: 31
Registered: September 2019
Member
Hi,

I upload the files.

Thanks
Re: FRM-41214: Unable to run report [message #677988 is a reply to message #677987] Tue, 29 October 2019 03:15 Go to previous messageGo to next message
Goldaxe
Messages: 31
Registered: September 2019
Member
I upload the file
Re: FRM-41214: Unable to run report [message #677992 is a reply to message #677988] Tue, 29 October 2019 05:57 Go to previous messageGo to next message
ranamirfan
Messages: 534
Registered: January 2006
Location: Pakistan / Saudi Arabia
Senior Member

Hi,

To verify that Reports Server is running, navigate to the following URL:

Quote:


http://host:port/reports/rwservlet/getserverinfo?server=server_name

Regards,
Muhammad Irfan
Re: FRM-41214: Unable to run report [message #677993 is a reply to message #677992] Tue, 29 October 2019 06:35 Go to previous messageGo to next message
Goldaxe
Messages: 31
Registered: September 2019
Member
Hi,

I have already made the report work

Thanks for all
Re: FRM-41214: Unable to run report [message #677995 is a reply to message #677993] Tue, 29 October 2019 10:43 Go to previous messageGo to next message
Littlefoot_fan
Messages: 18
Registered: June 2019
Location: Uruguay
Junior Member
Just for the record, I believe it should be:

 SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_SERVER, 'rep_wls_reports_dachserwls2'); 

Glad you solved it!
Re: FRM-41214: Unable to run report [message #677996 is a reply to message #677995] Tue, 29 October 2019 11:13 Go to previous messageGo to next message
Goldaxe
Messages: 31
Registered: September 2019
Member
Now we have the problem that the report runs correctly but does not send it to the printer.

The code is:

Procedure Lanza_Report Is
PL_ID PARAMLIST;
TMPDATA VARCHAR2(10):= 'LISTA';
Report_id Report_Object;
ReportServerJob VARCHAR2(4000) := '';
vjob_id varchar2(200);
vc_rep_status varchar2(200);
Begin

Report_id := find_report_object('CTR80250');
--Report_id := find_report_object('MODULE3');
PL_ID:=GET_PARAMETER_LIST(TMPDATA);
IF NOT ID_NULL(PL_ID) THEN
DESTROY_PARAMETER_LIST(PL_ID);
END IF;
PL_ID:=CREATE_PARAMETER_LIST(TMPDATA);

----- parametros del sistema
Add_parameter(PL_ID,'BACKGROUND', TEXT_PARAMETER, 'YES');

SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_COMM_MODE, SYNCHRONOUS);

--Muestra el informe en la pantalla y deja el informe en el servidor (%DOMAIN_HOME%\reports\cache)
--tipo de salida
--SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_DESTYPE, CACHE);

--Para imprimir en impresora desde el formulario
--tipo de salida
SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_DESTYPE, PRINTER);
--nombre de la salida
SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_DESNAME, 'IMPBIOPCL_HP');

SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_DESFORMAT, 'PDF');


SET_REPORT_OBJECT_PROPERTY(Report_id,REPORT_SERVER, 'rep_wls_reports_dachserwls2');

Add_parameter(PL_ID,'PRINTJOB' , TEXT_PARAMETER, 'YES');

Add_parameter(PL_ID,'PARAMFORM' , TEXT_PARAMETER, 'NO');

-- parametros de ususario
ADD_PARAMETER(PL_ID,'PV_ALMACEN' ,TEXT_PARAMETER,:GLOBAL.ALMACEN);
ADD_PARAMETER(PL_ID,'PV_ARTICULO' ,TEXT_PARAMETER,:B1.MVM_ARTICU);
ADD_PARAMETER(PL_ID,'PV_CLIENTE' ,TEXT_PARAMETER,To_Char(:B1.DRV_PROPIE));
ADD_PARAMETER(PL_ID,'PV_CODMOV' ,TEXT_PARAMETER,To_Char(:B1.MVM_CODIGO));
ADD_PARAMETER(PL_ID,'PV_FECDES' ,TEXT_PARAMETER,To_char(:B1.DRV_FECDES,'dd/mm/yyyy'));
ADD_PARAMETER(PL_ID,'PV_FECHAS' ,TEXT_PARAMETER,To_char(:B1.DRV_FECHAS,'dd/mm/yyyy'));
ADD_PARAMETER(PL_ID,'PV_OPERARIO' ,TEXT_PARAMETER,To_char(:B1.Mvm_Operar));
ADD_PARAMETER(PL_ID,'PV_PALETA' ,TEXT_PARAMETER,:B1.Mvm_Paleta);
ADD_PARAMETER(PL_ID,'PV_TIPMOV' ,TEXT_PARAMETER,:B1.Mvm_TipMov);
--ADD_PARAMETER(PL_ID,'PV_TIPO_STOCK',TEXT_PARAMETER,:GLOBAL.Tipo_Operacion);
ADD_PARAMETER(PL_ID,'PV_TIPO_STOCK',TEXT_PARAMETER,'1');
ADD_PARAMETER(PL_ID,'PV_VARLO1' ,TEXT_PARAMETER,:B1.Mvm_Varia1);
ADD_PARAMETER(PL_ID,'PV_VARLO2' ,TEXT_PARAMETER,:B1.Mvm_Varia2);
ADD_PARAMETER(PL_ID,'PV_VARLOG' ,TEXT_PARAMETER,To_Char(:B1.Mvm_Varlog));
ADD_PARAMETER(PL_ID,'PV_CODFA1' ,TEXT_PARAMETER,:B1.CODFA1);
ADD_PARAMETER(PL_ID,'PV_SUBFA1' ,TEXT_PARAMETER,:B1.SUBFA1);
ADD_PARAMETER(PL_ID,'PV_CODFA2' ,TEXT_PARAMETER,:B1.CODFA2);
ADD_PARAMETER(PL_ID,'PV_WHERE' ,TEXT_PARAMETER,:B1.Drv_Where);
ADD_PARAMETER(PL_ID,'PV_2WHERE' ,TEXT_PARAMETER,:B1.Drv_Where2);

ReportServerJob := run_report_object(Report_id,PL_ID);

message('9');pause;
PL_ID := GET_PARAMETER_LIST(TMPDATA);
IF NOT ID_NULL(PL_ID) THEN
DESTROY_PARAMETER_LIST(PL_ID);
END IF;
END;
Re: FRM-41214: Unable to run report [message #677999 is a reply to message #677996] Wed, 30 October 2019 02:36 Go to previous messageGo to next message
Littlefoot_fan
Messages: 18
Registered: June 2019
Location: Uruguay
Junior Member
Have a look at this. Maybe it can help you.

Also, from oracle documentation:

Valid Values for DESTYPE

PRINTER

Sends the output to the printer on the server named in DESNAME. You must have a printer that the OracleAS Reports Services can recognize installed and running.
Re: FRM-41214: Unable to run report [message #678002 is a reply to message #677999] Wed, 30 October 2019 08:02 Go to previous message
Goldaxe
Messages: 31
Registered: September 2019
Member
Thank you. He already sends us to print but prints badly. Not all report format (margins) fit.
Is there a way to send the report to a printer and print it correctly regardless of the style of the printer itself?
Previous Topic: Month Sequence in Matrix Report
Next Topic: Command line optional parameter
Goto Forum:
  


Current Time: Fri Dec 06 12:08:03 CST 2019