Component ID error in Repeater

I am trying to create a simple form in a Repeater, but I'm
getting the following compiler error on a RadioButtonGroup that
exists in the form:
Unable to generate initialization code within Repeater, due
to id or data binding on a component that is not a visual child.
Here is the code that generated this:
<mx:FormItem label="Select the user's role:">
<mx:RadioButtonGroup id="roleType" />
<mx:RadioButton groupName="roleType" id="roleTypeAdmin"
value="ADMIN" label="ADMIN" />
<mx:RadioButton groupName="roleType" id="roleTypeUser"
value="USER" label="USER" selected="true" />
</mx:FormItem>
Does anyone have any insight as to why this might be
happening?
Thanks.

Similar Messages

After soak test update, I get error messages repeatedly. The majority are "unfortunately, messaging has stopped", but you can replace messaging with "android os", or any other process, as it happens with more than just messaging. I have had numerous peopl

After soak test update, I get error messages repeatedly. The majority are "unfortunately, messaging has stopped", but you can replace messaging with "android os", or any other process, as it happens with more than just messaging. I have had numerous people call and ask why I didn't reply to their texts...and I look, but have not received any new texts. YES, I have restarted phone. I have cleared data as well as cache on all apps. I have downloaded the vzw messaging app, which seems silly, since it happens with several different processes and apps, but all to no avail. I am missing texts from my employer, from my family. This did happen, but rarely, before this "soak test". It is now Kitkat version 19.6.3.obake_verizon.en.US. THIS is when I started having problems...like 50 times a day kind of problems! I have seen hundreds of posts all over the internet over the past 3 days. Does no one know how to fix this??? Shouldn't there be a way to revert phone to a pre-update state? and no, hard reset did NOT work!!!! I have been with verizon for well over 15 years, but I have not upgraded my lines and will not in July either. This is ridiculous. It's not like my games aren't working, it is my messaging and "android os"...my lifeline at work!

kristinaf333,
Oh no, I am sorry to hear your messages are not working since the software update. I greatlly appreciate doing all that troubleshooting to try and get the messaging application back in business. I know how much I rely on my messages so I can understand the urgency to get this resolved. Have you had a resolution ticket opened since you started experiencing issues with your messages? Does this happen with all contacts or just some? Please provide additional information to ensure we get to the bottom of this for you.
KarenC_VZW
Follow us on Twitter @VZWSupport

I can't burn a disc from Itunes without getting error 4280 repeatedly.

I can't burn a disc from Itunes without getting error 4280 repeatedly. I was just able to burn a CD and now can't burn another. Any thoughts? I know my CD burner works as I just made a disc. I have tried changing file type from Audio to MP3 with no luck. Thanks for trying to help me.

Hello Sonni,
It sounds like you are unable to burn a disc with iTunes due to this error code. I would first use the following article to check issues with the type of disc drive:
Burning disc in iTunes for Windows using a Sony CD-RW/DVD CRX830E model drive fails with 4280 error
http://support.apple.com/kb/ta38101
If this is not the case, use the following article to help troubleshoot the issue:
iTunes for Windows: Additional troubleshooting tips for burning issues
http://support.apple.com/kb/TS1374
Thank you for using Apple Support Communities.
Cheers,
Sterling

Pojo/List/ManagedBean/ADF RF component yeilds error "Target Unreachable", J

Hello JDevelopers;
(Pojo/List/ManagedBean/ADF RF component yields error "Target Unreachable", JSF component does not.)
I am attempting to convert a page with jsf/html components to a page with ADF RF components.
I am using a pojo that returns a List.
The pojo is registered as a ManagedBean in adfc-config file.
I am not using a data control.
It all works fine with jsf/html components.
The following <h:inputText> works fine when using jsf/html component.
     <h:inputText value="#{taskRnDController.task.taskNum}" required="true" </h:inputText>
Changing it to an <af:inputText component and running the app produces the error listed below;
     <af:inputText value="#{taskRnDController.task.taskNum}" id="it1" label="Label 1" required="true"/>
