Error While Promoting the Numbers to Next Level

We have hierarchy defined for entities in Hyperion and are using Phased submissions under Process control . We have all the immediate child entities at 'SUBMITTED' phase but when we are promoting the Parent entity to 'SUBMITTED' phase we are getting following error
"Cannot promote a process unit to a level higher than any of its direct dependents."
I know that a parent can be promoted only to a level that is less than or equal to the lowest level of its immediate children.
However we have few of the Entities which are at "NO ACCESS" stage or "Not Started" stage so if this affecting the Parent from promoting to next stage. But these entities are not started only and the Parent Entity has already been promoted from Not Started to "First Pass" stage that point of time no error crept in.
Please let me know the probable cause of the error.
Regards
Rahul
Edited by: rj_700 on Jun 9, 2012 11:35 AM

Hi Rahul ,
I am a learner.
As per my Knowledge.
When we have issues about Phased Submission- Process Control there are certain things which are worth making note of.
1. Validation Accounts ,which might be preventing you from Promoting the Phase to the next level.
2.And Before promoting the submission group to the Next Phase, make sure all your child members have passed all the review levels to be promoted to next level
please check with experts if my reply is inappropriate.
Thanks,
David

Similar Messages

Error while promoting the repository to a global repository

Hi,
After restoring the repository, I try to promote the repository to a global repository in an Exclusive mode. When check the Global Repository check box and click OK. Pops up User name & password. I have used[i] admin user name and password. It gives me an error:
The following error occurred while performing a repository action. Error - [PCSF_10007] Cannot connect to repository [PowerCenter] because: [[REP_57060] Login failure. The user admin is not valid for the repository PowerCenter Failed to connect to repository service [PowerCenter].].
can anyone provide more information on this. Your guidance will be greatly appreciated.
Thanks in advance,
Ravi

Hi Experts,
I can connect to Informatica Repository with Administrator user, but the Integration Service is always down, how do I bring it up?
Here is the log info:
INFO Thu Feb 24 17:53:50 2011 6752 SF_34014 Service [Hyperion_Integration_Service] on node [PIFEL7_auhodifelp9] shut down.
FATAL Thu Feb 24 17:53:50 2011 6752 SF_34004 Service initialization failed.
ERROR Thu Feb 24 17:53:50 2011 6752 CMN_1006 Failed to connect to repository [Hyperion].
ERROR Thu Feb 24 17:53:50 2011 6752 REP_12400 Repository Error ([REP_55102] Failed to connect to repository service [Hyperion].)
ERROR Thu Feb 24 17:53:50 2011 6752 REP_12400 Repository Error (Failed to connect to repository service [Hyperion].)
ERROR Thu Feb 24 17:53:50 2011 6752 REP_12014 An error occurred while accessing the repository
ERROR Thu Feb 24 17:53:50 2011 6752 REP_12400 Repository Error (Failed to connect to repository service [Hyperion].)
ERROR Thu Feb 24 17:53:50 2011 6752 REP_12400 Repository Error ([REP_57060] Login failure. The user HCTR is not valid for the repository Hyperion)
ERROR Thu Feb 24 17:53:50 2011 6752 REP_12400 Repository Error (The user HCTR is not valid for the repository Hyperion)
ERROR Thu Feb 24 17:53:50 2011 6752 REP_12014 An error occurred while accessing the repository
INFO Thu Feb 24 17:53:50 2011 6752 CMN_1569 Server Mode: [ASCII]
INFO Thu Feb 24 17:53:50 2011 6752 CMN_1570 Server Code page: [MS Windows Latin 1 (ANSI), superset of Latin1]
INFO Thu Feb 24 17:53:50 2011 6752 SF_34012 Opened Service Port [10010] to listen for client connections.
INFO Thu Feb 24 17:53:50 2011 6752 SF_34002 Service is initializing.
Can someone please suggest me a solution for it?
Thanks in advance.
Krishan

Error while creating document numbering series via SDK add on

Dear Experts,
We receive the following error while creating the document numbering series through the SDK add on
[Microsoft][SQL Server Native Client 10.0][SQL Server]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.
From the above error message I can suspect the following possibilities
1. The limit for the document numbering must be less or equal to 2100.
2. There is a problem in the coding in SDK where it does not allow more than 2100 lines in the database.
We tried to create manually for the same fiscal year and period indicator disconnecting the add on, the same error occured.
Then we created a seried for a single document with the period indicator for the next fiscal year, it allowed.
After creating the document numbering for the next fiscal year, we were able to create the numbering for the previous year also.
Kindly help us on how to solve the same.
With regards,
Yeshwanth Prakash

Hi
You have, as far as i can determine without seeing the template,defined no Part Appraiser Column (PAPP) in your template. But you have defined a function on the template to automaticly default the part appraisers.
On the Appraisal document persons (appraiser / appraisee) are getting defaulted as part-appraisers although no part appraisal column excist,and therefor 00 Part Appraisers are allowed. This gives the error. Remove the Part Appraisers default functionality from the template and this problem will be solved.
FYI: The reason why this doesn't give a business check error is that the functions to default participants are BAdI's and we have no means of determining wether or not a BAdI implentation will create an inconsistency on the appraisal document.
Also, the reason that it occurs as a S message and not as E or W is because of programming restrictions in combination with messages. All errors on the Appraisal Document will come as 'S' messages.

Error while running the Report

Hi ,
I am trying to run the Report in Bex Analyzer. and once I enter the value for the variable, it gives me message that "Element is not correctly define (please check query)" and when i click on the error it gives me detail message as below :
Diagnosis
Additional elements that do not have the same dimension, such as quantities and amounts or amounts and ratios, are added to element Sales Qty Gallons .
Procedure
Check your definition.
If you still want to use this addition, you can suppress the dimensionality of one or both subexpressions by using the 'NODIM' operator. The system then interprets this or these subexpressions as nondimensional numbers.
In the executed query, you can use the Key Figure Definition function to analyze element Sales Qty Gallons .
Now the thing is I am already using "NODIM" operator to add those elements. and I m not sure why this error is coming up now because I have created this query a while ago and it wasnt giving me any error at that time but now I have make some changes into it and it;s giving me this error while running the Report. But the thing is I didnt change anything in the element for which it;s showing me error.
Thanks,
Naitik

Naitik,
There are two or more key figures in your report. They are defined by different dimensions and somewhere you have a formula with both these key figure.
Edit your query and select the Check Query icon. It will tell you which calculation you have the problem with. Edit this calculation to see which key figures are present.
If the formula is logically correct, best thing to do is to put a NODIM( ) on your key figures that make up the formula, and then change you formula to look at the NODIM( ) version.
That will fix things for you,
Regards
Gill

Error while opening the report.

hi,
Some time i am getting "500 Internal Server Error',while executing the report.Please check the following exception and give the possible reason for getting this kind of problem.
 500 Internal Server Error
