Self Service - Enter Contacts gives an error
Hi everyone, im trying to solv an error i'm experiencing in Self Service, when a user tries to enter contact information. The Below error occurs.
ORA-20001: The mandatory column ATTRIBUTE26 (also known as Salary Number(From IFMS)) has not been assigned a value. ORA-06512: at "APPS.HR_UTILITY", line 939 ORA-06512: at "APPS.HR_PROCESS_CONTACT_SS", line 9120 ORA-06512: at line 1
I'm aware that the fields pull from core hr, but the field giving an error is required in core hr, but i do not want it in self service, how do i change this?
yes you can personalise the forms.
Check -
http://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CDYQFjAB&url=http%3A%2F%2Foracle.anilpassi.com%2Ff…
Forms personalization for DFF
Similar Messages
-
In Every Page of Employee Self Service it is displaying this Error.
Hi All Experts,
In Employee Self Service i am Getting this Error,overview page is also not displayed.
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:862)
... 60 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0015.20080131100237.0000 (release=645_VAL_REL, buildtime=2008-02-15:22:35:17[UTC], changelist=475271, host=pwdfm101), build date: Tue Jul 08 13:48:16 GMT+05:30 2008
J2EE Engine 7.00 patchlevel 110760.44
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en_US
Time of Failure Thu Jul 31 10:12:26 GMT+05:30 2008 (Java Time: 1217479346562)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0014.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:46:55[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0014.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:47:02[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0014.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:35:31[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0014.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:52:27[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0014.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:36:15[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0014.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:36:09[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0014.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:44:27[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0014.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:49:22[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0014.20071029095230.0000 (release=645_VAL_REL, buildtime=2007-11-17:12:01:49[UTC], changelist=466194, host=pwdfm101)
SapWebDynproGenerationCore 7.0014.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:52:33[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0014.20071029095230.0000 (release=645_VAL_REL, buildtime=2007-11-17:12:01:49[UTC], changelist=466194, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0014.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:46:55[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0014.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:47:02[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0014.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:35:31[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0014.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:52:27[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0014.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:36:15[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0014.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:36:09[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0014.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:44:27[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0014.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:49:22[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0014.20071029095230.0000 (release=645_VAL_REL, buildtime=2007-11-17:12:01:49[UTC], changelist=466194, host=pwdfm101)
SapWebDynproGenerationCore 7.0014.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-11-17:11:52:33[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0014.20071029095230.0000 (release=645_VAL_REL, buildtime=2007-11-17:12:01:49[UTC], changelist=466194, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:862)
at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:259)
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:104)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:842)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1072)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
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.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1288)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)what user name did you use in JCo??? and the user you made can you give me some insight steps on it...
i mean the user is refernce user, dialuge user or what user.....
My basis team is using their own user name in JCO, bcoz of which only data relating to their user name is showing in ESS / MSS for all employees of PORTAL
also please let me know which profile you used for the user of JCO.
Regards -
OID Self Service Console - Page Cannot Found error
Hi,
I am using Oracle Collaboration Suite and facing problem while creating a user. I navigated to the OID Self Service Console and signed in successfully with orcladmin user. After successfull login as I click on Directory Tab to create user then Page Cannot be displayed typical browsing error appears. I cannot find whats wrong. Infrastructrue and middle tier components all are up and seem working fine.
I cannot find way to deal with Page Cannot Found error. Please help
Regards,
SamiTry typing in the URL yourself in the address location. Do you observe the same behavior?
If the forward-slash at the end still makes a difference, then verify that you have not modified your httpd.conf on the infrastructure instance.
Here, check if your HTTP Server had any redirection rules or any aliases setup in the httpd.conf in your infrastructure. The trailing forward-slash / is generally meaningful in those places.
Also note if you see the same problem with other targets too. for instances, sso-login server.
AMN -
Self Service request is going to error after final Approver.
Hi,
Here we configured leave system through EIT and we are using self service (EIT) to make leave request. We have 3 level of approver for Annual Leave. Problem here is after final approver (3rd approver) approves the leave then request is going in to error. I traced the item key through Workflow Administrator > Status Monitor.
The error is Details are given below (Status Monitor)
Failed Activity
Notify HR About Commit Application Error
Activity Type
Notice
Error Name
WFNTF_ROLE
Error Message
3205: '[email protected]' is not a valid role or user name.
Error Stack
Wf_Notification.Send([email protected], HRSSA, HR_EMBED_DEPT_COMMAPPLERR_MSG, WF_ENGINE.CB) Wf_Engine_Util.Notification_Send(HRSSA, 1649471, 195663, HRSSA:HR_EMBED_DEPT_COMMAPPLERR_MSG) Wf_Engine_Util.Notification(HRSSA, 1649471, 195663, RUN)
I appreciate if someone can help me.
Regards,
Jojo GeorgeOkay, if the $PROFILES$ reference has been working for a long time that doesn't sound like a problem. I would then suggest this is an unusual data scenario where the value the user selected was temporarily available. Don't ask me how - it's your data! The user that submitted it might be able to shed some light. For example, this kind of thing might do it:
1) Manager logs on to ESS, starts an SIT transaction (the one in question) and Saves for Later. This sets $PROFILES$.PER_PERSON_ID to themself.
2) Manager then switches to MSS and views one of their employees - this sets $PROFILES$.PER_PERSON_ID to their employee, not themselves.
3) Manager then navigates to Homepage and continues the Saved for Later transaction from the Worklist (ie, without clicking on the ESS responsibility). Perhaps $PROFILES$.PER_PERSON_ID is still set to their direct report rather than themselves?
4) Manager then selects one of their employees contracts rather than their own (because of $PROFILES$.PER_PERSON_ID being wrong).
5) Manager submits the transaction.
I don't know if that's possible or even if that's how it behaves. But it sounds plausible and is an example of perhaps the weird set of circumstances that might have happened here. Regardless, I'd still maintain that this value was available to the user in the Value Set at the time they submitted it.
If it's just a one-off data problem and this has been working fine for a while I wouldn't worry about it. Bin the workflow, get the employee to re-submit. Job done. -
OTL Self Service Error Message
We use OTL Timekeeper functionality for entering time, but want to switch to some Self Serve OTL time entry also. The error messages we are currently using work fine in OTL. The overtime rule goes out, validates the time entered, and returns an error apparopriately. When I try this in Self Service, I get the following errors:
The Oracle error is: ORA-20000: ORA-20001:ORA-20001: Formula KCI_JEAN_TEST_TOKEN: ORA-01403: no data found ORA-01403: no data found Cause: During the PL/SQL execution part, an Oracle error was detected. Action: Please refer to your system administrator..
I am unsure why. If I enter time in Timekeeper, it tells me I don't have enough regular time to charge overtime. However in self serve, I just get this weird message.
Ideas? I can post my entire fast formula (it calls a pl/sql function to do the actual verification that return any errors found to the fast formula) if you are interested.
Jean Farmer
KCI TechnologiesI wrote this code to test the passing of Tokens and it works perfectly. The messages come out condensed into two messages with tokens.
/********************SAMPLE1*************************************/
Default for MESG1 is ' '
Default for MESG2 is ' '
Default for MESG3 IS ' '
Default for MESG4 IS ' '
INPUTS ARE Resource_id,
submission_date(TEXT),
MESG1(TEXT),
MESG2(TEXT),
MESG3(TEXT),
MESG4(TEXT)
JEAN1 = 'JEAN LINE 1'
JEAN2 = ' '
JEAN3 = ' '
JEAN4 = ' '
JEAN5 = 'JEAN LINE 5'
JEAN6 = ' '
/*Squish the messages into just two lines, jean1,jean2*/
JEAN6=KCI_OTL_MESSAGE_ORDER(JEAN1,JEAN2,JEAN3,JEAN4,JEAN5)
IF LENGTH(JEAN1) > 3 THEN
RULE_STATUS = 'E'
MESSAGE1='HXC_XXKCI_OTL_ERR3'
TOKEN_NAME1='KCI_ERR3'
TOKEN_VALUE1=JEAN1
IF LENGTH(JEAN2) > 3 THEN
MESSAGE2='HXC_XXKCI_OTL_ERR4'
TOKEN_NAME2='KCI_ERR4'
TOKEN_VALUE2=JEAN2
RETURN RULE_STATUS, MESSAGE1, TOKEN_NAME1, TOKEN_VALUE1, MESSAGE2, TOKEN_NAME2, TOKEN_VALUE2
/*******************END SAMPLE 1*******************************/
This one keeps returning the no data found error I listed up top whenever it runs. I'm not really understanding what the issue is though... obviously something with the KCI_OVERTIME_VALIDATION. However the KCI_OVERTIME_VALIDATION runs currently in the current fastformula and it works great without tokens. It returns message1..5 without an error and reads correctly. However as soon as I try and put it in here with tokens, it starts giving me the no data found errors.
Please note - this works great with Timekeeper, but in Self Service OTL it returns the error.
/**************** SAMPLE 2 - WHICH RESULTS IN ERRORS ***************/
Default for MESG1 is ' '
Default for MESG2 is ' '
Default for MESG3 IS ' '
Default for MESG4 IS ' '
INPUTS ARE Resource_id,
submission_date(TEXT),
MESG1(TEXT),
MESG2(TEXT),
MESG3(TEXT),
MESG4(TEXT)
JEAN1 = ' '
JEAN2 = ' '
JEAN3 = ' '
JEAN4 = ' '
JEAN5 = ' '
JEAN6 = ' '
JEAN5=KCI_OVERTIME_VALIDATION(RESOURCE_ID,submission_date,JEAN1,JEAN2,JEAN3,JEAN4)
JEAN6=KCI_OTL_MESSAGE_ORDER(JEAN1,JEAN2,JEAN3,JEAN4,JEAN5)
IF LENGTH(JEAN1) > 3 THEN
RULE_STATUS = 'E'
MESSAGE1='HXC_XXKCI_OTL_ERR3'
TOKEN_NAME1='KCI_ERR3'
TOKEN_VALUE1=JEAN1
IF LENGTH(JEAN2) > 3 THEN
MESSAGE2='HXC_XXKCI_OTL_ERR4'
TOKEN_NAME2='KCI_ERR4'
TOKEN_VALUE2=JEAN2
RETURN RULE_STATUS, MESSAGE1, TOKEN_NAME1, TOKEN_VALUE1, MESSAGE2, TOKEN_NAME2, TOKEN_VALUE2
/*******************END SAMPLE 2 ********************************/ -
How To Display Error Message In Self Service Page
Dear All,
I am using 11.5.10 Oracle HRMS self Service ,,,
How can I display error message on the top of the self service page if some action happen ?
Best RegardsTime entry rules maybe?
-
Purchase Order Information in Self Service Pages in HRMS
Hi,
Our system is on 12.1.3. We have a requirement such that a OAF page needs to be built and put after Location Changes (Self Service) which would give the Accounting segments and some other details as in Personal Info --> Assignemnts --> Purchase Order Info (D2K Forms of HRMS). User woudl select the values and then proceed to the review page.
1. How the data which the users would enter will be saved in the Transaction_API tables?
2. will that Automatically populate the review page with the old and new valuues.
if any one has worked on this please share the approach.
ThanksHi,
As far as my understanding and experience goes, page build is very complex using SSHR architecture as you will need to inherit SSHR AMs and Controller modules in your pages and also understand the code and supply of parameters etc to the pages. This will need a lot of research and though I want to help, It will be difficult to put it in a forum post in sufficient detail.
I can assure you the work involved will be in weeks than in days. Also, there is no way to display the review page based on a new region without custom build to do it.
However, a possible workaround which you could do is to use DFF or EIT to capture this information and then transfer it to the "Correct Home" of the data offline through a CP or via another node in the workflow.
Sorry to be pessimistic. Please let me know if I can help with anything else.
Edited by: Vinayaka Prabhu on Feb 7, 2012 4:31 PM -
Customer self service form gives the error of "Page cannot be displayed"
Hi All,
Customer self service form from Navigation: Recievables -> Customers --> Standard gives the error of "Page cannot be displayed" but the same form gets opened when i navigate that from Order Management responsibility
Thanks&Regards,
APPS DBAHi All,
I have been trying to install the EBS 11i in configured system core 2 duo with 1 gb ram and 250 gb HDD,
have been following the below steps to install the EBS 11i,
1.installed Win20003 server edition
2.VC++ and copyind the link file into windows\system32,
3.GNU make done the path set everything,
4.MKS tool kit,
5IP config and installing MS loopback,
started the installtion direct from the DVDs,
Pre-Installtion everything was OK,
but after done everything I got struck last min, where the popup window appeared as login page responding but i did wait for 30 min and nothing has happened.
So closed and I restarted the System and I have restarted process putting 1st DVD and given the command rapidwiz -restart.from command prompt.
and Again its started as a new installtion, and preinstatltion wizard has came.
where I haeve commited the mistake i did not understand...?
Please guide me
regards
Satya -
Error in self service for my employee - Related Activities in MSS
Hi,
NW2004s SP9 EP7.0 ECC 6.0
we are trying to implement the self service for my employee in related activites functinality from the general information of team workset ( Team --> General informatio --> Related activities --> Self service for my employee ) in MSS which is a replicaiton of ESS in MSS functionality from the previous versions.
When
I click on any of the options like Personal data or Addresses it gives me a blank page with no information on it. (It does give a DONE message with error/warning message on the status bar of Internet explorer. The error message says getactivetrackingEntryValue() is null)
Do I need to do anything to get this page working. I do not see any config related to this.
Appreciate any inputs.
regards
samJames,
I think the note refers to note been able to display the general infromation iView itself. I have implemented the note and am able to see the genral information iView. My issue is I am not able to perform "Self service for my employees" in "related activities" iView.
Thank for you reply and correct me if I am wrong.
Sanjay, I have raised the issue with SAP, in the mean while if you can please let me know the patches or a list of them that are requried thyat would be awesome. Sorry for asking you this, but the basis team here asks to tell them what is requried even though I do not have sufficient authorizations to check them.
Appreciate you help on the same.
regards
Sam -
Error during password reset using self-service portal
I am working in a poc (proof of concept) using oim with ad, exchange, sap and database application tables connectors. During some tests I noticed that password reset through oim's self-service portal works fine for ad, exchange and sap, but it fires an error for the database application tables connector. The odd part is that i can change the user password using web console as xelsysadmin nicely. Also I can change the password when i retried the failed task.
Any help is appreciated.
I'm running OIM 9.1.0.2 with BP05 applied, Weblogic Server 10.3.2, Oracle Database 11.0.7. The OS is Windows 2003.
Log from oim web console
Resource Name: SOC_GTC
Description:
User: poc cassi17 [POC.CASSI17]
Status: Rejected
Response: OIM API Error
Response Description: An error was encountered in the Oracle Identity Manager API layer.
Notes:
wnqAd8gmdAhODUFjs4WMyQ==
Assigned to Group : SYSTEM ADMINISTRATORS
Log from Weblogic sdout
ERROR,22 Feb 2010 20:09:45,187,[XELLERATE.APIS],
java.lang.NullPointerException
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.getModelFromConnectorDefinition(Unknown Source)
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperationsSession.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperations_do1ndy_ELOImpl.lookup(GCOperations_do1ndy_ELOImpl.java:619)
at Thor.API.Operations.GCOperationsClient.lookup(Unknown Source)
at com.thortech.xl.gc.runtime.GCAdapterLibrary.executeFunctionality(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.GENERICADAPTER(adpSOC_GTC.java:125)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.implementation(adpSOC_GTC.java:70)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcOrderItemInfo.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateDataSetValuePost(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateProcessFormFieldValue(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeProcessAdapter(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeAdapter(Unknown Source)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOCSETNEWSENHA.implementation(adpSOCSETNEWSENHA.java:55)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.insertMileStones(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.trigger(Unknown Source)
at com.thortech.xl.client.events.tcUSRTriggerUserProcesses.implementation(Unknown Source)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.changePasswordForSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperations_voj9p2_EOImpl.changeCredForSelf(tcUserOperations_voj9p2_EOImpl.java:3325)
at Thor.API.Operations.tcUserOperationsClient.changeCredForSelf(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at Thor.API.Base.SecurityInvocationHandler.invoke(Unknown Source)
at $Proxy59.changeCredForSelf(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.changePassword(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcActionBase.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.execute(Unknown Source)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.SecurityFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
ERROR,22 Feb 2010 20:09:45,187,[XELLERATE.APIS],An exception occurred while creating the GenericConenctor Model from the Connector Definition file
ERROR,22 Feb 2010 20:09:45,187,[XELLERATE.APIS],An exception occurred while generating Generic Connector model from the connector definition xml of the connector 'SOC'
com.thortech.xl.gc.exception.ConnectorDefinitionOperationsException: An exception occurred while creating the GenericConenctor Model from the Connector Definition file
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.getModelFromConnectorDefinition(Unknown Source)
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperationsSession.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperations_do1ndy_ELOImpl.lookup(GCOperations_do1ndy_ELOImpl.java:619)
at Thor.API.Operations.GCOperationsClient.lookup(Unknown Source)
at com.thortech.xl.gc.runtime.GCAdapterLibrary.executeFunctionality(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.GENERICADAPTER(adpSOC_GTC.java:125)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.implementation(adpSOC_GTC.java:70)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcOrderItemInfo.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateDataSetValuePost(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateProcessFormFieldValue(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeProcessAdapter(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeAdapter(Unknown Source)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOCSETNEWSENHA.implementation(adpSOCSETNEWSENHA.java:55)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.insertMileStones(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.trigger(Unknown Source)
at com.thortech.xl.client.events.tcUSRTriggerUserProcesses.implementation(Unknown Source)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.changePasswordForSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperations_voj9p2_EOImpl.changeCredForSelf(tcUserOperations_voj9p2_EOImpl.java:3325)
at Thor.API.Operations.tcUserOperationsClient.changeCredForSelf(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at Thor.API.Base.SecurityInvocationHandler.invoke(Unknown Source)
at $Proxy59.changeCredForSelf(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.changePassword(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcActionBase.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.execute(Unknown Source)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.SecurityFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
... 92 more
Edited by: aviana on Feb 23, 2010 5:18 AMI changed the privileges as recommended, but it did no solved the problem. So I implemented the task retry as a workaround and it worked.
Anyway, I increased the adapter's log level to debug. Please check the log below.
ERROR,23 Feb 2010 19:44:28,531,[XELLERATE.APIS],
java.lang.NullPointerException
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.getModelFromConnectorDefinition(Unknown Source)
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperationsSession.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperations_do1ndy_ELOImpl.lookup(GCOperations_do1ndy_ELOImpl.java:619)
at Thor.API.Operations.GCOperationsClient.lookup(Unknown Source)
at com.thortech.xl.gc.runtime.GCAdapterLibrary.executeFunctionality(Unknown Source)
at sun.reflect.GeneratedMethodAccessor338.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.GENERICADAPTER(adpSOC_GTC.java:125)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.implementation(adpSOC_GTC.java:70)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcOrderItemInfo.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateDataSetValuePost(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateProcessFormFieldValue(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeProcessAdapter(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeAdapter(Unknown Source)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOCSETNEWSENHA.implementation(adpSOCSETNEWSENHA.java:55)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.insertMileStones(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.trigger(Unknown Source)
at com.thortech.xl.client.events.tcUSRTriggerUserProcesses.implementation(Unknown Source)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.changePasswordForSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperations_voj9p2_EOImpl.changeCredForSelf(tcUserOperations_voj9p2_EOImpl.java:3325)
at Thor.API.Operations.tcUserOperationsClient.changeCredForSelf(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at Thor.API.Base.SecurityInvocationHandler.invoke(Unknown Source)
at $Proxy59.changeCredForSelf(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.changePassword(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcActionBase.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.execute(Unknown Source)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.SecurityFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
ERROR,23 Feb 2010 19:44:28,531,[XELLERATE.APIS],An exception occurred while creating the GenericConenctor Model from the Connector Definition file
ERROR,23 Feb 2010 19:44:28,531,[XELLERATE.APIS],An exception occurred while generating Generic Connector model from the connector definition xml of the connector 'SOC'
com.thortech.xl.gc.exception.ConnectorDefinitionOperationsException: An exception occurred while creating the GenericConenctor Model from the Connector Definition file
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.getModelFromConnectorDefinition(Unknown Source)
at com.thortech.xl.ejb.beansimpl.GCOperationsBean.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperationsSession.lookup(Unknown Source)
at com.thortech.xl.ejb.beans.GCOperations_do1ndy_ELOImpl.lookup(GCOperations_do1ndy_ELOImpl.java:619)
at Thor.API.Operations.GCOperationsClient.lookup(Unknown Source)
at com.thortech.xl.gc.runtime.GCAdapterLibrary.executeFunctionality(Unknown Source)
at sun.reflect.GeneratedMethodAccessor338.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.GENERICADAPTER(adpSOC_GTC.java:125)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOC_GTC.implementation(adpSOC_GTC.java:70)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcOrderItemInfo.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateDataSetValuePost(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateProcessFormFieldValue(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeProcessAdapter(Unknown Source)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeAdapter(Unknown Source)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpSOCSETNEWSENHA.implementation(adpSOCSETNEWSENHA.java:55)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(Unknown Source)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.insert(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.insertMileStones(Unknown Source)
at com.thortech.xl.client.events.tcTriggerUserProcesses.trigger(Unknown Source)
at com.thortech.xl.client.events.tcUSRTriggerUserProcesses.implementation(Unknown Source)
at com.thortech.xl.client.events.tcBaseEvent.run(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.runEvent(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.eventPostUpdate(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.update(Unknown Source)
at com.thortech.xl.dataobj.tcDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcTableDataObj.save(Unknown Source)
at com.thortech.xl.dataobj.tcUSR.changePasswordForSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changePasswordforSelf(Unknown Source)
at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperationsSession.changeCredForSelf(Unknown Source)
at com.thortech.xl.ejb.beans.tcUserOperations_voj9p2_EOImpl.changeCredForSelf(tcUserOperations_voj9p2_EOImpl.java:3325)
at Thor.API.Operations.tcUserOperationsClient.changeCredForSelf(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at Thor.API.Base.SecurityInvocationHandler.invoke(Unknown Source)
at $Proxy59.changeCredForSelf(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.changePassword(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcActionBase.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcAction.execute(Unknown Source)
at com.thortech.xl.webclient.actions.tcChangePasswordAction.execute(Unknown Source)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.SecurityFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
... 91 more
***ERROR,23 Feb 2010 19:44:28,531,[XELLERATE.GC.FRAMEWORKPROVISIONING],An exception occurred while generating Generic Connector model from the connector definition xml of the connector 'SOC'***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal entered.***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString entered.***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: class - Value: java.lang.String***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: poRetVal.toString() - Value: GCPROV.ADAPTER_OIMAPIERROR***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: Returning:sRetVal - Value: GCPROV.ADAPTER_OIMAPIERROR***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString left.***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal - Data: Setting Adapter Return Value to GCPROV.ADAPTER_OIMAPIERROR - Value:***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal left.***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/finalizeProcessAdapter entered.***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/finalizeProcessAdapter - Data: Mapped to Response Code - Value:***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem entered.***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: event - Value: adpSOC_GTC***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: New Status - Value:***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: SchData - Value: GCPROV.ADAPTER_OIMAPIERROR***
***DEBUG,23 Feb 2010 19:44:28,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: Reason - Value:***
***DEBUG,23 Feb 2010 19:44:28,609,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem left.***
***DEBUG,23 Feb 2010 19:44:28,609,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/finalizeProcessAdapter left.***
***INFO,23 Feb 2010 19:44:28,609,[XELLERATE.ADAPTERS],Adapter: adpSOC_GTC has completed for the task: SENHA Updated.***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateDataSetValuePost left.***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateProcessFormFieldValue left.***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateProcessFormFieldValue left.***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/finalizeProcessAdapter - Data: No Response Code specified. Updating milestone status to Completed - Value:***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem entered.***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: event - Value: adpSOCSETNEWSENHA***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: New Status - Value: C***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: SchData - Value:***
***DEBUG,23 Feb 2010 19:44:28,625,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem - Data: Reason - Value:***
***DEBUG,23 Feb 2010 19:44:28,656,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/updateSchItem left.***
***DEBUG,23 Feb 2010 19:44:28,656,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/finalizeProcessAdapter left.***
***INFO,23 Feb 2010 19:44:28,656,[XELLERATE.ADAPTERS],Adapter: adpSOCSETNEWSENHA has completed for the task: Change User Password.***
***INFO,23 Feb 2010 19:44:28,656,[XELLERATE.ADAPTERS],Event: Triggering Processes related to User. has completed.***
Edited by: aviana on Feb 23, 2010 3:02 PM -
HR Self-Service Transactions - error notifications
In our HR system we are using Administrator Self Service, allowing staff to make changes to HR records for people they manage.
In quite a few cases, our central admin team are receiving notifications with subject lines like:
Application Error has occurred in your process Change Job and Terms performed on Bloggs, Mr Joseph
When opening the notification, the error message at the top of the page says a range of things, such as:
The changes were not applied because This transaction has failed because the employee's record or eligibility status has changed. Submit a new transaction.
Another user has updated this person's record. Please reject the transaction so the initiator can check whether the change is still valid for the updated record.It would seem that the cause of these is because between the HR Self Service transaction being submitted and the error notification going out, something has changed on the HR record in question.
Is there any way I can work out where that change is being made, or is that too hard?
I can see the HR Self Service Transaction via:
SELECT hat.creation_date hrss_tx_date
, wn.notification_id nid
, wn.begin_date notif_date
, wn.status
, wn.item_key
, REPLACE(
wn.subject
, 'Application Error has occurred in your process '
) subject
, fu.user_name originator_uname
, papf3.full_name hr_record_being_changed
, fu.description originator_description
, papf.full_name originator_full_name
, papf2.full_name manager_full_name
, fu2.user_name manager_login
, fu2.description manager_description
FROM applsys.wf_notifications wn
, applsys.fnd_user fu
, applsys.fnd_user fu2
, hr.hr_api_transactions hat
, hr.per_all_people_f papf
, hr.per_all_people_f papf2
, hr.per_all_people_f papf3
, hr.per_all_assignments_f paaf
WHERE hat.item_key = wn.item_key
AND hat.created_by = fu.user_id
AND papf2.person_id = fu2.employee_id
AND hat.creator_person_id = papf.person_id
AND papf.person_id = paaf.person_id
AND paaf.supervisor_id = papf2.person_id
AND hat.selected_person_id = papf3.person_id
AND SYSDATE BETWEEN papf.effective_start_date AND papf.effective_end_date
AND SYSDATE BETWEEN papf2.effective_start_date AND papf2.effective_end_date
AND SYSDATE BETWEEN papf3.effective_start_date AND papf3.effective_end_date
AND SYSDATE BETWEEN paaf.effective_start_date AND paaf.effective_end_date
AND recipient_role = 'HRMS_DEV_ROLE'
AND subject LIKE 'Application Error%'
AND wn.notification_id = :nid
ORDER BY wn.begin_date DESC;But if I look at e.g. the per_all_people_f or per_all_assignments_f tables to look for changes made to the same HR record that the Self-Service transaction was for, nothing recent is returned:
SELECT papf.employee_number
, paaf.assignment_number
, paaf.object_version_number paaf_ovn
, papf.creation_date papf_creation_date
, papf.last_update_date papf_last_update_date
, paaf.creation_date paaf_creation_date
, paaf.last_update_date paaf_last_update_date
, papf.object_version_number papf_ovn
FROM hr.per_all_people_f papf
, hr.per_all_assignments_f paaf
WHERE papf.person_id = paaf.person_id
AND papf.full_name LIKE :pn
ORDER BY paaf.last_update_date DESC;I have seen stuff on My Oracle Support about "object version number" e.g. 1300998.1 says:
"This is an expected behavior. Since after first approval the object version number of contact's personal details has changed. Now when you try to approve second notification we will compare the OVN in transaction tables to the OVN in database (which got changed). Hence we get an object version mismatch and above error."However, I am still stuck trying to see what has changed. I need to find this so I can go to the functional people who don't understand why they are getting the error notifications, so say "Look, this has changed since the Self-Service transaction was submitted, hence the error".
Any advice would be much appreciated.
ThanksHi,
In the end I wrote some SQL which identified the fact that the HR tables had been updated in Core Apps AFTER a Self-Service transaction had been started.
SELECT distinct hat.creation_date workflow_start
, wn.notification_id nid
, (SELECT MAX(last_update_date) FROM hr.per_all_assignments_f paaf2 WHERE paaf2.person_id = papf3.person_id) last_assig_update
, wn.begin_date error_date
, wn.begin_date - (SELECT MAX(last_update_date) FROM hr.per_all_assignments_f paaf2 WHERE paaf2.person_id = papf3.person_id) dd
, wn.item_key
, SUBSTR(
wn.subject
, 48
, INSTR(SUBSTR(wn.subject, 48 + 2), 'performed on ')
) transaction_type
, CASE
WHEN SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) LIKE '%Miss%' THEN REPLACE( SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) , ' Miss' , '' )
WHEN SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) LIKE '%Mrs%' THEN REPLACE( SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) , ' Mrs' , '' )
WHEN SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) LIKE '%Ms%' THEN REPLACE( SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) , ' Ms' , '' )
WHEN SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) LIKE '%Mr%' THEN REPLACE( SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 ) , ' Mr' , '' )
ELSE SUBSTR( wn.subject , INSTR(wn.subject, 'performed on ') + 13 , LENGTH(wn.subject) - INSTR(wn.subject, 'performed on ') + 13 )
END performed_on
, wn.subject
, papf3.full_name
, papf3.employee_number empno
, fu.user_name by_un
, fu.description by_desc
, papf.full_name by_name
FROM applsys.wf_notifications wn
, applsys.fnd_user fu
, hr.hr_api_transactions hat
, hr.per_all_people_f papf
, hr.per_all_people_f papf3
, hr.per_all_assignments_f paaf
WHERE hat.item_key = wn.item_key
AND hat.created_by = fu.user_id
AND hat.creator_person_id = papf.person_id
AND papf.person_id = paaf.person_id
AND hat.selected_person_id = papf3.person_id
AND SYSDATE BETWEEN papf.effective_start_date AND papf.effective_end_date
AND SYSDATE BETWEEN papf3.effective_start_date AND papf3.effective_end_date
AND SYSDATE BETWEEN paaf.effective_start_date AND paaf.effective_end_date
AND subject NOT LIKE '%Phone Numbers%'
AND recipient_role = 'HRMS_DEV_ROLE'
AND subject LIKE 'Application Error%'
AND papf.current_employee_flag = 'Y'
AND paaf.assignment_type = 'E'
ORDER BY 1 DESCIt helped compare things in the background and prove in our case that there wasn't a system problem.
Thanks -
Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"
I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server -
SCSM 2012 - Self Service Portal installation Error
Hi Everyone,
I am trying to update SCSM 2010 with 2012. So far I have successfully installed Database Server and Warehouse server, and now I am trying to install the self service portal but it is giving me an error saying "Setup has failed because of an unexpected
error. Please review C:\..\SCSMSertupWizard01.log for more details.
Here are some extra information in relation to this upgrade.
I have got 3 separate servers for my SCSM 2010 application. One act as a warehouse database server. second server holds the Service Manger Database and the third one has got Self-service portal on it.
Now as I said earlier, I did not face any issue upgrading the first two servers (warehouse and Database) but the last one is proving very difficult to just even start with.
Here is some interesting thing that is happening while I am trying to install my self service portal.
When I run the SCSM 2012 setup on my web portal server (Server 3) I get a setup screen with following option
and as I said earlier when I click this Upgrade option it starts the "requirements check" and fails just there with an error message.
Now here is the interesting thing, when I run the SCSM 2012 setup on my server 2 ( which has now got Database Server 2012 installed in it) gives me following option screen.
So when I select this option it starts to install Web content server and Sharepoint site server on my Database server. I do not want that. I want to have my web content server on Server 3 which already has SSP 2010 on it. I have also installed Sharepoint
2010 on my third server.
What is the solution here?
Do I have to merge my Database and Web content server? is it some sort of untold requirement of SCSM 2012 upgrade?
Please help me here.
SvapnilHi there,
thanks for the reply..
here is the screenshots of the log files.
Sorry all my 3 servers are on DMZ environment so it is bit hard for me to move files from virtual to live servers (Do not have enough permission level to do so!!)
Image No 2:
I hope this helps!! -
Receiving Error When Trying To Enroll a class In Learner self service
hi,
i will appreciate that if anyone can help me to fix the problem.
Steps to Reproduce:(ota.j)
==============
1) Responsibility => "Learner self service"
2) Try to enroll a class (need approval)
3) check button "review "
then Users receive the following error messages :
"You have encountered an unexpected error. Please contact the System Administrator for assistance. Click here for exception details."
oracle.apps.fnd.framework.OAException: No entities found, entityMaps not defined for attachment item (112).
## Detail 0 ##
oracle.apps.fnd.framework.OAException: No entities found, entityMaps not defined for attachment item (112).
oracle.apps.fnd.framework.OAException: No entities found, entityMaps not defined for attachment item (112).
Message was edited by:
wallaceWallace,
You can try one thing. Set the class to be restricted and disable the approval for user (Self Enrollment Option) and see if the error is there.
Is there any personalization been done in the review page? -
Hello Everyone,
i am novice to MBAM and i have gone thru the virtual lab and material and i am in process of implementing it for my Organization. i am having 2 issues :-
1) After installation, i am confused how to access the console or does there is no Admin console and it is just servername:portnumber\helpdesk only.
2) If i enter just servername:portnumber\ then it get redirected to selfservice portal which is not an issue. Issue is after accepting agreement and clicking continue i am getting below error :-
A required anti-forgery token was not supplied or was invalid.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Mvc.HttpAntiForgeryException: A required anti-forgery token was not supplied or was invalid.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[HttpAntiForgeryException (0x80004005): A required anti-forgery token was not supplied or was invalid.]
System.Web.Mvc.ValidateAntiForgeryTokenAttribute.OnAuthorization(AuthorizationContext filterContext) +546706
System.Web.Mvc.ControllerActionInvoker.InvokeAuthorizationFilters(ControllerContext controllerContext, IList`1 filters, ActionDescriptor actionDescriptor) +128
System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName) +658100
System.Web.Mvc.Controller.ExecuteCore() +125
System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__4() +48
System.Web.Mvc.Async.<>c__DisplayClass1.<MakeVoidDelegate>b__0() +21
System.Web.Mvc.Async.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _) +15
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +85
System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +51
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +454
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +263
I have checked and usersupportservice.svc is leading to the pade giving below page which i believe it is working OK or kindly correct me if i am thinking wrong :-
This is a Windows© Communication Foundation service.
Metadata publishing for this service is currently disabled.
only thing which i deviated from process was because of some condition i have to rename my MBAM server before installation however by before rename SQL and IIS was installed.
i will really appreciate any help in this regard.If that is the only link or admin console as well then if anyone can confirm what rights difference a user get when he is member of MBAM helpdesk, MBAM Advanced Helpdesk and MBAM Administrator group.
Also if i can get any help with the self service portal redirection then that will be really helpful. i was also checking if this could be because of any kind of certificate issue as server name was renamed after SQL and IIS installation.
Maybe you are looking for
-
Help required in developing SQL developer extension
Hi, We have a requirement to develop an extension for Sql Developer. The requirement matches the Reports framework in Sql Developer. We need to have a separate dock as in reports where we can navigate through the tree and execute some predefined quer
-
Feature to block a contact on iMessage
I am currently being harassed, and threats to my life are sent to me daily through iMessage, should I choose to enable it. I pay each month a fee to AT&T to block that number from calling and texting me, but they have an open conduit to make my life
-
What is the pin out for your PXI-2503?
Hello, I have purchased a PXI-2503 analog switch, and I have been unable to find the pinouts for this device anywhere. I have connecting directly from the PXI-2503 into my board.
-
How to activate multiple approval in time sheets
Hi Experts, I have a business requirement where we require multiple approval of time sheets. The requirement is is such that either of the two managers or the director should be able to approve the time sheets of the consultants. We use project syste
-
My imessge status is offline and I have tried everything to reactivate it and nothing works. I don't know what to do.. I am not very tech savy and new to Mac so I am not certain if there is something going on behind the scenes that I can do to addre