Analysis authorization not working on WAS server

Does BI Java required for Analysis authorization to work ?
Can we manage with WAS server to show analyis authorization ?
Actually we don't have BI java configured in our system...so we are executing the query on WAS server ( BI ABAP).....but on this we are not able to see analysis authorization working....system is showing all the possible values and not the authorized value in AA.....
Regards
Tripple k

Jason
1. 0BI_ALL is not assigned to the user.
2. I have already set the Authorization scheme as "New analysis authorization" in SPRO.
3. i am executing the report from T-Code RSRT
    A> Select the report and click on ABAP Web ( Choose query display as List or Analyzer or HTML) - System is showing entire orgunit while it should show only 3 org unit   assigned to user in RSECADMIN.
   B> Select the query and execute on Java Web - Error in connectin as BI java is not there on portal side
   C> Select the query and choose Query Display as "HTML" click on Execute button - Only 3 values restricted in RSECADMIN are appearing.
Hope somebody can throw some light on this.
Regards
Tripple k

Similar Messages

Analysis Authorization not working - Empty demarcation

Can someone help me on this Analysis Authorization? I read many threads in SDN, it seems that I followed the correct steps. The restriction on S_RS_COMP is working well but the restriction on the Analysis Authorization is not working. Surely I'm making some mistake, but can't find what's wrong.
I'm a User (say USER_00) in a test system, assigned to a Role (say Z:BI_USER). This is a broad role:
- S_RS_COMP and S_RS_COMP1 have full authorization (*) to all the fields,
- S_RS_AUTH has the BIAUTH field with Name of Authorization = *.
Also I have an InfoArea (ZIA_TEST) and an InfoCube (ZIC_TEST). The IC has some characteristics and key figures. The only authorization relevant characteristic is ZCA_CLI (client). The IC has only 5 lines, one for each client ("CLI_01" to "CLI_05").
Also there's a query (ZQR_TEST) on this IC, with an Authorization Variable (VAR_AUTH_CLI) restricting the characteristic ZCA_CLI.
I'm trying to create a new User and restrict him to this IC and only to the data of client "CLI_01". If it works I'll apply to a production system.
What I did:
1) With tcode SU01 created a new User (USER_01) with no Role neither Analysis Authorization.
2) With tcode PFCG copied the Role Z:BI_USER as Z:ROLE_TEST then made some changes:
a) S_RS_COMP
- Activity = 03 and 16
- InfoArea = ZIA_TEST
- InfoCube = ZIC_TEST
- Type of report component = *
- Name of report component = *.
b) S_RS_COMP1
- Kept * to all fields.
c) S_RS_AUTH
- I inactivated and deleted this Authorization Object.
(I don't want to keep characteristic values restriction inside the role. The idea is to associate different users to the same role, allowing them to see the same ICs and execute the same queries. And differentiate wich characteristic values each one can see by manually associating different analysis authorization to each one.).
3) With tcode RSECAUTH I created an Analysis Authorization (Z_AA_CLI_01) to restrict access only to client "CLI_01":
- ZCA_CLI = "CLI_01"
- 0TCAACTVT = "03"
- 0TCAIPROV = "ZIC_TEST"
- 0TCAVALID = "*".
4) With tcode PFCG I assigned User "USER_01" to the Role " Z:ROLE_TEST" and made Complete Comparison.
5) With tcode RSU01 I manually assigned Analysis Authorization " Z_AA_CLI_01" to User "USER_01".
It seems to me that these steps are enough. But:
a) When I log as USER_00 and go to tcode RSRT2, searching by InfoAreas I can see all the InfoAreas and all the InfoCubes, select and execute the query. That's OK.
b) When I log as USER_01 and go to RSRT2, searching by InfoAreas I can see only ZIA_TEST and under it I can see only ZIC_TEST. That's OK. Then I select and execute the query.
Wich means that S_RS_COMP is OK and each user is assigned to the correct Role.
c) The problem is that in both cases the query brings data from all Clients.
Under Information and Variable Values (when I run with HTML display) the message is "Empty demarcation".
I changed the variable to be Ready for Input, just to see wich values it brings. In both cases (as USER_00 and as USER_01) in the Variable Screen it brings all the 5 Clients from the IC and I can select and execute any value.
So the problem is with the Analysis Authorization or with the Variable, but I can't find what's wrong.
Any help will be very appreciated.
César

