Encounter another error when adding host target in EM 12c

Hi, all
After installing EM 12c successfully, I then tried to add target to the EM, I encountered such error:
Error Message: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. Pass in a valid hostname and port number for the OMS to successfully deploy the agent.
Exit Code :1
Again I am sure that my host name is reachable and port number it complains is open.
I also opened the SR with oracle support, the SR is 3-6060170341.
I would appreciate if anyone can help and shed some light on this issue.
Regards.
Yong

As i mentioned earlier if you need help from Oracle pls open a Service request (SR) with oracle support and upload the following logs:
<OMS_INSTANCE_HOME>/sysman/agentpush/*.*
Share the SR number.
Can you also ping the oms host from agent host and vice-versa?
Do you have any firwall ?
While deploying the agent using Add host wizard, keep the port input field blank and it will pick up the next free port automatically. There is some env setup issue which is causing this in both install types.
Once you log an SR, Oracle support will help you, they will look into your env and find the root cause. Posting small snapshot of failure in forum can’t be debugged further without logs or a web conference.
Edited by: Akanksha on Feb 11, 2013 2:32 PM

Similar Messages

  • I can't use Photobooth - when I open the app, I get the message: "Photo Booth couldn't save your photos - Photo Both encountered an error when trying to save your photos. You photos cannot be saved at this time."

    I can't use Photobooth - when I open the app, I get the message: "Photo Booth couldn't save your photos - Photo Both encountered an error when trying to save your photos. You photos cannot be saved at this time."
    i tried adding user macintosh hd/users/your_user/pictures/"photo booth"  but still photo booth is not working and even images in photo booth cant be deleted they keep coming back

    Back up all data.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    I've tested these instructions only with the Safari web browser. If you use another browser, they may not work as described.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box markedAllow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Triple-click anywhere in the following line on this page to select it:
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). I've tested these instructions only with the Safari web browser. If you use  another browser, you may have to press the return key after pasting.
    You'll be prompted for your login password. Nothing will be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command may take a few minutes to run, or perhaps longer if you have literally millions of files in your home folder. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
    Boot into Recovery. When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

  • Lightroom encountered an error when reading it's preview cache

    I been getting this error for over 2-3 months and thought it would go away with the new version releases, i tried all the standard fixes,deleting the catalog,compacting etc. even moving it to new folder, reinstalled the software twice.  The whole nine yards. IMHO, there's a problem with the software, it may be uique with differetent type of machine setup or a corrupt file in the in the catalog and the compacting doesn't fix it.
    The error always happens while in the develope and crashed, has to leave the software (sometimes it just hangs the software and you have to kill the task manually).  You have at least 10-15 seconds before going back in, otherwise it will still crash, a thread is still occuring from the orginal crash and still completing it's task. That's the error, annoying as heck.
    My only hoping is a new version of LR comes out soon (4.0) and it goes away, otherwise, I'm going to find something else-- driving me crazy, I spend about 10-15% of my time each week getting out and back in to make go away, then can go for a day(s) sometimes and no problems.  I tried recreating the problem on specific photos where I think it might be corrupt, that doesn't give any clue, there is no pattern to this at all, it happens randomly on new photos and old photos, yet i can go back to those photos again and no problems.
    Any NEW ideas would be appreciated (no compact, no new catalogs, new installs, turn off various options cache preview etc. move to new folder and more.....done that etc.).

    The error is exactly what's it in  the title of the post, Lightroom encountered an error when reading from its preview cache and needs to quit.  That's it.
    I don't know what else to tell you, i wish I had more.  This is all over the internet, I followed pretty much all the solutions, delete the catalog or delete the preview folders (tried both).  Tinker with the cachee preferences.   Most people kill the preview folders and the catlog gets recreated and there problem is resovled, doesn't work for me.
    No cloning, totally two different catalogs (not networked etc.)  a good question though.
    When I am refering to catalog and cache, I strictly talking about LR only, nothing outside of that or in the operating system, just LR files only, here they are:
    I  have a   LR catalog folder called--->   C:\Users\Mark\Documents\LightRoom Catalog\LR_Catalog
    you have another folder called: LR_Catalog Previews.lrdata   (with many subfolders underneath at)
    and I have LR catalog filein C:\Users\Mark\Documents\LightRoom Catalog\LR_Catalog
    LR_Catalog.LRCAT
    That's it, a file and a folder with many sub-folders.  I'll get a screen print with error next, but it's basically what I said earlier in the beginning, you can be in develope or even the library, and error occurs in a message box, you hit ok and the application exits. On average it can happen 6-7 times with an hour and sometimes not at all, working with same the photos.  Sometimes it can happen within mintues, sometimes not at all for over 2 hours.  There is no specific pattern to it. 

  • "Lightroom encountered and error when reading from its preview cache and needs to quit"

    I keep receiving this error every time I open LR, "Lightroom encountered and error when reading from its preview cache and needs to quit" and the app won't open. It said LR would try and fix this error next time I opened it but the error remains. I tried uninstalled and installing the app and the error remains.
    Any Ideas here? Is there another app that may be telling it where to look for the cache and it no longer there? I was using a ramdisk for a bit but ditched it. Not sure if that has something to do with it but it seems suspect.
    Your thoughts?
    --Kenny Brandon Wilson

    Talked to Adobe support this morning, this is their response in case anyone else is looking for help. I'm running a Windows 7 box, LR 5.6.
      Gokul: Click on start and type %appdata%, then open roaming folder.
      Edward: ok
      Gokul: Open Adobe folder.
      Gokul: Open Lightroom folder.
      Gokul: Open Lightroom folder> Preferences.
      Edward: ok
      Gokul: Rename Lightroom 5 Preferences.agprefs file as Lightroom 5 Preferences.agprefsOLD.
      Edward: OK
      Gokul: Please check if you can launch Lightroom without any error.
      Edward: it shows me a welcome screen and is asking me to select my country
      Edward: aka, register the software
      Gokul: You can skip and launch it.
      Edward: LR catalog not found
      Gokul: Please select the catalog.
      Edward: my original catalog?
      Gokul: Yes.
      Edward: testing integrity of catalog
      Edward: loaded just fine
      Gokul: Okay.
      Gokul: Please check if you can re-launch it again.
      Edward: yes, it worked!
      Gokul: Excellent!
      Gokul: Since your preferences were corrupted you were facing issue so we renamed the preferences file to reset it.
      Edward: aha....ok
    All of my import/export presets were intact along with develop user presets. I'm happy as a clam for my $10/month!

  • Lightroom encountered an error when reading from its preview cache and needs to quit.   Lightroom will attempt to fix this problem next time it launches. " But it doesn't fix it!

    I get the following window on loading Lightroom 5.7 -
    Lightroom encountered an error when reading from its preview cache and needs to quit.
    Lightroom will attempt to fix this problem next time it launches.
    I have tried several restarts, without success. Also reinstalled Lightroom; no joy
    Any suggestions?

    Using your system browser (Windows Explorer or Finder), open the folder that contains your catalog. In Windows it is in your pictures folder and then in a Lightroom folder. Inside of the Lightroom folder you will find another folder that has the extension .lrdata. It will have the same name as your catalog except for the extension. You need to delete that folder, and then start Lightroom again. Lightroom will generate a new previews folder, and you should be back in business.

  • Everytime I open lightroom I get a pop up message saying "Lightroom encountered an error when reading from its preview cache and needs to quit" and it closes. Ive already tried reinstalling, nothing seems to work. Help please!

    Every time I open lightroom I get a pop up message saying "Lightroom encountered an error when reading from its preview cache and needs to quit" and it closes. Ive already tried reinstalling, nothing seems to work. Help please!

    Open the folder containing your catalog. In that folder you will find another folder with the extension .lrdata, and you need to delete that folder. After you do that, Lightroom should start normally and will create a new preview cache.

  • Error when adding Essbase server...

    Hi,
    I installed Hyperion System 9.3.1 in my development machine and encounter the following error when adding a Essbase server in AAS for the first time.
    Error: 1042017: Network error: The client or server timed out waiting to receive data using TCP/IP. Check network connections. Increase the NetRetryCount and/or NetDelay values in the ESSBASE.CFG file. Update this file on both client and server. Restart the client and try again.
    I used the default user "admin" and password "password". I used my servername:10080 as the server name. I hope I am right.
    Why is this happening? I tried changing netdelay settings but still get the same. Is this something else? Does this have anything to do with my TCP/IP settings? I am installing this on a virtual PC.
    I couldn't find an answer in previous posts.
    regards
    h

    The things that come to mind:
    The server name you use should be the name of the virtual PC, not the machine it's running on. Also, depending on the settings for the Virtual PC environment, you may have to change the network options to allow it to be visible to the network, be in the right domain, etc...
    The above may or may not get you any closer, the error message itself is just saying it can't receive a response from the server, which means the server never got the request or can't send a response back.
    Good Luck,

  • Library error when adding contact or when logging in

    The messenger server has a replica of the partition holding the users.
    It's an OES 2 sp2 server, and the GW Messenger is 2.04.
    Sometimes we see an error that says 'Library error' when adding a contact, or it doesn't show all users that exists with the search parameter given.
    We also sporadically see a 'Library error' when some users log in to it.
    Looking in the log I see an error that says 0xAE16 when users log in fails.
    I can find the 0xAE11 error in the TID's but not the 0xAE16, I did find an article on the forums, mentioning this problem http://forums.novell.com/novell-prod...or-server.html, they mention memory problems, so it seems to me there is a bug that needs fixing.

    I've disabled the '/diruseralias-"Internet EMail Address"' setting that was set up in the strtup.ma and strtup.aa scripts.
    I've also, for now at least, chosen another replica.
    I haven't seen the errors yet, so here's hoping...

  • I received an error message in Lightroom 5 , Lightroom encountered an error when reading from its preview cache and needs to quit

    I was wondering now that I deleted my preview cache after receiving the lighgtroom encountered an error when reading from its preview cache  and needs to quit  , light room 5 opened fine now , but  I now have no previews showing  up , all I get is blank gray boxes ...  have  I lost everything ?
    how do I get the pictures or previews back ...all my folders I had catalogued , now show only grayed boxes where the previews were ...  can I get this back ?

    I will check for the meta data.. as to hows this adobes fault....first let me ask do you work for or get paid for by adobe?  If the answer is no, which i presume it is...then that answers it... how is it , or better yet why is it a billion dollar company, has or offers no support, no phone number, no email nothing...but depend on third party people who may or may not know or give the correct info to help, and do this free, all the while adobe makes $$$ and runs smaller companies that may have actually better products by getting or buying off reviews etc..that only rave, but never mention issues...the issue im having has been reported by adobe users since version 1, yet has not been addressed or even mentioned...why shouldusers get little true support from adobe, get a product that has un addressed issues is messed up...it would be like ford making newer vehicles say a f150, advertising all the bells and whistles , but knowing since their 2008 model  that if you go over 70 mph for more than 100 miles the engine will just shut off, then have know way to contact them to solve the problem...had no mechanics to fix it...no warranty...that would be insane...but yet companies like adobe and microsoft do this all the time, but since its notlife threatening as driving a truck would be somehow we accept it as ok....yet it sickens me the hardearned money spent on their products, its an investment,  like whether or not to go canon or nikon..your investing in the company its not easy to switch once you make that intial choice...  adobe and microsoft continously advertise all the so called (al beit meaningless) upgrades or improvents which are more fluff than  worth while improvent, but the way they present them you feel you need them...if they went back to the true ethics of buisness and american pride they would focus moe money and attention to customer service,  and truly improving the product rather than how to sell more...but then they know like my camera example once you choose your theirs...sad...i had an adobe salesman out right lie to me and misrepresented a product, as i was having an issue getting sound to work in creating a video of my granddaughters birth...i was using an older version, told him all the info , he said if i upgraded i would have no trouble, so i did...the sound still didnt work . Then they suggested another program to convert the files more money down...the other company also makes video editing programs, once that work...and cost less...but i am all tied up in adobe spending hundreds all ready...sad ...very sad...now that ive had some issues and have gone back and done more researching i see all tge issues, many go back 10 plus years and have yet to be addressed...yet many otherless known third party companies had similar issues, corrected them , are cheaper, have support teams but arent pushed in every photo magazine etc...and arent known where giants like Adobe that dont address there issues have or offer no Adobe paid support, yet through their money and muscle to dominate magazines, and web, by controlling how things are precieved....sad in deed...the more i learn, and experience the sadder things are....but enough complaining sadily im invested in adobe for now till i get rich,  just want the crap to work...so i can get my cherished pictures , once in a lifetime pics of my granddaughter  back...to bad people have to place faith in a company and risk loosing all the pictures that mean something to them,and realize the comoany only truly cares about $$$...sad

  • Activating DemoContent: Error when reading data target

    I'm trying to activate the SAP Demo cube <i>Purchasing Data</i> (0D_PU_C01). The Grouping Mode is set to <i>In Dataflow Before and Afterwards</i>.
    When I simulate installation, I get the error message <b>Error when reading data target 0D_PU_C01</b> (Message no. RSAU126) in the logs (although in the Collection Area the Simulation Result column is marked with a green check).
    I could find only 2 notes related to this error in the SAP Service Marketplace. SAP note nr. 540873 is about the BW indexing job. Note nr. 587796 (Error in after import of update rules) seams more appropriate, however not thoroughly right. In fact it refers to <b>BW 3.1 Content</b> or <b>BW 3.0B</b>.
    My system version instead is:
    BI_CONT 353
    SAP_BW 350
    The very same problem occurs when I try to activate the SAP Demo <i>Sales and Distribution</i>.
    Any suggestion?
    Thanks, Davide

    Ok, it worked! Now however I have some more doubts.
    1. I can't find the InfoObjects (e.g. 0D_GR_QTY, 0D_PLANT, 0D_MATERIAL, etc.) anywhere in <i>Modeling -> InfoObjects</i>, even if:
      a) I can find them under the <i>InfoSource</i> tree of the <i>SAP Demo</i> Application Component
      b) they appear activated in <i>Business Content</i>
    What's going on?
    2. The newly activated <i>Purchasing Data</i> cube has been added to the <i>Unassigned Nodes</i> InfoArea, and not to a newly created SAP Demo Purchasing (0D_MMPUR) InfoArea, similarly to the structure I saw when collecting the InfoProvider in Business Content. Is this the normal behaviour?
    3. No DataSource has been assigned to any of the InfoSources. I read at:
    http://help.sap.com/saphelp_erp2004/helpdata/en/43/57df37463a126ae10000009b38f842/content.htm
    that the <i>SAP Demo</i> Source System will be used. What I can't understand is if I need to manually create and select this Source System. I thought it would be automatically created and assigned during the Business Content's cube activation. This is not the case. What steps would I have needed to perform?
    Davide

  • Have a  problem with Lightroom 5.4.  Since the program crashed yesterday it won't launch, it comes up with the message "Lightroom encountered an error when reading its preview cache and needs to quit".  "  Lightroom will attempt to fix this problem net ti

    Have a  problem with Lightroom 5.4.  Since the program crashed yesterday it won't launch, it comes up with the message "Lightroom encountered an error when reading its preview cache and needs to quit".  "  Lightroom will attempt to fix this problem next time it launches".  Except that it doesn't, I keep getting the same message and the program closes.  Does anyone know what I  can do to repair it?  Can't back up, can't do anything.

    There are dozens of threads in this forum that describe the fix

  • Lightroom encountered and error when reading from it preview cache and needs to quit

    A power outage caused my Lightroom 5.2 to shut down without closing.  When I powered back up and opened lightroom it gives me an error "Lightroom encountered and error when reading from it preview cache and needs to quit" and then it says it will try to fix it the next time it opens. I have opened it 20 times and it is not fixing it. I removed the program completely and upgraded to 5.5 AND it is still giving me the same error.  Is my catalog corrupt or something? I had it set to automatically load the most currently used catalog, so it is not allowing me to open or start a new catalog either. HELP!!!

    Search the forum, this has been answered many times.

  • I'm unable to open up Lightroom 5, I get this message in a pop up box: "Lightroom encountered an error when reading from it's preview cache and needs to quit" Underneath  that is "Lightroom will attempt to fix this problem the next time when it launches."

    I'm unable to open up Lightroom 5, I get this message in a pop up box: "Lightroom encountered an error when reading from it's preview cache and needs to quit" Underneath  that is "Lightroom will attempt to fix this problem the next time when it launches."  It hasn't, what should I do? Thanks Shawn (Irish Se7en) .

    Can you try to rename (not delete!) the folder named "YOUR_CATALOG_NAME Previews.lrdata" and restart Lightroom?

  • LR encountered an error when reading from its preview cache and needs to quit.

    I have the 30 day trial version of Lightroom.  I was able to use it for one week, but the past 1.5-2 weeks, it has been locked up and giving this error message.  How do I resolve the problem?  And how do I reset the 30 day free trial?  I would like to have time using the product, before deciding on the annual contract.
    "LR encountered an error when reading from its preview cache and needs to quit.  Lightroom will attempt to fix this problem the next time it launches."
    Thank you.

    Delete the preview cache from the Lightroom folder in your Pictures folder if you used the default placement. It has the extension .lrdata.
    You cannot reset the trial period.

  • I keep receiving this error every time I open LR, "Lightroom encountered and error when reading from its preview cache and needs to quit" and the app won't open. It said LR would try and fix this error next time I opened it but the error remains. I tried

    I keep receiving this error every time I open LR, "Lightroom encountered and error when reading from its preview cache and needs to quit" and the app won't open. It said LR would try and fix this error next time I opened it but the error remains. I tried uninstalled and installing the app and the error remains. I have windows 8. Can anyone please help???

    Use Windows Explorer to open the folder containing your catalog. The normal location is Pictures\Lightroom. Locate a folder with the extension .lrdata and delete that folder. Then you should be able to start Lightroom again, and Lightroom will begin building and new previews folder. Do not delete anything else.

Maybe you are looking for