What is Error 17070

Does anyone know what error 17070 is about. Sometime the report works fine, other times we see 17070 error before parameters are displayed.

Find more posts tagged with

Comments

kclark

Are you getting any sort of stack trace with it?

Kite

2 kclark:I have the similar problem.The most annoying thing is that there is no stack trace so it's not possible to understand the cause of error.

micajblock

There are two ways to find the errors.1. Error Log window (should be in the bottom right pane (if you reset your perspective, it should be properties, problem, error log...)2. There is also a log file in the under <workspac directory>.metadata simply name ',log'

BRM

I usually get this error when the dataset and the column bindings for a table don't line up for some reason. Try this:1. Select a table in your report.2. Click bindings3. Set the dataset to "None" - you will get a dialog that says you are about to clear all your data bindings. Click OK.4. In the same dropdown set the dataset binding back to the dataset that should provide the data for the table.5. Re run the report. Note: there is a button on the bindings tab called "Refresh" that presumably should refresh the bindings without having to blow them away first but I have has limited luck with it. You could try this first in place of step 3 above. If it doesn't work then try Step 3 as above. Good luck.

BRM

Update: I am also getting this error when there is an error in a script element in a part of the report. Its a maddening error message because it just appears as an error message in the web viewer. There is no stack trace with it.

gowtham

Hi, I am getting this error after deploying in iServer. In development it is not showing any error and i am getting value.
 
Any idea to fix this? 
 
Regards, 
Gowtham

BRM

This is just a guess but make sure that the database drivers are the same between your dev environment and iServer. I have had problems when, for example, I tried to use one of the several MSSQL drivers in dev but iServer used (or required the use of) another (usually the Actuate one).

JFreeman

You are going to need to examine the errors within the log files to determine the cause of the error.
 
If you are running the report transiently, you will want to investigate the jsrvr log file and if you are scheduling the report as a background job you will want to examine the jfctsrvr log file.
 
For either way of running the report, the encycsrvr and jencycsrvr logs may also have some information about the error.