BEx Web Application
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator.
To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
Termination message sent
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:148)
at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:113)
Messages
ABEND: Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
ABEND: Error in BW:
System Environment
Server
BI Java Release: 7 - Patch level: 0000000009 - Description: BI Web Applications Java - Additional info: - Production mode: true
BI ABAP Release: 700 - Patch level: 0009 - Description: SAP NetWeaver BI 7.0 (BIPCLNT300) - Additional info: - Production mode: true
Java Virtual Machine Classic VM - IBM Corporation - 1.4.2
Operating System AIX - ppc64 - 5.3
Context
ACCESSIBLE false
BEx Runtime Version 1
CACHE true
CONTENT_PADDING true
COUNTRY
DEBUG false
DEBUG_LEVEL 0
DEBUG_MESSAGES false
Initial Query String BUILDTREE=false&NAVIGATIONTARGET=navurl%3A%2F%2F7b8b73fe5fd57ae6c5c1a24aed5d1ac4&NAVPATHUPDATE=false&RELATIVENAVBASE=&SAP-LAFVERSIONS=portal%3A7.0.9.0.1%3Bur%3A7.0.9.0.1&SAP-PP-CONSUMERBASEURL=3A80&SAP-PP-PRODUCERID=com.lenovo.BIP_Lenovosap&TEMPLATE=Z_WEB_CR_ZCRMOPPI_Q0032&THEME=LenovoBlueTwo
LANGUAGE en
Master System Alias BIPCLNT300
PROFILING false
RTL false
Request URL http
SAP_BW_IVIEW_ID pcd:portal_content/d029033/com..BI_Reports/com.BI_Analytics/Z_WEB_CR_ZCRMOPPI_Q0032
SAP_EXTERNAL_SID CLGF6EORaEN7Vivt8TVaQw==3eTBxzbQZSMLxB4o3h9+7w==
THEME_NAME LenovoBlueTwo
TRACE false
TRAY_TYPE PLAIN
Time Thu Oct 04 03:14:20 PDT 2007
User EPSUPPORT (USER.R3_DATASOURCE.EPSUPPORT)
Full Exception Chain
Log ID 00145ED13086005200000889000C719A00043BA80CB04B89
com.sap.ip.bi.webapplications.runtime.controller.MessageException: Error during conversion of the Web template "Z_WEB_CR_ZCRMOPPI_Q0032 from the master system at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2055) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:841) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:775) at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:412) at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21) at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java(Compiled Code)) at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java(Compiled Code)) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java(Compiled Code)) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code)) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code)) at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java(Compiled Code)) at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java(Compiled Code)) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code)) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code)) at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753) at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240) at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error during conversion of the Web template "Z_WEB_CR_ZCRMOPPI_Q0032 from the master system at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:93) at com.sap.ip.bi.webapplications.runtime.preprocessor.Preprocessor.parseTemplate(Preprocessor.java:161) at com.sap.ip.bi.webapplications.runtime.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:81) at com.sap.ip.bi.webapplications.runtime.template.TemplateAssembler.init(TemplateAssembler.java:118) at com.sap.ip.bi.webapplications.runtime.base.Template.doInit(Template.java:105) at com.sap.ip.bi.webapplications.runtime.base.PageObject.init(PageObject.java:232) at com.sap.ip.bi.webapplications.runtime.base.Container.init(Container.java:46) at com.sap.ip.bi.webapplications.runtime.impl.Page.initPageObject(Page.java:3226) at com.sap.ip.bi.webapplications.runtime.impl.Page.createPageObject(Page.java:3427) at com.sap.ip.bi.webapplications.runtime.impl.Page.setTemplate(Page.java:4355) at com.sap.ip.bi.webapplications.runtime.impl.Page.doSetTemplateCommand(Page.java:4091) at sun.reflect.GeneratedMethodAccessor293.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:101) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:410) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:325) at com.sap.ip.bi.webapplications.runtime.base.CommunicationProcessor.processCommand(CommunicationProcessor.java:144) at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandInternal(Page.java:1418) at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandSequence(Page.java:1713) at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:2424) at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:1977) ... 38 moreCaused by: com.sap.ip.bi.deploytime.BIBaseRareSystemException: BI runtime subsystem error: Retrieve MetadataResources Failed1.4.2com.sap.ip.bi.deploytime.metadataresourcecache.MetadataResourceCache:initialize Note call hierarchy at com.sap.ip.bi.deploytime.metadataresourcecache.MetadataResourceCache.initialize(MetadataResourceCache.java:212) at com.sap.ip.bi.deploytime.BISP2Jsp.transformDTT(BISP2Jsp.java:1130) at com.sap.ip.bi.deploytime.BISP2Jsp.convert(BISP2Jsp.java:497) at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:88) ... 59 moreCaused by: com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION MSGV1: SAPMSSY1 MSGV3: UNCAUGHT_EXCEPTION at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:148) at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:113) at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:144) at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:113) at com.sap.ip.bi.base.application.service.RfcService.fillMessages(RfcService.java:221) at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:171) at com.sap.ip.bi.base.application.service.rfcproxy.impl.RfcFunction.execute(RfcFunction.java(Compiled Code)) at com.sap.ip.bi.deploytime.service.validation_metadata.impl.ValidationMetadataService.getTransformData(ValidationMetadataService.java:53) at com.sap.ip.bi.deploytime.metadataresourcecache.MetadataResourceCache.initialize(MetadataResourceCache.java:196) ... 62 more
Regards,
Ravi.M

hi,
 Any suggestion for the above query.
here i am using federated portal concept,once i am opening this report in the portal only i am facing the above problem.
Regards,
Ravi.M

Application Error while activating the feature - for creating list content type, list definition and list instance

Dear all,
I am getting application error while enabling the feature. if any body can point out the issue - that will be helpful.
content type
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Field ID="{4C1B0A21-FCE0-4CFE-8742-A250672AFE4F}" Type="Note" Name="CourseDesc" DisplayName="Course Description" Required="TRUE" Group="Training Site Columns"/>