<LifecycleImpl> <_handleException> ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6
javax.el.PropertyNotFoundException: Target Unreachable, 'task' returned null
     at com.sun.el.parser.AstValue.getTarget(Unknown Source)
     at com.sun.el.parser.AstValue.isReadOnly(Unknown Source)
     at com.sun.el.ValueExpressionImpl.isReadOnly(Unknown Source)
this is the adfc-config file
<managed-bean id="__3">
<managed-bean-name id="__2">taskRnDController</managed-bean-name>
<managed-bean-class id="__1">com.myorg.facade.TaskRnDController<;/managed-bean-class>
<managed-bean-scope id="__4">session</managed-bean-scope>
</managed-bean>
I need an <af:form> and an <af:table> components on the same page so that when a user
inserts a new record on the form and presses save btn it is immediately displayed
within the <af:table>.
I am stuck and any help is much appreciated.
Edited by: 848693 on Jun 15, 2011 4:28 PM

you just want to bind your input text to backing bean .then why you are using list ?
It is very simple just use any variable and bind with your UI component
Thanks
Prateek

When I am trying to assign mobile component getting error

Hi All,
Whenever I am trying to find mobile component which newly added I am getting following error.
com.sap.ip.mi.admin.core.ApplicationException: Field CHANGEDAT not a member of MEAPPLICATION_INTERFACE
Apart that I am getting following error in another window.
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
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:
   java.lang.NullPointerException
    at com.sap.ip.mi.admin.wd.device.DeviceMaintenance.supplyUserList1(DeviceMaintenance.java:794)
    at com.sap.ip.mi.admin.wd.device.wdp.InternalDeviceMaintenance.supplyUserList1(InternalDeviceMaintenance.java:562)
    at com.sap.ip.mi.admin.wd.device.wdp.IPublicDeviceMaintenance$IUserList1Node.doSupplyElements(IPublicDeviceMaintenance.java:7220)
    at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:408)
    at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:351)
    ... 41 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13
Version     null
DOM version     null
Client Type     ns7
Client Type Profile     nn7
ActiveX     disabled
Cookies     enabled
Frames     enabled
Java Applets     enabled
JavaScript     enabled
Tables     enabled
VB Script     enabled
Server
Web Dynpro Runtime     Vendor: SAP, build ID: 7.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Fri Oct 12 05:11:00 PDT 2007
J2EE Engine     7.00 patchlevel
Java VM     Java HotSpot(TM) Server VM, version:1.4.2_09-b05, vendor: Sun Microsystems Inc.
Operating system     Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale     en_US
Time of Failure     Wed Apr 16 14:56:36 PDT 2008 (Java Time: 1208382996754)
Web Dynpro Code Generation Infos
sap.com/tclmwebadminmainframewd
SapDictionaryGenerationCore     7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore     7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwddispwda
No information available     null
sap.com/tclmwebadminsldwd
SapDictionaryGenerationCore     7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore     7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwdcorecomp
No information available     null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.ip.mi.admin.wd.device.DeviceMaintenance.supplyUserList1(DeviceMaintenance.java:794)
     at com.sap.ip.mi.admin.wd.device.wdp.InternalDeviceMaintenance.supplyUserList1(InternalDeviceMaintenance.java:562)
     at com.sap.ip.mi.admin.wd.device.wdp.IPublicDeviceMaintenance$IUserList1Node.doSupplyElements(IPublicDeviceMaintenance.java:7220)
     at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:408)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:351)
     at com.sap.tc.webdynpro.progmodel.context.Node.createMappedElementList(Node.java:500)
     at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:395)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:351)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:339)
     at com.sap.tc.webdynpro.progmodel.context.Node.size(Node.java:723)
     at com.sap.ip.mi.admin.wd.device.AssignMobileComponentView.wdDoInit(AssignMobileComponentView.java:124)
     at com.sap.ip.mi.admin.wd.device.wdp.InternalAssignMobileComponentView.wdDoInit(InternalAssignMobileComponentView.java:332)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:398)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:311)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.handle(ApplicationWindow.java:277)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.handleWindowEvents(ApplicationWindow.java:262)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:149)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks in advance.
Regards,
Ameer.

Are you using "Shared" HR? You can refer to note >1074384.6 on Metalink for a resolution to this issue. If you are using the full install of HR then refer to note > 786785.1 on Metalink
Edited by: pillair on Jun 12, 2012 9:03 PM

