Automatic Error when opening Disk Utility

Hi guys, I recently noticed this problem when clicking "Calculate Image Checksum..." in the finder pulldown menu for Disk Utility. I don't open Disk Utility often, so I can't be sure if this error has always existed or if it only has recently began occurring. Anyways, when I open up Disk Utility, it seems as though it is detecting a .dmg file on my desktop named "Desktop.dmg." When opening Disk Utility and calculating image checksum, I automatically get a pop up error saying:
Disk Utility Progress:
Unable to checksum "Desktop". (Operation not supported on socket)
When opening Disk Utility regularly, (by going to Applications -> Utilities -> Disk Utility) the Desktop.dmg file is not there. Is this normal? Is there any way I can prevent the Desktop.dmg from showing up?
Any help appreciated,
Thank you!

ive also noticed that if i have the "Macintosh HD" icon highlighted on the desktop, then attempt to calculate checksum, then when Disk Utility opens up it proceeds to checksum the drive and prompts for my password.
So it seems as though whatever it is that is highlighted in finder, Disk Utility will somehow create a .dmg file with the same name and try to mount it. Since this is not a real disk image, the error pops up. I am very puzzled by this, can anybody give me some insight?

Similar Messages

  • URGENT!!!!- INTEL MAC "INVALID SIBLING DISK" error when run disk utility

    I am very upset, I ran my verify disk permissions, everything fine, repair disk permissions, everything fine, do t periodically just to mae sure all my stuff is in order,,,, then I decided to run te VERIFY DISK, because do not do it as much and want to mae sure my macbook pro is running fine, and I get:
    Verifying volume “minimal minimal”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Invalid sibling link
    The volume minimal minimal needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    !!!!!!!!!!!!!!! ***?!!!!!!!!!!!!!!!!! there is no way of repairing the disk, and when I search for possible solutons it says I need to run it from the original osx installer disk, and even when it does not necessarily repir this error. besides the fact that the original cd is in atlanta and I am currently in barcelona, some say that I would need to reformat my drive and either way this might not solve the problem. I HAVE WAY TOO MUCH IMPORTANT INFORMATION on my macbook pro to reformat, and i do not have the money to buy an external hardrive, I A VERY UPSET, A BRAND NEW COMPUTER, LESS THAN TWO MONTHS OLD, AND ALREADY I HAVE THESE KIND OF PROBLEMS WITH IT, WHERE IS MY SUPPORT?! please tell me, what do i do? I expect a decent, viable slution to the problem. I need my computer ad the information in it, I work from it and also use it to produce music. why would I have this kind of problem, when I search for answers, everything relates to external hardrives, ..... this is my internal hard drive that I am talking about--- WHAT DO I DO?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    The available Apple centers in Spain are:
    ADEMAC
    C Castelló, 109
    28006 Madrid
    Tel 91 562 11 00
    BANANA COMPUTER
    C Leon and Castillo, 88
    The 35004 Palms of Great Canary
    Tel: 928 24 28 28
    Fax: 928 24 82 31
    BANANA COMPUTER
    General boulevard Franco, 141
    38001. - Santa Cruz de Tenerife
    Tlf.: 922882126
    Fax.: 922206782
    BENOTAC
    C Doctor Castelo, 35
    28009 Madrid
    Tel 91 308 43 63
    BENOTAC
    C Babel Nº1, the Premises
    29006 Malaga
    Tel: 952 04 09 55
    Fax: 952 04 13 58
    BILBOMICRO
    Stolen c of Amezaga, nº 7 low
    48008 Bilbao (Biscay)
    Tel 94 423 02 13
    BILBOMICRO
    C Abendaño, 52
    01008 Vitoria
    Tel 945 28 41 33
    BUS Solutions
    C Cabrales, 100
    33201 Gijón - Asturias
    Tel: 985 35 90 85
    CTA Serveis
    C Consell de Cent, 382
    08009 Barcelona
    Tel 93 24 40 350
    GOLDENMAC
    C Bolt, 48
    29007 Malaga
    Tel 952 42 97 12
    GOLDENMAC
    Avda. White Carrero, 2
    41011 Seville
    Tel 95 427 12 13
    K-TUIN
    C Luis You live 8
    50006 Zaragoza
    Tel 976 56 72 27
    K-TUIN
    C Hernandez Lazaro 14
    46015 Valencia
    Tel 96 385 36 74
    K-TUIN
    C Muntaner 537 - 541
    08022 Barcelona
    Tel 93 418 02 03
    K-TUIN
    C Orense, 52
    28020 Madrid
    Tel 91 55 56 798
    K-TUIN
    C Aureliano Valle, 4
    48010 Bilbao
    Tel 94 410 07 77
    Microgestio, LIMITED LIABILITY COMPANY.
    C Valencia, 87-89
    08029 Barcelona
    Tel 93 454 63 63
    Rossellimac.
    C Painter Lopez Mosque, 12
    18002 Granada
    Tel 95 829 13 24
    SICOS
    Pza of Good Shepherd 6
    20005 San Sebastián (Guipuzcoa)
    Tel 94 344 12 79
    Valles Tecnologic, S.A.
    Plza. Of the Unio, 3 the Premises 1º
    08190 Sant Cugat of Valleys (Barcelona)
    Tel 93 590 80 60
    Perhaps, since you are under warranty, they may have a boot disk to attempt to run disk utility and see if the problem can be repaired before resorting to reformatting. Disk error may occur because of a number of issues (installed software, crashes, shutdowns, physical movement of the drive while disks spinning, etc.)
    In addition you may want to boot in the single user mode to access the FSCK command as follows: The following is from the Apple support site
    Mac OS X: How to Start up in Single-User or Verbose Mode
    You may use a key combination when starting up the computer to enter single-user mode or verbose mode, either of which can be used for troubleshooting and in software development. This document applies to Mac OS X and Mac OS X Server versions 10.0 and later.
    Steps to Enter Single-User or Verbose Mode
    1. Shut down the computer if it is on.
    2. Press the power button to start the computer.
    3. Immediately press and hold the Command (Apple) key and one of the following:
    the "s" key for single-user mode.
    the "v" key for verbose mode.
    4. To exit single-user mode type: reboot
    5. Press Return.
    You have successfully entered single-user or verbose mode when you see white text appear on the screen.
    Then you may try to repair as follows using the FSCK
    fsck is a command-line utility that may be able to verify and repair a disk. If you can successfully start up in Safe Mode or use Disk Utility while started up from a disc, you don't need to use fsck. However, here are some situations in which fsck may be necessary.
    Your Mac OS X disc isn't available.
    Your optical drive isn't available.
    You can't start with a Safe Boot.
    Tip: If you use a Mac OS X Extended (Journaled) formatted volume, such as with Mac OS X 10.3 or later, you probably won't need to use fsck. If you do use it for any reason, please be aware that benign error messages can appear.
    If you're not sure how your volume is formatted and you can't start up from your Mac OS X volume to find out, type the following command in a command-line interface and then press Return: diskutil info /
    If you see "File System: Journaled HFS+" returned, you have a Journaled volume.
    To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
    Start up your computer in single-user mode to reach the command line.
    Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
    At the command-line prompt, type /sbin/fsck -fy
    Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
    ** The volume (nameofvolume) appears to be OK
    If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
    *** FILE SYSTEM WAS MODIFIED ***
    Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
    When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
    Your computer should start up normally and allow you to log in.
    About live verification in Mac OS X 10.4.3 or later
    In Mac OS X 10.4.3 or later, you can verify your Mac OS X volume while started from it. This is known as live verification, and can be used in three different ways.
    Option 1: Verify your disk using Disk Utility while started from the startup disk. To find out how to do this, see this article. Please note that live verification does not involve any disk repair, so if verification finds something that should be repaired, start up from your Mac OS X Install disc and use Disk Utility as described above in "Try Disk Utility."
    Option 2 (advanced): Use the command line and the command-line utility, diskutil.
    Start up your computer and log in as an administrator.
    Open Terminal (/Applications/Utilities).
    At the prompt, type the following command and then press Return:
    diskutil verify /
    Note: Don't use this method to check non-startup volumes.
    You should see messages such as the following during the disk check:
    Could not unmount disk for verification, attempting live verify
    Started verify/repair on volume disk0s3 Macintosh HD
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Macintosh HD appears to be OK.
    Mounting Disk
    Verify/repair finished on volume disk0s3 Macintosh HD
    Option 3 (advanced): Use the command line and the fsck_hfs -l command.
    Start up your computer and log in as an administrator.
    Open Terminal (/Applications/Utilities).
    At the prompt, type the following command and then press Return to determine your filesytem ID:
    df -hl
    Look for some lines of text that look like this:
    Filesystem Size Used Avail Capacity Mounted on
    /dev/disk0s3 37G 20G 17G 55% /
    /dev/disk0s5 37G 37G 641M 98% /Volumes/Storage
    Make a note of the first "disk" name that appears after /dev/, such as "disk0s3." This is your filesystem ID for your startup volume.
    At the prompt, type the following command and then press Return:
    df -hl
    Then type the following command, where "disk0s3" is your filesystem ID you noted in step 4, then press Return:
    sudo fsck_hfs -l /dev/disk0s3
    When prompted, enter your admin password, then press Return to begin the verification.
    You should see messages like these during the disk check:
    ** /dev/rdisk0s3 (NO WRITE)
    ** Root file system
    ** Checking HFS Plus volume.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking multi-linked files.
    ** Checking Catalog hierarchy.
    ** Checking Extended Attributes file.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume Macintosh HD appears to be OK.
    Additional Information
    If you're interested in UNIX-style command-line syntax, here's a look at how a couple of flags used in our instruction can influence fsck:
    The -y flag: Tells fsck that you want to answer "yes" to all questions about fixing, repairing, or salvaging information. This is the optimal approach, as answering "no" to any question causes fsck to stop. You cannot determine that all necessary repairs have been made until fsck completes and gives its final report.
    The -f flag: Forces fsck to check "clean" filesystems when preening.
    Macbook Pro 17" 7200 HD 1GB Powerbook G4 (15 inch FW 800)   Mac OS X (10.4.6)  
    Macbook Pro 17" 7200 HD 1GB Powerbook G4 (15 inch FW 800)   Mac OS X (10.4.6)  
    Macbook Pro 17" 7200 HD 1GB Powerbook G4 (15 inch FW 800)   Mac OS X (10.4.6)  

  • Partitioning error when using Disk Utility

    To better facilitate backups, I have decided to create a dedicated partition on my external hard drive for Time Machine to use. This is a 300GB disk (don't laugh) with 116 GB of music on it (mostly in the iTunes library) plus some other original AIFF files. Disk Utility reports that there is 163 GB of free space on it. When I try to create a partition of about 100GB (or even 75) it gives me the "Partition failed with the error: No space left on device". I get this even if I just try to resize the original partition. I tried rebuilding the directory with Disk Warrior and it didn't help. If I give it a small enough partition to try- say 25 GB or so- it will work. Much above that though, and it always gives me the "No space" error.
    I should mention that this disc, without any partition, was used for a while as the Time Machine backup disc. I don't remember why we stopped backing up, but I think it had something to do with running out of space.
    I told Time Machine to use the (unpartitioned) disc once again as the backup disc, and it started backing up to it. I stopped it before it got too far.
    Could there be files on there that I can't see that are taking up space? I did the "Erase free space" thing in Disk Utility but that didn't seem to clear out any more space. Like I said, it reports that there is 163 GB of available space.
    I need to be able to Time Machine the startup drive so that I can install Snow Leopard and also re-do the Boot Camp thing so I can re-install Windows XP, as my wife will have a need to use the dark side for work starting next week. I'm trying not to spend any money, so getting another drive isn't really an option and neither is getting another partitioning utility, as they seem to run about $40-$50 dollars or so, and I can't be sure that they will work either.
    Any ideas on this?
    Thanks-
    Val

    Most likely issue is fragmentation. Clone it to another and then restore it after erasing. That will defrag the disk. BTW, TM usually needs about three or four times the size of what it's backing up. I suggest popping for another ext HD; they're relatively cheap: <$100 USD. for 500-1,000 GB.

  • Error when opening Airport Utility for Windows XP

    Help! I have recently purchased and Airport extreme base station and the supplied Airport Utility software will not open. I am operating on Windows XP pro, and have installed the latest software updates to no avail. Is there an older version or perhaps an oblique solution to run the utility software?
    Thanks.

    Hello jleo325. Welcome to the Apple Discussions!
    Here are the links for the last two versions of the AirPort Utility for Windows:
    o AirPort Utility Setup 5.3.2 for Windows
    o AirPort Utility 5.3.1 for Windows

  • Os x could not be installed on Mac book pro because storage system verify or repair failed. When i open disk utility HDD does not let me repair.

    os x could not be installed on Mac book pro because storage system verify or repair failed.
    When i open disk utility HDD does not let me repair.

    In order to repair the system disk you must boot from another disk drive. The operating system will not allow the disk drive it is running from to be repaired.
    Book the MBP and create a bootable clone on an external disk drive. Then boot from the external disk drive and repair the system disk drive from there.

  • Disk utility will not boot using COMMAND   R. It won't give me the 'ERASE' option when I open Disk Utility. How do I wipe my hard drive?

    Disk utility will not boot using COMMAND   R. It won't give me the 'ERASE' option when I open Disk Utility. How do I wipe my hard drive?

    If you're truly running 10.6.8, there is no Recovery partition - that didn't come along until 10.7x.
    You'll need to use the set of gray discs that originally shipped with your model. If you don't have them, you can always get your serial number from the bottom of the casing and call Apple to get a set of replacement discs. These will run you about $20 + shipping & taxes. Once you have the discs, boot from Disk One and use Disk Utility to erase your HD and then reinstall whichever version of OS X that shipped with your model. No way around of getting the discs.
    Clinton

  • After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely

    After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely." What do I do now? This is an iMac and I'm running 10.6.8.

    Clean Install of Snow Leopard
    Be sure to make a backup first because the following procedure will erase
    the drive and everything on it. See below for how to clone a drive.
         1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
             with your computer.  Insert the disc into the optical drive and restart the computer.
             After the chime press and hold down the  "C" key.  Release the key when you see
             a small spinning gear appear below the dark gray Apple logo.
         2. After the installer loads select your language and click on the Continue
             button. When the menu bar appears select Disk Utility from the Utilities menu.
             After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
             size.)  Click on the Partition tab in the DU main window.  Set the number of
             partitions to one (1) from the Partitions drop down menu, click on Options button
             and select GUID, click on OK, then set the format type to MacOS Extended
             (Journaled, if supported), then click on the Apply button.
         3. When the formatting has completed quit DU and return to the installer.  Proceed
             with the OS X installation and follow the directions included with the installer.
         4. When the installation has completed your computer will Restart into the Setup
             Assistant. Be sure you configure your initial admin account with the exact same
             username and password that you used on your old drive. After you finish Setup
             Assistant will complete the installation after which you will be running a fresh
             install of OS X.  You can now begin the update process by opening Software
             Update and installing all recommended updates to bring your installation current.
    Download and install Mac OS X 10.6.8 Update Combo v1.1.
    You may be able to backup your data if you have an erased external drive you can use. Before you do the above but after you have opened Disk Utility you can try to clone your drive:
    Clone using Restore Option of Disk Utility
      1. Open Disk Utility.
      2. Select the destination volume from the left side list.
      3. Click on the Restore tab in the DU main window.
      4. Select the destination volume from the left side list and drag
           it to the Destination entry field.
      5. Select the source volume from the left side list and drag it to
          the Source entry field.
      6. Double-check you got it right, then click on the Restore button.
    Destination means the external backup drive. Source means the internal startup drive.
    Now this will only work if the drive is accessible and can be cloned by Disk Utility. Otherwise, you would need to access your drive from another Mac that you can connect via Firewire - Target Disk Mode.

  • Error message using Disk Utility

    Okay, my System Preferences is not showing up, so I ran the Disk Utility and this is the error message I got:
    Volume Macintosh HD was corrupt and needs to be repaired.
    Error: This disk needs to be repaired...then use Disk Utility to repair the disk.
    What do I do? Do I reinstall Mac OS X Snow Leopard or is this a whole other issue? Do I take it in to get checked out? Can I fix this without taking it in? HELP!

    What you need to do is repair the disk using your install disk (after you make sure that you've backed up your important data or have a current Time Machine backup):
    insert install disk and hold down C key while restarting
    once booted from the install disk, go past the languages, and then up to Menu bar - Utilities. Open Disk Utility and run repair disk. If it says "repaired", you're done. If not, run it again until you get the repaired dialog. You can then restart from your internal disk, eject the install CD and you're all set.
    If Disk Utility can't repair it, you'd need a more powerful application or it could be other things - we'll wait with that until after you've run the repair function.

  • Java Error When opening ER Model in Jdev 11g release 2

    Dear All,
    I m getting below error when opening my ER model in jDev
    java.lang.IllegalArgumentException: Ref is null
         at oracle.modeler.dif.ModelerGraphicBridge.findBridgeFromRef(ModelerGraphicBridge.java:343)
         at oracle.modeler.dif.ModelerGraphicBridge.createEdgeGraphic(ModelerGraphicBridge.java:267)
         at oracle.modeler.dif.ModelerGraphicBridge.createEdgeGraphic(ModelerGraphicBridge.java:86)
         at oracle.diagram.dif.GraphEdge.createGraphic(GraphEdge.java:152)
         at oracle.diagram.dif.GraphElement.createContainedGraphics(GraphElement.java:213)
         at oracle.modeler.shape.config.DefaultDiagramGraphicBridge.createDiagramGraphic(DefaultDiagramGraphicBridge.java:122)
         at oracle.modeler.dif.ModelerGraphicBridge.createDiagramGraphic(ModelerGraphicBridge.java:250)
         at oracle.modeler.dif.ModelerGraphicBridge.createDiagramGraphic(ModelerGraphicBridge.java:86)
         at oracle.diagram.dif.Diagram.createGraphic(Diagram.java:152)
         at oracle.diagram.dif.Diagram.createGraphic(Diagram.java:141)
         at oracle.modeler.dif.ModelerGraphicBridge.getGrapher(ModelerGraphicBridge.java:426)
         at oracle.modeler.dif.ModelerGraphicBridge.getGrapher(ModelerGraphicBridge.java:367)
         at oracle.modeler.addin.ModelerNode.findOrCreateManager(ModelerNode.java:252)
         at oracle.modeler.addin.ModelerDiagram.findOrCreateGraphSystemFromContext(ModelerDiagram.java:358)
         at oracle.diagram.framework.editor.CommonDiagram.open(CommonDiagram.java:231)
         at oracle.modeler.addin.ModelerDiagram.open(ModelerDiagram.java:111)
         at oracle.diagram.framework.editor.IdeDiagramEditor.openDiagram(IdeDiagramEditor.java:323)
         at oracle.diagram.framework.editor.IdeDiagramEditor.openImpl(IdeDiagramEditor.java:273)
         at oracle.modeler.addin.ModelerEditor.openImpl(ModelerEditor.java:79)
         at oracle.ide.editor.AsynchronousEditor.contextAvailable(AsynchronousEditor.java:427)
         at oracle.ide.editor.AsynchronousEditor.updateContextImpl(AsynchronousEditor.java:411)
         at oracle.ide.editor.AsynchronousEditor.setDelayedContext(AsynchronousEditor.java:395)
         at oracle.ide.editor.AsynchronousEditor$3$1.run(AsynchronousEditor.java:362)
         at oracle.bali.ewt.util.PaintUtils.invokeAfterRepaint(PaintUtils.java:53)
         at oracle.javatools.util.SwingUtils.invokeAfterRepaint(SwingUtils.java:607)
         at oracle.ide.editor.AsynchronousEditor$7.run(AsynchronousEditor.java:563)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
         at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:642)
         at java.awt.EventQueue.access$000(EventQueue.java:85)
         at java.awt.EventQueue$1.run(EventQueue.java:603)
         at java.awt.EventQueue$1.run(EventQueue.java:601)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:612)
         at oracle.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
         at oracle.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
         at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
    Thanks

    User,
    As you did not give any other information other then the stack trace it's heard to help. Does this error show a dialog box which asks you if want to save your work and exit or save and continue?
    Where was the ER diagram created?
    Timo
    Edited by: Timo Hahn on 20.05.2012 17:10

  • Error when open fdf document from Safari

    Reproduced on
    * Adobe reader 9.1.0
    * Acrobat Pro 8.1.3
    NOT reproduced with Acrobat Pro 8.0.0( withou updates )
    have simple fdf document for example in root of disk c:
    =============
    %FDF-1.2
    1 0 obj
    <<
    /FDF
    <<
    /F (1.pdf)
    /JavaScript
    <<
    /After 2 0 R
    >>
    >>
    >>
    endobj
    2 0 obj
    <<
    >>
    stream
    endstream
    endobj
    trailer
    <<
    /Root 1 0 R
    >>
    %%EOF
    ================
    when open it with IE or FF, al works fine. but when try to open in safari  messagebox shown
    "There was an error when open this document. This file cannot be found."

    minified version of not worked fdf
    %FDF-1.2
    1 0 obj
    <<
    /FDF <</F (pdf.pdf) >>
    >>
    endobj
    trailer
    <<
    /Root 1 0 R
    >>
    %%EOF

  • Error When Opening Any Form

    Hi All.,
    Im facing some issue while opening any form..its stuck in below mention file while opening any form i tried all the ways still im not able to fix the issue.
    Application:11.5.10.2
    OS-----------HP-UX
    DB-----------10.2.0.4.0
    File Name:
    oracle/forms/ui/FLWTextArea
    Work Around
    Relink the all the files
    Regenerated the jar files
    Regenerated the forms
    f60gen help=y
    Forms 6.0 (Form Compiler) Version 6.0.8.28.0 (Production)
    Forms 6.0 (Form Compiler): Release - Production
    (c) Copyright 1999 Oracle Corporation. All rights reserved.
    PL/SQL Version 8.0.6.3.0 (Production)
    Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
    Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
    Oracle Multimedia Version 6.0.8.25.0 (Production)
    Oracle Tools Integration Version 6.0.8.17.0 (Production)
    Oracle Tools Common Area Version 6.0.5.32.0
    Oracle CORE Version 4.0.6.0.0 - Production
    Metalink Doc id
    java.lang.NoClassDefFoundError: oracle/forms/ui/FLWTextArea Error When Opening Any Form [ID 1219663.1]

    Thanks,
    From the below doc id we are currently in patch set 19 but im not able see that in ad_bugs.,
    Note: 232313.1 - Information on Previous Versions of Developer 6i Patchsets
    https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=232313.1
    Here is an example:
    If you have Forms: 6.0.8.27.x --> You are on Developer 6i Patch 18
    If you have Forms: 6.0.8.26.x --> You are on Developer 6i Patch 17
    If you have Forms: 6.0.8.25.x --> You are on Developer 6i Patch 16
    If you have Forms: 6.0.8.24.x --> You are on Developer 6i Patch 15
    SQL> select bug_number from ad_bugs where bug_number='&BUG_NUMBER';
    Enter value for bug_number: 9935935
    old 1: select bug_number from ad_bugs where bug_number='&BUG_NUMBER'
    new 1: select bug_number from ad_bugs where bug_number='9935935'
    no rows selected
    SQL>

  • Getting 500 Internal Server Error when opening GC page

    There was no change in configuration and all of a sudden, I can not connect to GC. I did notice that OC4J for OC4J_EM is down and I can't get it to go "Alive". Can someone run opmnctl status and print the output for me?
    I'm on Windows 2003/GC 10.1.0.4. Anyone has seen this problem?
    Cheers,
    Rodney

    Exact error when opening page is:
    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.
    Please contact the server administrator, [email protected] and inform them of the time the error occurred and anything you might have done that may have caused the error. More information about this error may be available in the server error log.

  • Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

    Hi,
    We update the BW landscape for version 7.4 suppport package 4 (whitout HANA).
    We use a external system connection to extract data from a SQLServer database (Microsoft Connector 1.1 for SAP/BW)
    In the previous version (BW 7.0.1 SP 10) run correctly, but now is in error.
    Below the  BW error log:
    Error: COMMUNICATION_FAILURE with function RSB_API_OHS_3RDPARTY_NOTIFY and target system SQLIS.
    Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679 Transaction program not regist).
    Error log of Integrations Services
    [SAP BI Destination 1 [476]] Error: Microsoft.SqlServer.Dts.SapBw.Connectivity.ERPException: An error occurred during the dispatch of the incoming function. The last return code was "RFC_FAILURE".
    em Microsoft.SqlServer.Dts.SapBw.Components.SapBwSourceBWLoader.ProcessInput(Int32 inputID, PipelineBuffer buffer)
    em Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket)
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "SAP BI Destination 1" (476) failed with error code 0x80131500 while processing input "SAP BI Destination Input" (491). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.  There may be error messages posted before this with more information about the failure.
    I checked the topic and notes below, but without success
    CPIC Return Code 679 - Transaction Program not Registered - ABAP Connectivity - SCN Wiki
    Note 1480644 - gw/acl_mode versus gw/reg_no_conn_info.
    Note 353597 - Registering RFC server programs
    Regards,
    Bruno

    Hi Bruno,
    We were able to resolve the issue. SAP RDS is assisting us with our upgrade and one of their consultants gave us this fix/workaround.
    Edit and add an entry into P:\usr\sap\<SID>\DVEBMGS00\data\reginfo.dat on your BW host server.
    Below is the entry I added.
    P TP=<NAME OF PROGRAM ID> HOST=<remote hostname where you creating the RFC to> CANCEL=<remote hostname> ACCESS=*
    P TP=CTSAPNPSCI_PORTAL_FPS HOST=ctsapnpsci CANCEL=ctsapnpsci ACCESS=*
    Then in BW system goto smgw > goto > Expert Funtions > External Security > ReRead ACL (N) & Globally
    I hope that this works for you.
    Regards
    James 

  • Error when opening an RFC connection (LB : Hostname or service of the messa

    Hi All,
    Im trying to transport datasources in BW, they are 7.x  RSDS datasources. but we did not change the source system, it was existing and we are using the same source for older BW version. we now installing new BW 7.x system.
    These  transports went fine in BQ system but failing in BP system with the below error :
    Error when opening an RFC connection (LB : Hostname or service of the message ser
    Error when activating DataSource 2LIS_17_I0NOTIF RP1CLT100
    Error when opening an RFC connection (LB : Hostname or service of the message ser
    Error when resetting DataSource 2LIS_17_I0NOTIF RP1CLT100 to the active version
    the datasource 2LIS_17_I0NOTIF is active in RP1CLT100 system. when this transport goes to prod it tries to overwrite the existing one, as there are no changes to the datasource the structure will be the same.
    but after that it cant able to activate that datasource.
    so my question is can we able to activate this datasource in RP rather than doing transport again from R/3 Dev---R/3 PRD.
    i tried RSDS_DATASOURCE_ACTIVATE_ALL but it doesn't help.
    another question is when we migrate from 3.x datasource to 7.x, does this change any metadata in R/3 system as well.
    Best Regards
    Robyn.

    Hi Rizwan,
    Looking at the error message it seems like there is some issue with RFC connection and whatever objects you are trying to move are not reaching to target system. Just have a check with basis team.
    Once you migrate DS from 3.x to 7.0 yes there will be some meta data changes e.g. the DS type will be changed from ISFS to RSDS. You will have to send the migration along with current data source.
    Regards,
    Durgesh.

  • Error when opening an RFC connection in IDT

    Hi Experts,
    I m trying to create a relational connection (JCO) from IDT to BW 7.4, and I m getting the following error:
    Error when opening an RFC connection (CPIC-CALL: ' ThSAPOCMINIT', communication
    I searched this error in Internet and I found many discussions about it ...And I think it's about autorizations in BW system that by default dosen't allow external servers to connect to it.
    So, I changed the values for the following parameters in RZ11 t-code:
    gw/acl_mode = 0
    gw/reg_no_conn_info = 0
    But I still get the same error ...When I checked the SM59 t-code I found that IDT create an entry in TCP/Ip connections ...
    Can you guide me to solve this issue...
    BW server is 7.4 version on AIX OS
    BO server is 4.1 SP05 on windows system
    Thank's a lot for your help.
    Abdess,

    Hi,
    test the RFC connection in sm59.If it is sussecfull then try to create conneciton otherwise see the error message.
    Amit

Maybe you are looking for