OK Marc, it worked.
Sorry for not answering earlier, but I could get back to this front only some days ago, then began testing your suggestions.
1) Security Concept
Authorization Mode was set to "Obsolete Concept with RSR Authorization Objects" (it would never work with this setting).
I changed to "Current Procedure with Analysis Authorizations".
Anyway, what's the function of this setting? Do old Reporting Authorizations work with "Current Procedure with Analysis Authorizations" setting?
2) Variable Representation
With "Multiple Single Values" it really led to problems.
With "Selection Option" it worked well.
3) 0TCAKYFNM
I don't understand why, but if the AA doesn't have the char/dimension 0TCAKYFNM, when the User tries to run the query (tcode RSRT2) it accuses "You do not have sufficient authorization".
Info Cube ZIC_VE95 has two KFs (ZKF_QTL95 and ZKF_VLT95). These KFs are used only on this IC (also in the KF Catalog, but it doesn't impact). This IC is used only on Query ZQR_VE95 (also in Transformation and DTP, wich doesn't impact).
Well, I inserted 0TCAKYFNM and it worked, either with CP, "*" or with EQ, the two KFs.
4) Authorization Policy Definition
The situation I'm working on is very typical. Ex.: Some users are Administrators, Managers, Operator 1, Operator 2 and so on. Each Role needs authorization to access some queries. At the same time, they can access information only of the Cost Centers to wich they are related.
There are many ways to implement it (I tested some of them and they worked well). My point is to define a most practical way, easy to understand and to maintain.
I'm now sympathetic to this way:
a) Create functional Roles (ex.: "Administrator", "Manager", "Operator 1", "Operator 2" and so on) defining only the Queries (or Info Areas, Info Providers, etc) each Role needs. No S_RS_AUTH definition.
b) Create Char Value Roles (ex.: "CC_100_to_199", "CC_200_to_299", etc), only with S_RS_AUTH definition, each one associated with a corresponding AA (ex.: AA for CC 100 to 199, AA for CC 200 to 299 and so on).
c) Create Composite Roles associating functional and char value Roles. Ex. Composite Role "Administrator for CC 100 to 199", composed of the Roles "Administrator" and "CC_100_to_199".
d) Associate Users to the Composite Roles.
Anyway, I'd appreciate if you could indicate some literature (blogs, articles, etc) on this theme.
Well, thank you very much for your answers. Now I can go on with my studies on this subject.
César Menezes

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.

EXEC SP_EXECUTESQL not working in sql server 2014

EXEC SP_EXECUTESQL not working in sql server 2014

EXEC SP_EXECUTESQL not working in sql server 2014
Hi Amar,
What's the error when executing this stored procedure?
I have tested it on my local environment, we can run this SP without any problems.
Please provide us more information, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Addon not working on Windows Server 2008 OS

Dear Friends,
I have developed an addon in XP and its working fine with XP operating system but it is not working on Windows Server 2008 Standard. Error is "An Attempt was made to load a program with an incorrect format.(Exception from HRESULT: 0x8007000B)".
Regards,
Mahesh.
Edited by: mahesh A on Sep 19, 2009 9:26 AM

Hi,
Since only Windows 2008 SBS is supported with SAP Business One and that Server is available for 64bit Hardware as defined by Microsoft, I guess you should look into that direction.
Regards
Mario

Group Chat feature in Office Communications Server 2007 R2 does not work in Windows Server 2008 R2 domains

   Hello to all, there are two confliting articles about this topic:
   1-
http://technet.microsoft.com/en-us/library/upgrade-domain-controllers-to-windows-server-2008-r2(v=ws.10).aspx#BKMK_Whatsnew : this one says that it does not work "The Group Chat feature in Office Communications Server 2007 R2 does not work in Windows
Server 2008 R2 domains". This article was updated in 2013.
   2-
http://technet.microsoft.com/en-us/library/ee692314(office.13).aspx: this other article says that it will function "Office Communications Server 2007 R2 Group Chat will function in a Windows Server 2008 R2 forest". This article was updated in
2010 and was refered by the first one.
   What is the correct support position for Group Chat feature in Office Communications Server 2007 R2 and Windows Server 2008 R2 domains?
   Regards, EEOC.

Hi,
I notice the following sentence in the link below “Office Communications Server 2007 R2, Group Chat will not function in a Windows Server 2008 R2 forest or when Group Chat member servers are joined to a Windows Server 2008 R2 domain.
We know of an issue with changes in Windows 2008 R2 that requires a Group Chat Client and Group Chat Admin Tools hotfix. The Group Chat Client and Group Chat Admin Tools hotfixes are currently scheduled for mid-April 2010.”
http://blogs.technet.com/b/nexthop/archive/2010/11/06/supportability-for-office-communications-server-2007-r2-and-windows-server-2008-r2.aspx
So in my opinion, if you update to the latest version of Windows Server 2008 R2, OCS Server 2007 R2 and Group Chat Client, Group Chat Admin Tools to the latest version, it should work.
However, the best method for you is make a lab to test the problem firstly.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Database Mail not working with SQL Server Agent

