Errors while rebuilding library: Master images found in data folders.

After an upgrade that wreaked havoc on my iPhoto library, I'm now using iPhoto Library Manager to rebuild the library based on a recommendation by Terence.
Out of 5000+ photos, the error log showed about 360 missing images. But when I searched inside the iPhoto library package, I found virtually all of the supposedly missing images, sometimes in what appeared to be the correct place, and sometimes in data folders. (And yes, the images in the data folders were the full-size images, not thumbnails.)
Two questions: Is there some known issue that would scatter image files into the wrong folders like this? And is there some way to have either iPhoto or iPhoto Library Manager seek and import out these misplaced images? When I did the rebuild, I selected the "scavenge" option, but that obviously didn't find everything.
Thanks.

No - iPhoto has no ability to move an image nor does IPLM
No idea how you situation occured - it has never been reported here - most like is user action but no way to know
and no neither iPhoot nor IPLM can find and import those imagesI sugget going back to the backup from before the upgrade and looking at the library - if things are in the right places - rebuild the older library with IPLM and then upgrade it
LN

Similar Messages

  • "Error while loading library. DBQueries."  installing OCMS

    Hi,
    I am trying to reinstall OCMS on a linux box and I get "Error while loading library. DBQueries." just on the DB details screen.
    Any idea?
    Thanks in advance.
    Fernando

    Hi Fernando,
    which version of OCMS you are using? which installation mode did you choose, development mode or install on an existing application server?
    I have experienced the same problem when trying to install the OCMS 10.1.3.4 on a Linux vmware machine, after I re-created a complete new linux image, and the installation worked fine.

  • I*sqlplus: Internal error (no valid library could be found)

    Hello
    I have installed Oracle 8.1.7 on Windows NT
    and Oracle 8.1.7 on Sun Sparc Solaris.
    On Windows NT, I have installed i*sqlplus.
    However, when connecting from browser
    in the index file
    I've given a valid username/password of
    a database in Oracle 8.1.7 on Sun Sparc
    and a connect string to the database
    on Oracle 8.1.7 on Sun Sparc.
    This connect string is created using
    Net 8 assistant and this connect string
    is on the Windows NT with Oracle 8.1.7.
    However, instead of connecting I
    am getting the error
    Internal error : (no valid library could be found)
    Can you please help me?
    Thanks

    Cyril,
    Can you connect to the database using the command line version of SQL*Plus? If so, you're using the correct syntax.
    It sounds like iSQL*Plus is not set up correctly. Do you have the necessary 8.1.7 components on the NT machine (Oracle HTTP Server, Net8, SQL*Plus)?
    Review the installation documentation, and/or post more specific information on your set up.
    Alison
    iSQL*Plus Team

  • ISQL*Plus: Internal error (no valid library could be found)

    I install iSQL*PLUS on middle tier (9i AS 1.0.2.1) according to documentation, when I trying to connect I am getting Internal error (no valid library could be found). The TNSNAMES.ORA file is correct.
    Any suggestions will be highly appreciated.

    My first suggestion is to use the HTTP listener on the RDBMS bundle. This is what iSQL*Plus 8.1.7 Beta was built for.
    The HTTP servers on the iAS and Database releases require mods to be compiled differently.
    - CJ

  • Error While Uploading GL Master Data in LSMW

    Hello Experts,
    I am running into error while uploading GL master data in LSMW, I created recording through FS00, then I mapped the fields, it all went good till 13th step, but last step got stuck(Run Batch Input Session), when I am running batch input session, system is showing this message "Function Code cannot be selected"
    Your help would be highly appreciated.
    Regards
    Muhammad Yousuf Ali
    SAP FI Consultant

    Hi,
    first can you pls check your Hierarchy mode setting in FS00 -  before executing Batch input session -
    Open FS00 - go to settings - and Do not display navigation tree select radio button and save it
    then Now Run fresh LSMW - your issue will resolve
    Mahesh

  • Error while processing library references

    Hi guys
    I tried to add BI Composer to ADF application. I did all steps and when I want to deploy my application from JDEV to destination WLS it has error :
    [06:04:17 PM] [Deployer:149193]Operation 'deploy' on application 'application1' has failed on 'AdminServer'
    [06:04:17 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application application1 on AdminServer.: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false], [Extension-Name: oracle.bi.adf.model.slib, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false]..
    [06:04:17 PM] Weblogic Server Exception: weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false], [Extension-Name: oracle.bi.adf.model.slib, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false].
    [06:04:17 PM] See server logs or server console for more details.
    [06:04:17 PM] weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false], [Extension-Name: oracle.bi.adf.model.slib, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false].
    [06:04:17 PM] #### Deployment incomplete. ####
    [06:04:17 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    Could anybody help me to how solve it ?
    Thanks in Advance

    I solved it,
    Firs of all your domain which you are going to deploy BI Composer should extended by Oracle JRF, if you install JDev on WLS, automatically it adds those needed library.
    In other hand generally any where you got this message "Unresolved application library references", manually you can find that library (sometime as .ear sometime as .war and etc.) [ you can search it in other installed domain or in internet ] , and in WLS console go to deployment and deploy it.
    I hope it can be useful :)

  • Error while processing library references. Unresolved application library r

    Hi Experts,
    When i try to deploy .ear file in weblogic 11g server (linux 64-bit redhat OEL 5.46), I am facing following error.
    Please help me out to resolve it.
    Eror Message
    <May 6, 2011 7:32:40 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1304690560384' for task '8'. Error is: 'weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: org.apache.commons.httpclient, exact-match: false].'
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: org.apache.commons.httpclient, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <May 6, 2011 7:44:58 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
    <May 6, 2011 7:44:58 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
    [JCABindingManager] : This operation is not supported for JCA based MDB
    <May 6, 2011 7:45:00 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <May 6, 2011 7:45:00 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on fe80:0:0:0:be30:5bff:fed3:5db0:8001 was shutdown.>
    <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on 10.108.26.246:8001 was shutdown.>
    <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[7]" listening on 0:0:0:0:0:0:0:1:8001 was shutdown.>
    <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[6]" listening on 127.0.0.1:8001 was shutdown.>
    <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on fe80:0:0:0:200:ff:fe00:0:8001 was shutdown.>
    <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.122.1:8001 was shutdown.>
    <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[4]" listening on fe80:0:0:0:fcff:ffff:feff:ffff:8001 was shutdown.>
    <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:05 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    [TopLink Info]: 2011.05.06 19:45:06.235--ServerSession(255740887)--deferred_session logout successful
    [TopLink Info]: 2011.05.06 19:45:06.236--ServerSession(256131953)--tracking_session logout successful
    <May 6, 2011 7:45:06 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:06 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:06 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent().
    To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
    <May 6, 2011 7:45:09 PM> <FINEST> <NodeManager> <Waiting for the process to die: 20074>
    <May 6, 2011 7:45:09 PM> <INFO> <NodeManager> <Server was shut down normally>
    <May 6, 2011 7:45:09 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Thanks
    Phani

    George,
    To solve my problemn I uninstall my JDev, remove all folders (Oracle_home, and JDeveloper folder in users - app data - roaming). Install again, and get Webcenter Bundle from Help - Updates. Before a uninstall I was using a bundle that a have here in my machine.
    Thks

  • Error while processing library references. Unresolved application library

    Hi All,
    I created one ADF task-flow,in which I used content from share point, and then I converted portlets and deployed into integrated WLS server.and then I consumed thoese portlets into web-center spaces its working file.
    but i want to deploy those portlets into standalone server while deploying those I am getting following Errors. I am using 11.1.1.1.6 version for all my development.(Jdeveloper,webcenter and all).
    [07:48:08 PM] [Deployer:149193]Operation 'deploy' on application 'SP2010_application1' has failed on 'AdminServer'
    [07:48:08 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application SP2010_application1 on AdminServer.: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.content.jcr.sharepoint, Specification-Version: 11.1.1, exact-match: false]..
    [07:48:08 PM] Weblogic Server Exception: weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.content.jcr.sharepoint, Specification-Version: 11.1.1, exact-match: false].
    [07:48:08 PM] See server logs or server console for more details.
    [07:48:08 PM] weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.content.jcr.sharepoint, Specification-Version: 11.1.1, exact-match: false].
    [07:48:08 PM] #### Deployment incomplete. ####
    [07:48:08 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    please take a look into this. resolve me.
    regards
    Siva

    George,
    To solve my problemn I uninstall my JDev, remove all folders (Oracle_home, and JDeveloper folder in users - app data - roaming). Install again, and get Webcenter Bundle from Help - Updates. Before a uninstall I was using a bundle that a have here in my machine.
    Thks

  • Error while loading library fileQueries

    Hello,
    I am running runInstaller to install 10g database on Red Hat Enterprise Linux AS release 3.
    I get the following message: "There was an error while loading library fileQueries". This message is displayed after selecting "File System" radio button in the "Specify Database File Storage Option:" screen.
    A response to this issue is highly appreciated.
    Thanks,

    You might want to post this on the Linux forum under the "Technologies" category.
    Tom Best

  • [J2EE:160149]Error while processing library references

    Hi,
    I have an application which was working 9.2.1. I have deployed this application to 9.2.3. I have modified weblogic-application.xml, but it is giving these erros:
    An error occurred during activation of changes, please see the log for details.
    [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml:
    [Extension-Name: beehive-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false],
    [Extension-Name: wls-commonslogging-bridge, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false],
    [Extension-Name: weblogic-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false],
    [Extension-Name: wlp-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false],
    [Extension-Name: wlp-webdav-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false],
    [Extension-Name: wlp-services-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false],
    [Extension-Name: p13n-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false].
    How can I resolve these errors?

    Hi,
    Weblogic Server has two clusters and admin server. The referenced libraries didnt targeted to admin server. Because of that it was giving these errors. I have targeted to admin server all referenced libraries and I have deployed it.
    But,
    When I say start my application, I am taking this error:
    [EJB:010127]Incorrect DataSource type detected.
    The DataSource with JNDI name 'weblogic.jdbc.jts.commercePool',
    specified in the RDBMS deployment descriptor for the EJB 'TrackedAnonymous'
    does not support global transactions. The EJB container requires a DataSource
    that supports global transactions to be specified for transactions to be managed correctly.
    Errors were encountered while performing this operation
    [EJB:010127]Incorrect DataSource type detected. The DataSource with JNDI name 'weblogic.jdbc.jts.commercePool', specified in the RDBMS deployment descriptor for the EJB 'TrackedAnonymous' does not support global transactions. The EJB container requires a DataSource that supports global transactions to be specified for transactions to be managed correctly.
    Here are my data sources:
    cgDataSource
    cgDataSource-nonXA
    DSFDS
    IXPOC9DATASOURCE
    NDSDataSource
    p13nDataSource
    portalDataSource
    portalDataSourceAlwaysXA
    portalDataSourceNeverXA
    samplesDataSource
    All of these datasources targeted to NDSCluster, NDSAdminServer.
    How can I solve this problem?

  • OUI-10151:There was an error while loading library: globalVarQueries

    Hi,
    I am installing Oracle Database 11g version 11.1.0.6.0 on RHEL 5.3 x64.
    After completing all the requirements & pre-reqs, when the installation starts it throws the following error :
    OUI-10151:There was an error while loading library: globalVarQueries
    For this I selected "Stop installation of this component only"
    After this it gives the following error:
    OUI-10151:There was an error while loading library: generalQueries
    For this I again selected "Stop installation of this component only"
    But, after this the previous error keeps getting repeated over & over again, until installation stops, with the following error:
    OUI-10133:Invalid staging area. There are no top level components for Linux available for installation in this staging area
    Please help me out here, guys.

    Hi,
    did you install all this packages?
    # mount /dev/cdrom /mnt; cd /mnt/Server
    # rpm -ivh libgomp-4.3.2-7.el5.x86_64.rpm \
               kernel-headers-2.6.18-128.el5.x86_64.rpm \
               glibc-headers-2.5-34.x86_64.rpm \
               libstdc++-devel-4.1.2-44.el5.x86_64.rpm \
               sysstat-7.0.2-3.el5.x86_64.rpm \
               glibc-devel-2.5-34.x86_64.rpm \
               libaio-devel-0.3.106-3.2.x86_64.rpm \
               gcc-4.1.2-44.el5.x86_64.rpm \
               gcc-c++-4.1.2-44.el5.x86_64.rpm \
               elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm \
               elfutils-libelf-devel-0.137-3.el5.x86_64.rpm \
               compat-db-4.2.52-5.1.x86_64.rpm \
               compat-gcc-34-3.4.6-4.x86_64.rpm \
               compat-gcc-34-c++-3.4.6-4.x86_64.rpm \
               gdb-6.8-27.el5.x86_64.rpm \
               libtermcap-devel-2.0.8-46.1.x86_64.rpm \
               readline-devel-5.1-1.1.x86_64.rpm \
               unixODBC-2.2.11-7.1.x86_64.rpm \
               unixODBC-devel-2.2.11-7.1.x86_64.rpm \
               glibc-devel-2.5-34.i386.rpm \
               libXp-1.0.0-8.1.el5.i386.rpm \
               libstdc++-devel-4.1.2-44.el5.i386.rpm \
               unixODBC-2.2.11-7.1.i386.rpm \
               unixODBC-devel-2.2.11-7.1.i386.rpm \
               libaio-devel-0.3.106-3.2.i386.rpmRegards,
    David
    OCP 9i /10g / 11g
    http://www.oratoolkit.ch/knowledge/howto/installation/eeSrv-11g-R1-on-RHEL-5.3-x86_64.php

  • 160149]Error while processing library references. Unresolved application

    hi am having this error when running my application am in jdeveloper 11.1.1.6.0
    <07 Mar 2013 9:17:19 AM> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1362640639128' for task '1'. Error is: 'weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.sdp.client, exact-match: false], [Extension-Name: oracle.soa.workflow.wc, exact-match: false].'
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.sdp.client, exact-match: false], [Extension-Name: oracle.soa.workflow.wc, exact-match: false].
         at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         Truncated. see log file for complete stacktrace
    >
    <07 Mar 2013 9:17:19 AM> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'VulindlelaScreens'.>
    <07 Mar 2013 9:17:19 AM> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.sdp.client, exact-match: false], [Extension-Name: oracle.soa.workflow.wc, exact-match: false].
         at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         Truncated. see log file for complete stacktrace
    >
    [09:17:19 AM] ####  Deployment incomplete.  ####
    [09:17:19 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    #### Cannot run application VulindlelaScreens due to error deploying to IntegratedWebLogicServer.
    [Application VulindlelaScreens stopped and undeployed from Server Instance IntegratedWebLogicServer]when i click my help->check updated its empty it does not show any updates,but when i run other project it show updates which are available
    Edited by: adf009 on 2013/03/07 10:20 AM
    Edited by: adf009 on 2013/03/07 10:48 AM
    Edited by: adf009 on 2013/03/07 10:50 AM

    Solution:
    open the weblogic server console, in home page--> click the Deployments-->Select the adf.oracle.domain-->select target tab-->Click Lock & Edit-->
    select the servers (admin and managed Server) and save.--> click Activate All changes.
    Redeploy the application.
    Regards
    Kumar

  • Error while opening the file store file "WLS_DIAGNOSTICS000000.DAT".....

    I have a WL 9.2.1 running on Sun solaris o/s .....it is failing to start thowing the following exception
    <Mar 19, 2009 5:21:17 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.diagnostics.lifecycle.DiagnosticComponentLifecycleException: weblogic.store.PersistentStoreException: java.io.IOException: [Store:280021]There was a
    n error while opening the file store file "WLS_DIAGNOSTICS000000.DAT"
    at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:44)
    at weblogic.diagnostics.lifecycle.DiagnosticFoundationService.start(DiagnosticFoundationService.java:107)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: weblogic.store.PersistentStoreException: java.io.IOException: [Store:280021]There was an error while opening the file store file "WLS_DIAGNOSTICS0
    00000.DAT"
    at weblogic.store.io.file.Heap.open(Heap.java:166)
    at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:85)
    at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:350)
    at weblogic.store.PersistentStoreManager.createFileStore(PersistentStoreManager.java:202)
    at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:61)
    at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:42)
    ... 4 more
    Caused by: java.io.IOException: [Store:280021]There was an error while opening the file store file "WLS_DIAGNOSTICS000000.DAT"
    at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:213)
    at weblogic.store.io.file.StoreDir.open(StoreDir.java:103)
    at weblogic.store.io.file.Heap.open(Heap.java:164)
    ... 9 more
    Caused by: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11
    at weblogic.store.io.file.direct.DirectIONative.open(Native Method)
    at weblogic.store.io.file.direct.DirectFileChannel.<init>(DirectFileChannel.java:51)
    at weblogic.store.io.file.direct.DirectIOManager.open(DirectIOManager.java:138)
    at weblogic.store.io.file.StoreFile.openInternal(StoreFile.java:112)
    at weblogic.store.io.file.StoreFile.open(StoreFile.java:142)
    at weblogic.store.io.file.StoreDir.open(StoreDir.java:95)
    ... 10 more
    i went ahead and checkd the file and the privs on the file they look correct -rw-r--r-- ...but when i just restart it ..it starts with no errors the next time......What could be the issue.....please help
    Then only reason i could think of is the size of the file is 35MB now...is this the problem....if yes....is there a way to automaticaly rotate this file ....

    The root cause appears to be right in the stack trace:
    Caused by: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11I think this indicates that either the file was either locked (because another instance of WebLogic had it opened), or that the file was unavailable for some reason. WebLogic locks files as a safety precaution to prevent misconfigured setups (multiple domains sharing the same directory and store name) from attempting to share the same file.
    I don't think that this message necessarily means there is a file corruption.
    As for rotation, the file store automatically adds new files as needed (I think its 1 file for every 2GB of data). The "diagnostics" file store is generated by the optional diagnostics feature, and I think that this feature has options for controlling the amount of stored data.
    Tom

  • Weblogic Portal: Error While Deploying: VALIDATION PROBLEMS WERE FOUND

    Hello friends
    I am getting following error while deploying EAR on server.
    “Module named 'MyEAR' failed to deploy. See Error Log view for more detail.”
    Steps I followed:
    1: Created one portal domain successfully and was able to start the serve after thatr.
    2: Created one Portal EAR Project and added it on server.
    Now when I am restarting the server, getting following error/log
    **“weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND**
    **problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>”**
    Exception stack Trace:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
    at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
    at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
    at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
    at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
    at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:301)
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:178)
    as it is ‘brand new ‘ – IDE generated application, weblogic-application.xml is untouched.
    Thanks & Regards

    I have seen this problem also. To be clear, this occurs straight out of the box. In other words - launch eclipse, create a new workspace, create a new portal EAR project with the wizard, and then try to deploy it without touching anything. In fact, try changing the portal's facets to anything, plain EAR, 11g default, Portal EAR - it doesn't matter. It will not deploy. Either you get this error or you get deployment errors complaining about missing library references in the weblogic-application.xml. Then - you have to do surgery just to get an 'out of the box' portal to run. Very frustrating.

  • 'Overlapping Time Intervals' error while loading the Master Data

    Guys,
              Need you help with this. I am trying to load the Master Data (attribute) for InfoObject 0FMD_FRSITM using DTP from DataSource 0FMD_FRSITM_ATTR and am getting an error 'Overlapping Time Intervals'.
    This is happening due to overlapping Valid From/Valid To date's for the same Financial Statement Item (0FMD_FRSITM) with different Editions.
    If I select the option 'Ignore Duplicate Records' while loading the data, it is successful. But not all the records are loads and Editions are missing.
    Below is an example of how the data looks like.
    FRSITM         Valid To                  Valid From                 Edition
    1001             12/31/9999             04/01/2010                2010.1.1
    1001             01/31/2010             03/01/2010                2010.1.2
    1001             12/31/9999             02/01/2010                2010.1.3
    In the above scenario, the Valid To Data for record 1 and record 3 is the same (12/31/9999) and the record 3 is being ignore when I select the option 'Ignore Duplicate Records'.
    And also I see that the Edition is not the Key Field.
    Any suggestions or ideas? Appreciate your help.
    Thanks.

    FRSITM Valid To Valid From Edition
    1001 12/31/9999 04/01/2010 2010.1.1
    1001 01/31/2010 03/01/2010 2010.1.2
    1001 12/31/9999 02/01/2010 2010.1.3
    1. While selecting ignore duplicate, make sure to-date is not part of symantic key.
    2. if system comes across two same records it picks up the latest one.
    3. It shall merge the timelines is overlap is found.
    4. I hope Edition is time dependent attribute
    I believe infoobjet key is FRSITM Valid To.
    In your case because first record has more period and may be the latets record system ignore the earlier one with the same time interval.
    have a look at Q table and you shall be able to figure out for your self.
    Hope it helps
    Vikash

Maybe you are looking for