Error Enabling Journaling with diskutil enableJournal diskXsX

I have few large backup volumes built specifically as HFS+ with Journaling disabled but now I notice problems where we have to wait very long time for hfs_fsck to complete its checkup and have decided to go back and enable journaling but keep getting errors. Here is more detail:
After I ran:
sudo fsck_hfs /dev/disk14s3
And it completed without problem then I ran:
sudo diskutil enableJournal disk14s3
Which gives me following error:
An error occured journaling the filesystem
Checking volume info it shows:
File System: HFS+
Owners: Enabled
Partition Type: Apple_HFS
Bootable: Is bootable
Media Type: Generic
Total Size: 9.2 TB
Free Space: 548.3 GB
Read Only: No
Ejectable: Yes
I have unmounted and mounted this volume without problem and have tried different variations of "diskutil enableJournal xxx" but everytime I get same error. I've also "Disk Utility" Enable Journaling option with no success and have tried diskutil with "sudo -s" option and tried "diskutil disableJournal xxx" and it shows:
Journaling was already disabled on the volume
I have another similar volume that has 2 TB available space and am getting same error not enabling journaling. First volume has around 85,000 files and second one close to 800,000.
Appreciate any input?

I'm able to enable journaling on all other volumes under 2TB beside those large ones (9TB). I've tried "mount_hfs -j -c /dev/disk13s3 /Volumes/BadJournal" and when I ran "diskutil info disk13s3" it shows File System is "HFS+ Journaled" which shouldn't be the case and after I ran "disktool -r disk13s3" it reverted back and showed HFS+ only. I've also ran multiple hfs_fsck, diskutil repairDisk, and reboot which don't show any problem and still not able to enable journaling.
Could this be a limitation of diskutil not able to enableJournal for 9TB volumes or volumes with large number of files?
Appreciate any help

