Deployment error: The Entity EJB requires the table: to be accessible

Hello
When I deploy my EJBs, WEBLogic throws an exception:
Unable to deploy EJB: OrderBean from ejb-jar-ic.jar:
The Entity EJB requires the table: Order to be accessible. Please ensure that th
is table exists and is accessible.
I use built in Cloudscape database.
And I have those lines in descriptor:
<weblogic-rdbms-bean>
<ejb-name>OrderBean</ejb-name>
<data-source-name>ejbDS</data-source-name>
<table-name>Order</table-name>
<field-map>
<cmp-field>totalAmount</cmp-field>
<dbms-column>totalAmount</dbms-column>
</field-map>
<field-map>
<cmp-field>time</cmp-field>
<dbms-column>ordertime</dbms-column>
</field-map>
<field-map>
<cmp-field>orderID</cmp-field>
<dbms-column>orderID</dbms-column>
</field-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>True</create-default-dbms-tables>
thanx in advance
Maris

Hi Maris,
I see that you have create-default-dbms-tables set to true so WLS should be creating
the database table for your EJB. If you can give me some more information, I'll be
able to help you further. What version of WLS + service pack are you using? Also,
is this a 1.1 bean or 2.0? Lastly, what are the types of the CMP fields in your
bean?
As a work-around, you can try creating the database table yourself before deploying
the bean. This should resolve the deployment problem.
- Matt
Maris wrote:
Hello
When I deploy my EJBs, WEBLogic throws an exception:
Unable to deploy EJB: OrderBean from ejb-jar-ic.jar:
The Entity EJB requires the table: Order to be accessible. Please ensure that th
is table exists and is accessible.
I use built in Cloudscape database.
And I have those lines in descriptor:
<weblogic-rdbms-bean>
<ejb-name>OrderBean</ejb-name>
<data-source-name>ejbDS</data-source-name>
<table-name>Order</table-name>
<field-map>
<cmp-field>totalAmount</cmp-field>
<dbms-column>totalAmount</dbms-column>
</field-map>
<field-map>
<cmp-field>time</cmp-field>
<dbms-column>ordertime</dbms-column>
</field-map>
<field-map>
<cmp-field>orderID</cmp-field>
<dbms-column>orderID</dbms-column>
</field-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>True</create-default-dbms-tables>
thanx in advance
Maris

Similar Messages

Crystal report error (The table '' could not be found)

Dear Expert,
As I know, the end user who don't want to edit the crystal report design no need to buy crystal report,right?
Using the 'Crystal reports for SAP B1', they already view the report.
But, how about, if I had created one crystal report, and then I want to distribute to end user. When I load the report on user machine that dont have crystal report, the system shown an error (The table '' could not be found).
I think, maybe because of the database location. When I create the report, of course I made connection to my machine as a source of database location. But, how i'm going to change the database location to user machine?
Is it when we login into SAP, did SAP auto detect the new location source? And will auto create connection to the crystal report?
Thanks in advance for any help.

Hi ,
We do not create the database connection for the end user. the end user must have the same database connection as it is set up on your machine. The report is looking for the same connection, with the same access into the database.
Best regards,
Jadie

Error:The table 'table1' refers to an invalid DataSetName 'dataList'

I am getting this error The table 'table1' refers to an invalid DataSetName 'dataList'
I check the data set name and it is spelled correct
what might be the reason for this error

Hi Developer,
In SQL Server Reporting Services, when you changed a dataset name or try to point to another dataset name, this error message is often generated as a result. This is because you have referred to a wrong dataset.
To troubleshoot this issue, we should make sure the desired dataset is created correctly without any error firstly. Then right-click the table which does cause the trouble to open the Properties dialog box, and then select the desired dataset under the Dataset
name drop-down list in the General tab. If the issue is still existed, please recreate the table to test again.
The following similar thread is for your reference:
http://social.technet.microsoft.com/Forums/en-US/5db17dc5-044e-4c0a-8dfd-dd4feceec6fe/rsinvaliddatasetname-the-table-table1-refers-to-an-invalid-datasetname-dataset1?forum=sqlreportingservices
If there are any other questions, please feel free to ask.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Errors when deploy a simple entity ejb module to oc4j 10g?

