Getting a Formula Error in Application Library during Deployment

Hi,
We're getting an odd error which baffles me... In the app library, we're deploying an app to Planning and get the following error:
Detail : Deployment update from product:An Exception occurred during Application deployment.: Unable to load the following resource: %RESOURCE_NAME%com.hyperion.planning.olap.HspVerifyOutlineException: Verify Outline failed with the following errors:
     Error [102000000] detected in member "Acct7055": Level 0 virtual members must have a formula associated with them
In EPMA, that account has a formula and is tagged with HSP_UDF. After deployment, Planning shows correctly the account as dynamic calc, with the formula, and the UDA. But in EAS, the account reverts back to nevershare, with no formula.
Any ideas welcomed!. thanks.

I hit this error in Planning for an upper level Account member of type NeverShare. In my case, the upper level member in question need was shared by 2 different planning databases, so Planning was trying to create an XREF formula for the upper level member was of type NeverShare. I resolved this issue by using the UDA member HSP_NOLINK, which tell's planning not to create the XREF formula.

Similar Messages

  • I just tried to install the 11.4 update (or whichever one is the most recent update as of 1/26/2014) and when it failed i tried to install manually and now whenever i try to use it, i get the following error: the application has failed to start because MS

    i just tried to install the 11.4 update (or whichever one is the most recent update as of 1/26/2014) and when it failed i tried to install manually and now whenever i try to use it, i get the following error: "The application has failed to start because MSVCR80.dll was not found. Re-installing the application may fix this problem." Right after i click ok i then get this error: "Itunes was not installed correctly. Please reinstall Itunes. Error 7 (Windows error 126)." I tried to uninstall Itunes and then reinstall the 11.03 version but that didnt work either. I want to know if i copy all of the music in my itunes folder to an external without consolidating can i still transfer all my itunes music from my current windows xp pc to a brand new one and have my current itunes library in my new pc? Basically i just want to know 3 things: What exactly does consolidating the itunes library do? Can i copy, paste, and transfer my itunes library to an external and from there to a new pc? Will i be able to transfer my itunes library without consolidating the files?

    I have found a temporary solution, allowing the previous version of iTunes (v. 11.1.3 (x64) in my case) to be re-installed.  It will allow you to re-establish use of iTunes until the Apple software engineers fix the most recent disasterous upgrade (v. 11.1.4).  Please see and follow the procedure in the following article:http://smallbusiness.chron.com/reverting-previous-version-itunes-32590.html   The previous version works beautifully.

  • Validaton Error in Application Library with Duplicated Alias Name

    Greetings,
    I getting a validation error in the Application Library. It seems that I'm trying to assign to an alias an already used name in the member? How can I check in EPMA where that is being done? Many thanks.
    Warning : A duplicate value exists in the Alias property for member 'Route Alt Hier' in the 'ReRoute' dimension. The member name must not be used for any of the alias values for that member.
    Warning : The Alias Route Alt Hier' in member 'Route Alt Hier', dimension 'ReRoute' duplicates a member name in dimension 'ReRoute'.

    Pablo,
    My ads file does not add any aliases for this particular member. I think this is what is happening:
    I delete all all members of that dimension from the Shared Library (as a test, to ensure that this dim is rebuilt from scratch)
    I run the import profile using the ads file
    once loaded (0 zeroes and no warning), I manually check some members and noticed that in the Property Grid that an alias is defined for that member. That alias happens to have the same name as the member. I really do not know where this comes from!
    The only thing i can think of is that the 'Alias' dimension is being used for a lot of dimensions inthe shared library. For my app, should I use another Alias dimension?
    Any ideas are welcome...
    thanks.

  • While importing a CD into my iTunes library I kept getting the following error message- iTunes library cannot be saved- An unknown error occurred (-54).  What does this error mean and what can I do about it??

    While importing a CD into my iTunes library I kept getting the following error message- iTunes cannot be saved- An unknown error occurred (-54).  what does this error mean and what can I do about it??

    The CD I imported (in the above post) is now not in my iTunes library. Any help would be appreciated .

  • Validation errors weblogic-webservices.xml during deploy for valid dd

    Hi,
    I am trying to set the login-config for my JAXWS EJB webservice endpoint, but I weblogic doesn't accept my weblogic-webservices.xml
    I validated my weblogic-webservices.xml using several xml validator tools and all say it is valid.
    Here is the weblogic-webservices.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-webservices
         xmlns="http://xmlns.oracle.com/weblogic/weblogic-webservices"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
         xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-webservices http://xmlns.oracle.com/weblogic/weblogic-webservices/1.1/weblogic-webservices.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <webservice-description>
    <webservice-description-name>AppManager</webservice-description-name>
    <port-component>
    <port-component-name>AppManager</port-component-name>
    <service-endpoint-address>
    <webservice-contextpath>/AppManagerService</webservice-contextpath>
    <webservice-serviceuri>/AppManager</webservice-serviceuri>
    </service-endpoint-address>
    <login-config>
    <j2ee:auth-method>BASIC</j2ee:auth-method>
    <j2ee:realm-name>myrealm</j2ee:realm-name>
    </login-config>
    </port-component>
    </webservice-description>
    </weblogic-webservices>
    Here are the validation errors I get during deployment:
    VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'auth-method@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null> problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'realm-name@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null>
    Error VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'auth-method@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null> problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'realm-name@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null>
    If I remove the namespace indicator 'j2ee' it complains about the same. So it would seem that weblogic ignores the 'j2ee' resulting indeed in a invalid xml.
    Can someone please help me to a weblogic-webservices.xml (example with login-config) that was accepted by weblogic?
    Thanks a lot,
    Eltjo.

    Hi,
    Please try the following: ( Looks like you are mixing the Tag contents of web.xml  as well as weblogic-webservice.xml   together.... )
    weblogic-webservice.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/weblogic-webservices" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-webservices http://www.bea.com/ns/weblogic/weblogic-webservices/1.0/weblogic-webservices.xsd">
          <webservice-description>
              <webservice-description-name>AppManager</webservice-description-name>
              <port-component>
              <port-component-name>AppManager</port-component-name>
                     <service-endpoint-address>
                        <webservice-contextpath>/AppManagerService</webservice-contextpath>
                        <webservice-serviceuri>/AppManager</webservice-serviceuri>
                     </service-endpoint-address>
              </port-component>
          </webservice-description>
    </weblogic-webservices>And Now provide the <login-config> information separately inside *"web.xml"* file
    <login-config>
         <auth-method>BASIC</j2ee:auth-method>
         <realm-name>myrealm</j2ee:realm-name>
    </login-config>.
    Thanks
    Jay SenSharma

  • Validation error in Tag Library at deploy time

    I am trying to deploy a JSF2 app to NW CE 7.1 EHP1. This application deploy's fine to Tomcat. When I deploy to SAP it gives an error: Error in parsing [META-INF/primefaces-i.tld] TLD file in the following [D:\usr\sap\NCX\J00\j2ee\cluster\apps\com.sap\IDMear\servlet_jsp\IDM\root\WEB-INF\lib\primefaces-1.0.0.jar] JAR file.
    [EXCEPTION]
    com.sap.engine.lib.xml.parser.NestedSAXParseException: Fatal Error: org.xml.sax.SAXParseException: Validation error : line: 13; col: 16; :description : Element is not allowed.(:main:, row=13, col=17) -> org.xml.sax.SAXParseException: Validation error : line: 13; col: 16; :description : Element is not allowed.
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:140)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:174)
    at com.sap.engine.lib.processor.SchemaProcessor.parse(SchemaProcessor.java:197)
    at com.sap.engine.services.servlets_jsp.server.deploy.descriptor.TagLibDescriptor.loadDescriptorFromStream(TagLibDescriptor.java:90)
    From looking at the TLD XSD for JEE 5, the Description field should be allowed. Do you know why it is not comparing the TLD against the correct schema or if there is another explanation?
    This is a 3rd party faces component library. Here is where it fails:
    <?xml version="1.0" encoding="UTF-8"?>
    <taglib xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.1">
         <tlib-version>1.2</tlib-version>
         <short-name>i</short-name>
         <uri>http://primefaces.prime.com.tr/touch</uri>
         <tag>
              <name>application</name>
              <tag-class>org.primefaces.touch.component.application.ApplicationTag</tag-class>
              <body-content>JSP</body-content>
              <attribute>
                   <name>id</name>
                   <required>false</required>
                   <description><![CDATA[Id of the component]]></description>               <rtexprvalue>false</rtexprvalue>
              </attribute>
    Any suggestions would be appreciated.

    It looks like the 3rd party tld did not have the description in the correct order. It has been corrected in a new build.

  • Gives Error when run XMLImporter during deployment

    After reading the deployment process from Developer
    guide i tried deployment but when i run the XMLImporter
    it gives the error
    Error: The root directory does not exist

    Are you using -validate and -includeSubPackages options while running the import command ?
    Try running it without -validate option.

  • HOWTO: Specify the parent application attribute during deployment

    Hi all,
    I wonder how can I specify the "parent application" attribute in order to deploy my application correctly
    (I am trying to deploy a BPEL application and I am needing to specify the "-parent orabpel" option in the admin.jar execution... but I didn't also find how to solve this problem in a general way...)
    Thank you in advance for your help

    I am very sorry with you, but I decided to put this question here, because the problem IS NOT BPEL related... (as I mentioned in my original post)
    If I build an application... for example "App1", and I deployed in the Oracle AS 10g, and then I want to deploy from my JDeveloper the "App2", but I want to specify that "App1" is parent application of "App2".... How can I do it from JDeveloper without using the admin.jar utility or using the EM console from my App Server?
    In my humble opinion (I am not an ACE member)... is a general problem of the IDE more than specific to BPEL
    Thank you again if someone can give me a real clue on this issue...

  • Application installation during deployment of VM from Template.

    Looking to install various agents and clients via install script and service templates. Finding lots of gotchas and undocumented "features". Has anyone successfully deployed software via this method?

    Here are the Service Templates I built:
    http://www.citrix.com/go/xendesktop-for-the-private-cloud.html
    It creates and entire XenDesktop farm, connects the dots, installs and configures the software.
    Yes, it can be done.  Yes, it takes time.  And yes, the most difficult part is learning about your software and its unique quirks (not so much the SCVMM service template stuff - lots of flexibility there)
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

  • I get an error message "application attempted to access C   runtime library incorrectly" when I try to update or reinstall iTunes. How can I resolve this issue?

    I get a Windows error message "application attempted to access C++ runtime library incorrectly" when I try to update or to reinstall iTunes. How do I resolve this issue?

    Hi there MRDLS,
    I would recommend taking a look at the troubleshooting steps found in the article below.
    iTunes 11.1.4 for Windows: Unable to install or open
    http://support.apple.com/kb/TS5376
    -Griff W.

  • IPhoto Start Error: Your photo library is either in use by another application or has become unreadable

    Having the same issues with iPhoto as an OP in another thread. When I try to start iPhoto I get the following error, "Your photo library is either in use by another application or has become unreadable."
    I have tried rebuilding the database with no joy to resolving the issue. The library has not been moved to another drive so I have not bothered with the "LockId" process someone recommended.
    Following the instructions provided by Linc Davis in another thread....
    Command Line In Terminal: "find ~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \) 2>&- | wc -l | pbcopy"
    I get the following response.
    319
    Does anyone have suggestions for what I can do to get iPhoto back up and running?
    SYSTEM:
    Hardware: iMac9
    OSx Version: 10.6.8

    Went thru the "rebuild library" process again. This time I selected to rebuild the library from an automatic back up. When I did that a screen came up saying "Upgrade or Quit - The photo library needs to be upgraded to work with this version of iPhoto". I selected Upgrade and everything seems fine now.
    Not sure why anything would require an upgrade as I haven't done anything to upgrade iPhoto. Hope this is not a virus.
    My Mac seems really slow. If anyone can recommend a cleanup process, I'm interested in going that route.
    Thanks for the help here on the community forums!

  • I can't open itunes when I click onn the icon the message I get is "error new itunes library"

    I can't open itunes..when I click on the icon on my desk top I get the message" error new itunes library". I have windows 7.

    Hi beachy85!
    When you remove iTunes, your music on your computer (and your iPod, too) will be saved.
    Let's try this:
    Go to "Add or remove programs" in Control Panel.
    Find iTunes and QuickTime from this list, and remove them both.
    Then, download the Windows Installer Cleanup Utility to remove the remainging installation files.
    For information on the WICU, see this:
    Description of the Windows Installer CleanUp Utility
    Then, go to this page, and QuickTime (get the Standalone version, not the one that includes iTunes in the pack):
    QuickTime download
    Then, install iTunes from this page here:
    Download iTunes - 7.1.1.5
    After you've done that, restart your computer.
    Now, try opening iTunes again. Do you still get that error message, or not?
    -Kylene

  • How do I get apps into the application library of iphone configurator utility?

    I am trying to use the iphone configuration utility to install apps on iphones adn ipads before distributing to users. How do I get the apps into the Application Library?

    I tried that. Everything gets downloaded to my C:\Users\michaelb\Music\iTunes\iTunes Media\Mobile Applications
    When I try and get to it I get this.
    I am using the windows version. If that matters.  Any assistance would be appreciated.   Thanx

  • Error during deployment of Message Driven Bean

    Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              I am getting some error (or perhaps warning) during deployment of Message
              Driven Bean. Any one seen this before?
              This error only comes on a machine with Dual Network card.
              Thanks.
              ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
              <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
              enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
              Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
              is of a non-final version of the appropriate specification. It is subject to
              change in future releases once the specification becomes finalized. This may
              cause application code developed for BEA WebLogic Server 6.1 that uses the
              new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              supported in future releases of BEA WebLogic Server.>
              ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              container will automatically attempt to re-establish the connection with the
              JMS server. This warning may occur during WebLogic Cluster start-up if the
              JMS destination is located on another server. When the JMS server connection
              is re-established, the Message-Driven EJB will again receive JMS messages.
              The Error was:
              Unable to create a JNDI InitialContext to lookup the JMS destination. The
              error was:
              javax.naming.CommunicationException. Root exception is
              java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router
              to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:307)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:211)
              at
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              ory.java:149)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              at javax.naming.InitialContext.init(InitialContext.java:217)
              at javax.naming.InitialContext.<init>(InitialContext.java:193)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              rivenBeanInfoImpl.java:641)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              nPoller.java:474)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              .java:418)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              nectionPoller.java:286)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              foImpl.java:511)
              at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              at weblogic.j2ee.Application.addComponent(Application.java:170)
              at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:360)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              Target.java:285)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              eploymentTarget.java:239)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              entTarget.java:199)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:636)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy34.updateDeployments(Unknown Source)
              at
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              ServerMBean_CachingStub.java:2977)
              at
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              icationManager.java:372)
              at
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              r.java:160)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:636)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy49.start(Unknown Source)
              at
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              ApplicationManagerMBean_CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              at weblogic.management.Admin.finish(Admin.java:644)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              at weblogic.Server.main(Server.java:35)
              >
              ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010009> <EJB Deployed EJB with JNDI name
              ASYNCMessageDrivenBean.>
              

    Hi Tom
              Yes we do have an URL provided in the descriptor. It's
              t3://jms.server.net:7001.
              and the jms.server.net is resolved via a hosts file in Win2K
              eg,
              192.168.100.200 jms.server.net
              You are right in saying that the loopback in a dual-net card is a problem.
              But our solution
              above solves the issue as long as your host file does not use 127.0.0.1 as
              the IP.
              We need the URL b/c depending on our client's deployment , the JMS Server
              may be remote or may be local.
              "Tom Barnes" <[email protected]> wrote in message
              news:[email protected]...
              > Hi x,
              >
              > Something to do with the loopback and dual-network cards is
              > messin' with WLS' mind. I do not know what the problem is,
              > but I can guess:
              >
              > You have specified an URL in the MDB descriptor when there
              > is no need for one. If t3://127.0.0.1:7001 is in the same
              > cluster the MDB is running in (I suspect this URL is
              > actually the same WL server), then don't specify the URL.
              > This URL is only useful for connecting an MDB to a JMS
              > server that is outside local server and outside the cluster.
              > The URL may be working on single-network card systems
              > as perhaps then WL has enough info to guess that you
              > actually mean the local WL server, and simply converts
              > the context to a local context.
              >
              > Note that the URL option in the MDB descriptor is actually
              > a WebLogic extension of J2EE.
              >
              > Tom
              >
              >
              >
              > x wrote:
              > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              > >
              > > I am getting some error (or perhaps warning) during deployment of
              Message
              > > Driven Bean. Any one seen this before?
              > > This error only comes on a machine with Dual Network card.
              > >
              > > Thanks.
              > >
              > >
              > >
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
              features
              > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
              1.2,
              > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
              6.1
              > > is of a non-final version of the appropriate specification. It is
              subject to
              > > change in future releases once the specification becomes finalized. This
              may
              > > cause application code developed for BEA WebLogic Server 6.1 that uses
              the
              > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              > > supported in future releases of BEA WebLogic Server.>
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              > > container will automatically attempt to re-establish the connection with
              the
              > > JMS server. This warning may occur during WebLogic Cluster start-up if
              the
              > > JMS destination is located on another server. When the JMS server
              connection
              > > is re-established, the Message-Driven EJB will again receive JMS
              messages.
              > > The Error was:
              > > Unable to create a JNDI InitialContext to lookup the JMS destination.
              The
              > > error was:
              > > javax.naming.CommunicationException. Root exception is
              > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              > > nested exception is:
              > > java.net.ConnectException: Connection refused: connect; No available
              router
              > > to destination
              > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:307)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:211)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              > > ory.java:149)
              > > at
              javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              > > at
              javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              > > at javax.naming.InitialContext.init(InitialContext.java:217)
              > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              > > rivenBeanInfoImpl.java:641)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              > > nPoller.java:474)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              > > .java:418)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              > > nectionPoller.java:286)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              > > foImpl.java:511)
              > > at
              weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              > > at weblogic.j2ee.Application.addComponent(Application.java:170)
              > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              > > arget.java:360)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              > > Target.java:285)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              > > eploymentTarget.java:239)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              > > entTarget.java:199)
              > > at java.lang.reflect.Method.invoke(Native Method)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > > .java:636)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy34.updateDeployments(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              > > ServerMBean_CachingStub.java:2977)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              > > icationManager.java:372)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              > > r.java:160)
              > > at java.lang.reflect.Method.invoke(Native Method)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > > .java:636)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy49.start(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              > > ApplicationManagerMBean_CachingStub.java:480)
              > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              > > at weblogic.management.Admin.finish(Admin.java:644)
              > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              > > at weblogic.Server.main(Server.java:35)
              > >
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010009> <EJB Deployed EJB with JNDI name
              > > ASYNCMessageDrivenBean.>
              > >
              > >
              >
              

  • What does this mean: ERROR! Shared library ioser12 could not be found.

    Hi all,
    I am trying to establisch a JDBC connection to a MaxDB database (former SapDB).
    I have a win2k system with jdk 1.4.2_01 installed.
    I have the JDBC connection working in the sense that i am able to execute SQL scripts by ant tasks,
    so far i think that everything is properly configured.
    Nevertheless, when i try to use the connection in my own class (a JUnit testcase), i get this message:
    "ERROR! Shared library ioser12 could not be found."
    The program then continues, and i get sql error messages that the user is still connected. I think these are followups from the first one - one testcase may be broken by this error, but the connection is not closed.
    I searched the web to find what i could do against it. I found some forum discussions about this problem and hence i tried to set my path and classpath to locations where the isoser12.dll is located (runtime environment/bin), and finally copied it to the windows/system32 dir.
    Nothing made this error disappear. I am still stuck with this one since two days.
    Btw, the same testcases work well with other databases like oracle or db2.
    Hence, i am calling to you for some ideas about this error.
    Thank you in advance for help,
    Andreas Schroeder

    Hi Andreas,
    I am also interested in making maxdb(sapdb) work with S1 application server. I would appreciate if you could let me know if you are able to make it work with S1 V8 server.
    Thanks,
    Gorton Zhao
    Hi all,
    I am trying to establisch a JDBC connection to a MaxDB
    database (former SapDB).
    I have a win2k system with jdk 1.4.2_01 installed.
    I have the JDBC connection working in the sense that i
    am able to execute SQL scripts by ant tasks,
    so far i think that everything is properly configured.
    Nevertheless, when i try to use the connection in my
    own class (a JUnit testcase), i get this message:
    "ERROR! Shared library ioser12 could not be found."
    The program then continues, and i get sql error
    messages that the user is still connected. I think
    these are followups from the first one - one testcase
    may be broken by this error, but the connection is not
    closed.
    I searched the web to find what i could do against it.
    I found some forum discussions about this problem and
    hence i tried to set my path and classpath to
    locations where the isoser12.dll is located (runtime
    environment/bin), and finally copied it to the
    windows/system32 dir.
    Nothing made this error disappear. I am still stuck
    with this one since two days.
    Btw, the same testcases work well with other databases
    like oracle or db2.
    Hence, i am calling to you for some ideas about this
    error.
    Thank you in advance for help,
    Andreas Schroeder

