Due problemi

Mi confesso subito, sono un vecchio contadino inesperto.
Ho pagato l'abbonamento per ADOBE CREATE PDF ma ho due problemi:
Quando creo un documento di una pagina tutto ok, ma quando poi lo apro non è più di una pagina infatti si porta dietro ( per la verità avanti ) una seconda pagina di un vecchio documento, sempre lo stesso,  dell'anno 2008.
Questo sempre su tutti i documenti creati , hanno una prima pagina eguale e non voluta e non richiesta, poi la seconda è il documento creato e voluto.
Secondo aprendo un allegato PDF ad una e-mail tutto ok.
Quando poi la stampo per conservarta o metterla in contabilità l'intestazione e qualche altra riga viene stampata come si vede a video, ma il contenuto è stampato in caratteri che non saprei come definire, non greci, nè russi, nè sumeri o arabi.
Come posso annullare questo problema?
Grazie se mi potete aiutare, tenere presente che non èarlo inglese, ma francese e tedesco , logicamnete italia.
Il vecchi contadino, Piero

Temo sia morto.
Sarebbe stato meglio non accenderlo.
Molti consigliano di metterlo per diversi giorni in un vaso con riso (per essicarlo).

Similar Messages

  • Balance due problem

    Hi all ..
    I need ur help .. on
    PROBLEM
    Problem is ...
    1. Customer purchase(A/R invoice) an item with the cost 2080..rs with qty. 1
    2.we received the partial payment against this invoice for Rs 2000.(balance due 80 Rs)
    3. Then i release that ... the payment need to be for Rs 2000.
    4.Now the problem arise ..if i make credit memo for Rs 80 then my inventory increase ...
    and if i pass the general entry then the invoice will always be open ...... and if i closed it manually then it shows with the balance due with 80 Rs ..which effect on aging report ..
    Wht should i need to do for that ... and how can we manage this scenario ..
    Thanks in advance

    Hello Arreba...
    Another alternative...
    You can create a SERVICE type AR credit memo and for the GL account put in the Sales Revenue Account...this might not a doubtful debt - it is an actual reduction in sales revenue...
    Most customers would not like to see a JE in their postings and this way makes it easier for auditors to follow....
    You can then do the reconciliatioin so it is INVOICE on CREDIT MEMO, not JE on Invoice - much nicer to see...
    Take Care - Zal

  • Teaming 2.1 Tasks Due problem

    The "Tasks due" tab in our workspaces shows completed tasks. If the "Within 2 Weeks" radio button is active, it shows the completed tasks even id they are older than 2 weeks. For example, this shows up in today's Tasks due tab in my workspace with the "Within 2 Weeks" or the "Anytime" buttons active:
    * Migrate TestWeb
    Priority: Medium
    Status: Completed
    Due Date: Jan 1, 2010
    Personal Projects // Toney Cassel
    Is there a setting that I can change this behavior?
    Thanks,
    Toney Cassel.

    There is currently no way to change this. There is an enhancement
    request against Teaming (Bugzilla bug 554254
    [https://bugzilla.novell.com/show_bug.cgi?id=554254]) requesting the
    functionality that you're asking for.
    MacWiz.
    On 2/22/10 11:16 AM, toneyc wrote:
    >
    > The "Tasks due" tab in our workspaces shows completed tasks. If the
    > "Within 2 Weeks" radio button is active, it shows the completed tasks
    > even id they are older than 2 weeks. For example, this shows up in
    > today's Tasks due tab in my workspace with the "Within 2 Weeks" or the
    > "Anytime" buttons active:
    >
    > * Migrate TestWeb
    > Priority: Medium
    > Status: Completed
    > Due Date: Jan 1, 2010
    > Personal Projects // Toney Cassel
    >
    > Is there a setting that I can change this behavior?
    >
    > Thanks,
    > Toney Cassel.
    >
    >

  • Crash applicazioni e problemi spazio

    Ciao!
    Ho bisogno del vostro aiuto!
    Ho un iphone 4s e ultimamente mi sta creando diversi problemi!
    - per prima cosa le applicazioni, per l'esattezza whatsapp mi si chiudono un secondo dopo averle aperte e inoltre non ricevo i messaggi!
    - per seconda cosa mi arriva spesso la segnalazione di archivio pieno. Ho eliminato tutte le immagini del rullino fotografico (530) pensando fosse quello che portasse via molto spazio. Il problema non l'ho risolto, anzi mi continua ad arrivare la segnalazione che non posso più scattare foto per mancanza di spazio nonostante l'album del rullino sia vuoto! di musica non ho nemmeno un file perchè le tengo tutte sull'pod e di applicazioni ne ho solo una decina.Come posso fare?
    Confido in voi per un aiuto, non so più che fare per rimediare a questi due problemi!
    Grazie!

    Hello,
    Have you tried clearing the temporary file folders on the computer?  Perhaps a program is creating temporary files and not deleting them when it is done with them.
    Regards,
    Aryeh Goretsky
    I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
    S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
      Deutsche Community   Comunidad en Español Русскоязычное Сообщество

  • Ipod touch 4G with phone 3G accessories

    Hi, I used to have an iphone 3G (still have the hardware, but due problems with AT&T I am not longer an iphone user). Now, I just bought an ipod touch 32GB 4G for my niece as a christmas present and I am wondering if I can give her all the accessories I have for my iphone 3G (data cable x 2, fm transmitter, car charger, alarm clock with docking station) for her to use them with her touch. I know the easier solution would be to try them out, but we don't live close to each other, and I will be shipping the ipod to her before christmas and I don't want to open her gift.
    Does anybody here has try iphone 3G compatible accessories with the new ipod touch? Do they work? is there any reason why they would not? I know some people are posting older accessories not working with the newer hardware, but I remember having a similar problem going from the first iphone to the 3G forcing me to replace most of them. Not sure if these people are referring to those older accessories and not the ones that are iphone 3G compatible
    thanks in advance.

    it should work, my iphone 3g accesories work with my new ipod touch 4g

  • JAVA_HOME does not point to the JDK Error.

    Hello Friends,
                         I unable build my local DC due problem with JAVA_HOME Parameter.
    I am using j2sdk1.4.2_08. Is this a problem. (JDK Version).
    I have checked the file C:\usr\sap\J2E\JC00\work\dev_server0
    I got the following error when try to build DC.
    Ant build finished with ERRORS
    Unable to find a javac compiler;
    com.sun.tools.javac.Main is not on the classpath.
    Perhaps JAVA_HOME does not point to the JDK
    Error: Build stopped due to an error: Unable to find a javac compiler;
    com.sun.tools.javac.Main is not on the classpath.
    Perhaps JAVA_HOME does not point to the JDK
    Build plugin finished at 2007-09-09 16:21:38 GMT+08:00 (SGT)
    Total build plugin runtime: 5.453 seconds
    Build finished with ERROR
    Cheers.. Sam

    Please find below is C:\usr\sap\J2E\JC00\work\dev_server0 content
    trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name   : ID4467550
    pid         : 5648
    system name : J2E
    system nr.  : 00
    started at  : Tue Sep 04 10:03:42 2007
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
        arg[02] : -DSAPINFO=J2E_00_server
        arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    [Thr 4672] Tue Sep 04 10:03:42 2007
    [Thr 4672] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
    [Thr 4672] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
    [Thr 4672] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    [Thr 4672] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host    : senthil
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : senthil
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID4467500  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID4467550  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    [Thr 4672] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4672] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 2992] WaitSyncSemThread: Thread 2992 started as semaphore monitor thread.
    [Thr 3280] JLaunchRequestFunc: Thread 3280 started as listener thread for np messages.
    [Thr 4672] Tue Sep 04 10:03:43 2007
    [Thr 4672] INFO: Invalid property value [JLaunchParameters/]
    [Thr 4672] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID4467550]
    -> node name       : server0
    -> node type       : server
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.engine.boot.Start
    -> parameters      :
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 4672] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4932] JLaunchIStartFunc: Thread 4932 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: -Djava.security.policy=./java.policy
    -> arg[  3]: -Djava.security.egd=file:/dev/urandom
    -> arg[  4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  7]: -Djco.jarm=1
    -> arg[  8]: -Dsun.io.useCanonCaches=false
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
    -> arg[ 12]: -Djava.awt.headless=true
    -> arg[ 13]: -XX:NewSize=85m
    -> arg[ 14]: -XX:MaxNewSize=85m
    -> arg[ 15]: -XX:MaxPermSize=192m
    -> arg[ 16]: -XX:PermSize=192m
    -> arg[ 17]: -XX:+DisableExplicitGC
    -> arg[ 18]: -XX:+UseParNewGC
    -> arg[ 19]: -XX:+PrintGCDetails
    -> arg[ 20]: -XX:+PrintGCTimeStamps
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 24]: -verbose:gc
    -> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
    -> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
    -> arg[ 29]: -Dmemory.manager=512M
    -> arg[ 30]: -Xmx512M
    -> arg[ 31]: -Xms512M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=5648
    -> arg[ 35]: -Djstartup.ownHardwareId=Z2123283434
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=yes
    -> arg[ 38]: -DSAPINFO=J2E_00_server
    -> arg[ 39]: -DSAPSTARTUP=1
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=J2E
    -> arg[ 42]: -DSAPMYNAME=senthil_J2E_00
    -> arg[ 43]: -DSAPDBHOST=
    -> arg[ 44]: -Dj2ee.dbhost=senthil
    [Thr 4932] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 5412] Tue Sep 04 10:03:50 2007
    [Thr 5412] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 5412] JLaunchISetClusterId: set cluster id 4467550
    [Thr 5412] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 5412] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 5184] Tue Sep 04 10:04:23 2007
    [Thr 5184] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 5184] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
    [Thr 5412] Tue Sep 04 10:04:49 2007
    [Thr 5412] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 3120] Tue Sep 04 10:04:50 2007
    [Thr 3120] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 336] Tue Sep 04 10:09:06 2007
    [Thr 336] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
    [Thr 2592] Tue Sep 04 12:34:36 2007
    [Thr 2592] JLaunchIExitJava: exit hook is called (rc=-337)
    [Thr 2592] JLaunchCloseProgram: good bye (exitcode=-337)
    trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name   : ID4467550
    pid         : 1432
    system name : J2E
    system nr.  : 00
    started at  : Tue Sep 04 12:34:40 2007
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
        arg[02] : -DSAPINFO=J2E_00_server
        arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    [Thr 5984] Tue Sep 04 12:34:40 2007
    [Thr 5984] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
    [Thr 5984] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
    [Thr 5984] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    [Thr 5984] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host    : senthil
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : senthil
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID4467500  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID4467550  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    [Thr 5984] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5984] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 5096] JLaunchRequestFunc: Thread 5096 started as listener thread for np messages.
    [Thr 1600] WaitSyncSemThread: Thread 1600 started as semaphore monitor thread.
    [Thr 5984] Tue Sep 04 12:34:41 2007
    [Thr 5984] INFO: Invalid property value [JLaunchParameters/]
    [Thr 5984] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID4467550]
    -> node name       : server0
    -> node type       : server
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.engine.boot.Start
    -> parameters      :
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 5984] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4812] JLaunchIStartFunc: Thread 4812 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: -Djava.security.policy=./java.policy
    -> arg[  3]: -Djava.security.egd=file:/dev/urandom
    -> arg[  4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  7]: -Djco.jarm=1
    -> arg[  8]: -Dsun.io.useCanonCaches=false
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
    -> arg[ 12]: -Djava.awt.headless=true
    -> arg[ 13]: -XX:NewSize=85m
    -> arg[ 14]: -XX:MaxNewSize=85m
    -> arg[ 15]: -XX:MaxPermSize=192m
    -> arg[ 16]: -XX:PermSize=192m
    -> arg[ 17]: -XX:+DisableExplicitGC
    -> arg[ 18]: -XX:+UseParNewGC
    -> arg[ 19]: -XX:+PrintGCDetails
    -> arg[ 20]: -XX:+PrintGCTimeStamps
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 24]: -verbose:gc
    -> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
    -> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
    -> arg[ 29]: -Dmemory.manager=512M
    -> arg[ 30]: -Xmx512M
    -> arg[ 31]: -Xms512M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=1432
    -> arg[ 35]: -Djstartup.ownHardwareId=Z2123283434
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=yes
    -> arg[ 38]: -DSAPINFO=J2E_00_server
    -> arg[ 39]: -DSAPSTARTUP=1
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=J2E
    -> arg[ 42]: -DSAPMYNAME=senthil_J2E_00
    -> arg[ 43]: -DSAPDBHOST=
    -> arg[ 44]: -Dj2ee.dbhost=senthil
    [Thr 4812] Tue Sep 04 12:34:42 2007
    [Thr 4812] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 4216] Tue Sep 04 12:35:05 2007
    [Thr 4216] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4216] JLaunchISetClusterId: set cluster id 4467550
    [Thr 4216] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4216] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 5892] Tue Sep 04 12:35:49 2007
    [Thr 5892] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 5892] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
    [Thr 4216] Tue Sep 04 12:36:14 2007
    [Thr 4216] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 516] Tue Sep 04 12:36:16 2007
    [Thr 516] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 332] Tue Sep 04 12:41:00 2007
    [Thr 332] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
    [Thr 5096] Tue Sep 04 20:53:33 2007
    [Thr 5096] JLaunchRequestFunc: receive command:17, argument:0 from pid:1152
    [Thr 5096] JLaunchIShutdownInvoke: set shutdown interval (stop:1188910413/end:1188910533/TO:120)
    [Thr 5096] JLaunchProcessCommand: Invoke VM Shutdown
    [Thr 5096] JHVM_FrameworkShutdownDirect: invoke direct shutdown
    [Thr 4196] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
    [Thr 4196] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
    [Thr 4196] Tue Sep 04 20:53:58 2007
    [Thr 4196] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
    [Thr 4988] Tue Sep 04 20:53:59 2007
    [Thr 4988] JLaunchIExitJava: exit hook is called (rc=0)
    [Thr 4988] JLaunchCloseProgram: good bye (exitcode=0)
    trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name   : ID4467550
    pid         : 272
    system name : J2E
    system nr.  : 00
    started at  : Tue Sep 04 20:54:04 2007
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
        arg[02] : -DSAPINFO=J2E_00_server
        arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    [Thr 4792] Tue Sep 04 20:54:04 2007
    [Thr 4792] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
    [Thr 4792] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
    [Thr 4792] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    [Thr 4792] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host    : senthil
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : senthil
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID4467500  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID4467550  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    [Thr 4792] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4792] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1072] JLaunchRequestFunc: Thread 1072 started as listener thread for np messages.
    [Thr 3240] WaitSyncSemThread: Thread 3240 started as semaphore monitor thread.
    [Thr 4792] Tue Sep 04 20:54:05 2007
    [Thr 4792] INFO: Invalid property value [JLaunchParameters/]
    [Thr 4792] JStartupIReadSection: debug mode is specified by program arguments
    [Thr 4792] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID4467550]
    -> node name       : server0
    -> node type       : server
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.engine.boot.Start
    -> parameters      :
    -> debuggable      : yes
    -> debug mode      : yes
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 4792] JLaunchISetDebugMode: set debug mode [yes]
    [Thr 2100] JLaunchIStartFunc: Thread 2100 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: -Djava.security.policy=./java.policy
    -> arg[  3]: -Djava.security.egd=file:/dev/urandom
    -> arg[  4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  7]: -Djco.jarm=1
    -> arg[  8]: -Dsun.io.useCanonCaches=false
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
    -> arg[ 12]: -Djava.awt.headless=true
    -> arg[ 13]: -XX:NewSize=85m
    -> arg[ 14]: -XX:MaxNewSize=85m
    -> arg[ 15]: -XX:MaxPermSize=192m
    -> arg[ 16]: -XX:PermSize=192m
    -> arg[ 17]: -XX:+DisableExplicitGC
    -> arg[ 18]: -XX:+UseParNewGC
    -> arg[ 19]: -XX:+PrintGCDetails
    -> arg[ 20]: -XX:+PrintGCTimeStamps
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 24]: -verbose:gc
    -> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
    -> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
    -> arg[ 29]: -Xdebug
    -> arg[ 30]: -Xnoagent
    -> arg[ 31]: -Djava.compiler=NONE
    -> arg[ 32]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50021
    -> arg[ 33]: -Dmemory.manager=512M
    -> arg[ 34]: -Xmx512M
    -> arg[ 35]: -Xms512M
    -> arg[ 36]: -DLoadBalanceRestricted=no
    -> arg[ 37]: -Djstartup.mode=JCONTROL
    -> arg[ 38]: -Djstartup.ownProcessId=272
    -> arg[ 39]: -Djstartup.ownHardwareId=Z2123283434
    -> arg[ 40]: -Djstartup.whoami=server
    -> arg[ 41]: -Djstartup.debuggable=yes
    -> arg[ 42]: -DSAPINFO=J2E_00_server
    -> arg[ 43]: -DSAPSTARTUP=1
    -> arg[ 44]: -DSAPSYSTEM=00
    -> arg[ 45]: -DSAPSYSTEMNAME=J2E
    -> arg[ 46]: -DSAPMYNAME=senthil_J2E_00
    -> arg[ 47]: -DSAPDBHOST=
    -> arg[ 48]: -Dj2ee.dbhost=senthil
    [Thr 2100] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 2588] Tue Sep 04 20:54:11 2007
    [Thr 2588] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 2588] JLaunchISetClusterId: set cluster id 4467550
    [Thr 2588] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 2588] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 3600] Tue Sep 04 20:54:52 2007
    [Thr 3600] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 3600] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
    [Thr 2588] Tue Sep 04 20:55:21 2007
    [Thr 2588] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 4848] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 5320] Tue Sep 04 21:01:07 2007
    [Thr 5320] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
    trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name   : ID4467550
    pid         : 5276
    system name : J2E
    system nr.  : 00
    started at  : Tue Sep 04 22:04:45 2007
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
        arg[02] : -DSAPINFO=J2E_00_server
        arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    [Thr 1532] Tue Sep 04 22:04:45 2007
    [Thr 1532] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
    [Thr 1532] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
    [Thr 1532] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    [Thr 1532] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host    : senthil
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : senthil
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID4467500  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID4467550  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    [Thr 1532] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 1532] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1636] JLaunchRequestFunc: Thread 1636 started as listener thread for np messages.
    [Thr 644] WaitSyncSemThread: Thread 644 started as semaphore monitor thread.
    [Thr 1532] Tue Sep 04 22:04:46 2007
    [Thr 1532] INFO: Invalid property value [JLaunchParameters/]
    [Thr 1532] JStartupIReadSection: debug mode is specified by program arguments
    [Thr 1532] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID4467550]
    -> node name       : server0
    -> node type       : server
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.engine.boot.Start
    -> parameters      :
    -> debuggable      : yes
    -> debug mode      : yes
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 1532] JLaunchISetDebugMode: set debug mode [yes]
    [Thr 5300] JLaunchIStartFunc: Thread 5300 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: -Djava.security.policy=./java.policy
    -> arg[  3]: -Djava.security.egd=file:/dev/urandom
    -> arg[  4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  7]: -Djco.jarm=1
    -> arg[  8]: -Dsun.io.useCanonCaches=false
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
    -> arg[ 12]: -Djava.awt.headless=true
    -> arg[ 13]: -XX:NewSize=85m
    -> arg[ 14]: -XX:MaxNewSize=85m
    -> arg[ 15]: -XX:MaxPermSize=192m
    -> arg[ 16]: -XX:PermSize=192m
    -> arg[ 17]: -XX:+DisableExplicitGC
    -> arg[ 18]: -XX:+UseParNewGC
    -> arg[ 19]: -XX:+PrintGCDetails
    -> arg[ 20]: -XX:+PrintGCTimeStamps
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 24]: -verbose:gc
    -> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
    -> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
    -> arg[ 29]: -Xdebug
    -> arg[ 30]: -Xnoagent
    -> arg[ 31]: -Djava.compiler=NONE
    -> arg[ 32]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50021
    -> arg[ 33]: -Dmemory.manager=512M
    -> arg[ 34]: -Xmx512M
    -> arg[ 35]: -Xms512M
    -> arg[ 36]: -DLoadBalanceRestricted=no
    -> arg[ 37]: -Djstartup.mode=JCONTROL
    -> arg[ 38]: -Djstartup.ownProcessId=5276
    -> arg[ 39]: -Djstartup.ownHardwareId=Z2123283434
    -> arg[ 40]: -Djstartup.whoami=server
    -> arg[ 41]: -Djstartup.debuggable=yes
    -> arg[ 42]: -DSAPINFO=J2E_00_server
    -> arg[ 43]: -DSAPSTARTUP=1
    -> arg[ 44]: -DSAPSYSTEM=00
    -> arg[ 45]: -DSAPSYSTEMNAME=J2E
    -> arg[ 46]: -DSAPMYNAME=senthil_J2E_00
    -> arg[ 47]: -DSAPDBHOST=
    -> arg[ 48]: -Dj2ee.dbhost=senthil
    [Thr 5300] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 2320] Tue Sep 04 22:04:55 2007
    [Thr 2320] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 2320] JLaunchISetClusterId: set cluster id 4467550
    [Thr 2320] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 2320] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 4712] Tue Sep 04 22:05:41 2007
    [Thr 4712] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 4712] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
    [Thr 2320] Tue Sep 04 22:06:47 2007
    [Thr 2320] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 6132] Tue Sep 04 22:06:48 2007
    [Thr 6132] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 2128] Tue Sep 04 22:13:14 2007
    [Thr 2128] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
    [Thr 5860] Wed Sep 05 21:49:01 2007
    [Thr 5860] JLaunchIExitJava: exit hook is called (rc=-335)
    [Thr 5860] JLaunchCloseProgram: good bye (exitcode=-335)
    trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name   : ID4467550
    pid         : 5224
    system name : J2E
    system nr.  : 00
    started at  : Wed Sep 05 21:49:06 2007
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
        arg[02] : -DSAPINFO=J2E_00_server
        arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    [Thr 5568] Wed Sep 05 21:49:06 2007
    [Thr 5568] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
    [Thr 5568] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
    [Thr 5568] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    [Thr 5568] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host    : senthil
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : senthil
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID4467500  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID4467550  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    [Thr 5568] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5568] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1716] JLaunchRequestFunc: Thread 1716 started as listener thread for np messages.
    [Thr 1928] WaitSyncSemThread: Thread 1928 started as semaphore monitor thread.
    [Thr 5568] INFO: Invalid property value [JLaunchParameters/]
    [Thr 5568] JStartupIReadSection: debug mode is specified by program arguments
    [Thr 5568] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID4467550]
    -> node name       : server0
    -> node type       : server
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.engine.boot.Start
    -> parameters      :
    -> debuggable      : yes
    -> debug mode      : yes
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 5568] JLaunchISetDebugMode: set debug mode [yes]
    [Thr 2500] JLaunchIStartFunc: Thread 2500 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: -Djava.security.policy=./java.policy
    -> arg[  3]: -Djava.security.egd=file:/dev/urandom
    -> arg[  4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  7]: -Djco.jarm=1
    -> arg[  8]: -Dsun.io.useCanonCaches=false
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
    -> arg[ 12]: -Djava.awt.headless=true
    -> arg[ 13]: -XX:NewSize=85m
    -> arg[ 14]: -XX:MaxNewSize=85m
    -> arg[ 15]: -XX:MaxPermSize=192m
    -> arg[ 16]: -XX:PermSize=192m
    -> arg[ 17]: -XX:+DisableExplicitGC
    -> arg[ 18]: -XX:+UseParNewGC
    -> arg[ 19]: -XX:+PrintGCDetails
    -> arg[ 20]: -XX:+PrintGCTimeStamps
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 24]: -verbose:gc
    -> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
    -> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
    -> arg[ 29]: -Xdebug
    -> arg[ 30]: -Xnoagent
    -> arg[ 31]: -Djava.compiler=NONE
    -> arg[ 32]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50021
    -> arg[ 33]: -Dmemory.manager=512M
    -> arg[ 34]: -Xmx512M
    -> arg[ 35]: -Xms512M
    -> arg[ 36]: -DLoadBalanceRestricted=no
    -> arg[ 37]: -Djstartup.mode=JCONTROL
    -> arg[ 38]: -Djstartup.ownProcessId=5224
    -> arg[ 39]: -Djstartup.ownHardwareId=Z2123283434
    -> arg[ 40]: -Djstartup.whoami=server
    -> arg[ 41]: -Djstartup.debuggable=yes
    -> arg[ 42]: -DSAPINFO=J2E_00_server
    -> arg[ 43]: -DSAPSTARTUP=1
    -> arg[ 44]: -DSAPSYSTEM=00
    -> arg[ 45]: -DSAPSYSTEMNAME=J2E
    -> arg[ 46]: -DSAPMYNAME=senthil_J2E_00
    -> arg[ 47]: -DSAPDBHOST=
    -> arg[ 48]: -Dj2ee.dbhost=senthil
    [Thr 2500] Wed Sep 05 21:49:07 2007
    [Thr 2500] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1148] Wed Sep 05 21:49:15 2007
    [Thr 1148] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1148] JLaunchISetClusterId: set cluster id 4467550
    [Thr 1148] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1148] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 6136] Wed Sep 05 21:50:06 2007
    [Thr 6136] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 6136] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
    [Thr 1148] Wed Sep 05 21:50:33 2007
    [Thr 1148] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 3344] Wed Sep 05 21:50:34 2007
    [Thr 3344] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 2620] Wed Sep 05 21:56:35 2007
    [Thr 2620] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
    [Thr 5688] Thu Sep 06 10:29:06 2007
    [Thr 5688] JLaunchIExitJava: exit hook is called (rc=-337)
    [Thr 5688] JLaunchCloseProgram: good bye (exitcode=-337)
    trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name   : ID4467550
    pid         : 3688
    system name : J2E
    system nr.  : 00
    started at  : Thu Sep 06 10:29:08 2007
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
        arg[02] : -DSAPINFO=J2E_00_server
        arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    [Thr 3348] Thu Sep 06 10:29:08 2007
    [Thr 3348] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
    [Thr 3348] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
    [Thr 3348] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    [Thr 3348] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host    : senthil
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : senthil
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_

  • Could not find Patch CR112484_81sp1.jar for WEBLOGIC 8.1

    Due problem with ACTUATE Server 7 WE have to install this patch but we could not
    find it ?
    Where is it on WL8.1 reference site ?
    Thanks

    Hello,
    As these patch is not publically avialble through BEA Advisories....so you need to open a support case to get this patch. Or otherwise you can upgrade to WLS 8.1 sp2 ,as this issue is fixed in this service pack.
    Regards,
    Kuldeep.

  • Output trigger in invoice

    Hello,
    The problem i am facing is when invoice was created initially print output was not triggered automatically. This was due to user exit in the system. This porblem is rectified,
    There are some 1000 faulty invoices where print output was not triggered automatically inspite of output condition record.If the invoices are accessed through VF02 it will trigger  (since intial probelm is rectified) but since the no. of invoices is more it is not possible access all invoices through VF02.
    Please suggest how to trigger the output in all the invoices again.
    Thanks in advance,
    Kiran

    Hello,
    As i know VF31 can only used if the output type exist in the invoice with some status.
    My requirement is to give the output type in the invoice.Intially the output type did got get determined in the invoice due problem in a user exit. This problem is rectified. In new invoices the output type is determined automatically.
    In faulty/old invoices when accessed though VF02 the output type is determined. SInce the no. of faulty invoices is more i cannot access every invoice through VF02, so that output type is determined in the invoice.Can any one suggest a method to access the invoices  (like some mass change) so that output type is determined in the invoice.
    Hope my requirement is clear
    Thanks in advance for support,
    Kiran

  • Canzoni che si interrompono dopo tre secondi e compare una schermata nera con scritte di colore giallo

    Premetto che il mio Ipod nano 6°generazione è finito in acqua. Dopo averlo tenuto spento per tutto un giorno, ora sembra funzionare ma presenta due problemi:il primo è che non si spegne, mentre il secondo è appunto il fatto che dopo tre secondi di ascolto, tutto si blocchi e compaia una schermata nera con scritte di colore giallo(credo sia una specie di bios ma non sono sicuro). Qualcuno saprebbe darmi una spiegazione in merito a questo problema? C'è speranza di salvare il mio Ipod o è da buttare? Grazie mille per l'attenzione.

    Temo sia morto.
    Sarebbe stato meglio non accenderlo.
    Molti consigliano di metterlo per diversi giorni in un vaso con riso (per essicarlo).

  • Cookies not sent back to server

    Server sends 'sessionid' as cookie, and Mozila works fine, cookie is returned back.
    Due problem of multiple services (sites) on same web server I've decided to rename 'sessionid' cookie name to 'vdssessionid'. Now FireFox simply ignores this cookies nothing is sent back, even if I see in Web Console that this cookie is originaly sent to FireFox, nothing is returned back.
    in other browsers this works fine.
    FF version 22.0 (updated today)

    >>> even if I see in Web Console that this cookie is originaly sent to FireFox, nothing is returned back.
    "Web Console" has integrated network (HTTP) analyzer with all headers.
    Why would I download another addon for firefox when I have one that works, or it doesn't!?
    My appologies forgot to mention this is Ajax (HTTPXMLRequest) that was communicating with server. And in response to Ajax request server responded with this cookie. Also in response as content was relative redirection URI that is set with top.location = ajax.response;
    Maybe something in this mechanism confuses FireFox, but I highly doubth. As same mechanism works just fine when cookie name is 'sessionid'.

  • Lamentela Genius Bar Apple store di orio center

    Vorrei segnalare un grave disservizio avuto presso l'apple store del centro commerciale "ORIOCENTER"
    Meno di un anno fà, per la precisione il 26/07/2012, acquistavo presso un negozio della catena "marco polo" un iPhone 4S 16 gb bianco come regalo di compleanno per mia moglie; (e terzo iPhone da me acquistato oltre ad un iPad) tengo a precisare che al momento dell'acquisto la confezione era sigillata con la apposita pellicola trasparente, ed al momento dell'apertura della confezione il telefono si trovava avvolto nella pellicola per proteggere sia il fronte che il retro come da tradizione Apple.
    Dopo nove mesi circa di utilizzo  immacolato da parte di mia moglie, il dispositivo cominciava ad avere due problemi; il primo presumibilmente di batteria, in quanto, quando l'indicatore di carica si trovava circa al 10% il telefono si spegneva improvvisamente anche in semplice modalità home ( senza app aperte in background) ed il secondo consisteva nello spegnimento totale del display alla fine di una chiamata e per riattivarlo, si doveva per forza eseguire il riavvio del telefono ( tasto accensione + tasto home)
    Dato che questo problema perseverava nel tempo, prendevo appuntamento al Genius Bar dell'apple store sito presso il centro commerciale "orio center" a Bergamo il giorno 28/06/2013.
    Giunto presso il negozio, insieme a mia moglie, prendevo contatto con il tecnico di Apple e gli illustravo il problema del dispositivo, dopo aver eseguito la diagnosi, lo stesso mi informava che in effetti la batteria risultava essere difettosa e che dunque me l'avrebbe sostituita.
    Dato che in precedenza, per un problema pressoché analogo il mio iPad era stato sostituito per intero, richiedevo al tecnico, a solo titolo informativo, come mai mi veniva sostituita solamente la batteria e non tutto il telefono, lo stesso mi diceva che preferivano sostituire la batteria in quanto se avessero dovuto sostituire l'intero telefono, io avrei prima dovuto contattare marco polo (effettivo rivenditore del telefono) per chiedere l'autorizzazione alla sostituzione in quanto in alcuni casi di sostituzione di dispositivi durante il primo anno di garanzia da parte di Apple, i rivenditori facevano decadere il secondo anno di garanzia. (Cosa che a mio riguardo sembrava completamente assurda).
    Dopo aver fatto firmare a mia moglie l'autorizzazione alla riparazione del telefono, il tecnico ci informava che l'intervento di sostituzione della batteria sarebbe durato una mezz'ora circa.
    Dopo una quarantina di minuti ritornavamo all'apple store per il ritiro del telefono, ma contattato il tecnico, lo stesso mi riferiva che non era stato possibile sostituire la batteria in quanto dopo aver aperto il dispositivo dichiarava a (a suo dire) che alcuni componenti non erano conformi agli originali e che mancava un sigillo.
    Dopo questa affermazione a dir poco ASSURDA chiedevo che mi fossero fatti visionare questi componenti non conformi e questo famoso sigillo mancante, per poi così procedere legalmente nei confronti del rivenditore; il tecnico con aria arrogante e sarcastica mi diceva che non poteva entrare nello specifico e che nella email che mi aveva inviato era certificato che il telefono non era idoneo alla riparazione in quanto manomesso.
    Alterato dalla situazione richiedevo se fosse stato possibile pagare l'intervento ( 68.00 euro circa) per così almeno avere il telefono funzionante ed anche a questa richiesta il "gentile" tecnico mi rispondeva che non era possibile.
    Mi recavo dunque, lo stesso giorno, all'apple store del centro commerciale "il leone" a Lonato del Garda, ovviamente dopo aver preso appuntamento, ed illustrato lo stesso identico problema, il tecnico, visionato il telefono, ed aver eseguito allo stesso modo la diagnosi, senza problemi mi sostituiva completamente il telefono in garanzia.
    Penso che  un marchio eccellente come Apple, che come punto di forza vanta senza dubbio un'assistenza inequiparabile ad ogni altro marchio concorrente non si possa permettere di avere dipendenti che, oltre che dichiarare cose non vere, come che in questo caso il telefono era stato aperto da personale non autorizzato che aveva sostituito componenti, trattano il cliente come un incompetente con aria arrogante, anche perché un cliente medio di Apple sborsa per un iPhone circa 700 euro.

    Anche io vorrei segnalare l'atteggiamento scorbutico e arrogante di un operatore del centro apple di Orio
    mi sono recato da loro per un iphone5 che non riuscivo a resettare, ho chiesto di collegare il telefono al pc
    mi è stato detto che il telefono era bagnato ed era inutile collegarlo ma poteva essere solo sostituito.
    Al di la del fatto che non mi risulta nel modo più assoluto di aver bagnato il telefono, avendo bisogno del telefono ho dovuto pagare e sostituirlo
    quello che mi ha fatto arrabbiare è l'atteggiamento indisponente dell'operatore che al mio diniego per il suo rifiuto nel voler collegare il telefono al pc
    se ne è andato demandando ad un menager l'intervento che a sua volta ci ha passato ad un terzo per la sostituzione
    sostenendo che loro sanno fare il loro lavoro !
    non mi dilungo oltre ma ho trovato l'operatore molto stupido, saccente e non degno del marchio che rappresenta
    bastava avere la pazienza di collegare il telefono al pc e dimostrarmi quello che asseriva
    ho un'azienda grafica da 25 anni, uso solo Apple,
    anche io mi sono sentito trattato come un incompetente con aria arrogante da uno stupido saputello.

  • Creation of data packages due to large amount of datasets leads to problems

    Hi Experts,
    We have build our own generic extractor.
    When data packages (due to large amount of datasets) are created, different problems occur.
    For example:
    Datasets are now doubled and appear twice, one time in package one and a second time in package two. Since those datsets are not identical, information are lost while uploading those datasets to an ODS or Cube.
    What can I do? SAP will not help due to generic datasource.
    Any suggestion?
    BR,
    Thorsten

    Hi All,
    Thanks a million for your help.
    My conclusion from your answers are the following.
    a) Since the ODS is Standard - within transformation no datasets are deleted but aggregated.
    b) Uploading a huge amount of datasets is possible in two ways:
       b1) with selction criteria in InfoPackage and several uploads
       b2) without selction criteria in InfoPackage and therefore an automatic split of datasets in data packages
    c) both ways should have the same result within the ODS
    Ok. Thanks for that.
    So far I have only checked the data within PSA. In PSA number of datasets are not equal for variant b1 and b2.
    Guess this is normal technical behaviour of BI.
    I am fine when results in ODS are the same for b1 and b2.
    Have a nice day.
    BR,
    Thorsten

  • System freezes due to hard disk problems only on Linux (not windows)

    Intro/context:
    Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
    I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
    tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
    What i've done so far:
    The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
    I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
    Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
    I found no firmware update for this hard drive.
    So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
    Info:
    Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
    Some logs i've recollected all this time:
    journalctl -xfa --system
    abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
    abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
    abr 21 13:51:24 echoes kernel: ata1: hard resetting link
    abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 13:51:24 echoes kernel: ata1: EH complete
    abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
    res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
    dmesg
    [55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
    [55661.023034] ata1.00: failed command: READ FPDMA QUEUED
    [55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [55661.023042] ata1.00: status: { DRDY }
    [55661.023046] ata1: hard resetting link
    [55666.358537] ata1: link is slow to respond, please be patient (ready=0)
    [55671.053813] ata1: COMRESET failed (errno=-16)
    [55671.053819] ata1: hard resetting link
    [55676.389438] ata1: link is slow to respond, please be patient (ready=0)
    [55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [55681.320305] ata1.00: configured for UDMA/100
    [55681.320319] ata1.00: device reported invalid CHS sector 0
    [55681.320349] ata1: EH complete
    [55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
    [55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
    dmesg
    [102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
    [102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
    [102884.890333] systemd[1]: systemd-journald.service failed.
    [102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
    [102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
    [104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
    [104179.117369] ata1.00: failed command: READ FPDMA QUEUED
    [104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [104179.117377] ata1.00: status: { DRDY }
    [104179.117381] ata1: hard resetting link
    [104184.453382] ata1: link is slow to respond, please be patient (ready=0)
    [104189.149114] ata1: COMRESET failed (errno=-16)
    [104189.149121] ata1: hard resetting link
    [104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [104189.952982] ata1.00: configured for UDMA/100
    [104189.952989] ata1.00: device reported invalid CHS sector 0
    [104189.953004] ata1: EH complete
    [104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    [104508.223798] ata1.00: failed command: SMART
    [104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [104508.223806] ata1.00: status: { DRDY }
    [104508.223810] ata1: hard resetting link
    [104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [104510.698126] ata1.00: configured for UDMA/100
    [104510.698157] ata1: EH complete
    One of the latest and worse
    journalctl -xfa --system
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
    res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
    abr 22 12:57:11 echoes kernel: ata1: EH complete
    abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
    abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
    abr 22 12:57:11 echoes kernel: ata1: EH complete
    Current smart status:
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: Toshiba 2.5" HDD MQ01ABD...
    Device Model: TOSHIBA MQ01ABD100
    Serial Number: Y44MT611T
    LU WWN Device Id: 5 000039 5e1a80e85
    Firmware Version: AX1P5E
    User Capacity: 1,000,204,886,016 bytes [1.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5400 rpm
    Form Factor: 2.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA8-ACS (minor revision not indicated)
    SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Sun May 3 16:42:06 2015 ART
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x82) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection: Enabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 120) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 234) minutes.
    SCT capabilities: (0x003d) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
    5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
    7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
    10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
    193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
    194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
    196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
    197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
    220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
    222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
    223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
    226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
    240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
    SMART Error Log Version: 1
    No Errors Logged
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Vendor (0x50) Completed without error 00% 611 -
    # 2 Short offline Completed without error 00% 611 -
    # 3 Short offline Completed without error 00% 597 -
    # 4 Vendor (0x50) Completed without error 00% 583 -
    # 5 Short offline Completed without error 00% 583 -
    # 6 Vendor (0x50) Completed without error 00% 575 -
    # 7 Short offline Completed without error 00% 575 -
    # 8 Short offline Completed without error 00% 547 -
    # 9 Extended offline Completed without error 00% 529 -
    #10 Short offline Completed without error 00% 355 -
    #11 Short offline Completed without error 00% 355 -
    #12 Extended offline Aborted by host 70% 355 -
    #13 Short offline Completed without error 00% 319 -
    #14 Vendor (0x50) Completed without error 00% 13 -
    #15 Short offline Completed without error 00% 13 -
    #16 Short offline Completed without error 00% 12 -
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
    Last edited by jesu (2015-05-03 19:42:53)

    Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
    Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
    $ lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 931,5G 0 disk
    ├─sda1 8:1 0 1000M 0 part
    ├─sda2 8:2 0 260M 0 part /boot
    ├─sda3 8:3 0 207,7G 0 part
    ├─sda4 8:4 0 25G 0 part
    ├─sda5 8:5 0 14,8G 0 part
    ├─sda6 8:6 0 80,5G 0 part /
    ├─sda8 8:8 0 599G 0 part /home
    └─sda9 8:9 0 2G 0 part [SWAP]
    So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
    Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
    Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
    dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
    [ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
    [ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
    [ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 653.821735] ata1.00: status: { DRDY }
    [ 653.821739] ata1: hard resetting link
    [ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
    [ 663.851604] ata1: COMRESET failed (errno=-16)
    [ 663.851610] ata1: hard resetting link
    [ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
    [ 673.881456] ata1: COMRESET failed (errno=-16)
    [ 673.881462] ata1: hard resetting link
    [ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
    [ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 703.012578] ata1.00: configured for UDMA/100
    [ 703.012584] ata1.00: device reported invalid CHS sector 0
    [ 703.012599] ata1: EH complete
    [ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
    [ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
    [ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
    [ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
    [ 742.443506] Buffer I/O error on device sda8, logical block 9323208
    [ 742.443508] Buffer I/O error on device sda8, logical block 9323209
    [ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
    [ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
    [ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
    [ 742.443524] Buffer I/O error on device sda8, logical block 9323216
    [ 742.443526] Buffer I/O error on device sda8, logical block 9323217
    [ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
    [ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
    [ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
    [ 742.443540] Buffer I/O error on device sda8, logical block 9323226
    [ 742.443542] Buffer I/O error on device sda8, logical block 9323227
    [ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
    [ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
    [ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
    [ 742.443555] Buffer I/O error on device sda8, logical block 9323234
    [ 742.443557] Buffer I/O error on device sda8, logical block 9323235
    [ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
    [ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
    [ 756.188116] systemd[1]: systemd-journald.service failed.
    [ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
    [ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
    [ 756.189143] systemd[1]: Listening on Journal Audit Socket.
    [ 756.189801] systemd[1]: Starting Journal Service...
    [ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
    [ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 758.503041] systemd[1]: Started Journal Service.
    [ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
    [ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867747] ata1.00: status: { DRDY }
    [ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867763] ata1.00: status: { DRDY }
    [ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867778] ata1.00: status: { DRDY }
    [ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867793] ata1.00: status: { DRDY }
    [ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867807] ata1.00: status: { DRDY }
    [ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867821] ata1.00: status: { DRDY }
    [ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867835] ata1.00: status: { DRDY }
    [ 974.867841] ata1: hard resetting link
    [ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
    [ 984.900902] ata1: COMRESET failed (errno=-16)
    [ 984.900908] ata1: hard resetting link
    [ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
    [ 994.930829] ata1: COMRESET failed (errno=-16)
    [ 994.930836] ata1: hard resetting link
    [ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 997.014012] ata1.00: configured for UDMA/100
    [ 997.014020] ata1.00: device reported invalid CHS sector 0
    [ 997.014023] ata1.00: device reported invalid CHS sector 0
    [ 997.014025] ata1.00: device reported invalid CHS sector 0
    [ 997.014026] ata1.00: device reported invalid CHS sector 0
    [ 997.014028] ata1.00: device reported invalid CHS sector 0
    [ 997.014030] ata1.00: device reported invalid CHS sector 0
    [ 997.014031] ata1.00: device reported invalid CHS sector 0
    [ 997.014065] ata1: EH complete
    There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
    root and home partitions are both ext4.

  • When I click on an email address on a web page, a page no longer opens in my email program. Not sure if this is a problem due to Firefox or due to recent installation of Office 2010. I use a PC with Vista.

    When I click on an email address embedded in a web page, a page would open in my email program with this address in the "To" line. I recently installed Microsoft Office 2010 and now when I click on an email address nothing happens. I am not sure if this is due to Office 2010 or a Firefox problem. I use a PC with Vista.

    https://support.mozilla.org/en-US/kb/change-program-used-open-email-links

  • Macbook Pro Retina keeps restarting "due to a problem" as well as imovie and Skype

    My new Macbook Pro Retina keeps restarting "due to a problem", when I open my skype it crashes and my imovie crashes all the time as well. I just got this computer last week. If someone could please help me out.
    These are the few of the errors on the console utility
    8/25/12 12:19:38.092 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** error: can't allocate region
    8/25/12 12:19:38.092 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** set a breakpoint in malloc_error_break to debug
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: iMovie(694,0xac8ba2c0) malloc: *** mmap(size=1223954432) failed (error code=12)
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** error: can't allocate region
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** set a breakpoint in malloc_error_break to debug
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: iMovie(694,0xac8ba2c0) malloc: *** mmap(size=1223962624) failed (error code=12)
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** error: can't allocate region
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** set a breakpoint in malloc_error_break to debug
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: iMovie(694,0xac8ba2c0) malloc: *** mmap(size=1223974912) failed (error code=12)
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** error: can't allocate region
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** set a breakpoint in malloc_error_break to debug
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: iMovie(694,0xac8ba2c0) malloc: *** mmap(size=979181568) failed (error code=12)
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** error: can't allocate region
    8/25/12 12:19:38.093 PM [0x0-0xaa0aa].com.apple.iMovieApp: *** set a breakpoint in malloc_error_break to debug
    8/25/12 12:19:38.094 PM iMovie: *** Canceling drag because exception 'NSMallocException' (reason '*** -[NSConcreteMutableData appendBytes:length:]: unable to allocate memory for length (979177572)') was raised during a dragging session
    8/25/12 12:22:06.000 PM kernel: IOSurface: buffer allocation size is zero
    8/25/12 12:22:07.000 PM kernel: IOSurface: buffer allocation size is zero
    8/25/12 12:23:33.000 PM kernel: IOSurface: buffer allocation size is zero
    8/25/12 12:23:37.000 PM kernel: IOSurface: buffer allocation size is zero
    8/25/12 12:23:37.000 PM kernel: IOSurface: buffer allocation size is zero
    8/25/12 12:23:39.000 PM kernel: IOSurface: buffer allocation size is zero
    8/25/12 12:24:29.322 PM [0x0-0xc50c5].com.skype.skype: DVFreeThread - CFMachPortCreateWithPort hack = 0x22e20e0, fPowerNotifyPort= 0x229f7d0
    8/25/12 12:24:29.322 PM [0x0-0xc50c5].com.skype.skype: DVFreeThread - CFMachPortCreateWithPort hack = 0x263d630, fPowerNotifyPort= 0x26221e0
    8/25/12 12:24:29.322 PM [0x0-0xc50c5].com.skype.skype: DVFreeThread - CFMachPortCreateWithPort hack = 0x263d840, fPowerNotifyPort= 0x2607c90
    8/25/12 12:25:18.000 PM kernel: IOSurface: buffer allocation size is zero
    8/25/12 12:27:27.481 PM com.apple.WindowServer: WindowServer(87,0x7fff74852960) malloc: *** error for object 0x7ff851ba0050: incorrect checksum for freed object - object was probably modified after being freed.
    8/25/12 12:27:27.481 PM com.apple.WindowServer: *** set a breakpoint in malloc_error_break to debug
    8/25/12 12:27:27.798 PM ReportCrash: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
    8/25/12 12:27:28.745 PM SystemUIServer: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.745 PM SystemUIServer: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.746 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.745 Google Chrome Helper[673:207] HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.745 Google Chrome Helper[673:207] port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.746 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.745 Google Chrome Helper[757:207] HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.745 Google Chrome Helper[761:207] HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.745 Google Chrome Helper[757:207] port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.746 PM Finder: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.745 Google Chrome Helper[761:207] port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.746 PM iTunes: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM Finder: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.746 PM iTunes: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.746 PM Google Chrome: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM Google Chrome Helper EH: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM rcd: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.746 PM Image Capture Extension: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.747 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.745 Google Chrome Helper EH[615:b03] HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.747 PM Google Chrome: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.747 PM Google Chrome Helper EH: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.747 PM rcd: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.747 PM Dock: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.747 PM Image Capture Extension: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.747 PM [0x0-0x90090].com.google.Chrome: 2012-08-25 12:27:28.746 Google Chrome Helper EH[615:b03] port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.748 PM Dock: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.750 PM com.apple.dock.extra: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.751 PM com.apple.dock.extra: 2012-08-25 12:27:28.746 com.apple.dock.extra[143:1707] HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.751 PM com.apple.dock.extra: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.752 PM com.apple.dock.extra: 2012-08-25 12:27:28.750 com.apple.dock.extra[143:1707] port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.752 PM talagent: HIToolbox: received notification of WindowServer event port death.
    8/25/12 12:27:28.753 PM talagent: port matched the WindowServer port created in BindCGSToRunLoop
    8/25/12 12:27:28.775 PM UserEventAgent: CaptiveNetworkSupport:UserAgentDied:139 User Agent @port=26115 Died
    8/25/12 12:27:28.782 PM com.apple.launchd.peruser.501: (com.apple.Dock.agent[114]) Exited with code: 1
    8/25/12 12:27:28.856 PM Google Chrome: MIG: server died: CGSReenableUpdateForConnections: Failed
    8/25/12 12:27:28.856 PM Google Chrome: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    8/25/12 12:27:28.857 PM Google Chrome: (ipc/send) invalid destination port: CGSSetEventMask: error setting window event mask
    8/25/12 12:27:28.858 PM Google Chrome: (ipc/send) invalid destination port: CGSDisableUpdateForConnections: Failed
    8/25/12 12:27:28.858 PM Google Chrome: (ipc/send) invalid destination port: CGSReenableUpdateForConnections: Failed
    8/25/12 12:27:28.858 PM Google Chrome: (ipc/send) invalid destination port: CGSGetOnScreenWindowCount
    8/25/12 12:27:28.858 PM Google Chrome: (ipc/send) invalid destination port: CGSGetOnScreenWindowCount
    8/25/12 12:27:28.858 PM Google Chrome: (ipc/send) invalid destination port: CGSGetWindowPresenter
    8/25/12 12:27:28.858 PM Google Chrome: (ipc/send) invalid destination port: CGSOrderWindowList
    8/25/12 12:27:28.859 PM Google Chrome: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store
    8/25/12 12:27:28.859 PM Google Chrome: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing store

    melirodriguez13 wrote:
    My new Macbook Pro Retina keeps restarting "due to a problem", when I open my skype it crashes and my imovie crashes all the time as well. I just got this computer last week. If someone could please help me out.
    Call Apple Care. 
    #1 - You have 14 days from the date of purchase to return your computer with no questions asked.
    #2 - You have 90 days of FREE phone tech support.
    #3 - If you've purchased an AppleCare Protection Plan, your warranty last for 3 years.   You can obtain AppleCare anytime up to the first year of the purchase of your computer.
    Take FULL advantage of your warranty.  Posting on a message board should be done as a last resort and if you are out of warranty or Apple Care has expired. 

Maybe you are looking for