<ContentType ID="0x0100d57ecc53fde34177b096abd0ec90a8f9"
Name="TrainingCourses"
Group="Training Content Types"
Description="Defines a Course"
Inherits="TRUE"
Version="0">
<FieldRefs>
<FieldRef ID="{4C1B0A21-FCE0-4CFE-8742-A250672AFE4F}" Name="CourseDesc" DisplayName="Course Description" Required="TRUE"/>
</FieldRefs>
</ContentType>
</Elements>
List definition
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<ListTemplate
Name="TrainingCourses"
Type="10100"
BaseType="0"
OnQuickLaunch="TRUE"
SecurityBits="11"
Sequence="410"
DisplayName="TrainingCourses"
Description="Training Courses List Definition"
Image="/_layouts/images/itgen.png"/>
</Elements>
List instance
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<ListInstance Title="TrainingCourses"
OnQuickLaunch="TRUE"
TemplateType="10100"
Url="Lists/TrainingCourses"
Description="Training Course List Instance">
</ListInstance>
</Elements>
schema
<?xml version="1.0" encoding="utf-8"?>
<List xmlns:ows="Microsoft SharePoint" Title="TrainingCourses" FolderCreation="FALSE" Direction="$Resources:Direction;" Url="Lists/TrainingCourses-LD_TrainingCourses" BaseType="0" xmlns="http://schemas.microsoft.com/sharepoint/">
<MetaData>
<ContentTypes>
<ContentType ID="0x0100d57ecc53fde34177b096abd0ec90a8f9" Name="TrainingCourses" Group="Training Content Types" Description="Defines a Course" Inherits="TRUE" Version="0">
<FieldRefs>
<FieldRef ID="{4C1B0A21-FCE0-4CFE-8742-A250672AFE4F}" Name="CourseDesc" DisplayName="Course Description" Required="TRUE" />
</FieldRefs>
</ContentType>
</ContentTypes>
<Fields>
<Field ID="{4c1b0a21-fce0-4cfe-8742-a250672afe4f}" Type="Note" Name="CourseDesc" DisplayName="Course Description" Required="TRUE" Group="Training Site Columns" />
</Fields>
<Views>
<View BaseViewID="0" Type="HTML" MobileView="TRUE" TabularView="FALSE">
<Toolbar Type="Standard" />
<XslLink Default="TRUE">main.xsl</XslLink>
<RowLimit Paged="TRUE">30</RowLimit>
<ViewFields>
<FieldRef Name="LinkTitleNoMenu">
</FieldRef>
<FieldRef Name="CourseDesc">
</FieldRef>
</ViewFields>
<Query>
<OrderBy>
<FieldRef Name="Modified" Ascending="FALSE">
</FieldRef>
</OrderBy>
</Query>
<ParameterBindings>
<ParameterBinding Name="AddNewAnnouncement" Location="Resource(wss,addnewitem)" />
<ParameterBinding Name="NoAnnouncements" Location="Resource(wss,noXinviewofY_LIST)" />
<ParameterBinding Name="NoAnnouncementsHowTo" Location="Resource(wss,noXinviewofY_ONET_HOME)" />
</ParameterBindings>
</View>
<View BaseViewID="1" Type="HTML" WebPartZoneID="Main" DisplayName="$Resources:core,objectiv_schema_mwsidcamlidC24;" DefaultView="TRUE" MobileView="TRUE" MobileDefaultView="TRUE" SetupPath="pages\viewpage.aspx" ImageUrl="/_layouts/images/generic.png" Url="AllItems.aspx">
<Toolbar Type="Standard" />
<XslLink Default="TRUE">main.xsl</XslLink>
<RowLimit Paged="TRUE">30</RowLimit>
<ViewFields>
<FieldRef Name="Attachments">
</FieldRef>
<FieldRef Name="LinkTitle">
</FieldRef>
<FieldRef Name="CourseDesc">
</FieldRef>
</ViewFields>
<Query>
<OrderBy>
<FieldRef Name="ID">
</FieldRef>
</OrderBy>
</Query>
<ParameterBindings>
<ParameterBinding Name="NoAnnouncements" Location="Resource(wss,noXinviewofY_LIST)" />
<ParameterBinding Name="NoAnnouncementsHowTo" Location="Resource(wss,noXinviewofY_DEFAULT)" />
</ParameterBindings>
</View>
</Views>
<Forms>
<Form Type="DisplayForm" Url="DispForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" />
<Form Type="EditForm" Url="EditForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" />
<Form Type="NewForm" Url="NewForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" />
</Forms>
</MetaData>
</List>
I am applying the feature to SPWeb level.
cheers
Sathya

redeployed a new solution; since I was getting this error. I would have done typo errors etc.
https://naveengopisetty.wordpress.com/2011/09/10/error-occurred-in-deployment-step-activate-features-invalid-file-name-the-file-name-you-specified-could-not-be-used-it-may-be-the-name-of-an-existing-file-or-directory-or-you-may-not-have-pe/
Cheers
Sathya

Error while invoking the WSDL service of EBS from BPEL process

