Report Designer - Binding Error

Hi Guys,
I am trying to use the report designer to build some reports. When I assign any dataprovider to my report - query/query view, I am getting an error "Binding Error for Characteristics"/"Binding Error for Key Figures". Can you please let me know if someone has faced this error and what can be the possible resolution. This is kind of urgent because none of the queries seem to work. We are on SPS 9 which I know is not the best.
Thanks,
Pratik.

is it an DROPDOWN you trying to add dataprovider??
Hope it Helps
Chetan
@CP..

Similar Messages

Report data binding error

I have created a banded report split into departments. Each
recore has a value associated with it. The report runs fine if I
dont try to sub-total each departments vale, but if I add a
calculated field to the banding, I get the following error:
Report data binding error Error evaluating expression :
textField_2 Source text : calc.Department_Total.
Variable calc.Department_Total is undefined.
The calculated field is simply the sum of the values, with an
initial value of 0 and set to reset when the group changes on the
department. I am using the same data type for the calc field as it
automatically gave for the original Value field (Big Decimal)
Any ideas?
Dave H

Does anyone have any ideas about this, Its getting a bit
critical now. Has anyone else been able to do sums that calculate
on group changes?? The sum total works for the report, jusyt not
the bands. I desparate here, pulling my hair out.
Regards
Dave H

Report data binding error unknown column name

Hi,
I am having a problem with the new 7.02 update of Report
Builder. The issue is it's not finding my SQL query.
I have wrote my query initally in the advance mode, and it
doesn't seem to reconize it. Is there an issue with this?
I did manage to fix one of my reports by using the basic mode
and selecting all my tables and seting my linkage and criteria.
I have other computers that i have not updated to 7.02 and
they do not have this issue. Below is the error:
Error Occurred While Processing Request
Report data binding error Unknown column name : work_phone.
Please try the following:
Check the ColdFusion documentation to verify that you are
using the correct syntax.
Search the Knowledge Base to find a solution to your problem.
Browser Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;
.NET CLR 1.1.4322; .NET CLR 2.0.50727)
Remote Address 127.0.0.1
Referrer
Date/Time 13-Jul-06 02:33 PM
Stack Trace (click to expand)
coldfusion.runtime.report.Report$ReportDataBindingException:
Report data binding error Unknown column name : work_phone.
at
coldfusion.runtime.report.Report.runReport(Report.java:420)
at
coldfusion.filter.ComponentFilter.invoke(ComponentFilter.java:96)
at
coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:225)
at
coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:52)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)
at
coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:69)
at
coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8)
at
coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at
coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at
coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.xml.rpc.CFCServlet.invoke(CFCServlet.java:106)
at coldfusion.xml.rpc.CFCServlet.doGet(CFCServlet.java:157)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:78)
at
jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at
jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at
jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:257)
at
jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527)
at
jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:204)
at
jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:349)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:457)
at
jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:295)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
This report works in 7.01. So all query variables match with
a variable in the SQL select statement.
Anyone have any Ideas??
Thanks,
Daniel

Thank you very much for help.
The "Unknown column name " is a field still used in my
report, so I can't remove it.
After I clear the query in the report and reopen the report
and apply the same query back to it, I get different error message:
Element TASKNUM is undefined in QUERY.
The error occurred in : line 1
-1 : Unable to display error's location in a CFML template.
I know for sure this "Element TASKNUM is undefined in QUERY."
is defined in query. each time it complains something different. I
get really confused.
Thanks again.
Yueming

Report data binding error with date values