I work as following steps:
1. new project
2. new Digram-->EJB Diagram
3. Drag a Entity bean ico to Diagram and name it with Student, then add a id&name column to it.
4 set the entity-ejb Student's Resource Reference's property: name(MysqlPool),ResourceType(com.mysql.jdbc.Driver),Authentification(Container)
(in oc4j, I have set the pool connection--MysqlPool)
5 use command to start oc4j 10.1.3 in jdev10.1.3
6 In Jdeveloper IDE, select ejb-jar.xml and use right mouse button to call out the menu and then select "Cretae ejb or jar deploy profile", set the deploy platform to my oc4j connection.
7 select the deploy profile and deploy to my oc4j connection, then errors were reported as following:
Target platform is Standalone OC4J 10.1.3 (AppServerConnection1).
Wrote EJB JAR file to D:\jdevj2ee1013\jdev\mywork\Application1\Project1\deploy\ejb1.jar
Wrote EAR file to D:\jdevj2ee1013\jdev\mywork\Application1\Project1\deploy\ejb1.ear
Uploading file ...
Application Deployer for ejb1 STARTS.
Do not undeploy previous deployment
Copy the archive to D:\jdevj2ee1013\j2ee\home\applications\ejb1.ear
Initialize D:\jdevj2ee1013\j2ee\home\applications\ejb1.ear begins...
Unpacking ejb1.ear
Done unpacking ejb1.ear
Initialize D:\jdevj2ee1013\j2ee\home\applications\ejb1.ear ends...
Starting application : ejb1
Initializing ClassLoader(s)
Initializing EJB container
Loading connector(s)
Starting up resource adapters
Processing EJB module: ejb1.jar
Compiling EJB generated code
Error while compiling EJB component: D:\jdevj2ee1013\j2ee\home\applications\ejb1\ejb1.jar
com.evermind.compiler.CompilationException: Error finding a suitable DataSource: Error looking up cmt-datasource at jdbc/OracleDS (name not found)
     at com.evermind.server.ejb.compilation.EntityBeanCompilation.createTable(EntityBeanCompilation.java:257)
     at com.evermind.server.ejb.compilation.EntityBeanCompilation.preCompile(EntityBeanCompilation.java:318)
     at com.evermind.server.ejb.compilation.Compilation.generateAnyOldStyle(Compilation.java:1728)
     at com.evermind.server.ejb.compilation.Compilation.compile(Compilation.java:162)
     at com.evermind.server.ejb.compilation.Compilation.doGenerateCode(Compilation.java:216)
     at com.evermind.server.ejb.EJBContainer.postInitBatch(EJBContainer.java:1197)
     at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1118)
     at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:200)
     at com.evermind.server.Application.setConfig(Application.java:299)
     at com.evermind.server.Application.setConfig(Application.java:226)
     at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1740)
     at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:403)
     at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:144)
     at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:95)
     at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:53)
     at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:68)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:299)
     at java.lang.Thread.run(Thread.java:534)
application : ejb1 is in failed state
java.lang.InstantiationException: Error initializing ejb-module; Exception
Error compiling D:\jdevj2ee1013\j2ee\home\applications\ejb1\ejb1.jar: Error finding a suitable DataSource: Error looking up cmt-datasource at jdbc/OracleDS (name not found)
     at com.evermind.server.ejb.EJBContainer.throwInstantiationException(EJBContainer.java:2285)
     at com.evermind.server.ejb.EJBContainer.postInitBatch(EJBContainer.java:1422)
     at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1118)
     at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:200)
     at com.evermind.server.Application.setConfig(Application.java:299)
     at com.evermind.server.Application.setConfig(Application.java:226)
     at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1740)
     at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:403)
     at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:144)
     at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:95)
     at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:53)
     at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:68)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:299)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.InstantiationException:
Error compiling D:\jdevj2ee1013\j2ee\home\applications\ejb1\ejb1.jar: Error finding a suitable DataSource: Error looking up cmt-datasource at jdbc/OracleDS (name not found)
     at com.evermind.server.ejb.EJBContainer.postInitBatch(EJBContainer.java:1226)
     ... 12 more
Operation failed with error:
java.lang.InstantiationException: Error initializing ejb-module; Exception
Error compiling D:\jdevj2ee1013\j2ee\home\applications\ejb1\ejb1.jar: Error finding a suitable DataSource: Error looking up cmt-datasource at jdbc/OracleDS (name not found)
Deployment failed
Elapsed time for deployment: 41 seconds
#### Deployment incomplete. #### 2005-2-15 10:46:02
what's the meaning about Error finding a suitable DataSource: Error looking up cmt-datasource at jdbc/OracleDS (name not found)?
I didn't use jdbc/OracleDS Datasource, and I deleted it from config\data-source.xml.
Is it cause those errors or my operation rong?
Who can tell me the entity ejb's deploy method&step?

Yes, now I added a connection pool and a datasource in oc4j, and set the datasource's jndi name to "jdbc/OracleDS".For The connection pool,I use the mysql database.
Followed the above operation, I repeat the deployment and it deployed successfully.
Viewed by web-control-for-oc4j, I found jdeveloper automaticly created a datasource and pool for the ejb module.However, the datasource's parameter(connection-factory factory-class="oracle.jdbc.pool.OracleDataSource") is wrong.
So I open Tools Menu->Preferences menu and setted the Deploy property to "unbundle datasource...".Then I Created a file named data-sources.xml in project and filled out the correct properties.
After I deploied the ejb-module, I openned the deploied .ear file with winrar to view its contents.I found the factory-class property's value is still wrong which included in data-sources.xml file in Mata-Inf directory,but the property of the data-sources.xml file in .jar file is correct.So, the class factory value of the deploied ejb-application's connection pool still is "oracle.jdbc.pool.OracleDataSource".It couldn't work surely.
Of course, I can modity the data-sources.xml in .ear file.
But has some more better method to settle this problem while not manuelly?