I'm running SQL Server 2005 Standard edition 64 bit with SP2 on a 64 bit machine.
Database mail does not work with SQL Server Agent. When I configure SQL Server Agent to use database mail the test email button is greyed out and inactive therefore I cannot send emails using operators or for jub success failure etc.
I've read that there was supposed to be a fix for this with SP1 but I have SP2 and still receive the same problem. Please can somebody help as I do not wish to use SQL Mail as a work around due to this becomming redundant in future versions of SQL Server.
Kind Regards

The problems solved
steps:
1)we create a mail profile at at Managment->Database Mail ,of SQL Managment
2)we set this account as "default" at Managment->Database Mail -> Configure Database Mail -> Manage profile security
3)At tab "Alert System" of SQL Server Agent properties , we check the "Enable mail profile" , Mail System=Database Mail, Mail profile = "the profile we already create"
4)we create a new operator at "Operators" of sql agent, where at "notification options" -> "Email name" we put the mail where we want to sent the agent the mails at failured job
5)We go at a specific job, at tab "Notifications" ,we check the "email" check box and then we choose the operator we just create, at the text box next to check box.
I hope not to forget something
Thank You all for the help

Web Service Client(Console App) not working on Windows Server 2008 R2 Standard Edition

I am trying to consume an ASMX Web Service in a console app, its working fine in Windows 7,Windows Server 2012 Standard,Windows Server 2008 R2 DataCenter,Windows Server 2008 R2 Enterprise, But its not working in Windows Server 2008 R2 Standard Edition which
is the deployment server.
I tried consuming the ASMX web service using Web Reference and Service Reference as well but its not helping. Its throwing up the following error,
Message:There is an error in XML document (1, 331491).
Inner Exception : System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 331491.
The scenario is that i call the web service and it returns me an XML i am not able to receive the XML on Windows Server 2008 R2 Standard Edition.
Please provide suggestions on this I need to resolve this ASAP.

Hi,
This question is better asked here:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=asmxandxml
Experts here are more familiar about it and they can give you more efficient suggestion.
Thank you.

Oc4jadmin not working for application server control in SOA suite 10.1.3.1.

Hi,
We have installed the SOA suite, and I can login to the various components using oc4jadmin/password (bpel, esb, rules author), but for some reason that oc4jadmin password is not working for Application Server Control, which is the only piece of this I really need to log in to.
Any thoughts on what is going wrong?
Cheers,
Pat Rock

Maybe you change this password internally for another application (such BPEL, WSM,etc) and didn't make change for your main OC4J container.
You can try to change this password by...
1. Open the file [OASHome]\j2ee\home\config\system-jazn-data.xml
2. Find the section that looks like this
[user]
[name]oc4jadmin[name]
[display-name]OC4J Administrator[display-name]
[guid]88836370D11611DC9F30F9C1CD6F1A73[guid]
[description]OC4J Administrator[description]
[credentials]{903}F+iG1A46edXG9RdfY0pD2O4Ge/qyEjsg[credentials]
[user]
3. Replace the value separated by the "Credentials" starting and ending tags with your new desired password, prefixed with an exclamation point
Example:
[user]
[name]oc4jadmin[name]
[display-name]OC4J Administrator[display-name]
[guid]88836370D11611DC9F30F9C1CD6F1A73[guid]
[description]OC4J Administrator[description]
[credentials]!newpassword[credentials]
[user]
4. Save the file and restart OAS
This should not affect other applications.
Greetings.

Hi I have iphone 4s and my Bluetooth and wifi do not work. it was working before and I did not do any update for IOS or anything but it just happened. what I should I do to resolve this?

Hi I have iphone 4s and my Bluetooth and wifi do not work. it was working before and I did not do any update for IOS or anything but it just happened. what I should I do to resolve this?

Hae you tried to do a hard reset of your phone? This will not lose any data. Hold the sleep/wake button and the home button until the phone turns off ignoring any slide to power off messages. Then power the phone back on.

IPhoto -share to email not working-The email server didn't recognize your username/password combination- for hotmail and big pond- since apple technical support re-hotmail on iPhone.

iPhoto -share to email not working-The email server didn’t recognize your username/password combination- for hotmail and big pond- since apple technical support re-hotmail on iPhone.

in the iPhoto preferences ==> accounts delete your e-mail account and reenter it
OR
IMHO the better solution is to set Apple mail as the email client in the iPhoto preferences
LN

[CS5 Server/JSX] allGraphics parent geometricBounds not working on InDesign Server