Hi Team,
when we are calling webservice client to call WSDL service which is published in Oracle EBS integrated SOA Gateway from BPEL process.
After invoking, we are getting the below error
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>FND_SOA_SERVICE_EXECUTION_ERR:oracle.apps.fnd.soa.util.SOAException: ServiceExecutionError: Error while executing the service Exception returned from JCA Service Runtime. Exception returned from JCA Service Runtime. null :Please see service monitor logs for full error trace</summary></part><part name="detail"><detail>oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : FND_SOA_SERVICE_EXECUTION_ERR:oracle.apps.fnd.soa.util.SOAException: ServiceExecutionError: Error while executing the service Exception returned from JCA Service Runtime. Exception returned from JCA Service Runtime. null :Please see service monitor logs for full error trace</detail></part><part name="code"><code>{http://schemas.xmlsoap.org/soap/envelope/}Server</code></part></remoteFault></bpelFault>
API Name : OE_ORDER_PUB.PROCESS_ORDER
could you please let me know the exact problem and provide the solution.
Thanks
Phani Ch.

Hi Phani,
Are you able to reproduce issue as below:
1. Login to Application as sysadmin.
2. Navigate to Intergrated SOA Gateway > Integration Repository.
3. Click on search on right hand side of the page.
4. In the Internal Name type "FND_USER_PKG" and click Go.
5. Click on the User link.
6. Under the "Web Service - SOA Provider", click in the "View WSDL". Copy the complete URL "http://test:8003/webservices/SOAProvider/plsql/fnd_user_pkg/?wsdl"
7. Open the soapUI.
8. Click File > new soapUI Project.
9. Test the web service.
If yes,
I think you might be need to execute a patch:
solution:
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for iAS Patch 18855074.
Note: Above Merge Label Request (MLR) is build for EBS 12.1.3 having OC4J 10.1.3.5.
2. Enable the profile option "EBS Adapter for BPEL, Function Security Enabled".
a. Login as SYSADMIN user and Navigate to System >Profile and Search for "EBS Adapter for BPEL, Function Security Enabled" (Internal name :EBS_ADAPTER_FUNCTION_SEC_ENABLED)
b. Set the Value to 'Y' at SITE level . This means function security feature is enabled and all API calls for PL/SQL APIs, Oracle e-Commerce Gateway, and concurrent programs will be checked for user security before they are invoked.
3. Retest the issue by Generating and Deploying the required package.
4. Migrate the solution as appropriate to other environments.
Thanks
Ranjan

Error while executing the rule session

Hi, I am using Oracle Business Rules Engine 10.1.3.3.0.I am developing rules using XML Facts.I am using a complex type array schema and binding it to define XML facts.Earlier the depth of the schema is 1 and it worked fine,now our schema's depth is 2 and while binding this schema is also working fine.The sample structure of the present schema I am binding is
<xsd:schema>
<xsd:element name = 'ruleRepository' type = 'RuleRepositoryType'/>
<xsd:complexType name='RuleRepositoryType'>
<xsd:sequence>
<xsd:element ='ruleFacts' type='RuleFactsType' minOccurs='0' maxOccurs='unbounded'/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name='RuleFactsType'>
<xsd:sequence>
<xsd:element name='fact1' type='xsd:string'/>
<xsd:element name='fact2' type='xsd:string'/>
<xsd:element name='fact3' type='xsd:string'/>
<xsd:element name='fact4' type='Fact4' minOccurs='0' maxOccurs='unbounded'/>
<xsd:sequence/>
</xsd:complexType>
<xsd:complexType name='Fact4'>
<xsd:sequence>
<xsd:element name='element1' type='xsd:string'/>
<xsd:element name='element2' type='xsd:string'/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Earlier I have binded the similar schema as above but without 'fact4'.It went well and the rules were executing fine.
However when I am trying to bind a similar schema like the above one, its binding fine but when executing from the BPEL Process,its giving errors like,
"Error Caching Decision Services metadata,fact3 is undefined in DM,line6,Column 12",
Please note that I am using fact1 and fact2 only for defining the rules , I am niether using fact3 which is a simple type nor fact4 which is a complex type.
I have asserted Package.RuleRepositoryType in the definitions of the rule author.I have tried with different combinations of assertions but no one worked.
The above error(
"Error Caching Decision Services metadata,fact3 is undefined in DM,line6,Column 12") is coming for the first run of the decision service only,in the next runs its giving another error,which is like
<2008-04-10 07:52:30,772> <ERROR> <default.collaxa.cube.services> <::> ORABPEL-36333
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::>
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> Error while executing the rule session.
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> The rule session {0} failed to execute.
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::>
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.rpi.oracle.OracleRuleSession.execute(OracleRuleSession.java:251)
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.impl.DecisionServiceImpl.process(DecisionServiceImpl.java:1385)
<2008-04-10 07:52:30,773> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.impl.DecisionServiceImpl.assertExecuteWatchStateless(DecisionServiceImpl.java:546)
<2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.invoke_assertExecuteWatchStateless(BookOrderDecisionSOAPBinding_Tie.java:162)
<2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.processingHook(BookOrderDecisionSOAPBinding_Tie.java:457)
<2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
<2008-04-10 07:52:30,774> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
<2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
<2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
<2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
<2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
<2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
<2008-04-10 07:52:30,783> <ERROR> <default.collaxa.cube.services> <::> at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
<2008-04-10 07:52:30,784> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
<2008-04-10 07:52:30,801> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at java.lang.Thread.run(Thread.java:595)
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> Caused by: java.lang.NullPointerException
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.rpi.oracle.RuleSessionPool.getSession(RuleSessionPool.java:463)
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> at oracle.bpel.services.rules.rpi.oracle.OracleRuleSession.execute(OracleRuleSession.java:224)
<2008-04-10 07:52:30,802> <ERROR> <default.collaxa.cube.services> <::> ... 26 more
<2008-04-10 07:52:30,803> <ERROR> <oracle.bpel.services> <::>
java.lang.NullPointerException
at oracle.bpel.services.rules.rpi.oracle.RuleSessionPool.getSession(RuleSessionPool.java:463)
at oracle.bpel.services.rules.rpi.oracle.OracleRuleSession.execute(OracleRuleSession.java:224)
at oracle.bpel.services.rules.impl.DecisionServiceImpl.process(DecisionServiceImpl.java:1385)
at oracle.bpel.services.rules.impl.DecisionServiceImpl.assertExecuteWatchStateless(DecisionServiceImpl.java:546)
at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.invoke_assertExecuteWatchStateless(BookOrderDecisionSOAPBinding_Tie.java:162)
at oracle.bpel.services.rules.runtime.BookOrderDecisionSOAPBinding_Tie.processingHook(BookOrderDecisionSOAPBinding_Tie.java:457)
at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
08/04/10 07:52:30 pFaultMessage is org.collaxa.thirdparty.apache.wsif.base.WSIFDefaultMessage@6e0e5f name:operationErroredFault
08/04/10 07:52:30 QName string is operationErroredFault
where 'BookOrderDecision' is the name of the decision service I am using in BPEL.
I dont understand why I am getting two errors for the same BPEL Process.
Kindly help me in this problem.I am stuck with this for about a week but could not get to the solution.
Thanks in advance.
Regards,
Venkat.

Hi Venkat,
Whenever you do schema changes, you need to go through the cycle of
re-importing the XML schema in the rule repository, re-create the decision
service partnerlink, re-deploy the decision service.
I suspect you have maybe imported the entire XML fact type model (with fact3 and
fact4) instead of just fact1 and fact2 (might want to check in rule author).
So even if you don't use fact3 and fact4 in decision service, they are part of the rules
datamodel.
Regards,
Ralf

Error while creating the HTTP client with destination GB_DPSRetrieve

Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
Kishore

Hi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar

WWC-00000 error while creating the user

Any one can help me on the WWC-00000 error while creating the
user from the Admin tab of Oralce Portal. In fact I can't use
the Login server administration. same problem exists.
I granted DBA privileges to the PORTAL30, just to verify and NO
use.
I am using the latest version of Portal S/W on iAS9i 1.0.2.2.1
- Suneel

Hi Suresh,
This error trace is not sufficient to understand the issue and at what step you got this error.
First tell me, did you got the User Admin Tab in your portal access. if yes.. did you got the next step...which is Identity Management. Please elaborate when did you got this error (i mean at what step) after that only we can give it a try.
Thanks,
Vinod

Serial number error while creating the production order

Hello frds,
I am getting the following error while creating the production order.
"Item 000000 requires exactly 100 serial numbers for the asset".
If i give 100 serial numbers in the order, the error is solved. But i do not want to assign 100 serial numbers, i want to assign only 2 numbers.
I have tried using the new serial number profile also, but it is giving same error.
Kindly guide.
Regards,
Narendra Bora

Dear Narendra
Select the serial number profile and go to serialization procedure and set the ser. usage status 02 - Optional as below.
Procd Procedure description Ser.Usage
PPRL PP order release 02
since the serail number creation is optional for order relase this will allow you to relase with out error and with serail number assigned in partial.
Regards
Soundar

Datamover error while creating the peopletools system database

i am using
os=suse linux 12.2
database = db2 9.72
peopletools = 8.53
i am getting the following error while running the datamover script for the peopletools system databse. i have attached the following error for your view plz help me........
db2inst1@linux2:~/PT853/bin> ./psdmtx -CT DB2UNIX -CD SL290101 -FP /home/db2inst1/PT853/scripts/sl290101dbx.dms
PeopleTools 8.53 - Data Mover
Copyright (c) 2013 PeopleSoft, Inc.
All Rights Reserved
Started: Tue Feb 26 13:12:25 2013
Data Mover Release: 8.53
Database: SL290101 (ENG)
Input file: /home/db2inst1/PT853/data/ptengs.db (ENG)
Commit done at end of record
Importing ACCESS_GRP_LANG
Import ACCESS_GRP_LANG 0
SQL Error. Error Position: 0 Return: -2300 - End of fetch (SQLSTATE PS001)
RUN STATISTICS FOR TABLE (PS_ACCESS_GRP_LANG,LOW)
Error: SQL execute error for %UpdateStats(PS_ACCESS_GRP_LANG)
Error: Import Record name ACCESS_GRP_LANG
Ended: Tue Feb 26 13:12:30 2013
Unsuccessful completion

thanks for reply anygma,
datamover script created the PS_ACCESS_GRP_LANG table in an back end so i think no need to create that record in an application designer....
And also i edit that datamover script as set start after ACCESS_GRP_LANG now its again return the same error for the next table but in back end the table are created.......
db2inst1@linux2:~/PT853/bin> ./psdmtx -CT DB2UNIX -CD SL290101 -FP /home/db2inst1/PT853/scripts/sl290101dbx.dms
PeopleTools 8.53 - Data Mover
Copyright (c) 2013 PeopleSoft, Inc.
All Rights Reserved
Started: Wed Feb 27 03:17:03 2013
Data Mover Release: 8.53
Database: SL290101 (ENG)
Input file: /home/db2inst1/PT853/data/ptengs.db (ENG)
Commit done at end of record
Searching ACCESS_GRP_LANG ... please wait
Found ACCESS_GRP_TBL
Restart record ACCESS_GRP_TBL
Importing ACCESS_GRP_TBL
Creating Table ACCESS_GRP_TBL
Import ACCESS_GRP_TBL 58
Building required indexes for ACCESS_GRP_TBL
SQL Error. Error Position: 0 Return: -2300 - A table or view could not be found (SQLSTATE PS601)
RUN STATISTICS FOR TABLE (PS_ACCESS_GRP_TBL,LOW)
Error: SQL execute error for %UpdateStats(PS_ACCESS_GRP_TBL)
Error: Import Record name ACCESS_GRP_TBL
SQL Spaces: 0 Tables: 1 Triggers: 0 Indexes: 1 Views: 0
Ended: Wed Feb 27 03:17:14 2013
Unsuccessful completion

Error while executing the Job for Objects :null Batch Risk Analysis

Hi All,
We've recently upgraded Virsa to version 5.3_14 . I'm encountering a problem when executing the Batch Risk Analysis job for users, roles and profiles. The job does not complete for some objects and it seems to be sporadic and shows this error: -
Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
I've attached the log for your review.
Thanks in advance for your help.
Linda Lewis
Feb 9, 2011 1:47:53 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
FINEST: ObjAuthMatcher constructed: 4ms, #singles=2141, #ranges=0, #super=0
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
WARNING: Job ID:395 : Failed to run Risk Analysis
java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1019)
at com.virsa.cc.xsys.util.RuleLoader.getPermRule(RuleLoader.java:573)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1609)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:321)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1166)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1464)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
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.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
WARNING: Error: while executing BatchRiskAnalysis for JobId=395 and object(s):ABROWN: Skipping error to continue with next object: null Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job for Object(s) :ABROWN:null
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
INFO: --- BKG User Permission Analysis (System: P20:020) completed --- elapsed time: 4522 ms
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
Edited by: Linda Lewis on Feb 9, 2011 9:08 PM