RAS Error - The table could not be found.

Hi,
Bo version : XI2 SP2
BO SDK : RAS
I am getting following error while setting table location for the report going against Sybase (ODBC CR driver 5.1 wired protocol) database report.
com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException: The table 'CASH' could not be found.
Error in File C:\WINDOWS\TEMP\{6F59C5DB-DB01-4905-BFE6-5A302D2A9283}.rpt:
The table could not be found.---- Error code:-2147482939 Error code name:failed
     at com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException.throwReportSDKServerException(Unknown Source)
     at com.crystaldecisions.proxy.remoteagent.s.a(Unknown Source)
     at com.crystaldecisions.sdk.occa.report.application.cf.a(Unknown Source)
     at com.crystaldecisions.sdk.occa.report.application.z.a(Unknown Source)
     at com.crystaldecisions.sdk.occa.report.application.ak.if(Unknown Source)
     at com.crystaldecisions.sdk.occa.report.application.ad.int(Unknown Source)
     at com.crystaldecisions.sdk.occa.report.application.bk.for(Unknown Source)
     at com.crystaldecisions.proxy.remoteagent.v.a(Unknown Source)
     at com.crystaldecisions.proxy.remoteagent.v.if(Unknown Source)
     at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(Unknown Source)
     at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(Unknown Source)
