I presume that when it gives the error you mention, you don't get any output at all (ie not even a blank PDF).
One reason to get this message it that report could not be found in the REPORTS_PATH.
Can you give more details about the time when you do get output, what do you see in the job queue details?
The fact that it runs ok in the reports develop indicates it is generally a configuration issue on the reports server.
As Tony was suggesting, FRM-41214 errors are most likely due to the fact that the REPORTS_PATH variable is not set up properly. As FRM-41214 is a very generic error, you can view the detailed results by going to http://hostname.domain:9002/reports/rwservlet/showjobs?server=name_of_reports_server. Clicking on the red X next to the failed reports job will reveal specific errors relating to the problem. The key error to look for is REP-110 where a file (report) cannot be opened.
To configure the REPORTS_PATH, all you need to do is:
If your environment is Windows:
1. Go to %ORACLE_INSTANCE%\config\reports\bin and modify the REPORTS_PATH inside the reports.bat to point to a directory where the report is deployed. Also, remove the "@REM" in the file with the line "set REPORTS_PATH". NOTE: Always make a backup of any configuration file or script before making any changes.
2. Update the REPORTS_PATH in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OH######## to point to a directory where the report is deployed. IMPORTANT: Make sure to backup the registry before making any changes.
Both will require a restart of the WLS_REPORTS server.
If your environment is Unix/Linux:
1. Go to $ORACLE_INSTANCE/config/reports/bin and modify the REPORTS_PATH inside the reports.sh to a directory where the report is deployed. NOTE: Always make a backup of any configuration file or script before making any changes.
This will require a restart of WLS_REPORTS.
After restarting WLS_REPORTS, test to see if the report runs.