Insert data using peoplesoft webservice gives component API error

Hi,
I am using jdeveloper 11g to consume a peoplesoft webservice using the wsdl file and JAX-Ws approach to build the proxy.
I have been successfull in getting to work the "get", "find" methods for the webservice but while trying to access the create/Update(inserting data) method, it gives me the following exception.
In CREATE method
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Component Interface API.
     at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
     at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:135)
     at $Proxy32.createCompIntfcKCMWEBCASECI(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstance$ClientInstanceInvocationHandler.invoke(ClientInstance.java:363)
     at $Proxy33.createCompIntfcKCMWEBCASECI(Unknown Source)
     at project1.proxy.KCM_WEB_CASE_CISoapClient.createKCMMethod(KCM_WEB_CASE_CISoapClient.java:318)
     at project1.proxy.KCM_WEB_CASE_CISoapClient.main(KCM_WEB_CASE_CISoapClient.java:116)
Process exited with exit code 1.
From the exception it is not clear what is missing or where am i going wrong. I have provided all the mandatory values required by the method.
The create method generated needs almost 40 parameters, hence i am intializing all of them and sending it.
Few parameters are INOUT or out mode, depending on that i even created the required holder etc.
I dont have any access to peoplesoft logs, is there a way to debug this further.
Basically i am stuck here as i am not able to decode this exception.
Can anyone tell me where is it failing, is it a some formation error or is it creating a query at db and getting a sql error??
as mentioned earlier, its very difficult to get access to db resources hence its becmong very difficult to debug the error.
Any help will be appreciated.
Thank you in advance
Ashvini
Edited by: [email protected] on Jun 7, 2010 7:49 AM
Edited by: [email protected] on Jun 8, 2010 6:37 AM

Hi, I have exact the same problem. Have you got any answer for this problem yet? Please forward it to me if you have one. Many thanks.

Internal Error while repeatedly querying

I’m having a problem when I try to repeatedly query the Berkley XML DB. I’m using XML DB 2.3.8 on Windows and Java 1.4.2_13.
Typically my first 2000 or so queries will work, and then they will begin to fail with the following exception.
com.sleepycat.dbxml.XmlException: std::exception thrown from C++ API: bad allocation, errcode = INTERNAL_ERROR
     at com.sleepycat.dbxml.dbxml_javaJNI.XmlManager_query__SWIG_2(Native Method)
     at com.sleepycat.dbxml.XmlManager.query(XmlManager.java:606)
I assume the problem is that I’m not setting something up properly or not cleaning up objects after each query. I was hoping someone could tell me what the exception could be caused by and what I should check my code for.
If it helps my code basically does the following:
During initialization open an environment
For each query
1)     open container
2)     Create an XmlQueryContext
3)     Obtain an XmlResults object by calling XmlManager.query(String, XmlQueryContext)
4)     Obtain an XmlValue by calling XmlResults.next()
5)     Obtain an XmlDocument by calling XmlValue.asDocument()
6)     Call XmlContainer.delete()
7)     Call XmlQueryContext.delete()
8)     Call XmlResults.delete()
9)     Call XmlValue.delete()
10)     Call XmlDocument.delete()
My environment is being opened with the following parameters:
EnvironmentConfig config = new EnvironmentConfig();
config.setCacheSize(50 * 1024 * 1024);
config.setMaxLockers(100000);
config.setMaxLockObjects(100000);
config.setMaxLocks(100000);
config.setAllowCreate(true);
config.setInitializeCache(true);
config.setTransactional(true);
config.setInitializeLocking(true);
config.setInitializeLogging(true);
config.setAllowCreate(true);
config.setErrorStream(System.err);
//config.setRunFatalRecovery(true);
config.setRunRecovery(true);
The container is being opened with the following parameters:
XmlContainerConfig config = new XmlContainerConfig();
config.setTransactional(true);
config.setAllowCreate(true);
Thanks,
Eric

Hi Eric,
You will probably need to delete each XmlValue and XmlDocument in the loop before getting a new one. I expect this is why you are seeing odd errors, which are almost certainly out of memory issues.
John

NWDS: Component deploying error