I have CF7.02 with a Microsoft Visual FoxPro 9.0 SP1 Database
that I connect to using ODBC (FoxPro Driver 6.01.8630.01). I send
my sql results to a CF Report Builder 7.02 PDF report and it works
fine. If I dump the date values before I change them, they look
like the following: {ts '2004-12-20 00:00:00'} . However I have
tried a number of ways of manipulating the date before sending it
to the report, but I continue to get errors. I don't care what
format they go to the report in, since the report reformats them
anyway. I checked to make sure that none of the dates were null.
For example <cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDateTime(#ldCFPrcInputDate#) /> yields values in the
{ts '2004-12-20 00:00:00'} format when I dump the query results to
screen. Where:
ldCFPrcInputDate = 12/20/2004
CreateODBCDateTime(ldCFPrcInputDate) = {ts '2004-12-20
00:00:00'}
ReportQuery.PrcInputDate[lcCurRow] = {ts '2004-12-20
00:00:00'}
I get the error:
Report data binding error Unable to get value for field
'prcinputdate' of class 'java.util.Date'.
coldfusion.runtime.OleDateTime -> Date
Not using the CreateODBCDate function for example <cfset
ReportQuery.PrcInputDate[lcCurRow] = #ldCFPrcInputDate# /> I
get:
Report data binding error Unable to get value for field
'prcinputdate' of class 'java.util.Date'.
java.lang.String -> Date
Here are some of my failed attempts:
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDateTime(#ldCFPrcInputDate#) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
#ldCFPrcInputDate# />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
DateFormat(CreateODBCDate(#ldCFPrcInputDate#),'mm/dd/yyyy') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(DateFormat(#ldCFPrcInputDate#,'mm/dd/yyyy') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(DateFormat(#ldCFPrcInputDate#,'mm-dd-yyyy') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
Trim(createODBCDateTime(ldtmpdate)) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate({05-07-2006}) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate('{05-07-2006}') />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(05/07/2006) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate('05/07/2006')/>
<cfset ReportQuery.PrcInputDate[lcCurRow] =
CreateODBCDate(parseDateTime('05/07/2006')) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
parseDateTime(CreateODBCDateTime(05/07/2006)) />
<cfset ReportQuery.PrcInputDate[lcCurRow] =
parseDateTime(CreateODBCDateTime('#ldCFPrcInputDate#')) />
<cfset ReportQuery.PrcInputDate[lcCurRow] = '{05-07-2006}'
/>
<cfset ReportQuery.PrcInputDate[lcCurRow] = '{05/07/2006}'
/>
<cfset ReportQuery.PrcInputDate[lcCurRow] = '05/07/2006'
/>
I also did some googling without success. Any help is
appreciated.

You may want to make sure that the column is not included in
the query variable list in your report cfr file.
The newest version of the Report Builder, which may be
installed on the server, no longer tolerates vars appearing in that
list of they are not in the query itselft.

Report Data Binding Error with CFREPORT

I'm getting this error on my production server but not my
testing server when I try to print a report:
Report data binding error Unknown column name :
PK_RegistrationID.
The thing is, the column PK_RegistrationID is not in the
query I'm passing to the cfreport file. And it's not in the
cfreport fiile itself. It is used in other cfreport files in my
application. I'm wondering if this has anything to do with the
version of cfreport on the production server.

You may want to make sure that the column is not included in
the query variable list in your report cfr file.
The newest version of the Report Builder, which may be
installed on the server, no longer tolerates vars appearing in that
list of they are not in the query itselft.

"Report Designer" Execution Error

Hi Gurus...
client is using SAP GUI 710 version. while executing the report using "Report Designer".
we are getting an error, "This report web Itemcan display reports with versionnumber 2.1 or lower. this report has version number 2.2" To display this report, use a newer version of the report web Item"
this is the error, <removed by moderator>
Cheers
Edited by: Siegfried Szameitat on Jan 19, 2009 12:48 PM

Unable to see Hierarchies in report designer?
cheers

Report Desinger: Binding error for characteristic / Key Figure

Hi,
I am getting the error "Binding error for characteristic: Reference to characteristic".
I have created a report using a query and I have to change the query as per requirement, removed a characteristic.
Now when I execute a report, getting Data binding error.
Does system not changes the report if we change the provider query?
How can this issue be handled apart from deleting existing report and creating a new one?
Appreciate your help in advance.
Regards,
Amit

Amit,
First, try doing a save as on your report and save it under a new name. Delete the old one, then re-save it as the same name as before. Then, go in and clear cache so that it will re-build all references in the query. This should remove the error and you won't have to rebuild anything.
Cheers,
Rusty

Microsoft Report Designer: Undocumented Error

Hi all, I am working with asp.net reporting using RDLC file. Everything was working fine but now when I add a new dataset, an error occurs.
Undocumented Error.
Could not load file or assembly 'PrecisionCareEntity, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
I have no more info than this, to provide you people to diagnose the problem. Have anyone idea what would be happening?
I just want to add a new dataset.

I solved the problem by following this method:
1. Add a datasource in your report viewer i.e. in aspx page
<asp:ObjectDataSource ID="odsAdmission" runat="server"
OldValuesParameterFormatString="original_{0}"
SelectMethod="SelectAdmissionForReport"
TypeName="PrecisionCareBLL.AdmissionBLL.AdmissionLogic">
<SelectParameters>
<asp:QueryStringParameter Name="admissionId" QueryStringField="Id"
Type="Int32" />
</SelectParameters>
</asp:ObjectDataSource>
2. Go to its designer and click on the arrow appearing in front of datasource, and click on it.
3. Click Refresh Scehma and Save the file.
4. Go to its code again and comment the datasource code.
5. Try adding new dataset in rdlc. It will allow adding new datasets now.
I solved my problem in this way. Hopefully it will be helpful for you as well. Don't forget to response here if it is helpful.

BI Report Designer throws error while executing.

When I execute a query in query designer, it asks for username and password of the portal, I give mine and enter side. The page loads for 1 minute and then throws this error
Exception in BI runtime
Initial cause
Message:
No message was provided.
Stack trace:
java.lang.OutOfMemoryError
Message:
No message was provided.
Stack trace:
com.sap.ip.bi.webapplications.runtime.controller.MessageException     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:1575)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:884)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:835)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:328)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)     at java.security.AccessController.doPrivileged(Native Method)     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Caused by: java.lang.OutOfMemoryError
Sometimes, it is throwing this 2nd error
2ND ERROR
500 Connection timed out
Error: -5
Version: 7000
Component: ICM
Date/Time: Thu Aug 31 11:34:04 2006
Module: icxxthr.c
Line: 2646
Server: spotbiwd1_BID_01
Error Tag: {-}
Detail: Connection to partner timed out after 60s
Please help me resolve this issue.

Hi There,
know it is an older thread but I am running into something similar but not really the same.
When executing a bex query in the designer I get the 2 following messages:
Stack trace:
java.lang.NullPointerException     at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Structure.getString(Jco640Structure.java:84)     at com.sap.ip.bi.base.application.service.impl.statistic.StatisticService.writeEvents(StatisticService.java:47)     at com.sap.ip.bi.base.application.statistic.impl.StatisticApplicationStep.endApplicationStep(StatisticApplicationStep.java:78)     at com.sap.ip.bi.base.application.statistic.impl.StatisticManager.stepClose(StatisticManager.java:179)     at com.sap.ip.bi.base.application.impl.Application.endApplicationStep(Application.java:218)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:1096)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:694)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:666)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:318)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)     at java.security.AccessController.doPrivileged(Native Method)     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Message:
No message was provided.
Stack trace:
com.sap.ip.bi.webapplications.runtime.controller.MessageException     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:715)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:666)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:318)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)     at java.security.AccessController.doPrivileged(Native Method)     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Caused by: java.lang.NullPointerException     at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Structure.getString(Jco640Structure.java:84)     at com.sap.ip.bi.base.application.service.impl.statistic.StatisticService.writeEvents(StatisticService.java:47)     at com.sap.ip.bi.base.application.statistic.impl.StatisticApplicationStep.endApplicationStep(StatisticApplicationStep.java:78)     at com.sap.ip.bi.base.application.statistic.impl.StatisticManager.stepClose(StatisticManager.java:179)     at com.sap.ip.bi.base.application.impl.Application.endApplicationStep(Application.java:218)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:1096)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:694)     ... 35 more
Any idea?
Thanks,