Hi,
Was a solution found for this error?
Thanks,
Glen

Error while running the Managed server

Hi
i am getting the below error while running the Managed server.
java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
 at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
 at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
 at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
 at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050633> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050711> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
####<Dec 6, 2011 7:47:30 PM IST> <Error> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050726> <BEA-149231> <Unable to set the activation state to true for the application 'DMS Application [Version=11.1.1.1.0]'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "Spy" failed to preload on startup in Web application: "dms.war".
java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
 at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
 at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
 at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
 at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
 at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
 at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
 at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
 at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
can anyone help

Srinath is 100% correct.
If the deployment failed, then there will very likely be some mention in the log.
You state that you checked the log, but you didn't mention whether you found an error, no error, a successful startup, etc. you are providing painfully few details to assist.
I would bet if you posted your .log and .out logs to Pastebin.com - #1 paste tool since 2002 and provided us links, We would be able to point out the error.
Lacking that information, my best advice would be to re-install and double-check you're completing all steps in the correct order.
Also, be sure to always search the product documentation first, the search this forum. For basic issues (e.g., standard installation), there is a high probability that someone else has asked that question.
I hope that helps,
-ryan

Error while installing the named instance SQL 2012 Sp1

Hi,
I am getting below error while installing the named instance with features Data base engine. on same server box 2 named instance already installed and working...please suggest. i have done a lot of troubleshooting..(configure local system for Db engines
during installation, tried to install after another domain ID., repair and uninstalled existing and retried.) .. please s if i need to do anything else to resolve the issue.. installation account is domain admin account...
Can i rename the installation domain account profile from sql server that used for 2 named instance and for 3 rd named instance i am trying... is any impact after profile rename from the local sql server on any instance already configured...
Shailendra Dev