Hi,
i'm trying to deply a component with NWDS. But it raise the error:
<i>None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.</i>
Visual Adm, SMD works fine; access to DTR granted.
configuration:
NWDS 7.0.11
sap.com UMEADMIN 7.00 SP11 (1000.7.00.11.0.20061128062751) SAP AG MAIN_APL70SP_C 20061128144405
sap.com BI_MMR 7.00 SP10 (1000.7.00.10.0.20061021201000) SAP AG SAP AG 20061128135902
sap.com BI_UDI 7.00 SP10 (1000.7.00.10.0.20061021205400) SAP AG SAP AG 20061128140800
sap.com SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500) SAP AG SAP AG 20061128135127
sap.com SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500) SAP AG SAP AG 20061128135123
sap.com BASETABLES 7.00 SP10 (1000.7.00.10.0.20061022040500) SAP AG SAP AG 20061128135125
sap.com SAP_JTECHF 7.00 SP10 (1000.7.00.10.0.20061022040800) SAP AG SAP AG 20061128135124
sap.com SAP_JTECHS 7.00 SP10 (1000.7.00.10.0.20061022040900) SAP AG SAP AG 20061128140701
Name: Java HotSpot(TM) Server VM
Vendor: Sun Microsystems Inc.
Version: 1.4.2_12-b03
full log here:
16.07.2007 15:29:04 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[008]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\F48\JC30\SDM\program\log\sdmcl20070716112902.log]/>
<!PATTERN[sdmcl20070716112902.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1251]/>
<!LOGHEADER[END]/>
Jul 16, 2007 3:29:02 PM Info: -
Starting deployment -
Jul 16, 2007 3:29:02 PM Info: Error handling strategy: OnErrorStop
Jul 16, 2007 3:29:02 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jul 16, 2007 3:29:02 PM Info: Update strategy: UpdateAllVersions
Jul 16, 2007 3:29:02 PM Info: Starting deployment prerequisites:
Jul 16, 2007 3:29:02 PM Info: Loading selected archives...
Jul 16, 2007 3:29:02 PM Info: Loading archive 'C:\usr\sap\F48\JC30\SDM\program\temp\temp65389sap.compcui_gpxsscfg.sda'
Jul 16, 2007 3:29:02 PM Info: Selected archives successfully loaded.
Jul 16, 2007 3:29:02 PM Info: Actions per selected component:
Jul 16, 2007 3:29:02 PM Info: Initial deployment: Selected development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP53SP_D'/'1166839'/'0' will be deployed.
Jul 16, 2007 3:29:02 PM Info: Ending deployment prerequisites. All items are correct.
Jul 16, 2007 3:29:02 PM Info: Saved current Engine state.
Jul 16, 2007 3:29:02 PM Info: Starting: Initial deployment: Selected development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP53SP_D'/'1166839'/'0' will be deployed.
Jul 16, 2007 3:29:02 PM Info: SDA to be deployed: C:\usr\sap\F48\JC30\SDM\root\origin\sap.com\pcui_gp\xsscfg\MAIN_ERP53SP_D\0\1166839\temp65389sap.compcui_gpxsscfg.sda
Jul 16, 2007 3:29:02 PM Info: Software type of SDA: J2EE
Jul 16, 2007 3:29:02 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 16, 2007 3:29:04 PM Info: Begin of log messages of the target system:
07/07/16 15:29:02 - ***********************************************************
07/07/16 15:29:02 - Start updating EAR file...
07/07/16 15:29:02 - start-up mode is lazy
07/07/16 15:29:03 - EAR file updated successfully for 120ms.
07/07/16 15:29:03 - Start deploying ...
07/07/16 15:29:03 - EAR file uploaded to server for 541ms.
07/07/16 15:29:04 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/pcui_gp_xsscfg.ear.
                     Reason: None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:570)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at java.security.AccessController.doPrivileged(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                     For detailed information see the log file of the Deploy Service.
07/07/16 15:29:04 - ***********************************************************
Jul 16, 2007 3:29:04 PM Info: End of log messages of the target system.
Jul 16, 2007 3:29:04 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 16, 2007 3:29:04 PM Error: Aborted: development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP53SP_D'/'1166839'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/pcui_gp_xsscfg.ear.
Reason: None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jul 16, 2007 3:29:04 PM Info: Starting to save the repository
Jul 16, 2007 3:29:04 PM Info: Finished saving the repository
Jul 16, 2007 3:29:04 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jul 16, 2007 3:29:04 PM Error: -
At least one of the Deployments failed -
any advices?
Best regards,
Dima

Hello Ken,
Im tried to deploy this application as a prerequisite of ESS development, but with other DC the same problem. Anyway I'm a newbie in all these tools using, so I just don't know where and how I should check - is "GP installed" or not... and what means "None of the available containers", what they are?
Cheers,
Dima

Component Usage error in MSS Leave Request approval

Hi All,
We are getting the below mentioned error only for few users while approving the leave request in MSS.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
    ... 41 more
Kindly share your views on the same.
Thanks and Regards,
Vivek.

Hi Anup,
Please find the complete Trace below.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; MS-RTC LM 8)
Version     null
DOM version     null
Client Type     msie6
Client Type Profile     ie6
ActiveX     enabled
Cookies     enabled
Frames     enabled
Java Applets     enabled
JavaScript     enabled
Tables     enabled
VB Script     enabled
Server
Web Dynpro Runtime     Vendor: SAP, build ID: 7.0013.20080611120129.0000 (release=NW04S_13_REL, buildtime=2008-09-11:17:05:50[UTC], changelist=42127, host=pwdfm114), build date: Wed Nov 19 19:21:28 CET 2008
J2EE Engine     7.00 patchlevel 109044.44
Java VM     IBM J9 VM, version:2.3, vendor: IBM Corporation
Operating system     AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale     en
Time of Failure     Sat Jan 02 12:26:56 CET 2010 (Java Time: 1262431616916)
Web Dynpro Code Generation Infos
sap.com/ess~lea
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwddispwda
No information available     null
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwdcorecomp
No information available     null
sap.com/pcui_gp~tecl
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
       at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
       at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
       at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
       at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
       at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
       at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:258)
       at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
       at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
       at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
       at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
       at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
       at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:841)
       at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1071)
       at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
       at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
       at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
       at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
       at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
       at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
       at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
       at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
       at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
       at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
       at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
       at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
       at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
       at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
       at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
       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:387)
       at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
       at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
       at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
       at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
       at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
       at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
       at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
       at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
       at java.security.AccessController.doPrivileged(AccessController.java:219)
       at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
       at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks and Regards,