Error at report designer while opening the query

Hi
in report designer i am trying to open query
i am getting error like
error while loading query meta data
check the query and portal settings
i am getting this error only this report only
Diagnosis
An error occurred in the BI components on the SAP J2EE Engine.
System Response
Procedure
Contact your system administrator to have the error analyzed in detail.
Procedure for System Administration
Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.

Hi Suneel,
If you are using any JAVA based applications or objects in the Report designer this error is thrown.
It's better to install Java engine to correct this error.
You must contact Basis people in order to solve this issue.
With Regards,
Ravi Kanth

WAD report with Report Item occurs binding error

Hi,
We created a report by Report Designer and embaded in a WAD report. If we run the report in Report Designer,
It can generate the result correctly, but it will show "Binding error for characteristic value: / Binding error for key figure:Dynarmic" if we run it from WAD. Our server is on 7.01 SP6.
Thank you
Best Regards,
Michelle Lee

Hi Michelle,
The normal data references in a query have a reference to a dataprovider which should be static binding.
It may be that by using the Report Designer and then embedding the query in the WAD, the references have been lost and therefore you see the 'dynamic' mesage as the binding is not available anymore.
Hope this helps,
Karen

Report Designer - Error while opening a saved report

Hi,
I am not sure if this is an authorization issue or configuration issue.
When I try to open a saved report on Report designer, I keeping getting an error: Report Version is invalid: "0".
Has anybody faced similar problem?
We are on SP09.
Regards,
Payal.