Similar Messages

  • Bootcamp partitioning error: "enable journaling", but my drive is journaled already.

    Hi,
    I'm trying to partition my Mac OS X (10.6.8) to install Windows 7, but during the partitioning process an error comes up that tells me my drive needs to be in Extended (Journaled) format, and directs me to Disk Utilities. However, my drive is already in that format, it always has been, and the option to do so is grayed out as a result. I've combed the message boards for similar problems but the only solution I've seen involved already existing partitions that weren't all journaled, but that doesn't apply to my case. Any thoughts?
    Thanks!

    Are there any other partitions on the drive besides your startup volume?
    You might try:
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. 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 your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • Do I need to repair after enabling journaling on MBP with software update?

    My new 17" 2.4GHz MacBook Pro for some reason came without journaling turned on. Now the new MacBook Pro Software Update 1.0 wants to enable journaling, but the instructions says I need to do a disk repair afterwards booting from the OS X DVD. Unfortunately I don't have the DVD with me as I'm on a long trip.
    Do I really need to do the repair afterwards? Could I just as well enable journaling from Disk Utility without running the software update? Or should I wait until I get back? I've had some stability issues with the MBP and therefore want to enable journaling to see if that makes things more stable.

    Actually... I don't believe you "have" to run disk repair afterwards. The info posted by Apple states "Note: After MacBook, MacBook Pro Software Update 1.0 has been installed, the Macintosh startup volume will have journaling enabled.":
    http://docs.info.apple.com/article.html?artnum=306442
    I believe the idea behind running the disk repair is just precautionary. I have updated a MacBook and three MacBook Pros and ran the disk repair utility from the install disks. The utility did not find any issues with any of the four machines I ran the update on. If you don't have access to your install DVD now... just run it when you get back home. To be honest... I expect the VAST majority of users out there will just install the update and never go through the step of going through a disk repair from the install DVD.

  • EXT4-fs error loading journal - whats best way to recover

    uh oh, i have a hard drive crash it appears.  i was doing some web dev and i dont want to lose this work.   yesterday i noticed the hard light was on almost if not solid. i couldnt log remtoely into ssh, it did answer and let me atleast get to the username, but the password prompt wouldnt come up. the apache server was still running to serve web files, but the WebDAV wouldnt allow file connection, hittting the space bar and mouse wouldnt awake the monitor at all, this went on for several minutes.
    so i had to reset (restart).  looking back, i think this is the 2nd time i messed up things by resetting the file system while it was doing god knows what.
    now when it boots im getting sector and mount errors.
    Failed command: Read DMA
    Status DRDY ERR
    ata1:00 error: { UNC }
    end_request: I/O error, dev sda, sector 38762983
    Failed to read block at offset 1628
    EXT4-fs (sda3): error loading journal
    ^Zmount: wrong fs type, bad option, bad superblock on /dev/sda3
    missing code page, or helper program, or other error.
    in some cases userul info is found in syslog - try dmesg | tail or so
    now im dropped to an emergency shell
    # dmesg | tail
    outputs almost same error
    Descriptor sense data with sense descriptors (in hex)
    {followed by hex output}
    JBD2: Failed to read block at offset 1628
    JBD2: recovery failed
    EXT4-fs (sda3): error loading journal
    it appears i jacked it up when i reset it during file operations.
    where to go from here?  i was going to load a partition program just to see if it can read teh drive at all, in the attemtpt to relocate the drive to another pc to backup backup my home directory. 
    what kind of repair tools can i run from the emergency shell to repair?
    this link might help somebody hele me figure out whats best here http://www.linuxinsight.com/ext4-root-p … rrors.html  how do i make sure the partition isnt mounted, assuming it isnt is not good enough for me, since this is business data.
    im thinking of running fsck
    Last edited by wolfdogg (2012-02-24 17:52:34)

    Hard drive has quited down, thats a change.
    After pulling back up the attribs for the drive it is saying the same thing it said after both the short, and long test before i ran the WD Diagnostics and repair on it.  Thats expected im guessing since the SMART is just a log, so i wouldnt expect not to see the info that has already been logged.
    ill include a few of those attributes here that were reported when i ran those tests here incase anybody can help figure out their real meaning.  What i want to point out is that i found out that if the TYPE attribute comes up as "pre-fail" and "oldage", its my take that it means replacement is suggested, but does NOT mean the drive is failing.  Although this is counter intuitive, basically the more important attribute is "WHEN_FAILED".  see the quote from the man below for more info on this...
    Some of the attributes displayed for
    smartctl --all /dev/sda3
    Raw_Read_Error_Rate | Pre-fail
    Spin_Up_Time | Pre-fail
    Start_Stop_Count | Old_age
    this goes on and on for 15 attributes with Pre-fail and Old_age in all of them, with Old_age being in most. 
    note, the WHEN_FAILED column is filled only with hyphens - therefore, there has been no failure.
    so for future reference, i want to quote a portion of the smartmontools which relates to hard drive fail attributes http://smartmontools.sourceforge.net/ma … ctl.8.html
    Each Attribute also has a Threshold value (whose range is 0 to 255) which is printed under the heading "THRESH". If the Normalized value is less than or equal to the Threshold value, then the Attribute is said to have failed. If the Attribute is a pre-failure Attribute, then disk failure is imminent.
    Each Attribute also has a "Worst" value shown under the heading "WORST". This is the smallest (closest to failure) value that the disk has recorded at any time during its lifetime when SMART was enabled. [Note however that some vendors firmware may actually increase the "Worst" value for some "rate-type" Attributes.]
    The Attribute table printed out by smartctl also shows the "TYPE" of the Attribute. Attributes are one of two possible types: Pre-failure or Old age. Pre-failure Attributes are ones which, if less than or equal to their threshold values, indicate pending disk failure. Old age, or usage Attributes, are ones which indicate end-of-product life from old-age or normal aging and wearout, if the Attribute value is less than or equal to the threshold. Please note: the fact that an Attribute is of type 'Pre-fail' does not mean that your disk is about to fail! It only has this meaning if the Attribute's current Normalized value is less than or equal to the threshold value.
    If the Attribute's current Normalized value is less than or equal to the threshold value, then the "WHEN_FAILED" column will display "FAILING_NOW". If not, but the worst recorded value is less than or equal to the threshold value, then this column will display "In_the_past". If the "WHEN_FAILED" column has no entry (indicated by a dash: '-') then this Attribute is OK now (not failing) and has also never failed in the past.
    I have a couple questions
    Do i have this figured out right? 
    This particular hard drive is ok for stable use until i can afford to replace it?   I plan to keep an eye on the SMART monitor to look for fails as well.
    How would i run a proper file check, as opposedf to a file system check, because localhost/phpmyadmin isnt working, and thats where it all started.  im sure the files got chewed up there, and elsewhere.
    Last edited by wolfdogg (2012-02-25 07:51:22)

  • Trying to install Lion. says this disk is not enabled (journaled) - but when I look at the drive it actually is os extended journaled - Stuck! Have tried repair disk permissions and still no luck

    trying to install Lion. says this disk is not enabled (journaled) - but when I look at the drive it actually is os extended journaled - Stuck! Have tried repair disk permissions and still no luck - any thoughts? Have spent two weeks trying to get apple support and itunes to help me get lion after a hard drive fail and now they are closed and I really just want to get moving!

    Are you installing OS X Lion over an existing installation of Snow Leopard, or are you reinstalling?
    First be sure you have everything on your system backed up. Then reboot with the Command-R keys held to get to the OS X Lion recovery volume. In here, select Disk Utility and use the First Aid tab in here to run a verification on your boot drive. If there are any errors, fix them and then try the installation again.
    The next step would be to format the drive, so with your backup secured, use Disk Utility's Erase tab to re-format the drive to Mac OS X Extended (journaled), and then quit Disk Utilty and attempt the installation again.

  • Error in WebDynpro with WebServices

    Hi all,
    I’m getting some errors using applications deployed in WEB AS SP9 that runs as a WebDynpro IView in EP.
    Running the application as standalone (out of EP) this works fine.
    NetWeaver Developer Studio 2.0.9
    WebDynpro application using WebServices that access Oracle 8i database in the follow sequence:
    WebServices -> Session Bean stateless -> Entity Bean CMP (manage connections; generate sql code, etc.)
    In WebDynpro application we import WebService Model by the follow sequence:
    New Model - Import Web Service Model - Local Server for WSDL Source - <WebService deployed>
    In each WebServices we have created these methods:
    findByID(ID);
    getAll();
    insert(parameters);
    remove(ID);
    update(parameters);
    We guess that the error is generated in Entity Bean because all WebServices generate these errors.
    <b>Error 1 - Application with WebServices Model</b>
    Error stacktrace:
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Repository Object br.com.xxx.fluxo.Fluxo/ComponentInterface:FluxoInterface/InterfaceViews:CadastroSituacaoFluxoInterfaceView/InboundPlugs:Default associated via relation RepositoryObjectRelation(br.com.xxx.fluxo.application.CadastroSituacaoFluxoApp, StartupPlug) does not exist.
         at com.sap.tc.webdynpro.repository.RelationToOne.resolveTargets(RelationToOne.java:124)
         at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:108)
         at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:72)
         at com.sap.tc.webdynpro.repository.RelationToOne.getTarget(RelationToOne.java:174)
         at com.sap.tc.webdynpro.repository.RepositoryObject.getRelatedModelObject(RepositoryObject.java:349)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getStartupPlugInternal(IWDApplicationInfo.java:319)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:355)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    -- end --
    <b>Error 2 - Application with WebServices Model</b>
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
    Web Dynpro code generators of DC local/Apontamentos:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: (unknown)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87037.313
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller NotProductiveEventController
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    <b>Error 3 - Application with RFC Model</b>
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
    Web Dynpro code generators of DC local/Apontamentos:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: (unknown)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87037.313
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller ZMANPP012Controller
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

    Hi,
    I feel this error is nothing to do with webservice model.
    Please check your application properties like startupPlug,Interface View etc. Set the properties correctly and deploy once again.
    Regards, VIP

  • Enable - Create With Reference in Sales order

    Hi All,
    I want to enable - Create With Reference in Sales order
    We have 1 billing doc type YX1 to be used as reference for a sales order type ZX3
    How to enable Create with reference from Sales Document type YX1 to Sales Document type ZX3.
    Currently, I am getting error 'Copying from sales document type YX1 to ZX3 is not supported'.
    Please let me know the steps to be followed.
    Thank you!
    Regards,
    Shanu Jain

    Hi,
    The error clearly suggests that there is no copy control maintained b/w invoice YX1 and sales order type ZX3. You need to maintain that in SPRO > Sales and Distribution > Sales Documents > Copy control for sales documents. (You may check the correct node here). Here, you select the billing document to sales document.
    Check for source and destination. You can take the source as F2 and CR (if ZX3 is a credit Memo request) as Destination document. You can copy the same and change the source and destination as YX1 as source and ZX3 as destination. Then, at the item level, if you have a new item category you can specify it as the 'Proposed Item Category'. Save it.
    Now try to create the sales document ZX3 w.r.t YX1... It should work.
    Hope this helps
    Thanks
    Mukund S

  • Enabling Journals in a Model in SAP BPC 10.0 MS

    Hi,
    Where does one enable journals functionality in SAP BPC 10.0 MS?
    Here's the background:
    I created a new Environment from EnvironmentShell
    Worked on dimensions, member sheets etc. in the Consolidation Model
    In the SAP Web Administration, Consolidation Monitor, I get the error Initialization Failed when clicking on the Journal item in the TreeView on the left. Clicking on the See Details, I get the error JOURNAL_NOT_ENABLED.
    In the Planning and Consolidation Administration Client, I get a similar error when clicking on Define Journal Validation Rules or Define Journal Translation Rules. (Journal in not enabled in Consolidation)
    I then thought I would be clever and modified the column 'Journal' in the table dbo.tblApp by putting a '1' there.
    Refreshing the Planning and Consolidation Administration Client, I see that for the Consolidation Model, the Journals are specified as 'in use'. However, returning to the SAP Web Administration and clicking on the Journal option, the error I now get is 'Invalid object name dbo.jrnAddedItems', probably because my backdoor hack circumvented some code.
    Where does one enable journals in a Model on the MS 10.0 platform? For the life of me, I can't find it. This despite much searching. Clearly I am missing something obvious.
    Kind Regards
    Nick

    Hi Arnold,
    Thanks. Yip, that's it. (I knew I was missing something remarkably obvious - it's just that I could not find it for some strange reason.)
    Again, many thanks.
    Kind Regards
    Nick

  • Error creating bean with name 'org.springframework.dao.annotation.Persisten

    Hello
    I am using Hibernate 4, Spring 3 , JSF 2.0 and Weblogic 10.3.6
    When I start weblogic server and server starts successfully, however whenever it starts publishing application, I am getting the following exception.
    Error creating bean with name
    'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0'
      defined in ServletContext resource [/WEB-INF/applicationContext.xml]:
      Initialization of bean failed; nested exception is
      org.springframework.beans.factory.BeanCreationException:
        Caused By: org.springframework.beans.factory.BeanCreationException: Error creating
       bean with name 'entityManagerFactory'defined in ServletContext resource
       [/WEB-INF/applicationContext.xml]: Invocation of init method failed;
       nested exception is java.lang.NoSuchMethodError:
       javax.persistence.spi.PersistenceUnitInfo.getSharedCacheMode()Ljavax/persistence/
       SharedCacheMode;
    Caused By: java.lang.NoSuchMethodError:
    javax.persistence.spi.PersistenceUnitInfo.getSharedCacheMode()
    Ljavax/persistence /SharedCacheMode;    at
    org.hibernate.ejb.util.LogHelper.logPersistenceUnitInfo(LogHelper.java:38)  at
    org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:525)
    at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)     at  org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManager I have the following in applicationContext.xml
    <beans xmlns="http://www.springframework.org/schema/beans"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tx="http://www.springframework.org/schema/tx"
        xmlns:context="http://www.springframework.org/schema/context"
        xsi:schemaLocation="http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
    http://www.springframework.org/schema/tx
    http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
    http://www.springframework.org/schema/context
    http://www.springframework.org/schema/context/spring-context-3.0.xsd">     
        <context:component-scan base-package="net.test" />
        <!-- Data Source Declaration -->
        <bean id="DataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource"
            destroy-method="close">
            <property name="driverClass" value="oracle.jdbc" />
            <property name="jdbcUrl" value="jdbc:oracle:thin:@server:1521:DB" />
            <property name="user" value="scott" />
            <property name="password" value="tiger" />
            <property name="maxPoolSize" value="10" />
            <property name="maxStatements" value="0" />
            <property name="minPoolSize" value="5" />
        </bean>
        <bean
            class="org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor" />
        <!-- JPA Entity Manager Factory -->
        <bean id="entityManagerFactory"
            class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
            <property name="dataSource" ref="DataSource" />
            <property name="packagesToScan" value="net.test.entity" />
            <property name="jpaVendorAdapter">
                <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter">
                    <property name="showSql" value="true" />
                    <property name="generateDdl" value="false" />
                    <property name="databasePlatform" value="${jdbc.dialectClass}" />
                </bean>
            </property>
        </bean>
        <bean id="defaultLobHandler" class="org.springframework.jdbc.support.lob.DefaultLobHandler" />
        <!-- Session Factory Declaration -->
        <bean id="SessionFactory"
            class="org.springframework.orm.hibernate4.LocalSessionFactoryBean">
            <property name="dataSource" ref="DataSource" />
            <property name="annotatedClasses">
                <list>
                    <value>net.test.entity.Department</value>
                    <value>net.test.entity.Employees</value>
                </list>
            </property>
            <property name="hibernateProperties">
                <props>
                    <prop key="hibernate.dialect">org.hibernate.dialect.Oracle10gDialect</prop>
                    <prop key="hibernate.show_sql">true</prop>
                    <prop key="hibernate.query.factory_class">org.hibernate.hql.internal.classic.ClassicQueryTranslatorFactory
                    </prop>
                </props>
            </property>
        </bean>
        <!-- Enable the configuration of transactional behavior based on annotations -->
        <tx:annotation-driven transaction-manager="txManager" />
        <tx:annotation-driven transaction-manager="transactionManager" />
        <!-- Transaction Config -->
        <bean id="txManager"
            class="org.springframework.orm.hibernate4.HibernateTransactionManager">
            <property name="sessionFactory" ref="SessionFactory" />
        </bean>
        <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
            <property name="entityManagerFactory" ref="entityManagerFactory" />
        </bean>
        <context:annotation-config />   
        <bean id="hibernateStatisticsMBean" class="org.hibernate.jmx.StatisticsService">
            <property name="statisticsEnabled" value="true" />
            <property name="sessionFactory" value="#{entityManagerFactory.sessionFactory}" />
        </bean>
        <bean name="ehCacheManagerMBean"
            class="org.springframework.cache.ehcache.EhCacheManagerFactoryBean" />
        <bean id="mbeanServer" class="org.springframework.jmx.support.MBeanServerFactoryBean">
            <property name="locateExistingServerIfPossible" value="true" />
        </bean>   
        <bean id="jmxExporter" class="org.springframework.jmx.export.MBeanExporter"
            lazy-init="false">
            <property name="server" ref="mbeanServer" />
            <property name="registrationBehaviorName" value="REGISTRATION_REPLACE_EXISTING" />
            <property name="beans">
                <map>
                    <entry key="SpringBeans:name=hibernateStatisticsMBean"
                        value-ref="hibernateStatisticsMBean" />
                    <entry key="SpringBeans:name=ehCacheManagerMBean" value-ref="ehCacheManagerMBean" />
                </map>
            </property>
        </bean>
    </beans>
    pom.xml
    <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
              http://maven.apache.org/maven-v4_0_0.xsd">
        <modelVersion>4.0.0</modelVersion>
        <groupId>net.test</groupId>
        <artifactId>myappp</artifactId>
        <packaging>war</packaging>
        <version>1.0-SNAPSHOT</version>
        <name>myappp</name>
        <url>http://maven.apache.org</url>
        <repositories>
            <repository>
                <id>prime-repo</id>
                <name>PrimeFaces Maven Repository</name>
                <url>http://repository.primefaces.org</url>
                <layout>default</layout>
            </repository>
        </repositories>
        <properties>
            <spring.version>3.1.1.RELEASE</spring.version>
        </properties>
        <dependencies>
            <!-- Spring 3 dependencies -->
            <dependency>
                <groupId>org.springframework</groupId>
                <artifactId>spring-core</artifactId>
                <version>${spring.version}</version>
            </dependency>
            <dependency>
                <groupId>org.springframework</groupId>
                <artifactId>spring-context</artifactId>
                <version>${spring.version}</version>
            </dependency>
            <dependency>
                <groupId>org.springframework</groupId>
                <artifactId>spring-web</artifactId>
                <version>${spring.version}</version>
            </dependency>
            <dependency>
                <groupId>org.springframework</groupId>
                <artifactId>spring-tx</artifactId>
                <version>${spring.version}</version>
            </dependency>
            <dependency>
                <groupId>org.springframework</groupId>
                <artifactId>spring-orm</artifactId>
                <version>${spring.version}</version>
            </dependency>
            <dependency>
                <groupId>org.springframework</groupId>
                <artifactId>spring-test</artifactId>
                <version>${spring.version}</version>
            </dependency>
            <!-- JSF library -->
            <dependency>
                <groupId>com.sun.faces</groupId>
                <artifactId>jsf-api</artifactId>
                <version>2.1.6</version>
            </dependency>
            <dependency>
                <groupId>com.sun.faces</groupId>
                <artifactId>jsf-impl</artifactId>
                <version>2.1.6</version>
            </dependency>
            <dependency>
                <groupId>javax.servlet</groupId>
                <artifactId>jstl</artifactId>
                <version>1.2</version>
            </dependency>
            <!-- Primefaces library -->
            <dependency>
                <groupId>org.primefaces</groupId>
                <artifactId>primefaces</artifactId>
                <version>3.4.2</version>
            </dependency>
            <dependency>
                <groupId>org.primefaces.themes</groupId>
                <artifactId>afterwork</artifactId>
                <version>1.0.8</version>
            </dependency>
            <!-- Hibernate library -->
            <dependency>
                <groupId>org.hibernate</groupId>
                <artifactId>hibernate-core</artifactId>
                <version>4.1.0.Final</version>
            </dependency>
            <dependency>
                <groupId>javassist</groupId>
                <artifactId>javassist</artifactId>
                <version>3.12.1.GA</version>
            </dependency>
            <dependency>
                <groupId>javax.inject</groupId>
                <artifactId>javax.inject</artifactId>
                <version>1</version>
            </dependency>
            <!-- Oracle Java Connector library -->
            <dependency>
                <groupId>com.oracle</groupId>
                <artifactId>ojdbc6</artifactId>
                <version>11.2.0.3</version>
            </dependency>
            <dependency>
                <groupId>c3p0</groupId>
                <artifactId>c3p0</artifactId>
                <version>0.9.1.2</version>
            </dependency>
            <!-- Log4j library -->
            <dependency>
                <groupId>log4j</groupId>
                <artifactId>log4j</artifactId>
                <version>1.2.16</version>
            </dependency>
            <dependency>
                <groupId>org.testng</groupId>
                <artifactId>testng</artifactId>
                <version>6.4</version>
            </dependency>
            <dependency>
                <groupId>org.hibernate</groupId>
                <artifactId>hibernate-jpamodelgen</artifactId>
                <version>1.2.0.Final</version>
            </dependency>
            <dependency>
                <groupId>org.hibernate</groupId>
                <artifactId>hibernate-entitymanager</artifactId>
                <version>4.1.0.Final</version>
            </dependency>
            <dependency>
                <groupId>org.hibernate.javax.persistence</groupId>
                <artifactId>hibernate-jpa-2.0-api</artifactId>
                <version>1.0.1.Final</version>
            </dependency>
            <dependency>
        <groupId>org.apache.myfaces.extensions.cdi.core</groupId>
        <artifactId>myfaces-extcdi-core-api</artifactId>
        <version>1.0.5</version>
        <scope>compile</scope>
    </dependency>
            <dependency>
                <groupId>org.hibernate</groupId>
                <artifactId>hibernate-ehcache</artifactId>
                <version>4.0.1.Final</version>
            </dependency>      
        </dependencies>
        <build>
            <resources>
                <resource>
                    <directory>src/main/resources</directory>
                </resource>
            </resources>
            <plugins>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-compiler-plugin</artifactId>             
                    <configuration>
                        <source>1.6</source>
                        <target>1.6</target>
                        <compilerArgument>-proc:none</compilerArgument>
                    </configuration>
                </plugin>
                <plugin>
                    <groupId>org.bsc.maven</groupId>
                    <artifactId>maven-processor-plugin</artifactId>
                    <version>2.0.6</version>
                    <executions>
                        <execution>
                            <id>process</id>
                            <goals>
                                <goal>process</goal>
                            </goals>
                            <phase>generate-sources</phase>
                            <configuration>
                                <!-- source output directory -->
                                <outputDirectory>target/metamodel</outputDirectory>
                            </configuration>
                        </execution>
                    </executions>
                </plugin>
            </plugins>
        </build>
    </project>In Weblogic 10.3.6 I have enabled JPA2 support by adding the following in commEnv.cmd
    @rem Enable JPA 2.0 functionality on WebLogic Server
    set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.1.0.0_2-0.jar;
    %BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-1.jarApplication which works on WLS 10.3.6 is http://download.oracle.com/otn/nt/middleware/11g/wls/1036/wls1036_dev.zip and the one which is not working is
    http://download.oracle.com/otn/nt/middleware/11g/wls/1036/wls1036_win32.exe.
    How can I resolve these errors and exceptions? Any help is highly appreciable.
    Thanks

    Looks like you might have a spelling error in your spring config, or are trying to set a read-only property. BdasInterfaceManagerImpl has been configured as having a method called setBdasInterfaceJdbcDao() : does it?
    By the way, we now know that you're writing code for JP Morgan - there's a slight risk that this could bite you in the @ss at some point (there are some malicious people around) you might want to take that into consideration next time!

  • SP2-0611: Error enabling STATISTICS report

    Hai
    I created table test2 with 20,000 records,and trying to set autotrace on in order to get statistics ,i got the below error.
    SQL> SET AUTOTRACE ON
    ERROR:
    ORA-24315: illegal attribute type
    SP2-0619: Error while connecting
    SP2-0611: Error enabling STATISTICS report
    Any idea about this
    Regards
    mohan

    SP2-0619 Error while connecting
    Cause: An error occurred while AUTOTRACE attempted to make a second connection to the database instance.
    Action: Check that the database limit on number of active sessions has not been exceeded.

  • Conversion Error: I/O error while communicating with native process

    Hi,
    I am trying to use Oracle Outside In Technology Image Export for conversion of images. I am trying to run the example ExportTest that comes with the downloaded SDK.
    I get the below error while running the ExportTest example.
    Conversion Error: I/O error while communicating with native process .
    Am I missing any settings?
    Please guide to the right forum if this is not the one for posting queries on Oracle Outside In Technology Image Export.
    Thank you.

    Hi Revanth,
    I am using Image Export 8.3.7 and I am trying to run the java class "ExportTest" that is in the location sdk\samplecode\ExJava\Examples\ExportTest\src of the download.
    My input folder has one jpg - puzzle.jpg (this is just a simple jpg), I am trying to convert it to TIFF. ExportTest.java uses the classes in Export.jar . Export.jar is located in the sdk\samplecode\ExJava\Examples\ExportTest . You can see source files of the Export.jar at location sdk\samplecode\ExJava\Java API\src of the download. I am running the 'ExportTest' by providing the arguments (input folder, output folder and ix.cfg - this file comes with the download). So now when I run this class I was getting the error I mentioned in this post. Inorder to find more details about the error I modified the 'Export.java' (at sdk\samplecode\ExJava\Java API\src\com\outsideinsdk) just to printStackTrace when the exception occurs and rebuilt the 'Export.jar' and ran the 'ExportTest.java'.
    And below is the stack trace that I got :
    java.io.IOException: CreateProcess: nullexporter.exe "inputpath_u=AGkAbgBwAHUAdA
    BcAHAAdQB6AHoAbABlAC4ASgBQAEc=" "outputpath_u=AG8AdQBwAHUAdABcAHAAdQB6AHoAbABlAC
    4ASgBQAEcALgBUAEkARgBG" "outputid=FI_TIFF" "fallbackformat=FI_TEXT" "tiffcolorsp
    ace=24BitRGB" "preferoitrendering=false" "tiffcompression=Packbits" "mapbuffersi
    ze=8192" "defaultprintfontheight=20" "graphicwidthlimit=0" "reordermethod=off" "
    unmappablechar=0x002A" "timezone=0" "graphicheightlimit=0" "defaultmarginleft=14
    40" "ssshowheadings=false" "quickthumbnail=false" "graphicoutputdpi=0" "ssdirect
    ion=AcrossandDown" "defaultmarginbottom=1440" "ssshowgridlines=false" "dbshowhea
    dings=false" "readbuffersize=2" "whattoexport=all" "graphicsizelimit=0" "imagewa
    termarkopacity=0" "blue=-1" "handlenewfileinfo=no" "outputid=FI_TIFF" "lzwcompre
    ssion=enabled" "usedocpagesettings=true" "defaultmarginright=1440" "numberofstat
    callbacks=0" "dbfittopage=NoScaling" "tempbuffersize=2048" "pdffilterreorderbidi
    =no" "imagecropping=nocropping" "defaultmargintop=1440" "documentmemorymode=larg
    e" "m?
    at java.lang.Win32Process.create(Native Method)
    at java.lang.Win32Process.<init>(Win32Process.java:66)
    at java.lang.Runtime.execInternal(Native Method)
    at java.lang.Runtime.exec(Runtime.java:566)
    at java.lang.Runtime.exec(Runtime.java:491)
    at java.lang.Runtime.exec(Runtime.java:457)
    at com.outsideinsdk.Export.convert(Export.java:262)
    at com.outsideinsdk.ExportTest.convert(ExportTest.java:142)
    at com.outsideinsdk.ExportTest.main(ExportTest.java:214)
    hope this helps to find the problem.
    Thank you

  • Can't Enable Journaling

    So, Im trying to Install windows Vista on my new Macbook pro, When I attempted to install it through bootcamp it said I need to "Enable Journaling" However when I open my Disc Utility I can't click on the option to enable journaling. Its unselectable.
    Quick question, would enabling journaling cause me to loose data?

    Hi nonfikshun,
    1/ You should post what Mac you're using - will help with helping you...
    2/ Windows 6 doesn't exist - you meant win 7?
    3/ Did you just try to restart the computer? (and see if it might work) sometime it gets fixed by itself...
    4/ Try to start from (Mac OS) install DVD, choose your language, go to Menu Bar (on top), find/choose 'Disk Utilities', choose Mac HD, 'Repair Disk', 'Repair disk Permissions'.
    (You can also repair your windows partition with 'Disk Utilities' - I had done it MANY times {without any problems afterwards} - but it's NOT generally recomended).

  • Patchdownloader: ERROR: DownloadContentFiles() failed with hr=0x800701f6

    Hi,
    SCCM 2012 R2 updates work fine. Only when I create an automatic deployment rule for Endpoint Protection definition updates, it has errors in the patchdownloader.log.
    I already used the upddwnlodcfg.exe /bypassproxy but that didn't work (should I restart?).
    Folders are there but content is not.
    Downloading content for ContentID = 16784900,  FileName = AM_Delta_Patch_1.165.995.0.exe.    Software Updates Patch Downloader    1/2/2014 12:11:17 PM    3308 (0x0CEC)
    HttpSendRequest failed 502    Software Updates Patch Downloader    1/2/2014 12:11:17 PM    5048 (0x13B8)
    "Bypass proxy server for local addresses" setting may be disabled    Software Updates Patch Downloader    1/2/2014 12:11:17 PM    5048 (0x13B8)
    To enable the setting use: UpdDwnldCfg.exe /ByPassProxy    Software Updates Patch Downloader    1/2/2014 12:11:17 PM    5048 (0x13B8)
    Download http://wsus.ds.download.windowsupdate.com/msdownload/update/software/defu/2014/01/am_delta_patch_1.165.995.0_28c14f6ef7d54eb33f4be5b2c4f1a932fd2c6e71.exe to C:\windows\TEMP\CAB56A8.tmp returns 502    Software Updates Patch Downloader  
     1/2/2014 12:11:17 PM    5048 (0x13B8)
    ERROR: DownloadContentFiles() failed with hr=0x800701f6    Software Updates Patch Downloader    1/2/2014 12:11:17 PM    3308 (0x0CEC)
    Please advise.
    J.
    Jan Hoedt
    Note: I CAN download the file manually using Internet Explorer: "http://wsus.ds.download.windowsupdate.com/msdownload/update/software/defu/2014/01/am_delta_patch_1.165.995.0_28c14f6ef7d54eb33f4be5b2c4f1a932fd2c6e71.exe"

    HTTP status 502 – the server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
    http://msdn2.microsoft.com/en-us/library/aa387293.aspx
    When I implement a software updates/endpoint protection solution, I always configure the proxy to "whitelist" traffic between my site server and the MS updates sites. Whitelist = no scanning & no filtering.
    In this way I can avoid these kinds of problems.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Won't install on clean OS X: Error enabling server management.

    Hi All,
    I'm getting seriously fed up of Server.app.
    I previously had it installed on my Mac Mini, but due to various reasons did a clean install of OS X. On boot, the only app I have installed so far is Parallels. My second app is Server.app, well it would be but it fails when trying to configure it:
    Error enabling server management.
    A problem was detected with Server. Please redownload Server from the App Store.
    Obviously I did do this, to no avail. I also copied over a known working version of Server.app from another machine and got the same message. I mean what gives? Why isn't it even letting me install it?!
    Thanks

    Not only do I have that folder already in existence, but I have a plist file located there that is for the server.app I'm sure.
    com.apple.serverd.plist
    I have tried deleting this and relaunching to no avail.
    Still stuck with the error.
    And terminal doesn't seem to agree with that command.
    Says "-al" isn't a valid command?
    Console is giving me a tiny bit of info that might help...
    3/21/13 12:40:19.800 PM Server[8383]: Could not find image named 'XSLock'.
    3/21/13 12:40:34.388 PM launchdadd[8388]: Could not open /Applications/Server.app/Contents/Library/LaunchServices/com.apple.serverd (open() error 2: No such file or directory)
    3/21/13 12:40:34.388 PM launchdadd[8388]: Could not close file descriptor for old temporary tool. Continuing on. We will be left with a dangling reference to the file, and this will prevent it from being cleaned up automatically by the system until launchdadd is either relaunched or the system is rebooted. (close() error 9: Bad file descriptor)
    3/21/13 12:40:34.389 PM launchdadd[8388]: FAILURE: Could not create a request for tool at path /Applications/Server.app/Contents/Library/LaunchServices/com.apple.serverd
    3/21/13 12:40:34.390 PM Server[8383]: ERROR: failed to enable serverd: Error Domain=kSMErrorDomainFramework Code=5 "The operation couldn’t be completed. (kSMErrorDomainFramework error 5 - The tool at the specified path is not valid.)" UserInfo=0x7fba6c0bc270 {NSDescription=The tool at the specified path is not valid.}
    Not sure where to go from here.

  • OAM Error : Enable JavaScript to use OAM Server.

    Hi Friends,
    I see following script when I try to access a resource protected using OAM in Mozillla and Safari browsers.
    <body onLoad="document.myForm.submit()"><noscript><p>JavaScript is required. Enable JavaScript to use OAM Server.</p></noscript>The same configuration works with IE.
    Could you please help me understand if any patch need to be applied to OAM or if I am missing something in the configurations?
    Note: We are using OAM 11.1.1.5.0 to protect webcenter 11.1.1.5.0.
    Thanks,
    Sachin
    Edited by: 873687 on Feb 3, 2012 2:54 AM

    Hi,
    We had a customer that ran into the same exact issue and symptoms described in this thread. The issues occurred after some upgrades were made to browsers and java. Our customer was using Forms/Reports 11.1.2.1 (11gR2), OAM/OID (11.1.1.5) and mod_osso for the Forms-OAM integration.
    The issue was caused by a bug in OAM 11.1.1.5. The problem is when OAM authentication occurs, it does some web directs within it's internal java code. The HTML/JavaScript it tries to execute fails only in Chrome/Firefox. Applying the patch, supposedly fixes that faulty HTML/Javascript generated by OAM.
    Oracle Support documents on the issue and bug:
    - There is a Oracle Support article describing the issue: 1447194.1
    - Oracle Support Bug Number: 13254371
    To fix the issue:
    - Apply OAM Patch: 13115859. Its a generic patch that will work on any environment type.
    - If you use WebGates for your application, check out patch 13453929
    I wrote an article on how to install the patch: http://pitss.com/us/2013/04/04/oam-error-enable-javascript-to-use-oam-server/
    I hope this helps!
    Thank you,
    Gavin

Maybe you are looking for

  • Basic Difference in Query Designer

    Hi All, Can anybody let me know the difference between Characteristic Restriction and "Default Values" tabs under the Filter section in Query Designer. I am able to restrict the same on both these tabs.I am able to use variables on both side even con

  • CREATING A FORM UTILIZING MULTIPLE TABLES

    I'd like to know if it's feasable to create a form using multiple tables and if so, how? Thanx

  • In Calendar, deleting one event in a recurring event deletes everything...

    When I delete one event in a recurring event, calendar deletes the entire event, both past and future. I am clicking the option "delete only this event," and the rest of the recurring event doesn't disappear on my iphone 4 (linked through iCloud). Th

  • Message in Develop "The File Could Not be Opened"

    My photos are in an external 500 gig hard drive. I am using a new iMac. In Lightroom when I go to the develop module and select an image I get a message saying The File Could Not Be Opened. I can not do any editing. I can open photos from the hard dr

  • J2ee example problem

    Hi,           I am trying the sample hello1 example from JavaEETutorial. I have deployed the war in weblogic 9.2           After enter the name and click on submit, the values does not seem to be populated for ${param.username}.           The respons