what all properties needs to be set for Logon and also Location specific, any sample code for the RAS + ODBC + SYBASE will be highly appreciated.
code giving error
               // DatabaseController databaseController = reportClientDoc.getDatabaseController();
               Tables tables = reportClientDoc.getDatabaseController().getDatabase().getTables();
               ITable newTable = null;
               for (Object object : tables) {
                    Table table = (Table) object;
                    newTable = (Table) table.clone(true);
                    log.info("Table Name " + table.getName());
                    IConnectionInfo connectionInfo = table.getConnectionInfo();
                    com.crystaldecisions.sdk.occa.report.lib.PropertyBag propertyBag = connectionInfo.getAttributes();
                    log.info("propertyBag.size >> " + propertyBag.size());
                    databaseName = (String) propertyBag.get(DB_NAME);
                    dsnName = (String) propertyBag.get(DSN);
                    Set<Object> set = propertyBag.keySet();
                    for (Object key : set) {
                         log.info("Key >> " + key);
                         log.info(" === Value >> " + propertyBag.get(key));
                    log.info("----
                    // newTable.setQualifiedName(table.getAlias());
                    // Change connection information properties
                    connectionInfo = newTable.getConnectionInfo();
                    // Set new table logon properties
                    // 1. Set the DSN
                    // 2. Set the Data Source (Database)
                    PropertyBag newPropertyBag = (PropertyBag) propertyBag.clone(true);
                    // Set new table logon properties (the DSN and the data source)
                    PropertyBag logonPb = new PropertyBag();
                    //logonPb.putStringValue("DSN", dsnName);
                    logonPb.put("Database Type", "ODBC (RDO)");
                    logonPb.put("Data Source Name", dsnName);
                    logonPb.put("DSN", dsnName);
                    logonPb.putStringValue("Database", databaseName);
                    logonPb.putBooleanValue("UseDSNProperties", false);
                    String dataSource = "";
                    DatabaseInfoVO databaseInfoVO = null;
                    if (StringUtils.indexOf(dsnName, "XXXX") != -1) {
                         dataSource = "EPAM-" + databaseName;
                         databaseInfoVO = this.getDatabaseInfoMap().get(dataSource.toUpperCase());
                    } else if (StringUtils.indexOf(dsnName, "YYYY") != -1) {
                         dataSource = "EIMCO-" + databaseName;
                         databaseInfoVO = this.getDatabaseInfoMap().get(dataSource.toUpperCase());
                    } else if (StringUtils.indexOf(dsnName, "ZZZZ") != -1) {
                         dataSource = "CRD-" + databaseName;
                         databaseInfoVO = this.getDatabaseInfoMap().get(dataSource.toUpperCase());
                    } else if (StringUtils.indexOf(dsnName, "WWWW") != -1) {
                         dataSource = "AA-" + databaseName;
                         databaseInfoVO = this.getDatabaseInfoMap().get(dataSource.toUpperCase());
                    log.info("databaseInfoVO >>" + databaseInfoVO);
                    // Overwrite any existing properties with updated values
                    newPropertyBag.put(PropertyBagHelper.CONNINFO_CRQE_LOGONPROPERTIES, logonPb);
                    newPropertyBag.putStringValue(PropertyBagHelper.CONNINFO_CRQE_SERVERDESCRIPTION, dsnName);
                    newPropertyBag.putStringValue(PropertyBagHelper.CONNINFO_CRQE_DATABASENAME, databaseName);
                    newPropertyBag.putStringValue(PropertyBagHelper.CONNINFO_DATABASE_DLL, "crdb_odbc.dll");
                    newPropertyBag.putBooleanValue(PropertyBagHelper.CONNINFO_CRQE_SQLDB, true);
                    newPropertyBag.putBooleanValue(PropertyBagHelper.CONNINFO_SSO_ENABLED, false);
                    set = newPropertyBag.keySet();
                    for (Object key : set) {
                         log.info("Key2 >> " + key);
                         log.info("Value2 >> " + newPropertyBag.get(key));
                    connectionInfo.setAttributes(newPropertyBag);
                    connectionInfo.setUserName(databaseInfoVO.getUserName());
                    connectionInfo.setPassword(EZSuiteEncodeUtil.decrypt(databaseInfoVO.getPassword()));
                    connectionInfo.setKind(ConnectionInfoKind.CRQE);
                    newTable.setConnectionInfo(connectionInfo);
                    newTable.setName(table.getName());
                    newTable.setAlias(table.getAlias());
                    newTable.setQualifiedName(table.getQualifiedName());
                    // Update the table information
                    reportClientDoc.getDatabaseController().setTableLocation(table, newTable);
Thanks,
Rupesh
Edited by: Rupesh Raut on Oct 28, 2008 8:45 PM
Edited by: Rupesh Raut on Oct 28, 2008 8:46 PM

Hi,
This error message appears when the user does not have sufficient rights to the business view on which the report is based.
To resolve this error message, open the Business View Manager and verify that the user's rights are set up correctly.
To view a report based on a business view, the user or the group to which the user belongs, must have 'View' rights to the business view. Also, verify that none of the groups, including the Everyone group, to which the user belongs, has been explicitly denied 'View' rights.
If this does'nt help try to update database driver.
Make the copy of database and save it with different name ( without underscore) and point the crystal report to it.
Regards,
Shweta

SCCM 2012 Deploy --- Error = The software change returned error code 0x87D00324(-2016410844).

Deployment to the client is successful but the error reported within Clients "SCCM Software Center"
The software change returned error code 0x87D00324(-2016410844).
Also States on "Status" Past Due - Will be Retired"
Can't figure this one out and I did some googling with no success in finding a solution?
I am running an Adobe Flash install (.EXE)
Any help or direction would be greatly appreciated
RF

Hi,
Thank you for your response
""Wow6432Node is not valid on x86 systems."""
Yes, that I am aware of that.....Windows on Windows, for running x86 apps on x64 Windows<o:p></o:p>
When I first created the detection method I had only created the "WoW" Check
for Flash value in the reg, which was running against both x86 & x64 Win 7
systems, and forgot to include the x64 check/, either case, the error appeared
on the WOW check. Presently I have 2 "Detection Clauses" one for x86
and the second clause is x64 ( non WOW Path), and still receive the same erorrs
on both x86 & x64 systems. ( and x64 system have both reg entries since Win 7 has both x86 & x64 versions of IE)
Looking at the registry of an x64 Win 7 system I find the Adobe Flash registry entry is
located in both Wow6432Node and also in the x64 sections of the reg.....<o:p></o:p>
""""Also, why use the default value? I doubt there's anything in there (the default value is the
value display in a key in regedit with the name of
"@").""""<o:p></o:p>
When Default Value is selected the boxes/options below that allow for more detailed
information to be entered when performing the "reg check"? This is
where I had been able to enter specific Build/Version to look for, Flash
11.4.402.265, so that if it does not discover the build # it will proceed with
the install.....<o:p></o:p>
I figured having the option to check for Build/Version # would omit SCCM reinstalling on
systems that have build 11.4.402.265 already?<o:p></o:p>
From what I understand is that Adobe Flash x64 installs both versions x86 & x64 since Win 7 has both IE
x86 & IE x64 bit versions by default, and this would explain the Wow6432Node reg
entries and the true x64 reg entries in both locations when installing.
Overall, I am thinking I may be heading in the wrong direction in resolving this, as x86 & x64 versions install on the systems, so this tells me it is detecting when / what needs to be installed, the issue seems to be how it reports back after installing......
Looking further, I view the Content Status Page, and there reporting info in Asset Detail under [Success] all others { / In Progresss / Error /Unknown } has no info......
If this helps provide further details.....
Thanks
Regards,
Ron
RF

SSIS packages deployment error- The package failed to load due to error 0xC0011008 Error loading from XML

I am trying to deploy SSIS packages to file system using manifest file. These packages are upgraded from SSDT 2005 to SSDT 2010. Also I have changed the protection level from 'EncryptSensitiveWithPassword' to 'DontSaveSensitive' to upgrade it.
I coun't complete the deployment and the error details shown below.
TITLE: Package Installation Wizard
Package "Packagename.dtsx" could not be loaded. The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed
error information can be stored.". This occurs when CPackage::LoadFromXML fails.
Package ""Packagename.dtsx" could not be loaded. The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where
detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails.
ADDITIONAL INFORMATION:
The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when
CPackage::LoadFromXML fails.
The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when
CPackage::LoadFromXML fails.
BUTTONS:
OK
Please give a solution.
Sreekanth Mohan

Check this
blog post as it gives complete information about error.
It looks like its still using SQL 2005 DTEXEC.exe instead of latest version.
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

HELP - ERROR INVOKING ENTITY EJB METHOD

Hi,
I keep getting a java.rmi.NoSuchObject exception when using my entity ejb, but cannot see why, as I already have the ejb in a collection... code & stack trace below: Any one know what is causing this ??
java.rmi.NoSuchObjectException: com.syntegra.cec.insurance.entity.AATreportPK@7a6c34
java.rmi.NoSuchObjectException: com.syntegra.cec.insurance.entity.AATreportPK@7a6c34 at AATreport_EntityBeanWrapper14.getPayment_reference(AATreport_EntityBeanWrapper14.java:1881) at com.syntegra.cec.insurance.dtofactory.RecordsDTOFactoryBean.fetchAAT(RecordsDTOFactoryBean.java:151) at com.syntegra.cec.insurance.dtofactory.RecordsDTOFactoryBean.fetchRecords(RecordsDTOFactoryBean.java:62) at RecordsDTOFactory_StatelessSessionBeanWrapper49.fetchRecords(RecordsDTOFactory_StatelessSessionBeanWrapper49.java:108)
HashMap records = new HashMap();
Collection theEJBs = null;
int counter = 0;
//Find the beans
AATreportHome home = (AATreportHome)lookUpHome
(com.syntegra.cec.insurance.entity.AATreportHome.class,
"AATreport");
theEJBs = home.findByStatus(type);
//Populate the DTO's
if(theEJBs != null)
Iterator it = theEJBs.iterator();
while(it.hasNext())
AATreport theEJB = (AATreport)it.next();
AATreportDTO theDTO = new AATreportDTO
----- This is where the error comes from --
---Line 151 ---(theEJB.getPayment_reference(),
theEJB.getTenant_ref_no(),
theEJB.getInsurance_no(),
theEJB.getName(),
theEJB.getAddress_line_1(),
theEJB.getPremium(),
getDateAsString(theEJB.getAction_date()));
records.put(new Integer(counter), theDTO);
counter++;

Greetings,
Hi,
I am trying to access a bean from a JSP and have the
foll. code piece:
<%
String op="";
try {
// Contact the AccountBean container (the "AccountHome") through JNDI.
Context ctx = getInitialContext();
out.println("initial context got !!");
DemoHome home = (DemoHome) ctx.lookup("demo.DemoHome");
out.println("home got !!");Though it doesn't seem to be the problem in this case, good EJB coding practices dictate that your code should be narrowing the home reference before calling any of it's methods (i.e. create(...) )... WebLogic may allow handling of its protocol objects in their native state, but other vendors do not... your application is not portable without narrowing.
It gives an error on trying to access the method "demoSelect".
e.printStackTrace gives the output:
java.lang.RuntimeException: javax.ejb.EJBContext.getEnvironment is deprecated inThe error is not in your JSP, but in the bean... it seems your bean is attempting to acquire its "environment properties" in the pre-1.1 style, when...
EJB 1.1. EJB 1.1 compliant containers are not required to implement this
method. Use java:comp/env instead. ...instead, it should be looking them up in its JNDI namespace.
What is wrong???
pls help! Regards,
Tony "Vee Schade" Cook

Error when deploying an CMP-Entity EJB

Hi ,
I am unable to deploy a simple example of CMP ,when i select Entity,then select Deployment Settings->Generate Default SQL,
My SQL Query is:'SELECT OBJECT(p) FROM Product p' for FfindAllProducts().
I get the error message:
ERROR:while generating SQL.
The SELECT clause has a return type that does not match the return type
of the select query for which it is defined
EJB QL statement: 'SELECT OBJECT(p)fROM Product p'
EJB QL method:public abstract java.util.Collection com.aa.ProductHome.findAllProducts() throws javax.ejb.FinderException,java.rmi.RemoteException.
Followinng are the codes of My bean
ProductHome.java
import javax.ejb.*;
import java.rmi.RemoteException;
import java.util.Collection;
public interface ProductHome extends EJBHome
Product create(String productId,String name , String description , double basePrice) throws CreateException,RemoteException;
public Product findByPrimaryKey(ProductPK key) throws FinderException,RemoteException;
public Collection findByName(String name) throws FinderException,RemoteException;
public Collection findByDescription(String description) throws FinderException,RemoteException;
public Collection findAllProducts() throws FinderException,RemoteException;
ProductBean.java
import javax.ejb.*;
import java.rmi.RemoteException;
public class ProductBean implements EntityBean
protected EntityContext ctx;
public String productid;
public String name;
public String description;
public ProductBean()
public String getName() throws RemoteException
return this.name;
public void setName(String name) throws RemoteException
this.name=name;
public String getDescription() throws RemoteException
return this.description;
public void setDescription(String description) throws RemoteException
this.description=description;
public String getProductId() throws RemoteException
return this.productid;
public void setProductId(String ProductId) throws RemoteException
this.productid=ProductId;
public void ejbActivate()
public void ejbPassivate()
public void ejbRemove()
public void ejbLoad()
public void ejbStore()
public void setEntityContext(EntityContext ctx)
this.ctx = ctx;
public void unsetEntityContext()
this.ctx = null;
public void ejbPostCreate(String productId,String name,String description,double baseprice)
public ProductPK ejbCreate(String productId,String name,String description,double baseprice) throws CreateException,RemoteException
called ");
setName(name);
setProductId(productId);
setDescription(description);
return null;
Product.java
import javax.ejb.*;
import java.rmi.RemoteException;
public interface Product extends EJBObject
public String getName() throws RemoteException;
public void setName(String name) throws RemoteException;
public String getDescription() throws RemoteException;
public void setDescription(String description) throws RemoteException;
public String getProductId() throws RemoteException;
public void setProductId(String productid) throws RemoteException;
ProductClient.java
import java.rmi.*;
import javax.rmi.*;
import javax.naming.*;
import javax.ejb.*;
import java.util.*;
public class ProductClient
public static void main(String ars[])
ProductHome home=null;
try
Context initial = new InitialContext();
Context myEnv = (Context)initial.lookup("java:comp/env");
Object objref = myEnv.lookup("ejb/TheProduct");
home = (ProductHome)PortableRemoteObject.narrow(objref,ProductHome.class);
home.create("123-446-7890","p5-350","350 Mhz Pentium",200 );
home.create("123-446-7891","p5-400","400 Mhz Pentium",300 );
home.create("123-446-7892","p5-450","450 Mhz Pentium",400 );
home.create("123-446-7893","p5-500","500 Mhz Pentium",500 );
home.create("123-446-7894","p5-550","550 Mhz Pentium",600 );
Iterator i = home.findByName("p5-400").iterator();
System.out.println(" Product Match the name of p5-400 " );
if ( i.hasNext() )
Product prod = (Product)PortableRemoteObject.narrow(i.next(),Product.class);
System.out.println(prod.getDescription());
else
throw new Exception(" Could not find Product ");
catch(Exception e)
System.out.println("Caught Exception " );
e.printStackTrace();
finally
if ( home != null)
System.out.println(" Destroying all products " );
try
Iterator i = home.findAllProducts().iterator();
while ( i.hasNext() )
Product prod = (Product)PortableRemoteObject.narrow(i.next(),Product.class);
if (prod.getProductId().startsWith("123"))
prod.remove();
catch (Exception e)
e.printStackTrace();
ProductPk.java
import java.io.Serializable;
public class ProductPK implements java.io.Serializable
public String ProductId ;
public ProductPK(String id)
this.ProductId = id;
public ProductPK()
public String toString()
return ProductId;
public int hashCode()
return ProductId.hashCode();
public boolean equals(Object Product)
return ((ProductPK)Product).ProductId.equals(ProductId);

can u pls tell me u are using ejb1.1 specifications or ejb2.0 specifications.in both cases pls shoe u are descripters so that i can check.

Weblogic 10.3.0 Deployment error when using ejb-jar.xml

Hi,
I am getting the following error while deploying my EJB3 application on Weblogic 10.3.0. This is happening only if I include ejb-jar.xml.
As per the EJB3 descriptor spec, Remote Home or Local home are not exists.
Is this a issue in Weblogic 10.3.0 or am I missing any special setup ?
Please help.
weblogic.application.ModuleException: Exception preparing module: EJBModule(egm-poc.jar)
Unable to deploy EJB: C:\appsrv\domains\WeblogicRS1.1-domain\servers\admin\tmp\_WL_user\_appsdir_egmear_ear\ot2591\egm-poc.
jar from egm-poc.jar:
In EJB JPATestBean, both the remote home and remote component interface must be specified. Currently, only one of them is spec
ified.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
My ejb-jar.xml is
- <ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<description>JPA Test Application</description>
<display-name>JPATest</display-name>
- <enterprise-beans>
- <session>
<ejb-name>JPATestBean</ejb-name>
<remote>egm.poc.jpa.JPATestBeanRemote</remote>
<local>egm.poc.jpa.JPATestBeanLocal</local>
<ejb-class>egm.poc.jpa.JPATestBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
- <session>
<ejb-name>AuditInfoDAOH</ejb-name>
<local>egm.poc.jpa.Audit</local>
<ejb-class>egm.poc.jpa.AuditInfoDAOH</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
- <assembly-descriptor>
- <container-transaction>
- <method>
<ejb-name>JPATestBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
- <container-transaction>
- <method>
<ejb-name>AuditInfoDAOH</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Regards
Saji

Hi,
Seems the issue is not common. Can anyone throw some light on this ?
Regards
Saji

Deployment error while running the application

Hi Every body,
I am new to JEE though an old pro at JDK.I have also worked on tomcat.
I have got Sun Java System Application Server 9.1 installed with NetBeans 6.1 on winXP.
I am trying to create a EJB app-client module.I even tried to run the sample application AnnotationOverrideInterceptor given in NetBeans . Every thing goes fine.The Build is also Successful but when i run it, i recieve the error message Deployment error .The module has not been deployed.
See the server log for details.
I am posting a part of server log stack.:
Application server startup complete.
[AutoDeploy] Selecting file C:\Program Files\glassfish-v2-b53\domains\domain1\autodeploy\amserver.war for autodeployment.
Initializing Sun's JavaServer Faces implementation (1.2_04-b19-p03) for context ''
javax.ejb.EJB.description()Ljava/lang/String;
Exception occured in J2EEC Phasejava.lang.IllegalStateException: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [AnnotationOverrideInterceptor] -- javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:388)
at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
Caused by: java.lang.IllegalStateException: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:363)
at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:318)
at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:213)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.readModulesDescriptors(ApplicationArchivist.java:321)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.open(ApplicationArchivist.java:238)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:763)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
... 10 more
Caused by: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:360)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:368)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:282)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:264)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:192)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:129)
at com.sun.enterprise.deployment.archivist.Archivist.processAnnotations(Archivist.java:445)
at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:346)
... 17 more
Caused by: java.lang.NoSuchMethodError: javax.ejb.EJB.description()Ljava/lang/String;
at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processNewEJBAnnotation(EJBHandler.java:276)
at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processEJB(EJBHandler.java:143)
at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processAnnotation(EJBHandler.java:98)
at com.sun.enterprise.deployment.annotation.handlers.AbstractResourceHandler.processAnnotation(AbstractResourceHandler.java:119)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:337)
... 24 more
Please help as i am trying the google and many other to find solution but i am unable to move forward.I am stuck up at this for last 15 days.It is very frustrating.
I haven't posted the full log as it is very long.I can post the entire server log, if asked for.
Please help
yoodleyee

Hi jwenting,
Thanks alot for replying.
But i am still unable to come out of the mess.Here is the program i am using please help me find out the error.
Here we go:
package hello;
import javax.ejb.Stateless;
@Stateless
public class HelloBean implements HelloRemote {
private String name="Yoodleyee";
public String sayHello() {
//return null;
return "My Name is "+name;
// Add business logic below. (Right-click in editor and choose
// "EJB Methods > Add Business Method" or "Web Service > Add Operation")
package hello;
import javax.ejb.Remote;
@Remote
public interface HelloRemote {
String sayHello();
In the Hello-app-client module i have main()==>>
package hello;
import javax.ejb.EJB;
public class Main {
@EJB
private static HelloRemote helloBean;
* @param args the command line arguments
public static void main(String[] args) {
// TODO code application logic here
System.out.println("Hi "+helloBean.sayHello());
since this program does not require deployment descriptor and also NetBean creates its own deployment discriptor hence i have not written any.
Please tell me where and waht i should change.Also tell me is diployment descriptor necessary.
Awaiting for the reply.
yoodleyee

InfoView - Error in File ...The table could not be found

When I run the a report out of Crystal Reports 2008 Developer using a 32 bit ODBC data source Microsoft Visual FOxPro Driver, the report runs fine. All of my reports run fine in the Crystal Developer
But when I run the same report in Java SAP BusinessObjects InfoView Enterprixe XI, the same report would get an error: The Table could not be found. Other errors I would get: Encapsulating page failed. None of the reports work in InfoView, but they would work in the Crystal Developer.
Our environment is Windows Server 2008 R2 on a 64-bit Dell PowerEdge Server.

Hello,
If you create the System DSN on the Server and test the connection does it work? If it does then BOE either can't find the DBF file or it doesn't have access to the folder.
Check the permissions on the folder where the database files reside, if they are not local then map the driver where they do exist.
Don

What is the table for query name

Hi All,
I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
Thanks,
Alex.

hi Alex,
try RSRREPDIR, RSZCOMPDIR.
there is one oss note all the tables.
Table containing Work Book and query relation
Query Detailes
oss 792779
Symptom
Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
The program is recommended for BW system administrators.
Other terms
Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
Reason and Prerequisites
ATTENTION: the described version of the program is delivered with the following Support Packages:
SP27 for release BW 3.0B
SP21 for release BW 3.1C
SP13 for release BW 3.5
All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
Check prerequisites
Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
Checks for query elements in 'D' version are possible only in the systems which are set as content.
Checks description
Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
1. Table RSRREPDIR
The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
The following errors can be found:
- queries with missing definition;
- queries with missing GENUNIID;
- queries with technical names different than in RSZCOMPDIR;
- non-queries in the table.
1.1 Queries with missing definition
The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
1.2 Queries with missing GENUNIID
Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
1.3 Queries with technical names different than in RSZCOMPDIR
The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
1.4 Non-queries in the table
The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
2. Table RSZCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
The following errors can be found:
- local elements in RSZCOMPIC;
- components with inconsistent definition;
- components based on non-existing InfoProviders;
- components based on non-active InfoProviders.
2.1 Local elements in RZSCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
2.2 Components with inconsistent definition
The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
2.3 Components based on non-existing InfoProviders
Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
2.4 Components based on non-active InfoProviders
Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
The check is available only for the query elements in object version 'A' (active).
3. Table RSZCOMPDIR
The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
The following errors can be found:
- duplicated technical names (COMPID);
- components with inconsistent definition;
- components without InfoProvider assignment;
- components with missing OWNER.
3.1 Duplicated technical names (COMPID)
The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
different queries are available in BEX Analyzer and RSRT under the same name;
wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
replacement of variables does not work... etc.
The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
3.2 Components with inconsistent definition
Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.3 Components without InfoProvider assignment
All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.4 Components with empty ONWER field
Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
4. Table RSZELTXREF
The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
The following errors can be found:
- missing elements (INCONSISTENCY dump);
- not supported relations between query elements;
- extended RSZELTXREF check.
4.1 Missing elements
Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
4.2 Not supported relations between query elements
Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
4.3 Extended RSZELTXREF check
The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
- records with empty INFOCUBE field
- records which are not used in any query or query component
Records with empty INFOCUBE field
The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
Records which are not used in any query or query component
The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
records used in existing queries or query components with empty INFOCUBE field;
records used in existing queries or query components with wrong INFOCUBE assignment;
records with or without INFOCUBE assignment which are not used in any query or query component.
For further check details read the OSS note 859086.
5. Table RSZGLOBV
The table RSZGLOBV contains the definitions and technical properties of the variables.
The following errors can be found:
- variables with inconsistent definition;
- variables with missing or incorrect properties;
5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
5.2 Variables with missing or incorrect properties
Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
6. Table RSZELTDIR
The table RSZELTDIR is the main directory table containing all query elements available in the system.
ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
The following errors can be found:
- local elements not in use;
- reusable elements not in RSZCOMPDIR table;
- reusable elements not in RSZCOMPIC table;
- structure (STR) without structure members;
- selections or RKF without definition in RSZSELECT table;
- formulas or CKF without definition in RSZCALC table;
- variables (VAR) without definition in RSZGLOBV table;
- queries (REP) without entries in RSRREPDIR table.
6.1 Local elements not in use
Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
6.2 Reusable elements not in RSZCOMPDIR table
Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
6.3 Reusable elements not in RSZCOMPIC table
Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
6.4 Structures (STR) without structure members
Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
6.5 Local selection of RKFs without records in RSZSELECT table
Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
6.6 Local formulas of CKFs without records in RSZCALC table
Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
6.7 Variables without records in RSZGLOBV table
Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
6.8 Queries without records in RSRREPDIR table
Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
hope this helps.

The table 'User1.V_Order' could not be found."

I wrote the codes below to change connection at runtime. I ran into error "The table 'User1.V_Order' could not be found." Anyone encountered this before? Any solution? Thank you.
Envionement: VS 2005 Crystal Report, Oracle Database, OraoleDB.Oracle (oledb)
1 Dim myConnectionInfo As New CrystalDecisions.Shared.ConnectionInfo
2
3 myConnectionInfo.ServerName = ServerName
4
5 myConnectionInfo.UserID = UserID
6
7 myConnectionInfo.Password = Password
8
9 For Each mySubreport In myCrystalReportSource.ReportDocument.Subreports
10
13 For Each myTable In mySubreport.Database.Tables
14
15 Dim crLogOnInfo As TableLogOnInfo = myTable.LogOnInfo
16
17 crLogOnInfo.ConnectionInfo = myConnectionInfo
18
19 myTable.ApplyLogOnInfo(crLogOnInfo)
20
23 myTable.Location = UserID & "." & myTable.Name
24 'myTable.Location = UserID & "." & myTable.Location.Substring(myTable.Location.LastIndexOf(".") + 1)
25 Next
28
29 Next
30
Edited by: user5122447 on Sep 12, 2008 9:43 PM

I had the same problem. Go to your confirm email and click the link with the verizonwireless.com/iphoneorder thing. Then under the start order button push that. and it will bring up the status page.

Application Deployment Error 0x87D00324

Hello All--
I have a deployment setup for Java 7 Update 45. I have two deployment types (x86 and x64). Each deployment type has a Windows Installer detection method set. I created a required deployment to 13+ test machines. Only two show this as 'Installed',
the rest show 'Past Due - Will be retried' with error code 0x87D00324. When I check AppEnforce.log, it shows a successful installation, but the next lines show 'Application not Detected'. All the machines are 32-bit.
Any thoughts/help would be much appreciated.
Thanks,
Matt

Hi,
I found a similar threads for your reference.
SCCM 2012 Deploy --- Error = The software change returned error code 0x87D00324
http://social.technet.microsoft.com/Forums/en-US/99b13d65-3305-46c7-b5a0-96513408520b/sccm-2012-deploy-error-the-software-change-returned-error-code-0x87d003242016410844?forum=configmanagerapps
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Deployment error: The Entity EJB requires the table: to be accessible

Similar Messages

Maybe you are looking for