Vivek.

Component SMS_MP_CONTROL_MANAGER error 4951

Good Day everybody! I have sccm2012 r2 primary site. After install in component status component SMS_MP_CONTROL_MANAGER shows error 4951. This is a chunk of mpMSI.log file:
Property(S): CcmValidateServerConfig_ActionText = Validates that IIS, BITS and WebDAV is installed and properly configured setup.
12:54:00] Getting settings from WMI and storing in D:\SMS_CCM\polmig.mof
CustomAction CcmMigratePolicySettingsInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (60:84) [12:54:00:442]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (60:84) [12:54:00:442]: Machine policy value 'DisableRollback' is 0
MSI (s) (60:84) [12:54:00:442]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 12:54:00: CcmMigratePolicySettingsInit. Return value 3.
MSI (s) (60:84) [12:54:00:442]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (60:84) [12:54:00:442]: No System Restore sequence number for this installation.
MSI (s) (60:84) [12:54:00:442]: Unlocking Server
Action ended 12:54:00: INSTALL. Return value 3.
Property(S): UpgradeCode = {ABD0F60F-1622-4311-8989-106B60D784FF}
Property(S): SourceDir = D:\Microsoft Configuration Manager\bin\x64\
Property(S): TARGETDIR = D:\SMS_CCM\
Property(S): ALLUSERS = 1
Property(S): ErrorDialog = ErrorDialog
Property(S): ProductName = ConfigMgr Management Point
Property(S): ProductCode = {F33B71BE-4C5F-4D30-82F2-96686638F622}
Property(S): PackageCode = {A64E1F54-C094-4AB7-9F58-C5D896BACE0B}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 5.00.7958.1000
Property(S): ProductLanguage = 1033
Property(S): CompleteDialog_SubTitle = Setup has finished updating your system.
Property(S): CompleteDialog_Info = Setup was successful.
Property(S): UserExitDialog_Title = Setup Aborted
Property(S): UserExitDialog_SubTitle = Setup was cancelled
Property(S): UserExitDialog_Info = The ConfigMgr Management Point setup was cancelled.
Property(S): InstallErrorDialog_Title = Setup Aborted
Property(S): InstallErrorDialog_SubTitle = Setup failed
Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue.
Property(S): PolReqStagingDir.1114972D_590D_4AB6_BA2E_779928CEDCC2 = D:\SMS_CCM\PolReqStaging\
Property(S): SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\Windows\SysWOW64\
Property(S): System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\Windows\system32\
Property(S): CcmDefaultPolicyAuthority = SMS:MP:Default:{F33B71BE-4C5F-4D30-82F2-96686638F622}
Property(S): MPVDirRoot.67022EC1_A401_46E9_91FC_2DF2ED04CF15 = D:\SMS_CCM\SMS_MP\
Property(S): Res1033.0EACD2EE_412B_4985_9727_96BC217AABD8 = D:\SMS_CCM\1033\
Property(S): Res1033.4CB41E5B_59DE_4D09_98C5_332377961F73 = D:\SMS_CCM\1033\
Property(S): MsiLogFileLocation = D:\Microsoft Configuration Manager\logs\mpMSI.log
Property(S): ProductState = -1
I did reinstall BITS. But this component still shows error. I need your expert help. Thanks!