Hi,
The following script works fine on InDesign Desktop CS5:
g = app.activeDocument.allGraphics;
for (i=0; i<g.length; i++)
g[i].parent.geometricBounds = [0,0,"150mm","150mm"];
g[i].fit(FitOptions.PROPORTIONALLY);
g[i].parent.fit (FitOptions.FRAME_TO_CONTENT);
When I run the script for InDesign Sever I get the following error:
Error Number 30614
Invalid object for this request,
g[i].parent.geometricBounds = [0,0,"150mm","150mm"];
Why does .parent not work on the server?

g = myDocument.allGraphics;
for (i=0; i<g.length; i++)
g[i].parent.geometricBounds = [0,0,"150mm","150mm"];
g[i].fit(FitOptions.PROPORTIONALLY);
g[i].parent.fit (FitOptions.FRAME_TO_CONTENT);
if(myDocument.textPreferences.smartTextReflow)
vDoc.recompose();
The solution!
Recompose() to automatically insert pages

Web Analysis is not working

Hi,
I recently installed Hyperion BI+ in my server and I'm trying to do some reports in Web Analyzer.
My installation and configuration went successfull.
I can open FR, IR ..
I'm trying to open WorkSpace and Web Analysis...
both are not working...
When Im trying to open web analysis using the below URL Im getting error..
http://<servername>i:19000/WebAnalysis/WebAnalysis.jsp
but when I'm using this URL http://<Servername>i:16000/WebAnalysis/WebAnalysis.jsp
I can see the open page.. but the Web Analysis window is not coming.. I'm getting blank page...
and for workspace also.. when I'm using 45000 port.. it is working but I cannot open any reports.. some debug error is coming..
when I'm using the default port 19000.. Im getting network error...
Please help me in this issue..
Do I need to do any modifications in my configuration or property files....
my Java application is Tomcat(default).. databases is Oracle 10G Enterprise Edition.

Hi,
Regarding Web Analysis- I believe- It's a problem of JRE.
- Just remove/uninstall the JRE from your Currently installed Programs. You may want to reboot the m/c
- Open Web Analysis Studio in the Web browser. Now, since it can't find JRE, it'll set up the relevant JRE for you & you may continue using Web Analysis.
- Please note- Unless you've changed to a different one during configuration, Web Analysis operates on 16000 port.
Check the following regarding Workspace-
- Your service may be down, thus, throwing Network error
- You may've to re-configure Workspace. Start the service & wait for few mins. before opening Workspace.
- Natesh

MFA not working on Windows Server 2012 R2

Been using MFA since PF days. Deployed it successfully many times but for some reason it's not working with Windows Auth, Terminal Services on a Win 2012 R2 DataCenter box? The machine was successfully added to my domain PhoneFactor group, I
can see and add the machine on the master MFA. Services are running but when I remote in I go right through without MFA stopping me? Any ideas?
TIA

6.3.0 has just been released and 2012 R2 is *still* not supported. What the hell?!?
"Version 6.3.0 of the Azure Multi-Factor Authentication Server adds the
following additional functionality:
* Added one-way SMS functionality for AD FS, RADIUS and User Portal
* Added .csv file import for OATH tokens
* Added support to parse phone numbers in E.164 format during import
From the directory
* Fixed problem preventing slave servers from performing MFA if the
master server was unavailable. This problem was found to exist in
all 6.2.x builds. All customers running 6.2.x should upgrade to 6.3.
* Fixed directory sync issue for recursive security groups
* Added additional logging to AD FS adapter
* Other minor bug fixes and security improvements
Known Issues:
* Windows Authentication for Terminal Services is still not supported for
Windows Server 2012 R2"
So they added a whole stack of other functionality, but still didn't get around to taking a look at this bug. I'm stunned. Is there any sort of timeline on fixing this, or is 2012 R2 just going to remain unsupported forever?

Web Analysis functions not working in Workspace

I am looking for a list of Web Analysis functions that are available in the Java client that will not work in the Workspace DHTML client (Version 9.3.1.0). Any guidance would be appreciated.

There are 4 types of differences:
- font differences, Workspace (DHTML) uses the WA Server fonts whereas WA Studio client machine fonts.
- Service Buttons are very restricted using Workspace
- Display: Tab selection, Splitter panels, Slider selection do not render in Workspace
- Cannot restrict WA Tools menu in Workspace at all, where you can in the Studio.
For exact details check out the Hyperion Web Analysis Studio User’s Guide from the Doc Library:
http://download.oracle.com/docs/cd/E10530_01/doc/nav/portal_4.htm
Cheers
Iain

Analysis authorization not working on WAS server

Similar Messages

Maybe you are looking for