Maybe you are looking for

  • 6.0.2 exe .vs. 6.1 exe

    Greetings ... I have some compiled EXE's (compiled under both 6.0.2 and 6.1) up on a network drive. The 6.1 apps all work: I installed the 6.1 runtime up on the network drive. However, on a number of PC's the 6.0.2 apps don't work (their icons are ge

  • No more than 6 entries will show on my site.

    I had a year long blog with an older version of iWeb, but this version is not displaying anymore than 6 entries at a time in Safari. I tried duplicating the entry and deleting the old #7, but it cuts off the bottom entry on the list leaving only six

  • Why is auto tagging failing?

    Everytime I try to auto-tag any of the scripts I'm currently working from I get an error message, "Auto tagging has failed, please try again later". Is this aspect of the service down. I just upadated my Adobe Air to see if that was the problem but i

  • Can I use Nokia prepaid in a country other than wh...

    We bought a Nokia 113 prepaid phone in Switzerland using Orange Communications. We are going to Italy and would like to use the same phone. Is it possible to use this phone by buying a SIM card in Italy using Telecom Italia? Is it that easy? Solved!

  • '&' character and BI Publisher Intergration

    Just wanted to post this for others when they start using BI Publisher and APEX.. I have a number of reports in APEX that we are using BI Publisher to produce printed output. In one of the reports I had a & in the region title in APEX. When BI Publis