Payal,
I am afraid, that your report might be corrupted. This might have happened, if in tx SE16 the version is changed. The Report XML displayed in SE16 for table RSERDATA, is limited to ca. 1024 charachters. When editing the version, after pressing the save button, the Report XML is cut off at 1024 charachters and the report is lost.
Please do not set the report version in tx SE16!
I will need to configure the program RS_REPORT_MAINTAIN, such that reports with version "0" can be saved with the minimum version 9.0.
Until then I recommend the following procedure for Reports that are ok, but have the Version "0" bug:
1) in tx SE38, program: RS_REPORT_MAINTAIN
    open your report with option "DT" (designtime)
2) Switch to Edit mode.
    Make a backup copy of the report using the "Save As" Button.
    You can copy the Report XML to the clipboard using Ctrl-A, Ctrl-C
3a) Open a dummy report in RS_REPORT_MAINTAIN created previously with
      Report Desginer ( --> The version is set to 9.0).
      Switch to edit mode and paste the Report XML and Save.
or
3b) Debug FUNCTION rs_bex_report_load_rfc.
      Open a report and change the value of E_REPORT_VERSION to "9.0"
      before leaving the function.
Hope this helps, karim
P.S.
I will update note 1016224

Error while generating PDF BI 7 Report Designer

Hi,
I am getting this error Error while generating PDF when i tried print version on report designer,
I tried to find information on this error but there was no information regarding this , so posted here.
Please let me know if you have any suggestions.
Thanks,
Kumar

We have restated the java server and now the issue solved.
Kumar

Error In Report Designer

Hi
When I'm opening a view in report designer I'm getting the following error.Can anyone please help me with this.Its very urgent for me to sort this issue.
<b>The report designer doesn't support the query drilldown.
Key figure in static filter is not yet supported.</b>
For this particular query I have used only cell definitions in rows and colums.and some Hierarchies are there in the global filter.

Hi Harinath,
I have had this problem due to the fact I had variable in the filter in the query designer, I put fix selection in the filter then generate the report an after I put back my varibale in the filter.
Hope this help.
Eric

Error message in Report designer "Activate Default Theme: 0TRADESHOW"

Hi,
While working in Report Designer, I repeatedly get an error message saying "Activate Default Theme: 0TRADESHOW. See Note 1071338". After following the instructions and activating this theme, the problem still persists.
Anyone with a solution to this problem? We are running BI 7, package level 17.
Regards
Nils

Hi all,
I had the same issue and finally solved re-installing BC in BACKGROUND mode.
For unknown reason, my first istallation generate the a 0TRADESHOW entry with version D in table RSTHEMES.
Later attempts to re-install BC were not modifying this table.
Until I tryied Background Installation. It promped for overwriting current installation, I accepted and A version get generated.
best regards
Carlos Serrano

Report Designer - Binding Error

Similar Messages

Maybe you are looking for