thanks alberto.
here is
2015-03-24 19:48:49.42 Server Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-03-24 19:48:49.42 Server (c) Microsoft Corporation.
2015-03-24 19:48:49.42 Server All rights reserved.
2015-03-24 19:48:49.42 Server Server process ID is 3460.
2015-03-24 19:48:49.42 Server System Manufacturer: 'Xen', System Model: 'HVM domU'.
2015-03-24 19:48:49.42 Server Authentication mode is WINDOWS-ONLY.
2015-03-24 19:48:49.42 Server Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG'.
2015-03-24 19:48:49.42 Server The service account is 'AIRWORKS\scadmin'. This is an informational message; no user action is required.
2015-03-24 19:48:49.42 Server Registry startup parameters:
-d D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\master.mdf
-e D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG
-l D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\mastlog.ldf
2015-03-24 19:48:49.42 Server Command Line Startup Parameters:
-s "SCSMDB"
-m "SqlSetup"
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2015-03-24 19:48:49.69 Server SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-24 19:48:49.69 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-24 19:48:49.69 Server Detected 15624 MB of RAM. This is an informational message; no user action is required.
2015-03-24 19:48:49.69 Server Using conventional memory in the memory manager.
2015-03-24 19:48:49.98 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-03-24 19:48:50.01 Server This instance of SQL Server last reported using a process ID of 5124 at 3/24/2015 7:48:48 PM (local) 3/24/2015 2:18:48 PM (UTC). This is an informational message only; no user action is required.
2015-03-24 19:48:50.03 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-03-24 19:48:50.07 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.
2015-03-24 19:48:50.30 Server Database Mirroring Transport is disabled in the endpoint configuration.
2015-03-24 19:48:50.58 spid5s Warning ******************
2015-03-24 19:48:50.65 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2015-03-24 19:48:50.66 spid5s Starting up database 'master'.
2015-03-24 19:48:50.90 spid5s 9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 19:48:51.04 Server CLR version v4.0.30319 loaded.
2015-03-24 19:48:51.17 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 19:48:51.17 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-03-24 19:48:51.39 Server Software Usage Metrics is enabled.
2015-03-24 19:48:51.81 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-03-24 19:48:51.83 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-24 19:48:51.86 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-03-24 19:48:52.02 spid5s SQL Trace ID 1 was started by login "sa".
2015-03-24 19:48:52.16 spid5s Server name is 'AWISCDB\SCSMDB'. This is an informational message only. No user action is required.
2015-03-24 19:48:52.35 spid12s The certificate [Cert Hash(sha1) "151C8B90A9A8AF12F5EFAE3439F691E2C01A7355"] was successfully loaded for encryption.
2015-03-24 19:48:52.35 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SCSMDB ].
2015-03-24 19:48:52.40 spid12s 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.
2015-03-24 19:48:52.43 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: 0x490, state: 16. Failure to register a SPN might cause integrated
authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-03-24 19:48:52.45 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
message. No user action is required.
2015-03-24 19:48:54.03 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service.
2015-03-24 19:48:54.03 spid14s A new instance of the full-text filter daemon host process has been successfully started.
2015-03-24 19:48:54.86 spid6s Starting up database 'mssqlsystemresource'.
2015-03-24 19:48:54.86 spid5s Starting up database 'msdb'.
2015-03-24 19:48:54.87 spid6s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-03-24 19:48:55.21 spid5s 12 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 19:48:55.32 spid5s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 19:48:55.32 spid6s Starting up database 'model'.
2015-03-24 19:48:55.32 spid5s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2015-03-24 19:48:55.72 spid6s Clearing tempdb database.
2015-03-24 19:48:57.22 spid6s Starting up database 'tempdb'.
2015-03-24 19:48:59.04 spid5s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184551476 to level 184552376.
2015-03-24 19:48:59.04 spid5s ----------------------------------
2015-03-24 19:48:59.04 spid5s Starting execution of PRE_MSDB.SQL
2015-03-24 19:48:59.04 spid5s ----------------------------------
2015-03-24 19:49:00.23 spid5s Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2015-03-24 19:49:00.57 spid5s -----------------------------------------
2015-03-24 19:49:00.57 spid5s Starting execution of PRE_SQLAGENT100.SQL
2015-03-24 19:49:00.57 spid5s -----------------------------------------
2015-03-24 19:49:00.61 spid5s Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
2015-03-24 19:49:00.73 spid5s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:00.73 spid5s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.78 spid5s Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 19:49:01.79 spid5s Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-03-24 19:49:01.80 spid5s DBCC TRACEOFF 1717, server process ID (SPID) 5. This is an informational message only; no user action is required.
2015-03-24 19:49:01.80 spid5s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2015-03-24 19:49:01.81 spid5s
2015-03-24 19:49:01.81 spid5s Creating table temp_sysjobschedules
2015-03-24 19:49:01.91 spid5s
2015-03-24 19:49:01.91 spid5s Alter table sysdownloadlist...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table sysjobhistory...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table systargetservers...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table sysjobsteps...
2015-03-24 19:49:01.99 spid5s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.99 spid5s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.99 spid5s
2015-03-24 19:49:01.99 spid5s -----------------------------------------
2015-03-24 19:49:01.99 spid5s Execution of PRE_SQLAGENT100.SQL complete
2015-03-24 19:49:01.99 spid5s -----------------------------------------
2015-03-24 19:49:02.01 spid5s DMF pre-upgrade steps...
2015-03-24 19:49:02.13 spid5s DC pre-upgrade steps...
2015-03-24 19:49:02.13 spid5s Check if Data collector config table exists...
2015-03-24 19:49:02.13 spid5s Data Collector state before upgrade: 0
2015-03-24 19:49:02.13 spid5s pre_dc100::Check if syscollector_collection_sets_internal table exists...
2015-03-24 19:49:02.13 spid5s pre_dc100::Capturing Collection set status in temp table...
2015-03-24 19:49:02.19 spid5s Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2015-03-24 19:49:02.19 spid5s End of DC pre-upgrade steps.
2015-03-24 19:49:02.19 spid5s DAC pre-upgrade steps...
2015-03-24 19:49:02.19 spid5s Starting DAC pre-upgrade steps ...
2015-03-24 19:49:02.19 spid5s End of DAC pre-upgrade steps.
2015-03-24 19:49:02.19 spid5s ----------------------------------
2015-03-24 19:49:02.19 spid5s Starting execution of MSDB.SQL
2015-03-24 19:49:02.19 spid5s ----------------------------------
2015-03-24 19:49:02.23 spid5s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:02.23 spid5s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:02.27 spid5s Checking the size of MSDB...
2015-03-24 19:49:02.53 spid5s
2015-03-24 19:49:02.53 spid5s Setting database option TRUSTWORTHY to ON for database 'msdb'.
2015-03-24 19:49:02.53 spid5s Setting database option RECOVERY to SIMPLE for database 'msdb'.
2015-03-24 19:49:02.64 spid5s ----------------------------------
2015-03-24 19:49:02.64 spid5s Finished execution of MSDB.SQL
2015-03-24 19:49:02.64 spid5s ----------------------------------
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Starting execution of MSDB_VERSIONING.SQL
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Finished execution of MSDB_VERSIONING.SQL
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Dropping view MSdatatype_mappings...
2015-03-24 19:49:02.65 spid5s Dropping view sysdatatypemappings...
2015-03-24 19:49:02.65 spid5s Dropping table MSdbms_datatype_mapping...
2015-03-24 19:49:02.66 spid5s Dropping table MSdbms_map...
2015-03-24 19:49:02.67 spid5s Dropping table MSdbms_datatype...
2015-03-24 19:49:02.67 spid5s Dropping table MSdbms...
2015-03-24 19:49:02.73 spid5s Creating table MSdbms
2015-03-24 19:49:02.75 spid5s Creating table MSdbms_datatype
2015-03-24 19:49:03.01 spid5s Creating table MSdbms_map
2015-03-24 19:49:03.02 spid5s Creating table MSdbms_datatype_mapping
2015-03-24 19:49:03.03 spid5s Definining default datatype mappings
2015-03-24 19:49:03.04 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE8
2015-03-24 19:49:03.21 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE9
2015-03-24 19:49:03.29 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE10
2015-03-24 19:49:03.37 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE11
2015-03-24 19:49:03.46 spid5s Creating datatype mappings for MSSQLSERVER to DB2
2015-03-24 19:49:03.54 spid5s Creating datatype mappings for MSSQLSERVER to SYBASE
2015-03-24 19:49:03.62 spid5s Creating datatype mappings for ORACLE8 to MSSQLSERVER
2015-03-24 19:49:03.71 spid5s Creating datatype mappings for ORACLE9 to MSSQLSERVER
2015-03-24 19:49:03.83 spid5s Creating datatype mappings for ORACLE10 to MSSQLServer
2015-03-24 19:49:03.95 spid5s Creating datatype mappings for ORACLE11 to MSSQLServer
2015-03-24 19:49:04.08 spid5s Creating view MSdatatype_mappings
2015-03-24 19:49:04.08 spid5s Creating view sysdatatypemappings
2015-03-24 19:49:05.08 spid5s
2015-03-24 19:49:05.08 spid5s Creating table syssubsystems...
2015-03-24 19:49:05.09 spid5s
2015-03-24 19:49:05.09 spid5s Creating view sysproxyloginsubsystem_view...
2015-03-24 19:49:05.11 spid5s
2015-03-24 19:49:05.11 spid5s Creating trigger trig_sysoriginatingservers_delete...
2015-03-24 19:49:05.11 spid5s
2015-03-24 19:49:05.11 spid5s Creating view sysoriginatingservers_view...
2015-03-24 19:49:05.12 spid5s
2015-03-24 19:49:05.12 spid5s Creating trigger trig_sysjobs_insert_update...
2015-03-24 19:49:05.13 spid5s
2015-03-24 19:49:05.13 spid5s Creating view sysjobs_view...
2015-03-24 19:49:05.15 spid5s
2015-03-24 19:49:05.15 spid5s Creating trigger trig_sysschedules_insert_update...
2015-03-24 19:49:05.16 spid5s
2015-03-24 19:49:05.16 spid5s Creating view sysschedules_localserver_view...
2015-03-24 19:49:05.21 spid5s
2015-03-24 19:49:05.21 spid5s Creating view systargetservers_view...
2015-03-24 19:49:05.23 spid5s
2015-03-24 19:49:05.23 spid5s Creating view sysalerts_performance_counters_view...
2015-03-24 19:49:05.25 spid5s
2015-03-24 19:49:05.25 spid5s Creating function SQLAGENT_SUSER_SNAME ...
2015-03-24 19:49:05.25 spid5s
2015-03-24 19:49:05.25 spid5s Creating function SQLAGENT_SUSER_SID ...
2015-03-24 19:49:05.26 spid5s
2015-03-24 19:49:05.26 spid5s Creating procedure SP_SQLAGENT_IS_SRVROLEMEMBER...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating procedure sp_verify_category_identifiers...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating function agent_datetime...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating procedure sp_verify_proxy_identifiers...
2015-03-24 19:49:05.28 spid5s
2015-03-24 19:49:05.28 spid5s Creating procedure sp_verify_credential_identifiers...
2015-03-24 19:49:05.29 spid5s
2015-03-24 19:49:05.29 spid5s Creating procedure sp_verify_subsystems...
2015-03-24 19:49:05.30 spid5s
2015-03-24 19:49:05.30 spid5s Creating procedure sp_verify_subsystem_identifiers...
2015-03-24 19:49:05.30 spid5s
2015-03-24 19:49:05.30 spid5s Creating procedure sp_verify_login_identifiers...
2015-03-24 19:49:05.31 spid5s
2015-03-24 19:49:05.31 spid5s Creating procedure sp_verify_proxy...
2015-03-24 19:49:05.31 spid5s
2015-03-24 19:49:05.31 spid5s Creating procedure sp_add_proxy...
2015-03-24 19:49:05.32 spid5s
2015-03-24 19:49:05.32 spid5s Creating procedure sp_delete_proxy...
2015-03-24 19:49:05.32 spid5s
2015-03-24 19:49:05.32 spid5s Creating procedure sp_update_proxy...
2015-03-24 19:49:05.33 spid5s
2015-03-24 19:49:05.33 spid5s Creating procedure sp_sqlagent_is_member...
2015-03-24 19:49:05.33 spid5s
2015-03-24 19:49:05.33 spid5s Creating procedure sp_verify_proxy_permissions...
2015-03-24 19:49:05.34 spid5s
2015-03-24 19:49:05.34 spid5s Creating procedure sp_help_proxy...
2015-03-24 19:49:05.35 spid5s
2015-03-24 19:49:05.35 spid5s Creating procedure sp_get_proxy_properties...
2015-03-24 19:49:05.36 spid5s
2015-03-24 19:49:05.36 spid5s Creating procedure sp_grant_proxy_to_subsystem...
2015-03-24 19:49:05.36 spid5s
2015-03-24 19:49:05.36 spid5s Creating procedure sp_grant_login_to_proxy...
2015-03-24 19:49:05.37 spid5s
2015-03-24 19:49:05.37 spid5s Creating procedure sp_revoke_login_from_proxy...
2015-03-24 19:49:05.37 spid5s
2015-03-24 19:49:05.37 spid5s Creating procedure sp_revoke_proxy_from_subsystem...
2015-03-24 19:49:05.38 spid5s
2015-03-24 19:49:05.38 spid5s Creating procedure sp_enum_proxy_for_subsystem...
2015-03-24 19:49:05.38 spid5s
2015-03-24 19:49:05.38 spid5s Creating procedure sp_enum_login_for_proxy...
2015-03-24 19:49:05.39 spid5s
2015-03-24 19:49:05.39 spid5s Creating procedure sp_reassign_proxy...
2015-03-24 19:49:05.40 spid5s
2015-03-24 19:49:05.40 spid5s Creating procedure sp_sqlagent_get_startup_info...
2015-03-24 19:49:05.41 spid5s
2015-03-24 19:49:05.41 spid5s Creating procedure sp_sqlagent_update_agent_xps...
2015-03-24 19:49:05.42 spid5s
2015-03-24 19:49:05.42 spid5s Creating procedure sp_sqlagent_has_server_access...
2015-03-24 19:49:05.45 spid5s
2015-03-24 19:49:05.45 spid5s Creating procedure sp_sqlagent_get_perf_counters...
2015-03-24 19:49:05.46 spid5s
2015-03-24 19:49:05.46 spid5s Creating procedure sp_sqlagent_notify...
2015-03-24 19:49:05.47 spid5s
2015-03-24 19:49:05.47 spid5s Creating procedure sp_is_sqlagent_starting...
2015-03-24 19:49:05.47 spid5s
2015-03-24 19:49:05.47 spid5s Creating procedure sp_verify_job_identifiers...
2015-03-24 19:49:05.48 spid5s
2015-03-24 19:49:05.48 spid5s Creating procedure sp_verify_schedule_identifiers...
2015-03-24 19:49:05.49 spid5s
2015-03-24 19:49:05.49 spid5s Creating procedure sp_verify_jobproc_caller...
2015-03-24 19:49:05.50 spid5s
2015-03-24 19:49:05.50 spid5s Creating procedure sp_downloaded_row_limiter...
2015-03-24 19:49:05.51 spid5s
2015-03-24 19:49:05.51 spid5s Creating procedure sp_post_msx_operation...
2015-03-24 19:49:05.54 spid5s
2015-03-24 19:49:05.54 spid5s Creating procedure sp_verify_performance_condition...
2015-03-24 19:49:05.58 spid5s
2015-03-24 19:49:05.58 spid5s Creating procedure sp_verify_job_date...
2015-03-24 19:49:05.59 spid5s
2015-03-24 19:49:05.59 spid5s Creating procedure sp_verify_job_time...
2015-03-24 19:49:05.61 spid5s
2015-03-24 19:49:05.61 spid5s Creating procedure sp_verify_alert...
2015-03-24 19:49:05.62 spid5s
2015-03-24 19:49:05.62 spid5s Creating procedure sp_update_alert...
2015-03-24 19:49:05.63 spid5s
2015-03-24 19:49:05.63 spid5s Creating procedure sp_delete_job_references...
2015-03-24 19:49:05.65 spid5s
2015-03-24 19:49:05.65 spid5s Creating procedure sp_delete_all_msx_jobs...
2015-03-24 19:49:05.66 spid5s
2015-03-24 19:49:05.66 spid5s Creating procedure sp_generate_target_server_job_assignment_sql...
2015-03-24 19:49:05.66 spid5s
2015-03-24 19:49:05.66 spid5s Creating procedure sp_generate_server_description...
2015-03-24 19:49:05.67 spid5s
2015-03-24 19:49:05.67 spid5s Creating procedure sp_msx_set_account...
2015-03-24 19:49:05.68 spid5s
2015-03-24 19:49:05.68 spid5s Creating procedure sp_msx_get_account...
2015-03-24 19:49:05.69 spid5s
2015-03-24 19:49:05.69 spid5s Creating procedure sp_delete_operator...
2015-03-24 19:49:05.70 spid5s
2015-03-24 19:49:05.70 spid5s Creating procedure sp_msx_defect...
2015-03-24 19:49:05.71 spid5s
2015-03-24 19:49:05.71 spid5s Creating procedure sp_msx_enlist...
2015-03-24 19:49:05.72 spid5s
2015-03-24 19:49:05.72 spid5s Creating procedure sp_delete_targetserver...
2015-03-24 19:49:05.73 spid5s
2015-03-24 19:49:05.73 spid5s Creating procedure sp_enlist_tsx
2015-03-24 19:49:05.74 spid5s
2015-03-24 19:49:05.74 spid5s Creating procedure sp_get_sqlagent_properties...
2015-03-24 19:49:05.76 spid5s
2015-03-24 19:49:05.76 spid5s Create procedure sp_set_sqlagent_properties...
2015-03-24 19:49:05.76 spid5s
2015-03-24 19:49:05.76 spid5s Creating procedure sp_add_targetservergroup...
2015-03-24 19:49:05.77 spid5s
2015-03-24 19:49:05.77 spid5s Creating procedure sp_update_targetservergroup...
2015-03-24 19:49:05.78 spid5s
2015-03-24 19:49:05.78 spid5s Creating procedure sp_delete_targetservergroup...
2015-03-24 19:49:05.78 spid5s
2015-03-24 19:49:05.78 spid5s Creating procedure sp_help_targetservergroup...
2015-03-24 19:49:05.79 spid5s
2015-03-24 19:49:05.79 spid5s Creating procedure sp_add_targetsvgrp_member...
2015-03-24 19:49:05.80 spid5s
2015-03-24 19:49:05.80 spid5s Creating procedure sp_delete_targetsvrgrp_member...
2015-03-24 19:49:05.81 spid5s
2015-03-24 19:49:05.81 spid5s Creating procedure sp_verify_category...
2015-03-24 19:49:05.81 spid5s
2015-03-24 19:49:05.81 spid5s Creating procedure sp_add_category...
2015-03-24 19:49:05.82 spid5s
2015-03-24 19:49:05.82 spid5s Creating procedure sp_update_category...
2015-03-24 19:49:05.83 spid5s
2015-03-24 19:49:05.83 spid5s Creating procedure sp_delete_category...
2015-03-24 19:49:05.83 spid5s
2015-03-24 19:49:05.84 spid5s Creating procedure sp_help_category...
2015-03-24 19:49:05.84 spid5s
2015-03-24 19:49:05.84 spid5s Creating procedure sp_help_targetserver...
2015-03-24 19:49:05.85 spid5s
2015-03-24 19:49:05.85 spid5s Creating procedure sp_resync_targetserver...
2015-03-24 19:49:06.06 spid5s
2015-03-24 19:49:06.06 spid5s Creating procedure sp_purge_jobhistory...
2015-03-24 19:49:06.09 spid5s
2015-03-24 19:49:06.09 spid5s Creating procedure sp_help_jobhistory...
2015-03-24 19:49:06.10 spid5s
2015-03-24 19:49:06.10 spid5s Creating procedure sp_add_jobserver...
2015-03-24 19:49:06.11 spid5s
2015-03-24 19:49:06.11 spid5s Creating procedure sp_delete_jobserver...
2015-03-24 19:49:06.11 spid5s Error: 10011, Severity: 16, State: 1.
2015-03-24 19:49:06.11 spid5s Access denied.
2015-03-24 19:49:06.11 spid5s Error: 917, Severity: 15, State: 1.
2015-03-24 19:49:06.11 spid5s An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message for the line which caused compilation to fail.
2015-03-24 19:49:06.11 spid5s Error: 912, Severity: 21, State: 2.
2015-03-24 19:49:06.11 spid5s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 917, state 1, severity 15. This is a serious error condition which might interfere with regular
operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective
actions and re-start the database so that the script upgrade steps run to completion.
2015-03-24 19:49:06.11 spid5s Error: 3417, Severity: 21, State: 3.
2015-03-24 19:49:06.11 spid5s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books
Online.
2015-03-24 19:49:06.12 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2015-03-24 19:49:06.50 spid12s The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service.
Shailendra Dev

Error While Promoting the Numbers to Next Level

Similar Messages

Maybe you are looking for