This is MPSetup.log
<08/07/14 10:00:04> SMSMP Setup Started....
<08/07/14 10:00:04> Parameters: D:\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:INF-SCCM SMSMP 0
<08/07/14 10:00:04> Installing Pre Reqs for SMSMP
<08/07/14 10:00:04> ======== Installing Pre Reqs for Role SMSMP ========
<08/07/14 10:00:04> Found 3 Pre Reqs for Role SMSMP
<08/07/14 10:00:04> Pre Req MSXML60 found.
<08/07/14 10:00:04> No versions of MSXML60 are installed. Would install new MSXML60.
<08/07/14 10:00:04> Enabling MSI logging. msxml6_x64.msi will log to D:\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<08/07/14 10:00:04> Installing D:\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<08/07/14 10:00:04> msxml6_x64.msi exited with return code: 0
<08/07/14 10:00:04> msxml6_x64.msi Installation was successful.
<08/07/14 10:00:04> Pre Req CcmSetup found.
<08/07/14 10:00:04> Installing pre-req using command line "D:\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp
<08/07/14 10:00:04> Pre-req installer "D:\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp finished with exit code 0
<08/07/14 10:00:04> Pre Req SqlNativeClient found.
<08/07/14 10:00:04> SqlNativeClient already installed (Product Code: {49D665A2-4C2A-476E-9AB8-FCC425F526FC}). Would not install again.
<08/07/14 10:00:04> Pre Req SqlNativeClient is already installed. Skipping it.
<08/07/14 10:00:04> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<08/07/14 10:00:04> Installing the SMSMP
<08/07/14 10:00:04> Passed OS version check.
<08/07/14 10:00:04> IIS Service is installed.
<08/07/14 10:00:04> No versions of SMSMP are installed. Installing new SMSMP.
<08/07/14 10:00:04> Enabling MSI logging. mp.msi will log to D:\Microsoft Configuration Manager\logs\mpMSI.log
<08/07/14 10:00:04> Installing D:\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0
CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<08/07/14 10:00:07> mp.msi exited with return code: 1603
<08/07/14 10:00:07> Backing up D:\Microsoft Configuration Manager\logs\mpMSI.log to D:\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<08/07/14 10:00:07> Fatal MSI Error - mp.msi could not be installed.
<08/07/14 10:00:07> ~RoleSetup().
mpMSI.log is very huge and i can't post it there. How I can add him as attachment?

Is a user defined for component AF - error ?

Hi All,
In my RWD > Component Monitoring - I have an alert showing up on the Adapter Engine, for the Self-Test Status. The error is on "Is a user defined for component AF?"
Any ideas how to resolve this ??
Thanks
Shane

