UME not working
Hi guys,
I have scrapped the old installation and started from scratch. did a complete OS format.
Now when i configure UME , the first test works , but the authentication test for users does not work. Just for clarity , when i put j2ee-j2e and do the test it works. but if i chose any other user which is part of the LDAP (nt login for me for example) it does not work.
Can you please tell me where we can find the traces for this test , or in fact all of UME ?
also we dont see the LDAP users imported into the DUET Java SAP system..
last time around we saw 3000 LDAP users imported into the Duet Java system
Please help
regards
shirish joshi
[email protected]
Hi Michael,
thanks again.
I have read the guides again , but am now totally confused.
I shall tell you what we are planning to do and maybe you could help. this is probably more than i should expect from a forum , but i dont know who else to ask.
1) we are planning to use the LDAP for our user store. We have a user [email protected] as the user which has read only to the LDAP. We have confirmed this using a LDAP browser.
2) We have the DUET server installed on an NT Machine (!!) with the pre-req JAVA SAP system with the SP PATCH 20 installed. This SID is J2E
3) We are planning to install the DUET ADD-ON on another NT Box with another SAP Java system installed with the patch 20. This SID is DUA (duet Addon)
4) we shall be connecting our ECC 6.0 IDES system to this DUET landscape. The ECC IDES is another box with SID IDE and this is what we shall be pretending is our production ECC system for our Demo.
With the above in view we have installed the 3 boxes. We have installeed the DUET server software on J2E and the Duet Add on from the J2E server onto the DUA (duet add on server) . The manual says that the duet add on has to be installed from the same Duet main server.
We have then been trying to configure the UME and this is where we are stuck. The connection test works , but the user id and password test dont work and we are completely puzzled.
We have chosen the right user and group path since we are using a flat LDAP Hierarchy ..so both our user and group comes to CN=USERS .....
Please let me know if you think there is some obvious mistake i am making.
I am sure i am but dont know where...hence the question
regards
shirish joshi
[email protected]
Similar Messages
-
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.
-
SAP IDM - User Sync to UME Not Working
Hi All,
Currently we're planning to implement IDM 7.1 SP05 for ESS/MSS user Password provisioning. We're done the basic configuration as per the guides and HR Employers has sync to VDS and then to SAP Master Identity Store.
Now we wanted to sync these users back to IDM UI for setup Password provisioning as per guide 'User management for the Identity Management User Interfaceu2019.
However every times we assign the PRIV:UME Role to users it called the Global Task Event 'Modified User'. However as we understand it should call Create UME User, Modified UME User or Delete UME user task and which will create users in IDM UME.
Therefore users not created IDM UME and system also does not show enough log to analyse it. We've assign correct Privilege Task under PRIV:UME and it point to Create, Modified and Delete UME task as well.
Appreciate the support on same.
Thanks.Dinesh
Thanks for the response.
But all you mentioned has been checked.
keys.ini is fine (I had a problem with that before), the provisioning option is set, all tasks are checked that they're enabled.
Simply when I assign PRIV:UME to a user a "ModifyUser" log entry appears of the corresponding (ssuccesfully) IDM user modification -> but that's it. Nothing else. Not other job log, no system log, nothing in the log of the java stack. Simply nothing. I don't know why the UME provisioning tasks are neither triggered nor ANY log entry appears. It's hard to continue analyzing when a system appears alike a black box and absolutely no informations are returned.
I also failed at several attempts to call these tasks directly/from manual created tasks.
These tasks "simply" do not react any more ..
Regards
Stefan -
Change User password not working in SAP ME 6.0
Hi,
In SAP ME 6.0 SP01 6.0.1.0 Counter 40, the activity "Change User Password" does not work for me or any other user.
The activity window (Netweaver) shows, but in the top it says "An error occurred - contact system administrator".
This is the output from the default trace file. Seems my user is not authorized, but where do I set this authorization?
Br,
Johan
#2.0 #2011 09 06 11:15:11:064#+0200#Error#com.sap.security.core.wd.jmxmodel.JmxModelComp#
#BC-JAS-SEC-UME#sap.com/tcsecumewduimodel#C0000AD3034800820000000100000450#9934850000000004#sap.com/tcsecumewdkit#com.sap.security.core.wd.jmxmodel.JmxModelComp#JONORD#16##380199ECD86811E088C3000000979802#ae0e9d52d86811e08e7a000000979802#ae0e9d52d86811e08e7a000000979802#0#Thread[HTTP Worker [@312363456],5,Dedicated_Application_Thread]#Plain##
public void supplyCompany(IPrivateJmxModelCompInterface.ICompanyNode node, IPrivateJmxModelCompInterface.IContextElement parentElement)
[EXCEPTION]
com.sap.engine.services.jmx.exception.JmxSecurityException: Caller JONORD not authorized, required permission missing (javax.management.MBeanPermission -\#getCompanyConceptEnabled[:SAP_J2EECluster="",j2eeType=UmeJmxServer,name=IJmxServer] invoke)
at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:100)
at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:101)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.checkMBeanPermission(MBeanServerSecurityWrapper.java:438)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:288)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
at com.sap.security.core.jmx._gen.IJmxServer$Impl.getCompanyConceptEnabled(IJmxServer.java:1415)
at com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.supplyCompany(JmxModelCompInterface.java:1498)
at com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.supplyCompany(InternalJmxModelCompInterface.java:710)
at com.sap.security.core.wd.jmxmodel.wdp.IPublicJmxModelCompInterface$ICompanyNode.doSupplyElements(IPublicJmxModelCompInterface.java:4301)
at com.sap.tc.webdynpro.progmodel.context.DataNode.supplyElements(DataNode.java:110)
at com.sap.tc.webdynpro.progmodel.context.Node.getElementListAsObject(Node.java:263)
at com.sap.tc.webdynpro.progmodel.context.MappedNode.createMappedElementList(MappedNode.java:78)
at com.sap.tc.webdynpro.progmodel.context.MappedNode.supplyElements(MappedNode.java:71)
at com.sap.tc.webdynpro.progmodel.context.Node.getElementListAsObject(Node.java:263)
at com.sap.tc.webdynpro.progmodel.context.MappedNode.createMappedElementList(MappedNode.java:78)
at com.sap.tc.webdynpro.progmodel.context.MappedNode.supplyElements(MappedNode.java:71)
at com.sap.tc.webdynpro.progmodel.context.Node.getElementListAsObject(Node.java:263)
at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:270)Hi,
Change User Password screen is in fact user self services screen of NW UME and to access it, user must have Manage_My_Password action. Installation and Security Guide ask to assign this action to all roles. -
SSO is not working for an Alias URL but is working for original portal URL
Hello,
We have a BSP running inside the portal and expects authentication.
When I run this BSP using the portal regular address everything is working OK and SSO is working after logging into the portal.
At next step, we have configured an alias for the portal URL at the DNS Server.
When activating the BSP from the alias URL it asks for 2nd authentication. Meaning, SSO is not working after logging into the portal.
I have activated an HTTP trace in order to see why and it seems like when running it from the alias name it recognizes it as a different domain and I assume this is why the authentication is coming up.
I would like to suppress this for the alias URL but don't know how.
I found this UME property on the server:ume.logon.security.relax_domain.level
This UME property controls the amount of sub domains to remove from the server name to obtain the domain for which the logon ticket is valid.
I have changed this property from its default value 1 to 3 (and restarted the server of course) which, in our case, leaves only ourCompany.com for the ticket in the original server URL. Yet, the authentication pop up is still not supressed when browsing through the alias URL.
Any idea what can I do next?
Thanks,
RoyHi Dezso,
I found the 401 let me know if I look on it right:
I have an entry node with two subnodes: request and response.
The response has:
<responseStatus>HTTP/1.1 401 Unauthorized</responseStatus>
And the request before that doesn't have any MYSAPSSO2 in it, all it has which is related to cookies is this:
<header name="Cookie">UserUniqueIdentifier=1174345919524; alreadyLogged=1179560552416</header>
<cookies>
<cookie name="alreadyLogged">1179560552416</cookie>
<cookie name="UserUniqueIdentifier">1174345919524</cookie>
</cookies>
Can you advice what to do next? -
SAML / OIF integration does not work - Could not extract SAML2 message
Hi gurus,
We are trying to establish SSO between SAP Portal 7.3 and OIF 11.1.5 (Oracle Identity federation). I configured SAP Portal as service provider and OIF is also configured. I changed Login Module and add SAMl as on top of my default auth stack. When we try to do end-to-end test is does not work and throws the following error:
Default SAML2 configuration is selected because login module option [provider] is not configured.
SAML2LoginModule is running in execution mode DEFAULT.
SAML2Principal not found in current client context.
Exiting method
Entering method
SAMLResponse: PHNhbWxwOlJlc3BvbnNlIHhtbG5zOnNhbWxwPSJ1cm46b2FzaXM6bmFtZXM6dGM6
<BR>U0FNTDoyLjA6cHJvdG9jb2wiIERlc3RpbmF0aW9uPSJodHRwczovL2ppZXB0ODIu
<BR>dWsuY2VudHJpY2FwbGMuY29tOjgxODIvc2FtbDIvc3AvYWNzIiBJRD0iaWQtVVRW...........................
Decoded SAMLResponse: <samlp:Response mlns:samlp="urn:oasis:names:tc: 4 пїЅГЈ"пїЅ пїЅ &пїЅFпїЅ6пїЅпїЅ" FW7FпїЅпїЅ.......................3E&saml2post=false
Could not extract SAML2 message from request.
[EXCEPTION]
java.lang.SecurityException: com.sap.security.saml2.lib.common.SAML2Exception: SAML parsing failed..................
No user name provided.
Entering method
Automatic IdP Selection mode configured for the Service Provider
POST parameters set as HTTP request attribute [sap.com/login_post_parameters] to be re-submitted during login: [SAMLResponse, SAMLart, RelayState]
Could not remove original application URL cookie because the provided name is invalid: <null>
Exiting method with true
LOGIN.FAILED
User: N/A
IP Address: 10.11.11.11
Authentication Stack: ticket
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.saml2.sp.SAML2LoginModule REQUIRED ok exception true Service Provider could not extract SAML2 message from request.
#1 AcceptedAuthenticationMethods = *
#2 Mode = Standalone
2. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false true
#1 trusteddn1 = CN=ERT,OU=I0020100174,O=SAP Web AS
#2 trustediss1 = CN=ERT,OU=I0020100174,O=SAP Web AS
#3 trustedsys1 = ERT,010
#4 ume.configuration.active = true
3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok false false
4. com.sap.security.core.server.jaas.CreateTicketLoginModule OPTIONAL ok false true
Decoded SAMl response looks strange with all non-readable characters and as a result, there is no username passed to the portal and SAML login fails and portal offers a fall-back login with username/password
Also, can you please comment the line from the help.sap.com (http://help.sap.com/saphelp_nw73/helpdata/en/bf/b0b879544740c8a3c8bdda87e50587/frameset.htm)
"Prerequisites for SAML
"Your service provider must be able to reach the identity provider over HTTP or HTTPS." "
We have our identity provider / service provider in two different segment of the network and there is no http/https connection between these segments as we assumed that all the communication is going through the browser and we would not need the port to be opened on the firewall. Is it something which is absolutely necessary? In our opinion it negates all the benefits of SAML
Help will be very much appreciated
Many thanks in advance,
Regards, ElenaHi Elena,
The issue was discovered and fixed during the SAML Interoperability Tests early last year (2011). I'm not sure I will be able to find a dedicated note because the fix was not downported but just submitted in the latest SP in correction. If you need a justification then you can open a support ticket with SAP and this will be the official answer there. If you do so please to not forget to attach traces from the system - use the tool described in 1332726 with type "SAML 2.0 (Info)". If you send me the ticket number I can speed-up the processing of the ticket.
Regards,
Dimitar -
ADS does not work.(Service call exception)
Hi All,
According to SAP note 937697 "Usage of SAP NetWeaver BI Diagnostics & Support Desk Tools", when running the tool, it gives following error:
ADS does not work.(Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://sapbwd.ni.ad.newsint:50000/AdobeDocumentServices/Config?style=document")
I have been looking into system to find out how to solve the issue, but could not, is there anyone who can help me with exact instructions what I do need to do.
Thanks in advance
sahmadDear Sahmad,
I would suggest you to check notes 1004321 and 944221. The first one says that mostly of this kind of issues (and I have already seen several ones) is caused for bad passwords for user ADSUSER or this account expired. The second note is a troubleshoot note you can also do.
You can also follow this procedure to check that:
Please open the Visual Administrator and browse to Server -> Services -> Security Provider -> Policy Configurations
In the Components tab you will see the service.destinations policy. Click on this and then click on the AccessDestinations security Role. Modify this and add the J2EE_ADMIN/Administrator user to this role and save.
Maybe the password is not set correctly as well. I think it worths to be set it again. First you have to identify where your ADSUSER maintained.
Go to http(s)://<SERVER>:<PORT>/useradmin search for ADSUSER If Datasource:
- LDAP -> check psw of ADSUSER in LDAP and enter it in SM59
- UME data -> check psw of ADSUSER in Visual Admin and enter it in SM59
- ABAP -> check psw of ADSUSER the ABAP system in the following client:
Visual Admin->UME Provider->Properties->ume.r3.connection.master.client
If you want, also, you can change the ADS by the SAP Export Library, as per SAP Note 1112132. It is very simple to activate and will bypass ADS, doing every function ADS does.
I hope it helps.
Kind Regards,
Marcio -
J2EE and user authentication not working
Hi,
has anyone gotten the basic/form based authentication to
work in the latest version of the 9iAS?
Oracle9iAS (9.0.2.0.0)
I've read all the posts and articles from orionsupport.com
BUT it still does not work.
Support Folks from ORacle: Where is the latest documentation
for the Server ???? Everything seems outdated??
cheers,
VijayHi,
You can change User and password through SU01 through UME. and also read SNote: Note 891614 - Login problems / Expired password
Regards
Thomas -
Hello All,
FPN in portal 7.3 is not working. Please advice.
Errors found in logs -
1.
Could not validate SPNEGO token.
[EXCEPTION]
com.sap.engine.services.security.authentication.umapping.UserMappingNoSuchUserException: No user with account attributes [[namespace=com.sap.security.core.authentication, name=principal, value=vs-sys45.IBM-ERP, isCaseSensitive=false], [namespace=com.sap.security.core.authentication, name=realm, value=ALJAZEERA.TV, isCaseSensitive=false]] found
at com.sap.engine.services.security.authentication.umapping.UserMappingServiceImpl.getUserByAccountAttributes(UserMappingServiceImpl.java:184)
at com.sap.security.core.server.jaas.spnego.util.SPNEGOUserMappingUtil.searchUser(SPNEGOUserMappingUtil.java:82)
2.
Could not validate SPNEGO token.
[EXCEPTION]
java.lang.Exception: Store of token in replay cache failed. Possible replay attack detected.
at com.sap.security.core.server.jaas.spnego.krb5.KrbApReq.throwValidationException(KrbApReq.java:125)
at com.sap.security.core.server.jaas.spnego.krb5.KrbApReq.validate(KrbApReq.java:118)
at com.sap.security.core.server.jaas.SPNegoLoginModule.validateSPNEGOToken(SPNegoLoginModule.java:323)
at com.sap.security.core.server.jaas.SPNegoLoginModule.processAuthorizationHeader(SPNegoLoginModule.java:504)
at com.sap.security.core.server.jaas.SPNegoLoginModule.login(SPNegoLoginModule.java:154)
at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:254)
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:66)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:269)
at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:876)
3.
LOGIN.FAILED
User: N/A
IP Address: 10.234.11.20
Authentication Stack: ticket
Authentication Stack Properties:
Login Module Flag Initialize Login Commit Abort Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false true
#1 ume.configuration.active = true
2. com.sap.security.core.server.jaas.SPNegoLoginModule OPTIONAL ok exception true Trigger SPNEGO authentication.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule SUFFICIENT ok false true
4. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUIRED ok false false
5. com.sap.security.core.server.jaas.CreateTicketLoginModule REQUIRED ok false true
4. Can't map exception.
[EXCEPTION]
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:131)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:269)
at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:876)
Caused by: javax.security.auth.login.LoginException: NTLM token received in authorization header.
at com.sap.security.core.server.jaas.SPNegoLoginModule.failedAuthenticationException(SPNegoLoginModule.java:369)
at com.sap.security.core.server.jaas.SPNegoLoginModule.checkAuthorizationHeaderToken(SPNegoLoginModule.java:463)
at com.sap.security.core.server.jaas.SPNegoLoginModule.parseSPNEGOToken(SPNegoLoginModule.java:282)
at com.sap.security.core.server.jaas.SPNegoLoginModule.processAuthorizationHeader(SPNegoLoginModule.java:484)
at com.sap.security.core.server.jaas.SPNegoLoginModule.login(SPNegoLoginModule.java:154)
at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:254)
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:66)
... 59 more
Have investigated a lot since last 3 days, tried many possible solutions but they are not working like to mention a few,
SAP Note # 1649110, http://scn.sap.com/people/holger.bruchelt/blog/2010/04/08/new-spnego-login-module--just-around-the-corner,
http://scn.sap.com/people/holger.bruchelt/blog/2008/01/09/configuring-and-troubleshooting-spnego--part-1
Please advice.
Thanks a tonne,
RituHi Ritu
Could you check this SAP Notes
1679902 - java.lang.NumberFormatException: multiple points in SPNego
1732610 - SPNego ABAP: Troubleshooting Note
1783663 - SPNego Authentication based relogin failed
Regards
Sriram -
EHP4 installation using EHPI : Error message: DDIC password does not work:
Dear All,
We are upgrating enhancement packages 4 using EHPI in 64 bit server. I am facing this error in Extraction phase , I have to provide DDIC / SAPServiceSID/ DB specific , next says ddic password is not correct. But when i tried to login with the same password into 000 client, it works. But when through EHPI , it throws error. Kidnly check the error and please suggest me ... Thanks in advance..
Error message: DDIC password does not work: RFC call to failed with key RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed Connect_PM DEST=R3D, GWHOST=SAPRBSBD-01, GWSERV=sapgw00, SYSNR=00 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner 'SAPRBSBD-01:3300' not reached TIME Thu Dec 24 12:27:13 200 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 3147 DETAIL NiPConnect2: 192.168.1.40:3300 SYSTEM CALL connect ERRNO 10051 ERRNO TEXT WSAENETUNREACH: Network is unreachabl.
Regards
RajDear Rajeev,
DDIC pwd for 001 is not same as 001,Will that be a problem ? But the Extraction requests for DDIC 000 client password. Are you sure UME comes into this scenario ?
@ Raghu - I have checked the link and it speaks about the resetting the EHPI. I dont want to reset and want to solve ddic password error.
Sorry if am wrong
@ Gerard,
Yes the hostname is SAPRBSBD-01.I am able telnet the IP 3300 and it works fine. FQDN SAPRBSBD-01.chen.local. The smicm service entries are with SAPRBSBD-01 but not with FQDN. Changing it to FQDN will help us to resolve the issue. Please suggest me.
Also the error refers to some RFC connection, any idea on that.
Thanks to all and looking for your valuable suggestions.
Raj -
User index not working as expected..
Hi all,
we have a ldap to which two instances running on two diff boxes are connected, there are approx 4000 users and all these users show up in instance one but for some strange reasons only 1000 odd users show up in instance two, ldap has been configured accordingly for maxhits....the ume index on the instance two was deleted and recreated but has not solved the prob...instance one is ep6 and instance two is ep7.0 ? can anyone who knows what might have gone wrong throw some light on this please ?
thanks in advance,
Anupama.Thanks for the reply Scott, I have just had one of those Homer Simpson Doh! moments. I was copying the code into this post and then realised that I was actually using the value of the username item that has changed in the first parameter which attempts to get the userid:
htmldb_util.edit_user(
p_user_id => htmldb_util.get_user_id(UPPER(:P18_USER_NAME))
,p_user_name => UPPER(:P18_USER_NAME)
,p_web_password => x_default_pw
,p_new_password => x_default_pw
,p_developer_roles => x_developer_privs
,p_group_ids => x_group_ids);
and quickly realised that this would not work as it was a value that could have been modified. so I created a new hidden item to store the original and modified the call to:
htmldb_util.edit_user(
p_user_id => htmldb_util.get_user_id(UPPER(:P18_ORIG_USER_NAME))
,p_user_name => UPPER(:P18_USER_NAME)
,p_web_password => x_default_pw
,p_new_password => x_default_pw
,p_developer_roles => x_developer_privs
,p_group_ids => x_group_ids);
and it works as expected.
Thanks for your help.
Stuart -
Hi...
I'm trying to use SSO between portal (jCo, webdynpro...) and ABAP System...
I follow "Single Sign-On in a Complex System Landscape" tutorial, but when I try to test any jCo connection, this error appears to me:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to enrich connection properties
And following logs, I can see this error:
Cannot provide X.509 certificate of user "Silva, Jose" (unique ID: "USER.PRIVATE_DATASOURCE.un:123456") because of an unexpected UME internal problem. (Backend system: "UMESystemLandscapeDummy")
[EXCEPTION]
com.sap.security.api.umap.NoLogonDataAvailableException: This user does not have a certificate.
at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:412)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.createPool(AbstractJCOClientConnection.java:346)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.checkPoolEntry(AbstractJCOClientConnection.java:296)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.getClient(AbstractJCOClientConnection.java:396)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.onActionTestConnection(JCOConnectionsDetails.java:229)
at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdInvokeEventHandler(InternalJCOConnectionsDetails.java:303)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
I don't know what to do...
My portal certificate has a problem, or is my abap certificate?
Thanx...
(sorry for my poor english)Hi,
If you are working with JCO's please make sure that SSO will not work for metadata jco creation.
use the UID PWD method as part of metadata jco creation.
it will work fine
this messege as per my knowledge, may be helpfull for you -
SLD connection user/password not working.
Hello friends,
I am new bee in SAP Netweaver.
I installed SAP Netweaver for java.
Now I want to connect it with BAPI from SAP.
so, some where i am sucked with SLD. I opened Visula Administrator and nothing there to connect.
I also tried http://localhost:50000/sld but my user/password not working.
1. What to do to see/get username/password for SLD?
2. How to connect netweaver to access SAP ZBAPI?
Regards,
RHHello friends,
I am new bee in SAP Netweaver.
I installed SAP Netweaver for java.
Now I want to connect it with BAPI from SAP.
so, some where i am sucked with SLD. I opened Visula Administrator and nothing there to connect.
I also tried http://localhost:50000/sld but my user/password not working.
1. What to do to see/get username/password for SLD?
2. How to connect netweaver to access SAP ZBAPI?
Regards,
RH
Hi Ronny.
Where is your UME running? On the java engine, on an ABAP system or at a LDAP?
What i want to say is that your user has to gain the rights to connect to the SLD. Easiest way is to give you admin rights - to do that you have to know where your userstore is running....
I am not sure if this is correct http://localhost:50000/sld
Normally it should look like http://my.sap.com/56600/sld where my.sap.com is a fqdn and 56600 is the port of the java engine. 66 ist the system number of the as java.
ZBAPI? I do not really know but i think you have to use a jco to connect...
regards,
Martin -
Automatic Deployment not working on Activation
Hi Experts,
I am using CE 7.1 developer studio, and NWDI set up.
Please see the steps that i have mentioned below...
I have a track which is containing a single DC of type WebDynpro, This DC is containing one view with a textView UI element with the text property "Hello World"
I have followed the below sequence of steps...
1) Import the development confuguration (Track) from the SLD into developer studio using the User ID1. (This ID has NWDI.Administrator UME Role assigned, as well as Administrator UME role assigned.)
2) Sync / Create Project (This will create a project structure and get the Inactive source from the DTR to my Local Machine)
3) goto the webdynpro perspective edit the view and change the text property to "Hello World has Change...!"
4) the above step will result in Creation of an activity.
5) Now I Save the changes and build the DC. (Please note that I have just built the DC, not deployed it).
6) From the Development Infrastructure Perspective Checkin the activity that was created from "Open Activities" view.
7) From the "Activation View" activate the activity that was "checked in" as mentioned in the previous step.
8) Activation process gets completed successfully.
Now Ideally, if I run the application it should reflect the last modified changes.
that is it should show "Hello world has changed",
But unfortunately it's not, it is showing the non modified version "Hello World"
According to standard NWDI activation process...
when the changes are activited...following sequence of steps are carried out.
1) Store the Sources into "Inactive Workspace" in DTR.
2) DTR Sends build request to CBS.
3) CBS will collect new objects from Inactive workspace as well as existing objects from Active workspace and builds the Sources.
4) After the build is successful, CBS will deploy the archives to central J2EE system, and store the sources in Active Workspace.
Additional Information: Now if delete the track and load the same track again,
it brings the correct modified source code with "Hello world has changed...!"
In both sycn Active Source and Sync Inactive Sources
This means that modified sources are getting checked in properly into both the Active and Iactive workspace but not getting deployed on activation.
Please someone help me understand why automatic deployment is not working on Activation?Hi there,
deployment in DEV and CONS works asynchronous. this means a request is not immediately deployed after the request is build. A successful build can although mean that there was a deployment error. So sometimes you jsut have to wait a couple of minutes for your changes to be deployed.
When creating a track or deleting a runtimesystem and reconfiguring it. NWDI tries to sync the track and the runtimesystem immediately.
So I would suggest to check this as follows:
- After the request finished successfully in CBS open CMS Gui and navigate to the DEV tier of your track in transport studio.
- there is a button "deployment" (second from the right) hit it...
- a window with the deployment details of the tier will open. here you can see if a queue is still pending. you can check when the DC was deployed last time. and you can initiate a deployment of the queue here to. But this will not always lead to a immediate deployment.
- Here you can check if there have been deployment erros (rc >4)
So here you can get some clues on what is going on. Usually deployment fails because NWDI cannot reach the runtime system or the user/password is wrong. Yo can check if the system is accessible by nwdi by getting the dubstitotion parameters of the system. You can find the line: View/Edit Deployment Substitution Variables at he bottom of every systems overview. At the right of this line is a button. if you press it and some variables should be shown. Nwdi can access your system for deployment. If not in the upper left an error message will be shown.
Let us know what your results are
Have a good time
Jan -
Not work tablet UI on Prestigio 5080 PRO tablet
I read that browser.ui.layout.tablet = "1" can fix this problem. But it not works. I can work only in pnone interface that is not good for my 8'' tablet.
Would it be possible for you to share the problematic pdf and OS information with us at [email protected] so that we may investigate?
Thanks,
Adobe Reader Team
Maybe you are looking for
-
Need to add tables in the pricing report(V/LB)
Hi I want to add some table in the existing pricing report.But I am unable to do so. My requirement was to add some new selection field in the Pricing report which is possible by adding the table in the existing pricing report. But I found If I go to
-
Crystal Reports for Visual Studio 2008 - dbf
Hello, I use both Visual Studio 2005 and 2008 on same PC. I can not work with dbf files (format foxpro2x, dbase IV) in VS 2005 and VS 2008. Q1. Work Crystal Reports for Visual Studio 2008 with database files - dbf (version foxpro2x, dbaseIV)? I get e
-
Importing Word Documents with Images
Hi, When I import word document in to Robohelp, it imports the images also. Now, I have duplicate images in multiple topics. How do I avoid duplicate images being imported? Is there anyway, where I can collate and store all the images in a single fol
-
Cluster shared volume disappear... STATUS_MEDIA_WRITE_PROTECTED(c00000a2)
Hi all, I am having an issue hopefully someone can help me with. I have recently inherited a 2 node cluster, both nodes are one half of an ASUS RS702D-E6/PS8 so both nodes should be near identical. They are both running Hyper-V Server 2008 R2 hosting
-
Hi All, Currently I am working on Human work flow activity, where my requirement is ,I will be sending 'creator' through request.aslo i ll be using getManager() fuction in Human WorkFlow Activity. ids:getManager(/task:task/task:creator) my payload is