Wily Enterprise Manager not found/offline

I am working on setting up our E2E, I've reached the setup of the managed systems but when I get into it I can't select the Enterpise Manager; it is not an option in the drop down list.
I've gone through and entered the correct server, port, and log-in information correctly as directed during the setup.
We have had our Wily setup for a while now and just are getting around to being able to use. The Manager is setup on a different server using a different platform if that makes a difference; don't think it should though.
Please let me know if you see that I am missing something on this. Thanks for your time.

Thank you for the suggestion. I did end up upgrading the EM from 7.2.2 to 8.1.0 but it still didn't help populating that drop down field.
One thing I was not able to do during the installation was the automatic update to the Introscope agent for my Solution Manager system, it is stating that the ISAGENT has either been deployed or is at a later version. The it was last effected was 12/2007 and is still on the 7.2.2 agent. Is there a way to undeploy this to bring in the new one?
Thanks again.

Similar Messages

  • Wily Enterprise Manager not starting

    Hello colleagues,
    After migrating SAP solution manager to a new server (standard sap method R3load based despite same platform in source/target) we find wily Enterprise manager console stops some seconds after start.
    We just copy the whole FS where wily was installed on source system and the log error is:
    !SESSION 2012-02-21 19:21:53.357 -
    eclipse.buildId=M20060629-1905
    java.version=1.4.2.25
    java.vendor=Hewlett-Packard Co.
    BootLoader constants: OS=hpux, ARCH=IA64N, WS=motif, NL=en
    Framework arguments:  -product com.wily.introscope.em.product
    Command-line arguments:  -consolelog -product com.wily.introscope.em.product
    !ENTRY org.eclipse.osgi 4 0 2012-02-21 19:21:57.872
    !MESSAGE Application error
    !STACK 1
    java.lang.RuntimeException: Application "com.wily.introscope.em.application" could not be found in the registry. The applications available are: org.eclipse.
    equinox.app.error.
            at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:236)
            at org.eclipse.equinox.internal.app.EclipseAppContainer.start(EclipseAppContainer.java:92)
            at org.eclipse.equinox.internal.app.Activator.addingService(Activator.java:129)
            at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1064)
            at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1042)
            at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:967)
            at org.eclipse.osgi.framework.internal.core.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:94)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1224)
            at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
            at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141)
            at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEventPrivileged(Framework.java:1603)
            at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEvent(Framework.java:1578)
            at org.eclipse.osgi.framework.internal.core.ServiceRegistrationImpl.<init>(ServiceRegistrationImpl.java:103)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.createServiceRegistration(BundleContextImpl.java:657)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:609)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:675)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:359)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:331)
            at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
            at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
            at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
            at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
            at org.eclipse.core.launcher.Main.main(Main.java:30)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:331)
            at com.zerog.lax.LAX.launch(DashoA8113)
            at com.zerog.lax.LAX.main(DashoA8113)
    !ENTRY org.eclipse.osgi 2 0 2012-02-21 19:21:57.972
    !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
    !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-21 19:21:57.973
    !MESSAGE Bundle update@plugins/com.opensymphony.quartz_1.6.0.jar [7] was not resolved.
    !SUBENTRY 2 com.opensymphony.quartz 2 0 2012-02-21 19:21:57.973
    !MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: J2SE-1.5
    !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-21 19:21:57.974
    !MESSAGE Bundle update@plugins/com.wily.authentication.ldap_8.0.0.jar [8] was not resolved.
    !SUBENTRY 2 com.wily.authentication.ldap 2 0 2012-02-21 19:21:57.974
    !MESSAGE Missing required bundle com.wily.introscope.em_0.0.0.
    !SUBENTRY 2 com.wily.authentication.ldap 2 0 2012-02-21 19:21:57.975
    !MESSAGE Missing required bundle com.wily.introscope.em.client_0.0.0.
    !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-21 19:21:57.975
    !MESSAGE Bundle update@plugins/com.wily.authentication.local_8.0.0.jar [9] was not resolved.
    Could you kindly help?
    Best Regards!!!!

    Hi,
    have you found any solution for this. If you found any solution please post it back here
    we are also facing the same issue.
    Thanks
    Chaitanya

  • Wily Enterprise Manager Service not Started in Windows 2008 Server

    Hi All,
    Our Solution Manager is in EHP1 SP21 and OS-Windows 2008 Server.
    We installed Wily Enterprise Manager 8.0. and found 1 non-fatal error in the installation log. The service is not starting.
    However it works fine for Windows 2003 Server.
    Can anyone encountered with the same kind of problem?
    This is the latest log file information:
    Summary
    Installation: Successfulwith errors.
    387 Successes
    0 Warnings
    1 NonFatalErrors
    0 FatalErrors
    Action Notes:
    Execute ANT Script:       Script:
                              Status: ERROR
                              Additional Notes: ERROR - E:\usr\sap\ccms\wilyintroscope\install\em.installer.exec.ant15.xml:425: Timeout: killed the sub-process
    Thank you in advance.
    Regards
    Sanjai

    Note 1273028 - Introscope 8 Release Notes resoved this issue.
    Known problems in all Releases 8.x
    2. Windows Server 2008 is not yet officially supported by CA Wily for the Enterprise Manager. If you want to install the Enterprise Manager anyway, set the "Windows 2003 compatibility mode" for the installer before launching it. To activate this mode, right click on the installer.exe file in the Windows Explorer, select tab "Compatibility", activate the check box for compatibility mode and select Windows 2003. If you do not set this, the installer will consider your OS as Unix and install shell scripts (no suffix) instead of batch files (.bat) and leave out some files for Windows Service registration.
    If the windows service still fails to start please check if files ServiceWrapper.jar and ServiceWrapper.dll are present in folder lib. If not download them from attachment of this note.
    The service should start although giving an error message regarding the ServiceWrapper.dll. You can ignore this error.

  • SSO from Solution Manager to Wily Enterprise Manager issue

    Hi,
    We are facing problem in SSO from Solution Manager to Wily Enterprise Manager. We have done the configuration as per the Wily Enterprise Guide- "Introscope Version 8 Installation Guide For SAP" Page 38.
    Our Solution Manager system is running on AIX platform and Wily Enterprise Manager is on Windows 2008.
    This is what we are trying
    SOLMAN Production Client --> SOLMAN_WORKCENTER --> INTROSCOPE WORKSTATION --> this opens a new browser page and from there we click on Start Introscope -->
    Result --> SSO doesn't work, still we get login window.
    Introscope Enterprise Manager logs says -->
    9/12/11 10:47:17 PM BST [WARN] [Manager] Single sign on failed: No SAP single sign on ticket was found in the request header.
    Note: Another Solution Manager system in our landscape (on windows 2008 platform) is connected to same Wily Enterprise Manager (windows 2008) and from this solution manager SSO to Wily Enterprise Manager is working.
    Please help me with your expertise to solve this problem.
    Best Regards
    Davinder

    Hello Singh,
    Could you check if you have maintained these parameters in instacne profile ?
    From SCN post -> http://scn.sap.com/thread/969538
    Hi Hector,
    To configure SSO as per initial setup guide, please check your profile parameters in your Solution Manager as below:
    You have set up SSO, see also:
    SAP Note 817529: Checking the SSO Configuration
    Installation Guide and Security Guide for SAP Solution Manager
    Create the following profile parameters in the instance profile:
    login/create_sso2_ticket = 2
    login/accept_sso2_ticket = 1
    icm/host_name_full = fully qualified server name
    This parameter must be attributed to the fully qualified server name (for example wdfd002568.wdf.sap). The name must contain at least two periods. See also SAP Note 434918.
    Hope this helps,
    Regards,
    -Rohan
    BR,
    kamil

  • Wily Enterprise Manager 8 connection to SM Ehp1 failed

    Hi guys ( SM eph1 sps18, x64 jdk_ 17,Wily Enterprise Manager 8 )
    Have installed Wily Enterprise Manager 8 successfully. Its up and running with out errors.
    when i go to Diagnostics Setup -- Managed Systems--Introscope Agent
    Unable  to find the wily enterprise server
    error: Enterprise Manager retrieval
    Operation Failed
    Operations results - java.sql.SQLException: All configured Enterprise Managers are offline - check configuration.
    I have checked multiple times , Enterprise manager is up and running( as windows service)
    any advise how to fix

    Hi David:
    It worked fine previously.  This has been installed  a while ago ( a couple of years). We did have a couple of problems recently with corrupt data files.  Deleting the concerned datafile and restarting Wily solved the problem.  However I haven't a clue on how to get this going.
    thanks , Viji

  • Web Service session manager not found.

    I'm trying to understand how to use the HTTP utilities, and I'm having trouble just creating a session.  I get a Web Service session manager not found error.  I've read where the client has to support cookies.  My eventual client will be a labview VI that talks to a web server.  I llooked at the Toolsptions, but don't see anything related to cookies.  Not sure if that's what's causing this anyway, but I'm just digging.  Also, I want to eventually send http messages across TCP/IP.  Do I need to use the TCP/IP VIs (i.e. open connection, etc) or do I use the http utilities alone.  If both are needed, how does the httpRequestID and the TCP/IP connection ID correlate.
    Attachments:
    htttGetSession.vi ‏9 KB
    WebServerError.PNG ‏13 KB

    Hi can you please let me know how you resolved this issue?

  • SMD Agent Metrics/BOE native code metrics Missing in wily Enterprise Manager

    SMD Agent and BOE native code metrics are not updated to wily EM. Previously the metrics were written to Wily EM. This is standalone setup of Wily Ent Manager without Solution Manager.
    Environment:
    Standalone Wily introscope Eterprise Manager - Introscope Enterprise Manager 9 SP15
    DIAGNOSTICS AGENT 7.3 SP03 (incl. HostAgent)
    BI 4.0 SP6 Patch 6, Windows 2008, Clustered/Distributed.
    Logs:
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Initialization done.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Service provider initialized.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       [AgentContext.startApplications] Agent Applications started.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Smd connector has been disabled
    Apr 25, 2014 3:54:35 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from INITIAL to CONNECTING
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to DISABLED
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Fatal      com.sap.smd.wily.hostagent.WilyHostService - init(...): Failed to start Agent!
    [EXCEPTION]
    java.rmi.RemoteException: WilyHostAgent start failed; nested exception is:
      com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:122)
      at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)
      at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
      at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)
      at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
      at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
      at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)
      at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)
      at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:111)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:154)
      at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:733)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStart(SMDAgeletsRuntimeContext.java:495)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStartAppsIfNeeded(SMDAgeletsRuntimeContext.java:354)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.statusChanged(SMDAgeletsRuntimeContext.java:311)
      at com.sap.smd.agent.connection.SMDConnector.triggerStatusChanged(SMDConnector.java:1016)
      at com.sap.smd.agent.connection.SMDConnector.setConnectionStatus(SMDConnector.java:933)
      at com.sap.smd.agent.connection.SMDConnectionTask.startOffline(SMDConnectionTask.java:862)
      at com.sap.smd.agent.connection.SMDConnectionTask.internalAttemptConnection(SMDConnectionTask.java:549)
      at com.sap.smd.agent.connection.SMDConnectionTask$1.run(SMDConnectionTask.java:107)
      at com.sap.smd.agent.connection.P4JNDIContextHelper.executeInSecurityContext(P4JNDIContextHelper.java:148)
      at com.sap.smd.agent.connection.SMDConnectionTask.attemptConnection(SMDConnectionTask.java:102)
      at com.sap.smd.agent.connection.SMDConnectionTask.run(SMDConnectionTask.java:1282)
      at java.lang.Thread.run(Thread.java:743)
    Caused by: com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:62)
      at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:510)
      at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:99)
      at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
      ... 26 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
      at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
      at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
      ... 29 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1782)
      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
      at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2857)
      at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:235)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
      at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
      at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
      at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
      ... 31 more

    Hello Gopal,
    Please refer to section Wily Introscope setup for BOE 4.0 of this wiki:
    Managed System Setup of BOE 4.0 system in Solman 7.1 - SAP Solution Manager Setup - SCN Wiki
    You may also found interesting
    Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki
    https://service.sap.com/sap/support/notes/1722874
    https://service.sap.com/sap/support/notes/1357901
    Best Regards.
    Luis Roel

  • CA Wily Introscope was not found in LMDB

    Hello
    When I setup solution manager 7.1 SP11 ,In Basic Configuration step Configure Automatically, the automatic activity Create Self-Monitoring Scenario is not able to find the Wily Introscope technical system. As note 1820491 ,one error has occoured. Please check the following for detail .
    ERROR
    As note 1820491
    I have perform the following steps manually successfully
    In Landscape Browser UI, open the LMDB Administration - Expert UI
    In the Expert UI, delete following Class Name:CIM Class Name: SAP_IPSERVICEPORT and CIM Refernce String: WLY
    Repeat the same for other CIM Classes like SAP_HTTPSERVICEPORT in case they are displayed in the warning of step Configure Wily Introscope
    Return to Basic Configuration step Configure CA Wily Introscope and use Edit and Save buttons
    But when I perform the following step, one error has occurred:
    When save , one error has occurred:
    TCODE : SLG1
    Technical System not found
    The technical system 'WLY~IS_EM' was not found in the landscape, but the authorization check is posi
    tive. [CX_DIAGST_RETRIEVE_EXCEPTION]
    How to create the WLY IS_EM technical system ?
    Can who help me to solve this ?
    Thanks
    LEO LEE

    Hi
    LMDB->Technical Systems->Create, Display, and Edit Technical Systems->
    Technical System Selection->Type->Wily Introscope Enterprise Manager (Standalone)-> Extended System ID:->WLY->EDIT->Arrtributes

  • What's the best way to merge, restore or reconstruct iPhoto and Aperture libraries to resolve images that are not found/offline?

    Hey there, Apple Support Communities.
    To start, I'm working on a MBP Retina 15" with a 2.3GHz i7 processor and 16 GB of RAM.  10GB free on a 256GB SS HD.  Attached are two external HDs - one 1TB Western Digital portable drive from 2011, one 2TB Porsche LaCie non-portable drive from 2013; both connected via USB.  All photo libraries in question are on the external drives.
    I have Aperture 3.5.1 and iPhoto 9.5.1.  I prefer to work in Aperture.
    The Issue(s)
    Over the years, I have accumulated a number of iPhoto libraries and Aperture libraries.  At one point, I thought my WD drive was dying so I purchased the LaCie and copied all libraries over the the LaCie drive.  (Turns out, there's probably an issue with my USB port reading drives, because I can once again see the WD drive and occasionally I can't see the LaCie drive.)
    So now I have old version of some libraries on the WD drive, and new versions on the LaCie drive.
    When I was moving things, I ran the software Gemini to de-dupe my iPhoto libraries.  Not sure what effect that may have had on my issues.
    In my main Aperture library and in some iPhoto libraries, I get the image-not-found badge or exclamation point.  I've dug through the hidden Masters folders in various libraries to find the original image.  In some cases, I have been able to find the original image, sometimes in a different version of the iPhoto library.
    My Question(s)
    1.  For Aperture libraries that have missing originals, is there some magical way to find them, or have they just disappeared into the oblivion?
    2.  For iPhoto libraries that have missing originals and I have found the original in another iPhoto library, what is the best way to proceed?
    3.  Are there quirks to merging iPhoto and Aperture libraries (by using the Import->Library) feature that I should be aware of?
    TL;DR: Too many iPhoto and Aperture libraries, and not all the original pictures can be found by the libraries anymore, though some originals still do exist in other libraries.  Steps/process to fix?
    Thank you!  Let me know if you need add'l info to offer advice.
    With appreciation,
    Christie

    That will not be an easy task, Christie.
    I am afraid, your cleaning session with Gemini may have actually removed originals. I have never used this duplicate finder tool, but other posters here reported problems. Gemini seems to replace duplicate original files in photo libraries by links, and this way, deleting images can cause the references for other images to break. And Aperture does not follow symbolic links - at least, I could never get it to find original files this way, when I experimented with this.
    1.  For Aperture libraries that have missing originals, is there some magical way to find them, or have they just disappeared into the oblivion?
    You have to find the originals yourself. If you can find them or restore them from a backup, Aperture can reconnect them. The reconnect panel can show you, where the originals are supposed to be, so youcan see the filename and make a Spotlight search.
    For iPhoto libraries that have missing originals and I have found the original in another iPhoto library, what is the best way to proceed?
    Make a copy of the missing original you found in a folder outside the iPhoto library. You can either open the iPhoto library in Aperture and use "File > Locate Referenced file" to reconnect the originals, or simply reimport them. Then Lift&Stamp all adjustments and metadata to the reimported version.
    See this manual page on how to reconnect originals:  Aperture 3 User Manual: Working with Referenced Images  (the paragraph:  Reconnecting Missing or Offline Referenced Images)
    Are there quirks to merging iPhoto and Aperture libraries (by using the Import->Library) feature that I should be aware of?
    References images will stay referenced, managed will remain managed. You need to unhide all hidden photos in iPhoto - this cannot be done in Aperture.
    and not all the original pictures can be found by the libraries anymore, though some originals still do exist in other libraries.  Steps/process to fix?
    That is probably due to Gemini's replacing duplicate originals by links, and your best cause of action is to fix this before merging the libraries. Reconnecting can be done for your iPhoto libraries in Aperture.

  • Enterprise manager not installed.

    Hello everybody
    I have installed the SOA 11.1.1.2 suite as per the documentation. But when i am starting teh weblogic server,during startup it throws error regarding enterprise manager.
    stacktrace is like this
    <Jan 8, 2010 12:00:40 AM GMT+05:30> <Warning> <J2EE> <BEA-160195> <The applicati
    on version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVers
    ionLifecycleListener is ignored because the application em is not versioned.>
    <Jan 8, 2010 12:00:41 AM GMT+05:30> <Error> <Deployer> <BEA-149205> <Failed to i
    nitialize the application 'em' due to error java.lang.NoSuchMethodError: weblogi
    c.application.ApplicationLifecycleEvent.getDeploymentOperation()Lweblogic/applic
    ation/DeploymentOperationType;.
    java.lang.NoSuchMethodError: weblogic.application.ApplicationLifecycleEvent.getD
    eploymentOperation()Lweblogic/application/DeploymentOperationType;
    at oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener.pre
    Start(JpsApplicationLifecycleListener.java:76)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.r
    un(BaseLifecycleFlow.java:277)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    121)
    at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListene
    rAction.invoke(BaseLifecycleFlow.java:194)
    Truncated. see log file for complete stacktrace
    java.lang.NoSuchMethodError: weblogic.application.ApplicationLifecycleEvent.getD
    eploymentOperation()Lweblogic/application/DeploymentOperationType;
    at oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener.pre
    Start(JpsApplicationLifecycleListener.java:76)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.r
    un(BaseLifecycleFlow.java:277)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    121)
    at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListene
    rAction.invoke(BaseLifecycleFlow.java:194)
    Truncated. see log file for complete stacktrace
    >
    I can see that em is not versioned error. when i am trying to invoke em then it gives Error 404--Not Found
    It's really annoying.
    I have tried instaling it on Red Hat linux also, same error.
    really frustrating. I dont know if i can ignore it or not.
    Guys need help from your side.
    Admins: please see in this matter.

    Select the folder you have installed SOA, right click eidt the folder permssions.
    * Add full control to the current user & administrator for this folder & sub-folders.
    And retry.
    Also make sure that your permssions have been propagated to sub folders as well.

  • Enterprise Manager not coming up

    We installed the Oracle Application 10.1.3.0.0. for HP-UX PA RISC. and then applied the needed patch to upgrade to 10.1.3.1.0.0. We followed the guidelines for the OAS installation, and the installation seemed to have been successful.
    However, we could not get the Enterprise Manager to come up. We were able to get to the home page through the browser. When we clicked on the Enterprise Manager link, we were able to go to the login page. After logging in, we get a page not found screen.
    We tried to start up the EM by ORACLE_HOME/bin/emctl start dbconsole command but it did not work. We also tried the ORACLE_HOME/bin/emctl start iasconsole command, but it also did not work. In both cases, we get an error saying that the emctl does not exist in the bin directory. We verified that the emctl really does not exist in the bin directory.
    Are we missing some files, like the emctl? Do we have to make an advanced installation to make the EM show? Do we have to download and install the EM separately? Is there any step that we are missing in the installation? Do we have to install 10.1.2.0 first to get the emctl file?
    Any help or enlightenment will be greatly appreciated. Thank you in advance.
    AM ESMERO

    Hi,
    have you installed your SOA Suite in advanced mode?
    Then you have to enable a checkbox with "Configure this as an OC4J administration instance"
    http://download.oracle.com/docs/cd/B31017_01/linux.1013/install/advanced_install.htm#CIHHJDJG

  • Connection Solution Manager - Wily Enterprise Manager

    Hi all,
    we want to use SOlutionDiagnostics to monitor our abap and java instances. First, we would like to connect a abap system
    to our Enterprise-Manager and watch the results in solution manager.
    In transaction http//solutionmanagerhost:port/smd we are able to connect manually to our enterprise manager und log in, but solution manager didn't find the enterprise manager. ( we got the message: all the enterprise manager are offline ).
    What could be the reason ?
    How is an abap system registered in Enterprise Manager ? For java systems you have to add addiontianl java parameters in configtool. But for abap systems ?
    is there any howtoguide, how to connect systems to diagnostic and wathc the results in solman_workcenter für E2E ?
    the solution manager diagnostic instance ist already installed and registered over http://>SOLMANHOST>:/smd/go/ADMIN_AGENT
    kind regards
    andreas

    Hello,
    Are you using versin 8.0? If not use version 8.0.
    Regards,
    Paul

  • Memory Requirements for Wily Enterprise Manager

    Hi,
    I am using Wily 8.0 and we are seeing slowness in SOLMAN JAVA stack and in Wily EM. Before throwing memory I am trying to understand following points. I have already gone through installation documents which does not cover following points
    1> I understand Wily EM requires heap memory. Does Wily EM heap memory is same as JAVA heap, I mean both JAVA node and Wily EM access same assigned part of memory OR both JAVA node and Wily EM needs seperate memory? As per this I will throw more memory at box.
    2> Installation guide say "Increase the heap size (u2013Xmx) of the Enterprise Manager if you have more than
    ~10 agents" but how much? I did not see any formula for this.
    3> I am observing Wily EM process at O.S level is keep running continuously since I restarted it last time (which is weeks now). Is it normal?
    Thanks

    Amit,
    Question 1.
    Wily needs JVM Heap memory, which would be different from J2EE Instance HEAP.  Adding additional physical RAM to your server will definitely help.
    Question 2.
    Set the Heap Size parameters to a minimum of 1024 MB
    Initial Java Heap Size (in MB)
    wrapper.java.initmemory=1024
    Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=1024 ((higher the better....)
    Set the Java VM parameter u2013Djava.awt.headless=true for all platforms.
    Otherwise, the Enterprise Manager will need an X server, i.e., the DISPLAY
    environment variable must point to a valid X Windows server.
    The file to maintain the parameterization is EMService.conf available in the
    standard insttallation path /usr/sap/ccms/wilyintroscope
    Please refer to SAP Note 1273028
    Question 3.
    The process should be running for Wily to work (this is my understanding).  We also have this running for months on our server.
    Regards,
    Ravi

  • After ORA-07445, a part of Oracle Enterprise Manager  not working?

    Hi! Everyone!
    My database was have error message ORA-07445.
    I found document in MetaLink, and try to modified it.
    [https://support.oracle.com/CSP/main/article?cmd=show&type=BUG&id=7038750]
    1. SQL> alter system set event='10422 trace name context forever, level 1' scope=spfile;
    2. shutdown DB & startup DB
    After that, Oracle Enterprise Manager "Space Summary -> Problem Tablespaces " from 5 become 0.
    And since these days, it did not change.
    This is on solaris 10 oracle 10.2.0.4
    How can I make it normal?
    Edited by: user10220946 on Nov 24, 2009 6:12 PM
    Edited by: user10220946 on Nov 24, 2009 7:33 PM

    Hi,
    For Ora-07445 and Ora-0600 raise an SR with oracle support.
    thanks,
    baskar.l

  • After upgrade from 10.2.0.1 to 10.2.0.4 enterprise manager not working

    after upgrade from 10.2.0.1 to 10.2.0.4
    on windows enterprise manager is not working
    Edited by: 830525 on Mar 24, 2012 9:44 AM

    F:\Documents and Settings\hakem>emctl start dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    https://M1C3:1158/em/console/aboutApplication
    Starting Oracle Enterprise Manager 10g Database Control ...The OracleDBConsoleor
    cl service is starting..........................................................
    The OracleDBConsoleorcl service could not be started.
    A service specific error occurred: 1.
    More help is available by typing NET HELPMSG 3547.
    F:\Documents and Settings\hakem>NET HELPMSG 3547
    A service specific error occurred: ***.
    EXPLANATION
    A service-specific error occurred.
    ACTION
    Refer to the Help or documentation for that service to determine the problem.
    that's what happen while trying to start db console

Maybe you are looking for