HttpSession Invalidate not working with WAS LTPA

I normally handle site logout with a JSP that executes <% session.invalidate(); %> then redirects to the home page. Now I am running on WebSphere Application Server 5.1 authenticating against a Novell eDirectory LDAP server using LTPA and a SSL Certificate. Session.invalidate() does not work. Someone suggested it is because WAS is using LTPA. LTPA creates an authentication cookie that is not cleared by session.invalidate (?).
IBM does have a proprietary logout JSP I could use**, but I don't want to use a vendor specific solution. Has anybody tackled a session logout that clears the LTPA cookie without being tied to a vendor's J2EE container?
Thanks!
Steve Mitchell
http://www.byteworksinc.com
** http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/xsec_formlogin.html

I saw this old post of mine and thought I would follow-up. I never found a vendor neutral solution. When running on WebSphere I redirect to a JSP that posts to ibm_security_logout. When testing on Tomcat I just call session.invalidate(). My Struts LogoutAction does the following:
if ( serverInfo.toUpperCase( ).indexOf( "WEBSPHERE" ) > -1 )
return mapping.findForward( "websphereLogoutForward" );
session.invalidate( );
return mapping.findForward( "success" );
Steve Mitchell
http://www.byteworksinc.com

Similar Messages

  • UME not working for WAS 700

    Hi,
           we are working on SAP WAS 700. We have just moved from WAS 640 and NWDS 2.0.09 to WAS 700 and NWDS 640. I am having a problem that when I try to open the UME from the WAS home page, I get the following error :
    Application error occurred during the request procession.
      Details:   com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
      Error compiling [/index.jsp] of alias [useradmin] of J2EE application [sap.com/com.sap.security.core.admin].
    The log gives the following message for this :
    #1.5#00174212003F004C000002D000000ADC00043341A6CA4DEF#1182256971041#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.engine.docs.examples finished successfully on server 307377350#
    #1.5#00174212003F004C000002D100000ADC00043341A6CA4E37#1182256971041#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.engine.docs.examples finished on current cluster node for 52474 ms.#
    #1.5#00174212003F004C000002D200000ADC00043341A6D48193#1182256971713#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.engine.class.download] finished successfully on Web Container.#
    #1.5#00174212003F004C000002D300000ADC00043341A6D483EC#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.engine.class.download finished successfully on server 307377350#
    #1.5#00174212003F004C000002D400000ADC00043341A6D48446#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.engine.class.download finished on current cluster node for 672 ms.#
    #1.5#00174212003F004C000002D500000ADC00043341A6D4A26C#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafummetadata~content finished successfully on server 307377350#
    #1.5#00174212003F004C000002D600000ADC00043341A6D4A2D8#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafummetadata~content finished on current cluster node for 0 ms.#
    #1.5#00174212003F004C000002D700000ADC00043341A6DB2A79#1182256972135#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.lcr.saprfc finished successfully on server 307377350#
    #1.5#00174212003F004C000002D800000ADC00043341A6DB2AE9#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.lcr.saprfc finished on current cluster node for 438 ms.#
    #1.5#00174212003F004C000002D900000ADC00043341A6DB482F#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafeugp~content finished successfully on server 307377350#
    #1.5#00174212003F004C000002DA00000ADC00043341A6DB489B#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafeugp~content finished on current cluster node for 0 ms.#
    #1.5#00174212003F004C000002E200000ADC00043341A6E854CD#1182256973010#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/cafruntimemonitoring~ear] finished successfully on Web Container.#
    #1.5#00174212003F004C000002E300000ADC00043341A6E85755#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/cafruntimemonitoringear : Application sap.com/cafruntimemonitoringear has a weak reference to resource jmsfactory/TopicConnectionFactory with type javax.jms.TopicConnectionFactory but the resource is not available and the application may not work correctly!#
    #1.5#00174212003F004C000002E400000ADC00043341A6E857BE#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafruntimemonitoring~ear finished successfully on server 307377350#
    #1.5#00174212003F004C000002E500000ADC00043341A6E85806#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafruntimemonitoring~ear finished on current cluster node for 859 ms.#
    #1.5#00174212003F004C000002E600000ADC00043341A6E87157#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###New internal library C:
    usr
    sap
    F48
    JC30
    j2ee
    cluster
    server0
    apps
    sap.com/com.sap.ip.bi.sdk.dac.olap
    bi_sdk_olap.jar will be downloaded.#
    #1.5#00174212003F004C000002E700000ADC00043341A7042104#1182256974823#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###New internal library C:
    usr
    sap
    F48
    JC30
    j2ee
    cluster
    server0
    apps
    sap.com/com.sap.ip.bi.sdk.dac.olap
    bi_sdk_olap_xmi.jar will be downloaded.#
    #1.5#00174212003F004C000002E800000ADC00043341A732696B#1182256977854#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.sdk.dac.olap finished successfully on server 307377350#
    #1.5#00174212003F004C000002E900000ADC00043341A73269DB#1182256977854#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.sdk.dac.olap finished on current cluster node for 4844 ms.#
    #1.5#00174212003F004C000002EA00000ADC00043341A7383749#1182256978245#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.ip.bi.sdk.monitoring] finished successfully on Web Container.#
    #1.5#00174212003F004C000002EB00000ADC00043341A73839D0#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.sdk.monitoring finished successfully on server 307377350#
    #1.5#00174212003F004C000002EC00000ADC00043341A7383A33#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.sdk.monitoring finished on current cluster node for 375 ms.#
    #1.5#00174212003F004C000002ED00000ADC00043341A7385752#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafeugpmodelpwflocaluwlconn finished successfully on server 307377350#
    #1.5#00174212003F004C000002EE00000ADC00043341A73857C1#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafeugpmodelpwflocaluwlconn finished on current cluster node for 0 ms.#
    #1.5#00174212003F004C000002F600000ADC00043341A796016E#1182256984386#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /SLDStart/plain, appName sap.com/tclmwebadminsldstartapp#
    #1.5#00174212003F004C000002F700000ADC00043341A796024E#1182256984386#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /SLDStart/secure, appName sap.com/tclmwebadminsldstartapp#
    #1.5#00174212003F004C000002F800000ADC00043341A79602A2#1182256984386#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminsldstartapp] finished successfully on Web Container.#
    #1.5#00174212003F004C000002F900000ADC00043341A79605A7#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/tclmwebadminsldstartapp : JAR File: sap.comtclmwebadminsldstart~ejb.jar XML file: ejb-j2ee-engine.xml Element: description is empty. It is not recommended to use empty value elements. Please remove the element or define its value!#
    #1.5#00174212003F004C000002FA00000ADC00043341A7960610#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminsldstartapp finished successfully on server 307377350#
    #1.5#00174212003F004C000002FB00000ADC00043341A7960657#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminsldstartapp finished on current cluster node for 6141 ms.#
    #1.5#00174212003F004C000002FC00000ADC00043341A83A10A5#1182256995138#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.netweaver.bc.uwl.moni] finished successfully on Web Container.#
    #1.5#00174212003F004C000002FD00000ADC00043341A83A1407#1182256995138#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.netweaver.bc.uwl.moni finished successfully on server 307377350#
    #1.5#00174212003F004C000002FE00000ADC00043341A83A1524#1182256995138#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.netweaver.bc.uwl.moni finished on current cluster node for 10752 ms.#
    #1.5#00174212003F004C000002FF00000ADC00043341A84C226F#1182256996325#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcwdpdfsvrchal] finished successfully on Web Container.#
    #1.5#00174212003F004C0000030000000ADC00043341A84C2558#1182256996325#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcwdpdfsvrchal finished successfully on server 307377350#
    #1.5#00174212003F004C0000030100000ADC00043341A84C25DE#1182256996325#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcwdpdfsvrchal finished on current cluster node for 1187 ms.#
    #1.5#00174212003F004C0000030900000ADC00043341A9823866#1182257016640#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tc~uddi' application started successfully.#
    #1.5#00174212003F004C0000030A00000ADC00043341A98238DF#1182257016640#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tc~uddi] finished successfully on Web Container.#
    #1.5#00174212003F004C0000030B00000ADC00043341A9823B30#1182257016640#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tc~uddi finished successfully on server 307377350#
    #1.5#00174212003F004C0000030C00000ADC00043341A9823B84#1182257016640#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tc~uddi finished on current cluster node for 20315 ms.#
    #1.5#00174212003F004C0000031400000ADC00043341A99803D0#1182257018078#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcsupportplatformwd finished successfully on server 307377350#
    #1.5#00174212003F004C0000031500000ADC00043341A998043E#1182257018078#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcsupportplatformwd finished on current cluster node for 1438 ms.#
    #1.5#00174212003F004C0000031600000ADC00043341A9C56179#1182257021047#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/cafeugpmodeliforms~eap] finished successfully on Web Container.#
    #1.5#00174212003F004C0000031700000ADC00043341A9C563D0#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/cafeugpmodeliformseap : JAR File: sap.comcafeugpmodeliforms~ejb.jar XML file: ejb-j2ee-engine.xml Element: description is empty. It is not recommended to use empty value elements. Please remove the element or define its value!#
    #1.5#00174212003F004C0000031800000ADC00043341A9C56434#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafeugpmodeliforms~eap finished successfully on server 307377350#
    #1.5#00174212003F004C0000031900000ADC00043341A9C5647C#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafeugpmodeliforms~eap finished on current cluster node for 2969 ms.#
    #1.5#00174212003F004C0000031A00000ADC00043341A9F0EE76#1182257023891#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminsysconfigapp] finished successfully on Web Container.#
    #1.5#00174212003F004C0000031B00000ADC00043341A9F0F0C9#1182257023891#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminsysconfigapp finished successfully on server 307377350#
    #1.5#00174212003F004C0000031C00000ADC00043341A9F0F120#1182257023891#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminsysconfigapp finished on current cluster node for 2844 ms.#
    #1.5#00174212003F004C0000032400000ADC00043341AA3CEBEA#1182257028876#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminperformanceprovider_ear] finished successfully on Web Container.#
    #1.5#00174212003F004C0000032500000ADC00043341AA3CEE34#1182257028876#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminperformanceprovider_ear finished successfully on server 307377350#
    #1.5#00174212003F004C0000032600000ADC00043341AA3CEE8D#1182257028876#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminperformanceprovider_ear finished on current cluster node for 4970 ms.#
    #1.5#00174212003F004C0000032E00000ADC00043341AAB4C8A8#1182257036736#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /BizcCommLayerUtilities/Config1, appName sap.com/tcbizcws~ear#
    #1.5#00174212003F004C0000032F00000ADC00043341AAB4CA9D#1182257036736#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /BizcCommLayerAuthoring/Config1, appName sap.com/tcbizcws~ear#
    #1.5#00174212003F004C0000033000000ADC00043341AAB4CAF2#1182257036736#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcbizcws~ear] finished successfully on Web Container.#
    #1.5#00174212003F004C0000033100000ADC00043341AAB4CD69#1182257036736#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcbizcws~ear finished successfully on server 307377350#
    #1.5#00174212003F004C0000033200000ADC00043341AAB4CDBF#1182257036736#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcbizcws~ear finished on current cluster node for 7860 ms.#
    #1.5#00174212003F004C0000033300000ADC00043341AAB582F5#1182257036783#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/caf~km.ep.kmtaskservice finished successfully on server 307377350#
    #1.5#00174212003F004C0000033400000ADC00043341AAB58363#1182257036783#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/caf~km.ep.kmtaskservice finished on current cluster node for 47 ms.#
    #1.5#00174212003F004C0000033500000ADC00043341AB3A1074#1182257045471#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader com.sap/irj on the system, but will register reference for furture usage.#2#sap.com/sap.comtckmccoll.room.wsdepl#com.sap/irj#
    #1.5#00174212003F004C0000033600000ADC00043341AB4D215A#1182257046721#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /RoomABAPWS/Config1, appName sap.com/sap.comtckmccoll.room.wsdepl#
    #1.5#00174212003F004C0000033700000ADC00043341AB4D21D7#1182257046721#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/sap.comtckmccoll.room.wsdepl] finished successfully on Web Container.#
    #1.5#00174212003F004C0000033800000ADC00043341AB4D24E1#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has hard reference to application sap.com/com.sap.km.application and is starting it!#
    #1.5#00174212003F004C0000033900000ADC00043341AB4D2542#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has weak reference to application sap.com/com.sap.netweaver.coll.appl.room.rfcadapter and is starting it!#
    #1.5#00174212003F004C0000033A00000ADC00043341AB4D2599#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has weak reference to application com.sap/irj and is starting it!#
    #1.5#00174212003F004C0000033B00000ADC00043341AB4D25E8#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/sap.comtckmccoll.room.wsdepl finished successfully on server 307377350#
    #1.5#00174212003F004C0000033C00000ADC00043341AB4D262F#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/sap.comtckmccoll.room.wsdepl finished on current cluster node for 9938 ms.#
    #1.5#00174212003F004C0000033D00000ADC00043341AB4F884D#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader library:kernel.sda on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#library:kernel.sda#
    #1.5#00174212003F004C0000033E00000ADC00043341AB4F89A8#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader library:com.sap.engine.client.lib on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#library:com.sap.engine.client.lib#
    #1.5#00174212003F004C0000033F00000ADC00043341AB4F8A6D#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.runtime.application.jcoclient on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#sap.com/com.sap.portal.runtime.application.jcoclient#
    #1.5#00174212003F004C0000034700000ADC00043341AB96ACB5#1182257051534#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sapportals.supportplatform' application started successfully.#
    #1.5#00174212003F004C0000034800000ADC00043341AB96AD31#1182257051534#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sapportals.supportplatform] finished successfully on Web Container.#
    #1.5#00174212003F004C0000034900000ADC00043341AB96AFE4#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Library kernel.sda is not deployed or loaded, but resolving of application sap.com/com.sapportals.supportplatform continues because it has weak reference to this library.#
    #1.5#00174212003F004C0000034A00000ADC00043341AB96B101#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Library com.sap.engine.client.lib is not deployed or loaded, but resolving of application sap.com/com.sapportals.supportplatform continues because it has weak reference to this library.#
    #1.5#00174212003F004C0000034B00000ADC00043341AB96B154#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.pcd.glservice and is starting it!#
    #1.5#00174212003F004C0000034C00000ADC00043341AB96B1B2#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.contentmigration.contentmigrationservice and is starting it!#
    #1.5#00174212003F004C0000034D00000ADC00043341AB96B1FF#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.httpconnectivity.urlfetcherservice and is starting it!#
    #1.5#00174212003F004C0000034E00000ADC00043341AB96B24C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.connectorservice and is starting it!#
    #1.5#00174212003F004C0000034F00000ADC00043341AB96B2A4#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.runtime.application.jcoclient and is starting it!#
    #1.5#00174212003F004C0000035000000ADC00043341AB96B2F1#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.systemlandscapeservice and is starting it!#
    #1.5#00174212003F004C0000035100000ADC00043341AB96B33B#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.iviewservice and is starting it!#
    #1.5#00174212003F004C0000035200000ADC00043341AB96B38C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.themes.designservice and is starting it!#
    #1.5#00174212003F004C0000035300000ADC00043341AB96B3D7#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.themes.lafservice and is starting it!#
    #1.5#00174212003F004C0000035400000ADC00043341AB96B421#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.productivity.resolverservice and is starting it!#
    #1.5#00174212003F004C0000035500000ADC00043341AB96B46C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.runtime.config and is starting it!#
    #1.5#00174212003F004C0000035600000ADC00043341AB96B4B6#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has a weak reference to resource jdbc/Resource1 with type javax.sql.DataSource but the resource is not available and the application may not work correctly!#
    #1.5#00174212003F004C0000035700000ADC00043341AB96B510#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sapportals.supportplatform finished successfully on server 307377350#
    #1.5#00174212003F004C0000035800000ADC00043341AB96B557#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sapportals.supportplatform finished on current cluster node for 4813 ms.#
    #1.5#00174212003F004C0000036000000ADC00043341AB9A0CF9#1182257051753#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminclusteradminwd finished successfully on server 307377350#
    #1.5#00174212003F004C0000036100000ADC00043341AB9A0D67#1182257051753#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminclusteradminwd finished on current cluster node for 219 ms.#
    #1.5#00174212003F004C0000036900000ADC00043341AC476D74#1182257063114#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tc~workflowmodeler] finished successfully on Web Container.#
    #1.5#00174212003F004C0000036A00000ADC00043341AC4770C7#1182257063114#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tc~workflowmodeler finished successfully on server 307377350#
    #1.5#00174212003F004C0000036B00000ADC00043341AC47712A#1182257063114#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tc~workflowmodeler finished on current cluster node for 11361 ms.#
    #1.5#00174212003F004C0000037300000ADC00043341AD0C9DC4#1182257076037#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv] finished successfully on Web Container.#
    #1.5#00174212003F004C0000037400000ADC00043341AD0CA03B#1182257076037#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv finished successfully on server 307377350#
    #1.5#00174212003F004C0000037500000ADC00043341AD0CA099#1182257076037#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv finished on current cluster node for 12923 ms.#
    #1.5#00174212003F004C0000037D00000ADC00043341AD0D14D7#1182257076068#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.biloggingconfig finished successfully on server 307377350#
    #1.5#00174212003F004C0000037E00000ADC00043341AD0D1549#1182257076068#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.biloggingconfig finished on current cluster node for 31 ms.#
    #1.5#00174212003F004C0000038600000ADC00043341AD0FDBFC#1182257076256#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.netweaver.bc.uwl.logging finished successfully on server 307377350#
    #1.5#00174212003F004C0000038700000ADC00043341AD0FDC70#1182257076256#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.netweaver.bc.uwl.logging finished on current cluster node for 188 ms.#
    #1.5#00174212003F004C0000038F00000ADC00043341AD383B60#1182257078897#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcsldstartup~app] finished successfully on Web Container.#
    #1.5#00174212003F004C0000039000000ADC00043341AD383DD5#1182257078897#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcsldstartup~app finished successfully on server 307377350#
    #1.5#00174212003F004C0000039100000ADC00043341AD383E2D#1182257078897#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcsldstartup~app finished on current cluster node for 2641 ms.#
    #1.5#00174212003F004C0000039900000ADC00043341AD48B35C#1182257079975#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.sdk.datasource.sys finished successfully on server 307377350#
    #1.5#00174212003F004C0000039A00000ADC00043341AD48B3CE#1182257079975#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.sdk.datasource.sys finished on current cluster node for 1078 ms.#
    #1.5#00174212003F004C000003A200000ADC00043341AD619BAC#1182257081616#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminmonitorcomplib~wd finished successfully on server 307377350#
    #1.5#00174212003F004C000003A300000ADC00043341AD619C1D#1182257081616#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminmonitorcomplib~wd finished on current cluster node for 1641 ms.#
    #1.5#00174212003F004C000003A400000ADC00043341AD794D3C#1182257083163#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.workflow.j2eemoni] finished successfully on Web Container.#
    #1.5#00174212003F004C000003A500000ADC00043341AD795057#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sap.workflow.j2eemoni : Application sap.com/com.sap.workflow.j2eemoni has weak reference to application sap.com/com.sap.workflow.apps and is starting it!#
    #1.5#00174212003F004C000003A600000ADC00043341AD7950BD#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.workflow.j2eemoni finished successfully on server 307377350#
    #1.5#00174212003F004C000003A700000ADC00043341AD795105#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.workflow.j2eemoni finished on current cluster node for 1547 ms.#
    #1.5#00174212003F004C000003A800000ADC00043341AD7AF3AE#1182257083272#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###The synchronization of applications with DB completed for 1631354 ms.#
    #1.5#00174212003F004D0000005B00000ADC00043341CABE84F0#1182257574096#/System/Server/WebRequests#sap.com/com.sap.security.core.admin#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####fedffd001e6311dcc5e900174212003f#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing HTTP request to servlet [jsp] finished with error.
    The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
    Exception in thread "main"
    Exception id: [00174212003F004D0000005A00000ADC00043341CABE8396]#
    #1.5#00174212003F004D0000005E00000ADC00043341CAD04526#1182257575252#/System/Server/WebRequests#sap.com/com.sap.security.core.admin#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####fedffd001e6311dcc5e900174212003f#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing an HTTP request by the error page [/error.jsp] finished with errors. Probably the exception [com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
    Exception in thread "main"
    ].] thrown by the requested servlet [/useradmin/error.jsp] cannot be processed.
    The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
    Exception in thread "main"
    Exception id: [00174212003F004D0000005D00000ADC00043341CAD04370]#
    I have JDK 1.4.2_014 installed on the system and WAS has its own JDK installed inside its own folder. I am having a similar problem with NWDS where it always picks up my JRE as default which is not installed inside my jdk 1.4._014. This remains the same even when I change the  jre path inside the NWDS preference from the Window->Preferences menu.
    This problem has stayed the same even after I uninstalled the jdk , NWDS, and WAS and reinstalled them from the scratch. Before that, I had actually got NWDS working when I added the tools.jar file from the jdk 1.4_014 to the jre my NWDS was pointing to. but this trick is not working with WAS.
    Also when I had deployed the web dynpro project, it did not show in the browser window which stayed blank.
    Please help me with it.

    I don't know. You would have to find people who pay attention to such things. Maybe try the developer forums at http://devforums.apple.com. From everything I have read, iAd is not one of the best advertising networks. Even the best advertising networks pay very, very little. I think it is much better to provide functionality that people are willing to pay for, probably via in-app purchases.

  • Hello,  I have iMac from Oct, 2010 and have OS 10.6.7 and multiple users.  Mail icon was accidently removed along with program.  Mail 4.4 is on other users but when I reloaded software my user got Mail 4.3. Mail 4.3 did not work with latest OS. Ideas?Matt

    Hello,  I have iMac Itel i3, from Oct, 2010 and have OS 10.6.7 and multiple users. 
    About 3-4 days ago the Mail icon in dock had question mark and was accidently removed, along with program on my user.  Oops.
    1. Mail 4.4 is on other users and works fine, but for me it does not work and tells me V4.3 does not work with latest OS X. 
    2. I reloaded software from my user with original disks  (Oct, 2010) and got Mail 4.3 again. Mail 4.3 did not work with latest OS.  I am unable to load Mail.  Gives Yellow error message.    
    "  You have Mail version 4.3 (1081/1084). It can’t be used on Mac OS X Version 10.6.7 (Build 10J869). For more information, click the Help button."
    3. Tried to update software and look for update for mail 4.3 on Apple site to no success.
    Hate to go to MS-Entorage ( I may need to learn something new and alien) mail program since contracts are in Mail/Address Book.
    Ideas?
    MattDeeds

    Matt,
    I would download and run the 10.6.7 combo update.
    http://support.apple.com/kb/DL1361
    Regards,
    Captfred

  • I had an iphone 4s and it worked nice with facetime and imessage using my phone number but  it was stolen on December so I buy a new iphone 4s using the same cellphone number  but now imessage and facetime does not work with my number, it only works with

    I had an iphone 4s and it worked nice with facetime and imessage using my phone number but  it was stolen on December so I buy a new iphone 4s using the same cellphone number  but now imessage and facetime does not work with my number, it only works with my apple ID.   Please Help me I speak Spanish so  if my English is not ok  I´m sorry about it.
    Do you think that apple has to   reset in their database of the old serial number attached with my phone number and that’s why I can´t activate imessage and facetime with my number in the new iphone 4s?? 

    I understand all of this Meg; that is why I bought an Iphone; but never expected my phone not even give a at least a 24 or even 12 hours....I work 12 hour shifts and also would expect to have to charge each night but not twice a day or more.  I am not always somewhere I can charge my phone.
    Your points are true; however it doesn't help me......

  • Ear Sir: Yesterday on 18.09.2014 evening, I wanted to install IOS 8.0 according to your instructions iPhone 5S.during installation Stopped working and was closd, I can not work with him. Ibought it in the United States Apple Store Fifth 40venue 767 N

    Dear Sir: Yesterday on 18.09.2014 evening, I wanted to install
    IOS 8.0 according to your instructions iPhone 5S.during installation
    Stopped working and was closd, I can not work with him. Ibought it in
    the United States
    Apple Store Fifth 40venue 767 New York NY1053
    iPhone 5s Spase Gray 32 gb verizon.
    Part Number: ME344ll / A.
    Serial number: DN*******NjM.
    Model A1533. I would like to request a new password for opening the
    iPhone.  Passwod..... Thank you very much,
    Im not difficult for you to request a quick answer.Israel.
    <Personal Information Edited By Host>

    We are fellow users here on these forums, you're not talking to iTunes Support nor Apple - it looks like somebody has asked the hosts to remove your personal info from your post (it's not a good idea to post any personal info on any public forum).
    What do you 'stopped working and was closed, I can not work with him' ? What exactly are you seeing on the phone's screen ?
    If it's the activation screen and you can't remember your password for your account then see if you can get it reset via http://iforgot.apple.com

  • I have laptop with digital persona (finger scanning) to automatic feed the passwords. it was working properly with the older version of firefox but is not working with the latest version of the firefox. why? give me a solution.

    i have laptop with digital persona (finger scanning) to automatic feed the passwords. it was working properly with the older version of firefox but is not working with the latest version of the firefox. why? give me a solution.

    Please authorize ADE 3 with same credentials that you used with older version of ADE

  • HT4061 hi i have purchased iphone4 from vodafone australia 2 years back.it is unlocked, when i went to india .it was not working with any carrier in india.it was displaying no service.is it a problem of iphone or any other anybody please could let me know

    hi i have purchased iphone4 from vodafone australia 2 years back.it is unlocked, when i went to india .it was not working with any carrier in india.it was displaying no service.is it a problem of iphone or any other anybody please could let me know?

    Hi ashish,
    Did you contact TPG about activating International Roaming before you left for India:
    http://www.tpg.com.au/support/international_roaming.php
    Cheers,
    GB

  • I recently uploaded OSX 10.6.7 and ever since then, my Boris titler in FCP does not work with all the fonts, notably Avenir. It actually crashes FCP now. It was fine with the previous version. What's up Apple?

    I recently uploaded OSX 10.6.7 and ever since then, my Boris titler in FCP does not work with all the fonts, notably Avenir. It actually crashes FCP now. It was fine with the previous version. What's up Apple?

    I know what your'e going through, Gary.   OSX 10.6.7 is an absolute disaster.   Since I upgraded, I've had problems in FCP, Logic, Garageband, even issue dealing with peripheral hardware like external monitors.
    Before 10.6.7 my system was running fine.
    I've brought this up with Apple repeatedly.   They smile and shrug.   They've been helpful resolving the issues, but none of them has been easy to solve.  I have spent days, dealing back and forth with tech support, sending logs, etc., before solutions have been found.  
    I wish I could give you an answer to your question.   My only guess is that Apple has totally dropped the ball on this one.   In the future they should provide a disclaimer when they offer an upgrade.  Something like:   "Caution: all of your software may not function after this upgrade. But go ahead, you'll feel cool that your OS is the latest thing."
    As someone who has been with Apple for close to 25 years, I'm disturbed by what appears to be an increasing sloppiness in their work.   This is especially disturbing when you depend upon their system to make your living.
    Good luck.
    david

  • HT201541 Final cut Pro 10.0.8 was installed on my computer when I got it. It now will not work with  OS Yosemite. How do I get update for final cut?

    Final cut Pro 10.0.8 was installed on my computer when I got it.
    It now will not work with  OS Yosemite. How do I update Final cut so I can use it?
    I am new to Mac Book Pro so I need help!!!

    You get FCPX legally only via AppStore; it then gets 'bonded' to your AppleID/Appstore account.
    To update, log in with the Account you have purchased it - click update (for free)
    If you don't have the Account data, you're not owner of the software. No free drinks updates.
    Log in with YOUR ID, click purchase  - ring! 300$ .............

  • My iPhoto will not work with Yosemite, and it says that it was purchased under a different account, but that's not the case.  Any ideas why I cannot update iPhoto?

    my iPhoto will not work with Yosemite, and it says that it was purchased under a different account, but that's not the case.  Any ideas why I cannot update iPhoto?

    How did you buy iPhoto? Did it come preinstalled on your computer with Lion or later, or did it come with Snowleopard on system installer disks?
    Which version of iPhoto?
    If you have a version of iPhoto '11 and it is showing on the Purchased tab of the App Store, with your Apple ID, then delete iPhoto from the Applications folder  (don't empty the Trash) and download iPhoto again from the Purchased tab.
    If that does not work, contact The App Store Support  from the Quick Links on the AppStore main page.
    Only apple Support can fix problems with apple ID.

  • My macbook is back from repairs. It is not working with my apple led cinema display. It was working prior to the repairs on the laptop. Is there a setting I don't know about that might have been changed?

    My macbook pro is just back from repairs.  It is not working with my apple led cinema display. I have followed the directions in the cinema display manual.  am I missing something?

    Take a look at the Displays preference panel to see if everything is ok, particularly the resolution and refresh rate.  Displays will probably try to put the panel for the ACD on the ACD where you won't see it.  So click "Gather Windows" to get the ACD panel on to your macbook.
    One more thing, make sure you fully seated the mini displayport plug.  They can be sneaky little devils in that they need to be fully pushed in.

  • I installed firefox 10 - it was offered on startup. I absolutely does not work with a cloud based program I use (corecon) and I want to GO BACK TO FIREFOX 9. how do i do this?

    firefox 10 ABSOLUTELY does not work with a cloud based program, Corecon. I want to UNINSTALL firefox 10 and GO BACK TO FIREFOX 9 . How do I do this? This is a subscription service, you may not be able to try it. v9 works fine.

    http://support.mozilla.com/en-US/kb/Installing+a+previous+version+of+Firefox
    http://www.mozilla.com/en-US/firefox/

  • Caller ID not working with Nokia 6600?

    I have a T-Mobile (US) Nokia 6600, and I can't seem to get address book to display incoming SMS or the caller ID of incoming calls. I've successfully paired the phone via bluetooth, and I can make address book dial the phone and send an sms. I can sync via iSync, use my phone as a modem, etc. etc.
    But regardless of what settings I tweak, I can't seem to get Address Book to show a bezel of any kind on incoming calls - not even an 'Unknown Caller' message! Am I missing something obvious? Third party apps like BluePhoneElite work just fine, so I'm pretty sure it's something wrong with Address Book...
    15" Aluminum Powerbook 1.5 GHz   Mac OS X (10.4.5)  

     
    mdcdsc wrote:
    My caller ID does not work with the new ap either.  I don't like the new ap at all.  The old one was beautiful.  Now my email is very hard to see, so much that I will just use the Apple email that comes with my IPOD.  The caller ID was my favorite thing with the old ap.  and now it doesn't work.  I have followed the instructions and turned everything on, but it just does not work.
    The Caller ID issue was due to an outage. It should be resolved anytime soon. Can yu log out and log back in. Go to app settings and in notifications and turn CAller ID off and on.
    On email - what do you mean 'email is very hard to see' ? I would like to pass on this feedback to the team.

  • My Time Capsule does not work with existing WiFi

    Following a question solved on March 24 by LaPastenague, but gone bad again.
    Apple AirPort Time Capsule
    I felt the need for a physical backup of my data, as I would not completely trust the different clouds. I use, and have used Dropbox for 4-5 years and are very satisfied with that, but I am still not sure if or when a political lunatic will shut off the internet.
    I purchased the Apple AP Time Capsule 2T, because all my other stuff are Apple, and that it's wireless. My old backup is Maxtor 300 GB.
    Since we stay 2-3 weeks on two locations, one in Norway and one in Sweden (two different countries) we must use Mobile Broadband 4G, cables or fibre connections are useless for us, and we don't have it up to the houses. I have one mini router for each country, we bring with us iPhones, iPads, iMac, Apple TV, APExpress. When we pass the boarder I change the mini router, and the system continues working perfect on the WiFi, except the APExpress that needs to be reconfigured,  but then it works.
    The APTC was difficult to make working as it would not accept to be in an existing network, but with good help from the Apple Community, LaPastenague, with forcing the TC connect to the APE with Ethernet cable in bridge mode, ref "My Time Capsule does not work with existing WiFi" from March 24, the problem was solved and all gadgets worked together in a perfect harmony, until we changed location.
    Now, as I have my second WiFi network, and the APExspress is reconfigured, it's like the TC thinks, I am the base boss here, I am not taking orders from APE one more time, and it simply does not work, not only that, it fluctuates all the time.
    I have a slight feeling that the two WiFi bands are making the trouble as during the configuration of the TC sometime the last figure 6 and 7 pops up, and that has something two do with the two different 2,4 and 5 GHZ bands
    So, I am curious if you have any idea ?
    I am thinking of returning the TC if I don't make it work now, but how do I delete all the data that's on it?

    I can deal with the last question first and easily.
    I am thinking of returning the TC if I don't make it work now, but how do I delete all the data that's on it?
    Open the airport utility .. go to the disk tab and select erase.
    When you select erase you will get mulitiple options.
    Quick removes the file table but does not delete the files,, it takes 2min or less.
    A Zero out data is the secure way,, by writing 0 ie low level drive format.
    It can take several hours..
    7 pass will take a week.. not recommended..
    35 pass erase is ridiculous.. it would take a month.. put an ax through the TC. It is quick and better.
    Now, as I have my second WiFi network, and the APExspress is reconfigured, it's like the TC thinks, I am the base boss here, I am not taking orders from APE one more time, and it simply does not work, not only that, it fluctuates all the time.
    The fact that it did work and has now failed might point to faulty unit.
    The only way to tell is reset it properly to factory and start over.
    Universal Factory Reset.. any model TC or AE.
    Unplug your TC/AE from power or turn off at the power point.
    Hold in reset. and power the TC/AE back on..  all without releasing reset and keep holding in for about 10sec. (this is often difficult without a 2nd person or a 3rd arm).
    Release it when the status light flashes rapidly. If it doesn’t flash rapidly you have missed it and try again.
    Note..
    Be Gentle! Feel the switch click on. It has a positive feel..  add no more pressure after that.
    TC/AE will reboot after a couple of minutes with default factory settings and will wipe out previous configurations of the router.
    No files are deleted on the hard disk in a TC.. No reset of the TC deletes files.. to do that you use erase from the airport utility.
    Generally having multiple wireless AP should not cause problems.. but it is better to set channels manually.. so it doesn't go beserk rotating channels.
    Remember to keep all names short, no spaces and pure alphanumeric.
    Sadly though the Apple routers have no logging now and no SNMP and almost nothing to help diagnose a problem, so if it continues .. take it back to apple.. they have given you no other method of fixing it.

  • External USB HD does not work with HAL:

    External USB HD does not work with HAL:
    From the last 10 days the HAL auto-mount with ntfs-3g file system of my external hard drive  does not woks.
    But the manual mount procedure with the command mount -t ntfs-3g /dev/sdb* /mnt/XYZ works.
    I've followed the instructions in the wiki: http://wiki.archlinux.org/index.php/HAL and the system has worked up to the last kernel or HAL update.
    My fat32 usb-stick works without any problem.
    If I try to open the device with KDE it appears an error popup wit this message:
    TODO: have to rethink extra options
    Error: kio_media_mount_helper
    The log from the kernel.log is
    Nov 6 22:03:16 myhost usb 5-1: new high speed USB device using ehci_hcd and address 4
    Nov 6 22:03:16 myhost usb 5-1: configuration #1 chosen from 1 choice
    Nov 6 22:03:17 myhost Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    Nov 6 22:03:17 myhost ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    Nov 6 22:03:17 myhost Initializing USB Mass Storage driver...
    Nov 6 22:03:17 myhost scsi6 : SCSI emulation for USB Mass Storage devices
    Nov 6 22:03:17 myhost usb-storage: device found at 4
    Nov 6 22:03:17 myhost usb-storage: waiting for device to settle before scanning
    Nov 6 22:03:17 myhost usbcore: registered new interface driver usb-storage
    Nov 6 22:03:17 myhost USB Mass Storage support registered.
    Nov 6 22:03:22 myhost scsi 6:0:0:0: Direct-Access WDC WD32 00JB-00KFA0 0811 PQ: 0 ANSI: 0
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Nov 6 22:03:22 myhost sdb: sdb1
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] Attached SCSI disk
    Nov 6 22:03:22 myhost sd 6:0:0:0: Attached scsi generic sg2 type 0
    Nov 6 22:03:22 myhost usb-storage: device scan complete
    and the error.log is
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Nov 6 22:03:22 myhost sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Do you have some idea ....
    Bye.

    I have done the following:
    Downloaded the patched hal version.
    used makepkg in /abs/local/trunk/ to create a pkg for pacman
    used sudo pacman -U pkgname to install it.
    used sudo nano /etc/hal/fdi/policy/preferences.fdi to create the fdi file with the following content:
    saved the file and removed my ntfs entryes from fstab and rebooted. and still there is no automount off ntfs partitions.
    have i done something wrong?
    br fjodork
    WARNING: what follows is a guide of what did work for me, I'm still in an early stage of learning linux, so please correct me if anything of what follows is wrong/dangerous/stupid. As I said, this worked for me, it's not pretty, since I was learning each step on the fly and I'm sure there are better ways to do this.
    So fjodork, you seem to have done the the necessary steps, though i couldn't get it to work until i first removed hal without dependencies
    pacman -Rd hal
    it will give you some warning about the dependencies, ignore  it since we are reinstalling hal in a few steps.
    First i tried to follow Raymano's link, obviously it showed me nothing in the browser so I thought it might be a broken link.
    So I downloaded the source tarball from here http://hal.freedesktop.org/releases/hal-0.5.10.tar.gz
    unpacked it changed the /tools/hal-storage-mount.c as per Milfadoodle's instructions.
    at first I tried to compile directly from source, the process would finish without a glitch though after reboot nothing changed, as if hal weren't
    installed, i guess there were issues with paths. anyway read on
    Then repacked the source in tarball, copied it to /var/abs/extra/system/hal and modified the PKGBUILD as follows
    makedepends=('pkgconfig' 'gperf')
    options=('!libtool')
    install=hal.install
    source=(${pkgname}-${pkgver}.tar.gz #removed url so makepkg looks in the current directory for the tarball
        hal
        hal-policy.patch
        cryptsetup_location.patch
        hal-0.5.9-hide-diagnostic.patch
        ntfs3g-valid-options.patch)
    md5sums=('6641c30a27c00485c6accac5110ff911' # replace with md5sum of your package's sourceball (run md5sum filename)
             '882f67668cb14a0a9e4a27ef22278027'
             '5ba8b610aa9763a5f42b9f7cbd7a86ad'
    then makepkg (i had to add --asroot, don't ask why
    and finally pacman -U hal-0.5.10-1-i686.pkg
    another reboot and everything worked without a glitch!:D (yeah i know i still haven't got rid of the reboot mentality )
    I have also put the policy files as per the wiki instructions.
    PS: I know this is a dirty way to getting things done but as i said, I'm just starting
    If anyone could comment/correct/explain this post I'd be more than happy, the automount issue was bothering me for about a month now (you'll say why do I need ntfs in the first place? well, I only recently switched for Linux as my primary OS, these are some relics of the M$ era

Maybe you are looking for

  • My Macbook pro is very slow after upgrading to Mavericks

    I upgraded to Mavericks on October 2013, since then my Mac is very slow, I have followed several suggestions in this forum, but the problem has not been fixed. Is it possible to return to Mountain Lion, my Mac had a good performace before the upgrade

  • APPRAISAL TEMPLATE

    Hi  HR Experts,  I am working on Appraisal Template and i have created template also and i want to have final result in Percentage.  How to do it.  Please let me know.

  • Itune sync with outlook calendar

    everytime itune sync with outlook calendar, a calendar folder under Outlook calendar is created. iphone only sync with the newly created blank folder therefore, nothing.

  • Unable to compile java classes in NWDS- "JSPDynPage cannot be resolved "

    Hi All, I am trying to write small JSPDynaPage when i am getting following complilation error in my Java classess. 1) "PageProcessorComponent cannot be resolved or is not a valid superclass" 2) "JSPDynPage cannot be resolved or is not a valid supercl

  • IPOD Nano works fine in Itunes, but doesn't show in explorer or My Computer

    When I first installed the Second Gen Nano, Windows explorer picked it up immediately as a drive and I could brouse all files on the Nano. My previously installed Itunes came up and stated I had to upgrade to a newer version for it to work. After ins