If this is in "Is a user defined for component AF" in red click on the details next to it ...it will show up what the problem is...
Usually XI uses XIAFUSER to connect to AF....Check whether these user is specified in exchange profile and then also check whether this existing and not locked...
Hope this helps...
Regards,
Ravi.
PS. Please post the solution once you solve your problem, so that it helps others and also close the question.

Could not resolve to a component implementation error

I am using the SuperImage component from
http://www.quietlyscheming.com/blog/2007/01/23/some-thoughts-on-doubt-on-flex-as-the-best- option-orhow-i-made-my-flex-images-stop-dancing/
The problem I am having is that when I try to use this
component in a TileList ItemRenderer, I recieve the error Could not
resolve <qs:SuperImage> to a component implementation.
In my Application tag, I use xmlns:qs="qs.controls.*" which
allows me to use the SuperImage component anywhere else, but the
error occurs when I use it in a Component.
I have searched for an answer but could not find anything
that worked. Can anyone help me figure out what is wrong? Below is
the code where the error occurs.
<mx:TileList>
<mx:itemRenderer>
<mx:Component>
<mx:VBox>
<qs:SuperImage/>
<mx:Label/>
</mx:VBox>
</mx:Component>
</mx:itemRenderer>
</mx:TileList>
Thank you for any help.

Why would Component not be able to find the package, but
everywhere else in the same file can?
If I add <qs:SuperImage/> right before the TileList, it
works correctly. Is there a way to specify the classpath for
Component specifically? I wasn't able to find a way to do
that.

Webdynpro Development Component project error

Hi All,
I am trying to use a DC1(Development Component) in another DC2 component, but when i am trying to deploy and run the application of DC2, which use the DC1 component. It is giving error like below.
java.lang.UnsupportedClassVersionError: com/hp/dc1/wdp/InternalDc1Comp1 (Unsupported major.minor version 49.0)
Can anybody help me in solve out this.
Thanks in advance,
Ravi

Hi Ravi,
This problem is not with the DC you are creating. This exception can occur when the source is compiled on one version of JDK that is not supported by JDK attemting to run it. In your case your DC was built targeting only JDK 1.5, but the Portal server JDK might be 1.4 or different then JDK 1.5.
You can check the JDK version of the server and if its other than JDK 1.5 then installed the same version on your machine to compile the code.
Hope this will resolve your problem.
Regards,
Nikhil

Problem with EL evalulation when used to assign component ID in ui:repeat

Hello everyone,
I've a problem when I try to assign the ID of a component with an EL within an ui:repeat component, e.g.:
0 <ui:repeat value="#{dm.categories}" var="category">
1      <rich:panel id="catPanel#{category.id}">
2         ....
3       </rich:panel>
4       <someohtertag someatt="catPanel#{category.id}" />
5 </ui:repeat>The above page renders correctly but the id in line 1 evaluates to ...catPanel in HTML. The other tag evaluates of course correctly to catPanel123.
When I use an EL variable from outside of the repeat tag it evaluates.
Am I doing something wrong here or are the ID attributes evaluated in a different rendering pass?
Does anyone have another idea how to assign the IDs in such a manner?
ciao,
Elmar

Hi,
Check in t.code CMOD whether project is active or not (Activate the Project)
BR,
Vijay

Tree Component AS3 Error

When I click a leaf in the Tree Component I have a function
called using the itemClick Property. When I click a node (the
folder icons) I get the AS3 error below. Does this only show up
with Debug versions of Flash Player. Plus how do I stop this error
from occurring if the user happens to have the debug version
installed?
Error #2044: Unhandled ioError:. text=Error #2032: Stream
Error.
at main/loadMyXML()
at main/collectionSelect()
at main/__gTree_itemClick()
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()
at mx.controls.listClasses::ListBase/mouseClickHandler()
at mx.controls::Tree/mouseClickHandler()

ORA-00600 internal errors should be reported to Oracle Support by SR. If you don't have a support contract try searching the web for more information and possible fixes or workarounds.
From the information available on MOS, if the type of the PG.ID_PAR_PLANO_GER column is not VARCHAR2, then try converting P22_ID_PAR_PLANO_GER to the same type.

Component ID error in Repeater

Similar Messages

Maybe you are looking for