Component Definition and Arrays in 8
Is there any way to get the component inspector window to
display the numbers next to items in an array? It's rediculous that
they won't appear, is it a bug? I'm on a Mac G5 OS 10.4.5.
Dan P.
you can assign a variable's default value in the component
definition dialog box, but you must initialize the variable in your
class definition and you must define what that variable does in
your class definition.
Similar Messages
-
Hello Team,
We have upgraded from Siebel 8.1.1.3 to Siebel Open UI 8.1.1.11.
But after up-gradation we are getting the below error in "My Account Opportunity" View.
We detected an Error which may have occurred for one or more of the following reasons:
Join in business component definition 'CG Opportunity My Accounts' has source fields that come from tables 'S_OPTY' and 'S_ORG_EXT'(SBL-DAT-00452).
Thanks,
Tirupati Nanda
Mob:-9742404115Hello Team,
We have upgraded from Siebel 8.1.1.3 to Siebel Open UI 8.1.1.11.
But after up-gradation we are getting the below error in "My Account Opportunity" View.
We detected an Error which may have occurred for one or more of the following reasons:
Join in business component definition 'CG Opportunity My Accounts' has source fields that come from tables 'S_OPTY' and 'S_ORG_EXT'(SBL-DAT-00452).
Thanks,
Tirupati Nanda
Mob:-9742404115 -
How to extract every component in an array?
Hello everyone!
Do you know how to extract every component from an array field?
For example:
The following is the defination of a table:
CREATE TABLE test (
id NUMBER PRIMARY KEY,
name VARCHAR2(32),
shape MDSYS.SDO_GEOMETRY
And then I insert a new record:
INSERT INTO test VALUES(
1,'first',
MDSYS.SDO_GEOMETRY(
2003,
NULL,
NULL,
MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),
MDSYS.SDO_ORDINATE_ARRAY(1,1, 5,7)
The Question is I want to read the every component (for example 1,1,5,7) in the sdo_ordinate_array one by one. Who knows how to write the SQL?
I have tried "select a.shape.sdo_ordinates(1) from test a". But it can't work.
Thank you very much!One solution is to read each ordinate from a cursor ina SQL block. Here is an example:
set serveroutput on
SET serveroutput on SIZE 1000000
set concat on
DEFINE layername = 'LAYER';
DEFINE geomcolname = 'GEOM';
DECLARE
id varchar2(10);
longitude number;
latitude number;
logmile number;
i number;
theLayer varchar2(32);
theGeomCol varchar2(32);
BEGIN
FOR rec IN (SELECT ROWID, id, &geomcolname FROM &layername ) LOOP
id := rec.id;
i := 1;
while i < rec.geom.sdo_ordinates.count loop
longitude:=rec.geom.sdo_ordinates(i);
latitude:=rec.geom.sdo_ordinates(i+1);
logmile:=rec.geom.sdo_ordinates(i+2);
dbms_output.put_line(id || ',' || longitude || ',' || latitude || ',' || logmile);
i := i + 3;
end loop;
END LOOP;
commit;
END;
Maybe that will help.
Dave
David R. Miller
Michael Baker Jr., Inc.
3601 Eisenhower Avenue
Alexandria, VA 22314
[email protected]
www.mbakercorp.com -
Set icon of component in an array
Hello,
i seem to have a slight problem. I hope there is someone who can help me.
I wrote an applet with all kinds of components in it. If you click a button, the icon of the button changed. All of this worked fine until i wanted all of my components stored in an array and create my components dynamically. So, not the usual way by creating a button with:
JButton nameofbutton = new JButton(imageicon),
but in a function with:
addbutton(new JButton(),"LichtVoorButton", lichtvoor,320,78,149,19, contentPane)
This way i can't reach the button the ordinary way in the actionlistener (nameofbutton.setIcon(icon)).....
Is there an other way?
I've included the important parts of my source code.
I hope there is someone who can help me.
Thanks in advance.
public class test extends JApplet{
public test(){
comps = new Component[0];
contentPane = getContentPane();
contentPane.setLayout(new BorderLayout());
addbuttons();
public void addComponent(Component component){
//function to add a component to the array (works fine)
public void addbuttons(){
addbutton(new JButton(),"LichtVoorButton", lichtvoor,320,78,149,19, contentPane);
public void addbutton(JButton button, String buttonnaam, ImageIcon licht, int x, int y, int width, int height, Container pane){
button.setName(buttonnaam);
button.setBorder(BorderFactory.createRaisedBevelBorder());
button.setIcon(licht);
button.setBounds(x, y, width, height);
button.addActionListener(new ButtonEvent());
addComponent(button);
class ButtonEvent implements ActionListener {
public void actionPerformed(ActionEvent e){
Object source = e.getSource();
for( int i=0; i<comps.length; i++ ) {
if(comps[ i].equals(source)){
if(comps[ i].getName().equals("LichtVoorButton")){
/******* the line that doesn't work ********/
comps[ i].setIcon(icon.gif);//doesn't work!
comps[ i].revalidate();
}Thanks, but i can't set the icon of the button directly like
(JButton)e.getSource().setIcon(lichtvoor); or
(JButton)comps.setIcon(lichtvoor).. I get the error 'not a statement'.
is this the only way?:
JButton tempbutton = (JButton)e.getSource();
tempbutton.setIcon(lichtvoor);
comps[i]=tempbutton -
RT Build Specifications: Component Definition Category is unresponsive
Hi,
I am using LabVIEW 2013 SP1 f2, with Real-Time 13.0.1
When I open the Properties page for a Real-Time Application build specification (to run on a cRIO-9075), and select the Component Definition category, I find that the following occurs:
- LabVIEW becomes unresponsive, and thinks for a while. It takes approximately 20-30 seconds or so to finally show the Component Defintion page.
- When I click on Create a component definition file (.cdf), nothing happens. As I write this, I see "Required software components", and then these are greyed out: "Software component description", and "Software version" - but there is nothing to select or change?
- If I click on another category, it takes in the order of 20 seconds to finally show this category.
- To close the build spec (by pressing OK), it also takes a long time (more than 60 seconds).
- Things are fine with the build spec if I never enter the Component Definition category.
Is anyone else experiencing this?
Any help would be appreciated.
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au
Solved!
Go to Solution.Hey Chris,
I believe the following patch is the fix that you are looking for.
LabVIEW Real-Time Module 2013 SP1 Application Builder Patch Details
http://digital.ni.com/public.nsf/allkb/D72B45C6905D327A86257CC800547992?OpenDocument
There's a link to download the patch at the bottom of that page.
Regards,
Ryan -
Error when create project definition and 2 wbs by bapi BAPI_PROJECT_MAINTAI
Hello everyone,
I have to create project definition and 2 wbs, I use function BAPI_PROJECT_MAINTAI but I have the error:
"WBS element 0033.3332.01.R already exists" but that wbs it's created.
This is my code.
data:
I_WBS_ELEMENT_TABLE type BAPI_WBS_ELEMENT occurs 0 with header line,
I_WBS_ELEMENT_TABLE_UPDATE type BAPI_WBS_ELEMENT_UPDATE occurs 0 with header line,
I_PROJECT_DEFINITION like BAPI_PROJECT_DEFINITION,
I_PROJECT_DEFINITION_UPD like BAPI_PROJECT_DEFINITION_UP,
I_METHOD_PROJECT type BAPI_METHOD_PROJECT occurs 0 with header line,
E_MESSAGE_TABLE like BAPI_METH_MESSAGE occurs 0 with header line,
RETURN type BAPIRETURN1,
lv_index LIKE bapi_method_project-refnumber.
lv_index = 1.
I_METHOD_PROJECT-OBJECTTYPE = 'ProjectDefinition'.
I_METHOD_PROJECT-METHOD = 'Create'.
I_METHOD_PROJECT-OBJECTKEY = '0033.3332'.
I_METHOD_PROJECT-REFNUMBER = lv_index.
append I_METHOD_PROJECT.
lv_index = lv_index + 1.
I_METHOD_PROJECT-OBJECTTYPE = 'WBS-Element'.
I_METHOD_PROJECT-METHOD = 'Create'.
I_METHOD_PROJECT-OBJECTKEY = '0033.3332.01'.
I_METHOD_PROJECT-REFNUMBER = lv_index.
append I_METHOD_PROJECT.
lv_index = lv_index + 1.
clear I_METHOD_PROJECT.
I_METHOD_PROJECT-OBJECTTYPE = 'WBS-Element'.
I_METHOD_PROJECT-METHOD = 'Create'.
I_METHOD_PROJECT-OBJECTKEY = '0033.3332.01.R'.
I_METHOD_PROJECT-REFNUMBER = lv_index.
append I_METHOD_PROJECT.
clear I_METHOD_PROJECT.
I_METHOD_PROJECT-OBJECTTYPE = space.
I_METHOD_PROJECT-METHOD = 'Save'.
I_METHOD_PROJECT-OBJECTKEY = space.
I_METHOD_PROJECT-REFNUMBER = space.
append I_METHOD_PROJECT.
I_PROJECT_DEFINITION-PROJECT_DEFINITION = '0033.3332'.
I_PROJECT_DEFINITION-DESCRIPTION = 'Training project'.
I_PROJECT_DEFINITION-PROJECT_PROFILE = 'ZAF0001'.
I_PROJECT_DEFINITION-COMP_CODE = '0033'.
I_PROJECT_DEFINITION-RESPONSIBLE_NO = 1.
I_PROJECT_DEFINITION-APPLICANT_NO = 1.
I_PROJECT_DEFINITION-PLANT = '033A'.
I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION = '0033.3332'.
I_WBS_ELEMENT_TABLE-WBS_ELEMENT = '0033.3332.01'.
I_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS 1'.
I_WBS_ELEMENT_TABLE-RESPONSIBLE_NO = 1.
I_WBS_ELEMENT_TABLE-APPLICANT_NO = 1.
I_WBS_ELEMENT_TABLE-COMP_CODE = '0033'.
I_WBS_ELEMENT_TABLE-PROFIT_CTR = '0033A99999'.
I_WBS_ELEMENT_TABLE-PLANT = '033A'.
append i_wbs_element_table.
clear I_WBS_ELEMENT_TABLE.
I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION = '0033.3332'.
I_WBS_ELEMENT_TABLE-WBS_ELEMENT = '0033.3332.01.R'.
I_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS 2'.
I_WBS_ELEMENT_TABLE-RESPONSIBLE_NO = 1.
I_WBS_ELEMENT_TABLE-APPLICANT_NO = 1.
I_WBS_ELEMENT_TABLE-COMP_CODE = '0033'.
I_WBS_ELEMENT_TABLE-PROFIT_CTR = '0033A99999'.
I_WBS_ELEMENT_TABLE-PLANT = '033A'.
append i_wbs_element_table.
PERFORM fill_update_flags USING 'BAPI_PROJECT_DEFINITION_UP'
CHANGING I_PROJECT_DEFINITION_UPD.
PERFORM fill_update_flags USING 'BAPI_WBS_ELEMENT_UPDATE'
CHANGING I_WBS_ELEMENT_TABLE_UPDATE.
append I_WBS_ELEMENT_TABLE_UPDATE.
append I_WBS_ELEMENT_TABLE_UPDATE.
CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
EXPORTING
I_PROJECT_DEFINITION = I_PROJECT_DEFINITION
I_PROJECT_DEFINITION_UPD = I_PROJECT_DEFINITION_UPD
TABLES
I_METHOD_PROJECT = I_METHOD_PROJECT
I_WBS_ELEMENT_TABLE_UPDATE = I_WBS_ELEMENT_TABLE_UPDATE[]
I_WBS_ELEMENT_TABLE = I_WBS_ELEMENT_TABLE[]
E_MESSAGE_TABLE = E_MESSAGE_TABLE
write: / 'Finish'.
*& Form FILL_UPDATE_FLAGS
FORM fill_update_flags USING value(p_ddic_name)
CHANGING p_struc_upd.
DATA: lt_dd03l LIKE dd03l OCCURS 0,
ls_dd03l LIKE dd03l.
DATA: s(40), c(40), sc(80) TYPE c.
FIELD-SYMBOLS: <s>, <c>, <sc> TYPE ANY.
TRANSLATE p_ddic_name TO UPPER CASE.
SELECT * FROM dd03l INTO TABLE lt_dd03l WHERE tabname = p_ddic_name.
s = 'P_STRUC_UPD'.
ASSIGN (s) TO <s>.
LOOP AT lt_dd03l INTO ls_dd03l.
ASSIGN ls_dd03l-fieldname TO <c>.
ASSIGN COMPONENT <c> OF STRUCTURE <s> TO <sc>.
<sc> = 'X'.
ENDLOOP.
ENDFORM. " FILL_UPDATE_FLAGS
Please help me!
Thank you!
Edited by: kishan P on Sep 10, 2010 9:37 AMHi,
Please try creating the project definition and then call the FM again to create the WBS.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/4c/226a7246e611d189470000e829fbbd/frameset.htm
Hope it helps.
Sujay -
Strange behaviour of "And array Elements"
If u connect an empty boolean array to "And Array Elements" function, The output is "True" !. Is this correct?. Is there something wrong ?. Please Help.
Hi J.A.C
This is correct.This is an explanation I've found: "This behavior is intentiional, and stems from elementary Boolean logic. The Boolean algebra primitives are analogous to numeric operations are integers. Just as the identity element for addition is 0, and for multiplication, 1; the identity for Boolean OR is FALSE, and for AND, TRUE. For example, x^0 == 1; that is, x times itself zero times is by definition 1. For the same reason boolean x ANDed with itself zero times is TRUE."
If this is not acceptable for your application, then just use the "Array Size" VI first to check if you've an empty Array (Array size=0) and then you can pass or not the array to the "And Array Elements" function.
Hope this helps.
Luca
Regards,
Luca -
Edit Component Definition button not working
Hello,
I am using Studio Edition Version 11.1.1.4.0 (Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923) and have a little problem with the property inspector.
I've created a JSF page and added an ADF Mater Table, Detail Table section.
When I click on either of the tables I can see the properties in the property inspector but when I click on the Edit Component Definition button nothing happens, no error, no new window.
Any idea what could be wrong?
Cheers,
AndyAnd suddenly it started to work. Not sure what happend.
--Andy -
Does creating a component definition in UI write to tables or schema ?
When I create a custom component in the UI in Enterprises > Component Definitions - let's say a Workflow Monitor Agent - and I activate it, I understand it will update the enterprise gateway store (siebns.dat). Will this also write to any tables in the database or update the siebel schema in any way?
We are in the middle of an upgrade from 8.1.1.3 SEA to 8.1.1.9 SIA. Currently our application stack is at release 8.1.1.9 SIA GA but our repository is still at 8.1.1.3 SEA. We want to create the header custom component definitions in the application UI to match what is in Dev to prepare for a cfgmerge after the upgphys is completed. Our concern is the risk of doing this while the app tier is not at the same release level as the repository. If we are only dealing with updates to the siebns.dat then I think we should be ok, and the cfgmerge will take care of it. But if we are writing to tables when I create these custom components in the UI then we have potential issues.
Thanks for any feedback!
Regards,
Michael Smith
Siebel Administrator
Strategic Technology Group
Gartner Group
Office: 1-203-964-0096 ext. 3450
Mobile: 1-505-720-7385I checked the Business Component in Tools and see it is based on virtual table (V_SRS_COMP) and not on a physical table.
So it looks like it doesn't write to the DB. -
Definition and use of Warehouse Request and Warehouse Order in WM
Can any one please give me the definition and use of Warehouse Request and Warehouse Order in warehouse management?
Thanks in advance.
Regards,
Nagi ReddyAs per my understanding :
Warehouse request is similar to transfer of requirements.
Warehouse Order is similar to Transfer Orders.
If iam not wrong pls go through this...
Transfer Requirement Locate the document in its SAP Library structure
Definition
This is a document that serves to plan goods movements using the Warehouse Management System (WMS).
By differentiating between the planning and execution of a goods movement, you can recognize immediately whether a goods movement needs to be still executed (transfer requirement is open), is currently being executed (transfer order is created), or is completed ( transfer order is confirmed).
Use
On the one hand, transfer requirements are used to pass on information on goods movements that are posted in Inventory Management (MM-IM) to the Warehouse Management System (WMS). You can, however, also use transfer requirements for the following purposes:
To initiate goods movements in WMS
To initiate material replenishment for production storage bins in the production supply areas using the Production Planning (PP) component
To call up transfer requirement reports in order to get an overview of all pending goods movements
On the basis of existing transfer requirements, the Warehouse Management System creates transfer orders, which, in turn, serve to execute the physical goods movements in the warehouse.
The system updates the transfer requirement:
When you create, confirm or cancel a transfer order
When you cancel a goods receipt or goods issue posting in Inventory Management (MM-IM) before the respective transfer order was generated in the Warehouse Management System (WMS).
In this case, the system automatically reduces the transfer requirement quantity by the quantity to be canceled, or it deletes the transfer requirement altogether if the entire requirement quantity is to be canceled.
Structure
A transfer requirement consists of a transfer requirement header with general information and one or several transfer requirement items with material information (see the section Creating Transfer Requirements).
The transfer requirement contains all the necessary information on a planned goods movement.
What should be moved?
Which quantity should be moved?
When should it be moved?
The planning date is important for further automatic processing.
Which transfer type is the basis of the goods movement?
Each goods movement in the warehouse is classified by a transfer type indicator. This key differentiates between:
A stock putaway
A stock pick
A stock transfer
Why is it to be moved?
Was the transfer order created as a result of a purchase order or a production order, or was it created manually?
Transfer Order
Definition
Document used for executing goods movements with the help of Warehouse Management (WM). Logical, physical goods movements or stock changes can be the basis for a transfer order. These include:
Picks
Putaways
Posting changes
Repacking
Inventory
Use
As a rule, you create the transfer order with reference to a source document from WMS or other SAP application components. A source document can be a:
Delivery document
Tansfer requirement
Material document
Posting change notice
The transfer order contains all the information required to execute the physical transfer of materials into the warehouse, out of the warehouse, or from one storage bin to another storage bin within the warehouse. In addition, it is also used for executing logical stock transfers. Logical transfers of stock occur, for example, when goods are released from inspection and made available for general use. These logical transfers are called posting changes in WM.
When you confirm a transfer order, you inform the system that it has been processed and that the goods have arrived at the intended destination (see the section on confirming transfer orders). If the planned quantity (target quantity) differs from the actual quantity of stock that is moved, a difference quantity exists. If you confirm a transfer order with a difference, the difference quantity is automatically posted to an interim storage type for differences (see the section on stock differences).
Once they have been carried out, transfer orders also have a control and monitoring function since they document movements in the warehouse (see Warehouse Controlling).
For certain inventory methods (for example, zero stock check, inventory based on putaway), transfer orders serve as inventory documents. In this case, when the actual quantity is confirmed (after the first putaway into a storage bin), it is updated in the system as the inventory quantity.
Structure
A transfer order contains all the necessary information on a planned goods movement.
What should be moved?
Which quantity should be moved?
Where should the bin be moved from (source storage bin), and where to (destination storage bin)?
The transfer order consists of a transfer order header with general information and one or several transfer order items with material information (see the section on creating transfer orders).
Transfer Order Header
The transfer order header contains the transfer order number and the date that it was created and confirmed. It also identifies the transfer requirement or delivery on which it is based as well as the movement type.
Transfer Order Item
A transfer order can have one or several items. The number of items contained in a transfer order depends on how many storage bins the system accesses in order to reach the total quantity of goods needed for the picking requirement or how many bins are needed to store the goods (putaway).
A transfer order item contains subsections that specify the direction of the goods movement for each item.
Source storage bin
This subsection contains the source storage bin and the quantity of material that is being transferred. It indicates the storage bin from which goods are to be picked (goods issue) or an interim storage type (such as the goods receipt area) from which goods are taken to be put away in the warehouse.
Destination storage bin
This subsection contains the quantity of material that is being transferred and the storage bin into which the goods are to be put away. For example, it may contain a storage bin in a high-rack storage area that has been selected for a stock putaway, or an interim storage type (the goods issue area) for a stock pick.
Return storage bin
If, for example, you have the complete stock requirement set and you pick more stock than required from a storage bin, the system creates a subsection for the return storage bin. This can be the case, for example, when a complete pallet is removed from the shelf, but only a portion of the materials on the pallet is picked. In this case, the remaining quantity can either be returned to its original storage bin or transferred to another one. -
I am looking at code from a book example. A symbol is called
from the library and used on the stage. The class appears to be
dynamic because a reference to a variable called cardface appears
out of nowhere in the as file (fla is set to STRICT). When
debugging, the variable doesn't exist until the line where it is
used. After this the variable can be seen. I am thinking to myself
that the library right-click option "Component definition" would
allow me to set the variable so that it is available in the Class.
Unfortunately there is no guidance in the help system on this. I am
required to endlessly search to try and get help (not yet found).
Why does Adobe not give us this essential help - i.e. how to use
their dialog boxes? I am such a fan of Flash (AS3) but there are
some part of the system still painfully inadequate.
Any pointers would be appeciated.you can assign a variable's default value in the component
definition dialog box, but you must initialize the variable in your
class definition and you must define what that variable does in
your class definition. -
Difference between cost component structure and cost component split
can anyone explain me the difference between cost component structure and cost component split with simple example
thanks
santoshHi ,
cost component structure
Definition
Number that identifies the structure.
Use
In Product Cost Controlling, the cost component structure determines how the results of material costing are updated. The cost component structure groups the costs for each material according to cost component (such as material costs, internal activities, external activities, and overhead). If the material is used in the production of another material, the cost component split (which breaks down the costs according to material costs, internal activities, external activities, overhead, and so forth) remains in the system when the costs are rolled up.
In the cost component split, you also define the following for material costing:
Which part of the costs are fixed costs
Which costs are
cost of goods manufactured and what are sales and administration costs
Which costs are relevant for stock valuation, commercial inventory valuation and tax inventory valuation
When the cost component structure is assigned to the organizational units, you can specify that two cost component splits are created:
Main cost component split
This is the principal cost component split, meaning that it is used in the standard cost estimate, which can be used to update the material master. The main cost component split can be a cost component split for cost of goods manufactured or a primary cost component split.
Auxiliary cost component split
This can exist in addition to the main cost component split, and is not used in the standard cost estimate. It can be used for analysis purposes, in that it can be displayed with the cost estimate and passed on to Profitability Analysis.
In Cost Center Accounting, the cost component structure determines how the results of the activity price calculation are updated. The cost component structure groups the costs for each activity type of the cost center according to components (such as material costs and labor costs). If an internal activity allocation is carried out, the cost component split (which breaks down the costs according to material, labor costs, and so forth) is retained at cost rollup.
If the cost component split is not to be retained, you can create a switching structure for the cost component structure for Cost Center Accounting. In the switching structure, you specify which sender cost component goes into which receiver cost component.
<b>require a cost component structure to calculate prices using cost component split.</b>
For each cost component structure you define a component such as energy, personnel, or raw materials. The components combine all costs occuring for a particular cost element area. In this way, you ensure greater cost transparency in activity price calculation when putting together the activity type prices - for example, it becomes easier to find how much of the activity price is taken up by the material costs.
In activity allocation, the cost component structure remains constant, meaning that the receiver takes on the sender cost elements and that the allocated costs are posted in the same cost components in the receiver as in the sender.
A cost component structure can have a maximum of 40 defined cost components.
Cost components are assigned to cost elements. You thereby determine which cost elements go to which rows in the structure, and how these components are updated in price calculation.
Hope ths helps
Please rewad points
Sunil -
Component SMS_Contol_manager and SMS_Notification_server install failed on SCCM2012
we have try to uninstall client and remove the ccm namespace from wmi, and reisntall MP, no luck
below log from mpmsi.log.lasterror
=== Verbose logging started: 8/27/2014 20:50:23 Build type: SHIP UNICODE 5.00.9600.00 Calling process: H:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
MSI (c) (9C:58) [20:50:23:592]: Resetting cached policy values
MSI (c) (9C:58) [20:50:23:592]: Machine policy value 'Debug' is 0
MSI (c) (9C:58) [20:50:23:592]: ******* RunEngine:
******* Product: h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi
******* Action:
******* CommandLine: **********
MSI (c) (9C:58) [20:50:23:592]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (9C:58) [20:50:23:592]: Grabbed execution mutex.
MSI (c) (9C:58) [20:50:23:594]: Cloaking enabled.
MSI (c) (9C:58) [20:50:23:594]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (9C:58) [20:50:23:594]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (24:FC) [20:50:23:598]: Running installation inside multi-package transaction h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi
MSI (s) (24:FC) [20:50:23:598]: Grabbed execution mutex.
MSI (s) (24:48) [20:50:23:599]: Resetting cached policy values
MSI (s) (24:48) [20:50:23:599]: Machine policy value 'Debug' is 0
MSI (s) (24:48) [20:50:23:599]: ******* RunEngine:
******* Product: h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi
******* Action:
******* CommandLine: **********
MSI (s) (24:48) [20:50:23:599]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (24:48) [20:50:23:603]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (24:48) [20:50:23:605]: SRSetRestorePoint skipped for this transaction.
MSI (s) (24:48) [20:50:23:606]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (24:48) [20:50:23:607]: File will have security applied from OpCode.
MSI (s) (24:48) [20:50:23:619]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi' against software restriction policy
MSI (s) (24:48) [20:50:23:619]: SOFTWARE RESTRICTION POLICY: h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi has a digital signature
MSI (s) (24:48) [20:50:23:619]: SOFTWARE RESTRICTION POLICY: h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (24:48) [20:50:23:619]: MSCOREE not loaded loading copy from system32
MSI (s) (24:48) [20:50:23:621]: End dialog not enabled
MSI (s) (24:48) [20:50:23:621]: Original package ==> h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi
MSI (s) (24:48) [20:50:23:621]: Package we're running from ==> C:\Windows\Installer\6257f6f.msi
MSI (s) (24:48) [20:50:23:624]: APPCOMPAT: Compatibility mode property overrides found.
MSI (s) (24:48) [20:50:23:624]: APPCOMPAT: looking for appcompat database entry with ProductCode '{6CED3AB0-05AF-4C81-8DBE-A62661C26F40}'.
MSI (s) (24:48) [20:50:23:624]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (24:48) [20:50:23:626]: Machine policy value 'TransformsSecure' is 1
MSI (s) (24:48) [20:50:23:627]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (24:48) [20:50:23:627]: Machine policy value 'DisablePatch' is 0
MSI (s) (24:48) [20:50:23:627]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (24:48) [20:50:23:627]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (24:48) [20:50:23:627]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (24:48) [20:50:23:627]: APPCOMPAT: looking for appcompat database entry with ProductCode '{6CED3AB0-05AF-4C81-8DBE-A62661C26F40}'.
MSI (s) (24:48) [20:50:23:627]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (24:48) [20:50:23:627]: Transforms are not secure.
MSI (s) (24:48) [20:50:23:628]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'h:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log'.
MSI (s) (24:48) [20:50:23:628]: Command Line: CCMINSTALLDIR=h:\Program Files\SMS_CCM CCMSERVERDATAROOT=h:\Program Files\Microsoft Configuration Manager USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE
CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 CURRENTDIRECTORY=H:\Program Files\Microsoft Configuration Manager\bin\x64 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=6556
MSI (s) (24:48) [20:50:23:628]: Product Code passed to Engine.Initialize: ''
MSI (s) (24:48) [20:50:23:628]: Product Code from property table before transforms: '{6CED3AB0-05AF-4C81-8DBE-A62661C26F40}'
MSI (s) (24:48) [20:50:23:628]: Product Code from property table after transforms: '{6CED3AB0-05AF-4C81-8DBE-A62661C26F40}'
MSI (s) (24:48) [20:50:23:628]: Product not registered: beginning first-time install
MSI (s) (24:48) [20:50:23:630]: Machine policy value 'DisableMsi' is 1
MSI (s) (24:48) [20:50:23:630]: Product {6CED3AB0-05AF-4C81-8DBE-A62661C26F40} is not managed.
MSI (s) (24:48) [20:50:23:630]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (24:48) [20:50:23:630]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (s) (24:48) [20:50:23:630]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (24:48) [20:50:23:630]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (24:48) [20:50:23:630]: Adding new sources is allowed.
MSI (s) (24:48) [20:50:23:630]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (24:48) [20:50:23:630]: Package name extracted from package path: 'mp.msi'
MSI (s) (24:48) [20:50:23:630]: Package to be registered: 'mp.msi'
MSI (s) (24:48) [20:50:23:631]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (24:48) [20:50:23:631]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (24:48) [20:50:23:631]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (24:48) [20:50:23:631]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (24:48) [20:50:23:631]: Running product '{6CED3AB0-05AF-4C81-8DBE-A62661C26F40}' with elevated privileges: Product is assigned.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CCMINSTALLDIR property. Its value is 'h:\Program Files\SMS_CCM'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CCMSERVERDATAROOT property. Its value is 'h:\Program Files\Microsoft Configuration Manager'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding USESMSPORTS property. Its value is 'TRUE'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding SMSPORTS property. Its value is '80'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding USESMSSSLPORTS property. Its value is 'TRUE'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding SMSSSLPORTS property. Its value is '443'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding USESMSSSL property. Its value is 'TRUE'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding SMSSSLSTATE property. Its value is '0'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CCMENABLELOGGING property. Its value is 'TRUE'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CCMLOGLEVEL property. Its value is '1'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CCMLOGMAXSIZE property. Its value is '1000000'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CCMLOGMAXHISTORY property. Its value is '1'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'H:\Program Files\Microsoft Configuration Manager\bin\x64'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (24:48) [20:50:23:631]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '6556'.
MSI (s) (24:48) [20:50:23:631]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (24:48) [20:50:23:632]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is 'd8d0cefc1249514889002637bb750a41'.
MSI (s) (24:48) [20:50:23:632]: RESTART MANAGER: Session opened.
MSI (s) (24:48) [20:50:23:632]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (s) (24:48) [20:50:23:632]: TRANSFORMS property is now:
MSI (s) (24:48) [20:50:23:632]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (s) (24:48) [20:50:23:633]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming
MSI (s) (24:48) [20:50:23:634]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Favorites
MSI (s) (24:48) [20:50:23:634]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (24:48) [20:50:23:635]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Documents
MSI (s) (24:48) [20:50:23:635]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (24:48) [20:50:23:636]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (24:48) [20:50:23:636]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (24:48) [20:50:23:637]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (24:48) [20:50:23:637]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (24:48) [20:50:23:638]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Local
MSI (s) (24:48) [20:50:23:638]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Pictures
MSI (s) (24:48) [20:50:23:639]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (24:48) [20:50:23:640]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (24:48) [20:50:23:640]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (24:48) [20:50:23:641]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (24:48) [20:50:23:641]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (24:48) [20:50:23:642]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (24:48) [20:50:23:643]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (24:48) [20:50:23:643]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (24:48) [20:50:23:644]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (24:48) [20:50:23:644]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Desktop
MSI (s) (24:48) [20:50:23:645]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (24:48) [20:50:23:645]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (24:48) [20:50:23:645]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (24:48) [20:50:23:648]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (s) (24:48) [20:50:23:648]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (s) (24:48) [20:50:23:648]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (24:48) [20:50:23:648]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (24:48) [20:50:23:648]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (24:48) [20:50:23:648]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\6257f6f.msi'.
MSI (s) (24:48) [20:50:23:648]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi'.
MSI (s) (24:48) [20:50:23:648]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (s) (24:48) [20:50:23:648]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
MSI (s) (24:48) [20:50:23:648]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
MSI (s) (24:48) [20:50:23:648]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (24:48) [20:50:23:648]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:48) [20:50:23:648]: User policy value 'DisableRollback' is 0
MSI (s) (24:48) [20:50:23:648]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
=== Logging started: 8/27/2014 20:50:23 ===
MSI (s) (24:48) [20:50:23:649]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (24:48) [20:50:23:649]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (s) (24:48) [20:50:23:649]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (24:48) [20:50:23:649]: Doing action: INSTALL
Action start 20:50:23: INSTALL.
MSI (s) (24:48) [20:50:23:650]: Running ExecuteSequence
MSI (s) (24:48) [20:50:23:650]: Doing action: System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933
MSI (s) (24:48) [20:50:23:650]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933'
MSI (s) (24:48) [20:50:23:650]: PROPERTY CHANGE: Adding System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933 property. Its value is 'C:\Windows\system32\'.
Action start 20:50:23: System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933.
MSI (s) (24:48) [20:50:23:651]: Doing action: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933
Action ended 20:50:23: System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933. Return value 1.
MSI (s) (24:48) [20:50:23:651]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933'
MSI (s) (24:48) [20:50:23:651]: PROPERTY CHANGE: Adding SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 20:50:23: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933.
MSI (s) (24:48) [20:50:23:651]: Doing action: SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3
Action ended 20:50:23: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933. Return value 1.
MSI (s) (24:48) [20:50:23:652]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3'
MSI (s) (24:48) [20:50:23:652]: PROPERTY CHANGE: Adding SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 20:50:23: SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3.
MSI (s) (24:48) [20:50:23:652]: Doing action: System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3
Action ended 20:50:23: SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3. Return value 1.
MSI (s) (24:48) [20:50:23:652]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3'
MSI (s) (24:48) [20:50:23:652]: PROPERTY CHANGE: Adding System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3 property. Its value is 'C:\Windows\system32\'.
Action start 20:50:23: System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3.
MSI (s) (24:48) [20:50:23:653]: Doing action: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61
Action ended 20:50:23: System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3. Return value 1.
MSI (s) (24:48) [20:50:23:653]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI (s) (24:48) [20:50:23:653]: PROPERTY CHANGE: Adding SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 20:50:23: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61.
MSI (s) (24:48) [20:50:23:653]: Doing action: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61
Action ended 20:50:23: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. Return value 1.
MSI (s) (24:48) [20:50:23:654]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI (s) (24:48) [20:50:23:654]: PROPERTY CHANGE: Adding System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is 'C:\Windows\system32\'.
Action start 20:50:23: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61.
MSI (s) (24:48) [20:50:23:654]: Doing action: SystemFolder.BFC13682_FB8F_4455_9724_4DDBBBF713D7
Action ended 20:50:23: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61. Return value 1.
MSI (s) (24:48) [20:50:23:654]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.BFC13682_FB8F_4455_9724_4DDBBBF713D7'
MSI (s) (24:48) [20:50:23:654]: PROPERTY CHANGE: Adding SystemFolder.BFC13682_FB8F_4455_9724_4DDBBBF713D7 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 20:50:23: SystemFolder.BFC13682_FB8F_4455_9724_4DDBBBF713D7.
MSI (s) (24:48) [20:50:23:655]: Doing action: System64Folder.BFC13682_FB8F_4455_9724_4DDBBBF713D7
Action ended 20:50:23: SystemFolder.BFC13682_FB8F_4455_9724_4DDBBBF713D7. Return value 1.
MSI (s) (24:48) [20:50:23:655]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.BFC13682_FB8F_4455_9724_4DDBBBF713D7'
MSI (s) (24:48) [20:50:23:655]: PROPERTY CHANGE: Adding System64Folder.BFC13682_FB8F_4455_9724_4DDBBBF713D7 property. Its value is 'C:\Windows\system32\'.
Action start 20:50:23: System64Folder.BFC13682_FB8F_4455_9724_4DDBBBF713D7.
MSI (s) (24:48) [20:50:23:655]: Doing action: SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2
Action ended 20:50:23: System64Folder.BFC13682_FB8F_4455_9724_4DDBBBF713D7. Return value 1.
MSI (s) (24:48) [20:50:23:656]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2'
MSI (s) (24:48) [20:50:23:656]: PROPERTY CHANGE: Adding SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 20:50:23: SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2.
MSI (s) (24:48) [20:50:23:656]: Doing action: System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2
Action ended 20:50:23: SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2. Return value 1.
MSI (s) (24:48) [20:50:23:656]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2'
MSI (s) (24:48) [20:50:23:656]: PROPERTY CHANGE: Adding System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2 property. Its value is 'C:\Windows\system32\'.
Action start 20:50:23: System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2.
MSI (s) (24:48) [20:50:23:657]: Doing action: LaunchConditions
Action ended 20:50:23: System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2. Return value 1.
Action start 20:50:23: LaunchConditions.
MSI (s) (24:48) [20:50:23:657]: Skipping action: CcmSwitchToRepairMode (condition is false)
MSI (s) (24:48) [20:50:23:657]: Doing action: AppSearch
Action ended 20:50:23: LaunchConditions. Return value 1.
Action start 20:50:23: AppSearch.
MSI (s) (24:48) [20:50:23:658]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:658]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:659]: PROPERTY CHANGE: Modifying CCMINSTALLDIR property. Its current value is 'h:\Program Files\SMS_CCM'. Its new value: 'C:\Windows\CCM\'.
MSI (s) (24:48) [20:50:23:659]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:659]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft\CCM\Embedded 3: 2
MSI (s) (24:48) [20:50:23:659]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:659]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE32\Software\Microsoft\CCM\Logging\DebugLogging 3: 2
MSI (s) (24:48) [20:50:23:660]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:660]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft\SMS\IIS 3: 2
MSI (s) (24:48) [20:50:23:660]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:660]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft\SMS\MP 3: 2
MSI (s) (24:48) [20:50:23:660]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:660]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft\SMS\MP 3: 2
MSI (s) (24:48) [20:50:23:660]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (24:48) [20:50:23:661]: Skipping action: CcmAbortIfEmbeddedExists (condition is false)
MSI (s) (24:48) [20:50:23:661]: Doing action: CCPSearch
Action ended 20:50:23: AppSearch. Return value 1.
MSI (s) (24:48) [20:50:23:661]: Note: 1: 2205 2: 3: CCPSearch
MSI (s) (24:48) [20:50:23:661]: Note: 1: 2228 2: 3: CCPSearch 4: SELECT `Signature_` FROM `CCPSearch`
Action start 20:50:23: CCPSearch.
MSI (s) (24:48) [20:50:23:661]: Doing action: RMCCPSearch
Action ended 20:50:23: CCPSearch. Return value 0.
MSI (s) (24:48) [20:50:23:662]: Note: 1: 2205 2: 3: CCPSearch
MSI (s) (24:48) [20:50:23:662]: Note: 1: 2228 2: 3: CCPSearch 4: SELECT `Signature_` FROM `CCPSearch`
Action start 20:50:23: RMCCPSearch.
MSI (s) (24:48) [20:50:23:662]: Doing action: ValidateProductID
Action ended 20:50:23: RMCCPSearch. Return value 0.
Action start 20:50:23: ValidateProductID.
MSI (s) (24:48) [20:50:23:662]: Skipping action: CcmSetInstallDir32 (condition is false)
MSI (s) (24:48) [20:50:23:662]: Doing action: CcmSetInstallDir64
Action ended 20:50:23: ValidateProductID. Return value 1.
MSI (s) (24:48) [20:50:23:663]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CcmSetInstallDir64'
MSI (s) (24:48) [20:50:23:663]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\Windows\CCM'.
Action start 20:50:23: CcmSetInstallDir64.
MSI (s) (24:48) [20:50:23:663]: Doing action: CcmSetInstallDirFromCmdLine
Action ended 20:50:23: CcmSetInstallDir64. Return value 1.
MSI (s) (24:48) [20:50:23:664]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CcmSetInstallDirFromCmdLine'
MSI (s) (24:48) [20:50:23:664]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\Windows\CCM'. Its new value: 'C:\Windows\CCM\'.
Action start 20:50:23: CcmSetInstallDirFromCmdLine.
MSI (s) (24:48) [20:50:23:664]: Doing action: CcmSetPrimaryFolder
Action ended 20:50:23: CcmSetInstallDirFromCmdLine. Return value 1.
MSI (s) (24:48) [20:50:23:664]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CcmSetPrimaryFolder'
MSI (s) (24:48) [20:50:23:664]: PROPERTY CHANGE: Adding PRIMARYFOLDER property. Its value is 'TARGETDIR'.
Action start 20:50:23: CcmSetPrimaryFolder.
MSI (s) (24:48) [20:50:23:665]: Doing action: FindRelatedProducts
Action ended 20:50:23: CcmSetPrimaryFolder. Return value 1.
Action start 20:50:23: FindRelatedProducts.
MSI (s) (24:48) [20:50:23:665]: PROPERTY CHANGE: Adding SMSSP1COLOCDOWNGRADE property. Its value is '{8864FB91-94EE-4F16-A144-0D82A232049D}'.
MSI (s) (24:48) [20:50:23:666]: Skipping action: SmsDetectUnsupportedUpgrade (condition is false)
MSI (s) (24:48) [20:50:23:666]: Skipping action: SmsDetectDowngrade (condition is false)
MSI (s) (24:48) [20:50:23:666]: Skipping action: CcmDetectUnsupportedUpgrade (condition is false)
MSI (s) (24:48) [20:50:23:666]: Doing action: SmsDetectColocationDowngrade
Action ended 20:50:23: FindRelatedProducts. Return value 1.
MSI (s) (24:48) [20:50:23:666]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SmsDetectColocationDowngrade'
Action start 20:50:23: SmsDetectColocationDowngrade.
MSI (s) (24:48) [20:50:23:666]: Product: ConfigMgr Management Point -- A newer version of the Configuration Manager Client is installed. Cannot continue installing this version of the management point.
A newer version of the Configuration Manager Client is installed. Cannot continue installing this version of the management point.
Action ended 20:50:23: SmsDetectColocationDowngrade. Return value 3.
Action ended 20:50:23: INSTALL. Return value 3.
Property(S): UpgradeCode = {ABD0F60F-1622-4311-8989-106B60D784FF}
Property(S): TARGETDIR = C:\Windows\CCM\
Property(S): ALLUSERS = 1
Property(S): ErrorDialog = ErrorDialog
Property(S): ProductName = ConfigMgr Management Point
Property(S): ProductCode = {6CED3AB0-05AF-4C81-8DBE-A62661C26F40}
Property(S): PackageCode = {5CBAF9F8-A298-49C0-B874-D0F5F0F39DB4}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 5.00.7804.1000
Property(S): ProductLanguage = 1033
Property(S): SMSCWSREGKEYNAME = MPCWSPath
Property(S): CcmCheckRepairNotInstalled_ActionText = Abort repair if the product has not been installed.
Property(S): CcmSwitchToRepairMode_ActionText = Product has been installed. Switch to repair mode for this installation.
Property(S): CcmSuppressReboot_ActionText = Suppress machine reboot after installation.
Property(S): CcmCheckFreeDiskSpace_ActionText = Check if the target volumn has enough space for the installation.
Property(S): CcmCheckFreeDiskSpace2_ActionText = Check if the target volumn has enough space for the installation.
Property(S): CcmSetInstallDirFromCmdLine_ActionText = Property custom action for setting install directory from command line.
Property(S): CcmCreateWmiNamespacesInit_ActionText = Processes the table CcmWmiNamespace and sends the context to CcmCreateWmiNamespaces.
Property(S): CcmCreateWmiNamespaces_ActionText = Creates the WMI namespaces found in the CcmWmiNamespace table
Property(S): CcmCreateWmiNamespacesRollback_ActionText = Calls CcmRemoveWmiNamespaces. Deletes the WMI namespaces.
Property(S): CcmRemoveWmiNamespacesInit_ActionText = Processes the table CcmWmiNamespace and sends the context to CcmRemoveWmiNamespaces.
Property(S): CcmRemoveWmiNamespaces_ActionText = Deletes WMI namespaces.
Property(S): CcmRegisterWmiMofFilesInit_ActionText = Queues MOF files in the CcmWmiMofFile table to be compiled.
Property(S): CcmRegisterWmiMofFile_ActionText = Compiles MOF files that were queued by CcmRegisterWmiMofFilesInit.
Property(S): CcmWmiRollback_ActionText = Deletes the existin site policy config and then recompiles MOF to restore old WMI instances.
Property(S): CcmDeleteWmiBackup_ActionText = Deletes the back up mof of the wmi namespace created for rolling back purposes.
Property(S): CcmRemoveWmiObjectsInit_ActionText = Queries the CcmWmiObject table for WMI objects to be removed.
Property(S): CcmRemoveWmiObjects_ActionText = Removes WMI objects found by CcmRemoveWmiObjectsInit.
Property(S): CcmRemoveWmiObjectsRollback_ActionText = Calls CcmRemoveWmiObjects. Removes WMI objects found by CcmRemoveWmiObjectsInit.
Property(S): CcmCreateIISVirtualDirectoriesInit_ActionText = Processes the CcmIISVirtualDirectory table and passes that information to CcmCreateIISVirtualDirectories to create the virtual directories.
Property(S): CcmCreateIISVirtualDirectories_ActionText = Creates the virtual directories specified in the CcmIISVirtualDirectory table.
Property(S): CcmRollbackIISVirtualDirectories_ActionText = Calls CcmRemoveIISVirtualDirectories. Removes IIS Virtual Directories found in CcmRemoveIISVirtualDirectoriesInit.
Property(S): CcmRemoveIISVirtualDirectories_ActionText = Removes IIS Virtual Directories found in CcmRemoveIISVirtualDirectoriesInit.
Property(S): CcmRemoveIISVirtualDirectoriesInit_ActionText = Queries the CcmIISVirtualDirectory table for IIS Virtual Directories to be removed.
Property(S): CcmCreateIISApplicationPoolsInit_ActionText = Processes the CcmIISAplicationPool table and passes that context to CcmCreateIISAplicationPools custom action.
Property(S): CcmCreateIISApplicationPools_ActionText = Creates the application pools specified in the CcmIISAplicationPools table.
Property(S): CcmCreateIISApplicationPoolsRollback_ActionText = Calls CcmRemoveIISApplicationPools. Removes IIS Application Pools found in CcmRemoveIISApplicationPoolsInit.
Property(S): CcmRemoveIISApplicationPoolsInit_ActionText = Queries the CcmIISApplicationPool table for IIS Application Pools to be removed.
Property(S): CcmRemoveIISApplicationPools_ActionText = Removes IIS Application Pools found in CcmRemoveIISApplicationPoolsInit.
Property(S): CcmDetectFilesInUseRemoveInit_ActionText = Detect if files are in used at uninstallation.
Property(S): CcmDetectFilesInUseInit_ActionText = Detects file in use.
Property(S): CcmDetectFilesInUse_ActionText = Moves files that are in use so that they will be deleted upon the next reboot.
Property(S): CcmDetectFilesInUseRollback_ActionText = Rolls back files moved by CcmDetectFilesInUse.
Property(S): CcmDetectFilesInUseCommit_ActionText = Commits action of CcmDetectFileInUse. After this we cannot rollback.
Property(S): CcmDetectFilesInUseRemoveRollback_ActionText = Calls CcmDetectFilesInUseRollback. Rolls back the files moved by CcmDetectFilesInUse.
Property(S): CcmDetectFilesInUseRemoveCommit_ActionText = Calls CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this the action cannot be rolled back.
Property(S): CcmLookupAccountNames_ActionText = Looks up the name of the Administrators group, Users group, and Creator Owner account, then sets the properties CcmAdministratorGroupName, CcmUsersGroupName, and CcmCreatorOwnerAccountName.
Property(S): CcmRegisterPerfCountersInit_ActionText = Processes the CcmPerfApplication table for components that will be registering a performance counter.
Property(S): CcmRegisterPerfCounters_ActionText = Registers performance counters gathered in the CcmRegisterPerfCountersInit action
Property(S): CcmUnregisterPerfCountersInit_ActionText = Processes the CcmPerfApplication table for components that will be unregistering a performance counter.
Property(S): CcmUnregisterPerfCounters_ActionText = Removes performance counters gathered in the CcmUnregisterPerfCountersInit action
Property(S): CcmRegisterPerfCountersRollback_ActionText = Rolls back any changes made by CcmRegisterPerfCounters if install fails.
Property(S): CcmUnloadWmiProvidersInit_ActionText = Enumerates component table and builds a list of files that will be installed
Property(S): CcmUnloadWmiProviders_ActionText = Enumerates all providers and unloads them, verifies they are unloaded, and then reloads them.
Property(S): CcmTypelibRollbackInit_ActionText = Queues a list of type libraries to be registered on rollback.
Property(S): CcmTypelibRollback_ActionText = In the event of install failing, this event rolls back the type libraries to the state before install started.
Property(S): CcmSetObjectSecurityInit_ActionText = Queries the CcmObjectSecurity table and passes this information to CcmSetObjectSecurity.
Property(S): CcmSetObjectSecurity_ActionText = Applying security permissions
Property(S): CcmSetInstallDir32_ActionText = Property action for setting installation directory for Configuration Manager Client on 32-bit platform.
Property(S): CcmSetInstallDir64_ActionText = Property action for setting installation directory for Configuration Manager Client on 64-bit platform.
Property(S): CcmSetPrimaryFolder_ActionText = Property action for setting target installation folder.
Property(S): PRIMARYFOLDER = TARGETDIR
Property(S): VersionNT64 = 603
Property(S): CCMINSTALLDIR = C:\Windows\CCM\
Property(S): System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933 = C:\Windows\system32\
Property(S): SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933 = C:\Windows\SysWOW64\
Property(S): CCMEXECFILEKEY = [#CcmExec_exe.A6940213_CD40_4753_8BA2_E803376DECC3]
Property(S): CcmDetectUpgradeOldClient_Message = A previous version of the Configuration Manager Client is installed. Please upgrade the client to Configuration Manager 2012 before attempting to upgrade.
Property(S): SmsDetectUpgradeOldMP_Message = A previous version of the Configuration Manager Management Point is installed. Please upgrade the management point to Configuration Manager 2012 before attempting to upgrade.
Property(S): SmsDetectUnsupportedUpgrade_ActionText = Detect if a previous version of the Configuration Manager Management Point is installed before upgrading Configuration Manager Client.
Property(S): CcmDetectUnsupportedUpgrade_ActionText = Detect if a previous version of the Configuration Manager Client is installed before upgrading Configuration Manager Management Point.
Property(S): CcmAbortIfEmbeddedExists_ActionText = Abort installation if the Configuration Manager Client Embedded version is installed.
Property(S): CcmRegisterHostingConfigurationInit_ActionText = Gathers configuration for Configuration Manager Client service to be registered on the system.
Property(S): CcmRegisterHostingConfiguration_ActionText = Register configuration for Configuration Manager Client service.
Property(S): CcmRegisterHostedApplicationsInit_ActionText = Gathers hosted out-of-proc DCOM applications running inside of Configuration Manager Client to be registered on the system.
Property(S): CcmRegisterHostedApplications_ActionText = Register hosted out-of-proc DCOM applications running inside of Configuration Manager Client.
Property(S): CcmRegisterHostedApplicationsRollback_ActionText = Rollback the registration of hosted out-of-proc DCOM applications running inside of Configuration Manager Client.
Property(S): CcmRemoveHostedApplicationsInit_ActionText = Prepare to remove the registration of hosted out-of-proc DCOM applications running inside of Configuration Manager Client.
Property(S): CcmRemoveHostedApplications_ActionText = Remove the registration of hosted out-of-proc DCOM applications running inside of Configuration Manager Client.
Property(S): CcmRegisterEndpointsInit_ActionText = Gathers information such as log file name on each endpoint to be registered on the system.
Property(S): CcmRegisterEndpoint_ActionText = Registers endpoint gathered in the action CcmRegisterEndpointsInit with WMI.
Property(S): CcmRegisterEndpointRollback_ActionText = In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint.
Property(S): CcmRemoveEndpointsInit_ActionText = Gathers information for each endpoint to be removed from the system.
Property(S): CcmRemoveEndpoint_ActionText = Removes endpoint gathered in the action CcmRemoveEndpointsInit with WMI.
Property(S): CcmRegisterSystemTasksInit_ActionText = Processes the CcmSystemTask table and passes this information to CcmRegisterSystemTask.
Property(S): CcmRegisterSystemTask_ActionText = Registers a System Task with WMI.
Property(S): CcmRegisterSystemTaskRollback_ActionText = Rolls back the changes made by CcmRegisterSystemTask.
Property(S): CcmRemoveSystemTasksInit_ActionText = Processes the CcmSystemTask table and passes this information to CcmRemoveSystemTask.
Property(S): CcmRemoveSystemTask_ActionText = Deletes a System Task from WMI.
Property(S): CcmRegisterProduct_ActionText = If product is registered in MSI database, then product is registered with WMI.
Property(S): CcmRegisterProductRollback_ActionText = Calls CcmUnregisterProduct. Deletes the instance from the WMI in the Configuration Manager namespace using the ProductCode instance in the session.
Property(S): CcmUnregisterProduct_ActionText = Deletes the instance from WMI in ccm namespace using the ProductCode instance in the session.
Property(S): CcmRegisterComponentsInit_ActionText = Generates the list of components for CcmRegisterComponets action to register.
Property(S): CcmRegisterComponents_ActionText = Registers components passed in from CcmRegisterComponentsInit
Property(S): CcmRegisterComponentsRollback_ActionText = In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents.
Property(S): CcmUnregisterComponentsInit_ActionText = Generates the list of components for CcmUnregisterComponets action to unregister.
Property(S): CcmUnregisterComponents_ActionText = Unregisters components passed in from the action CcmUnregisterComponentsInit.
Property(S): CcmSetupLoggingInit_ActionText = Gathers log file information from the LogFile table and passes this information to CcmSetupLogging.
Property(S): CcmSetupLogging_ActionText = Sets component logging information in WMI.
Property(S): CcmStopService_ActionText = Stops the ccmexec service.
Property(S): CcmStopServiceRollback_ActionText = Calls CcmStartService. Starts the ccmexec service.
Property(S): CcmStartService_ActionText = Starts the ccmexec service.
Property(S): CcmClearServiceSetupStamp_ActionText = Clear the time stamp for blocking the ccmexec service from starting up during upgrade.
Property(S): CcmSetServiceConfigInit_ActionText = Gathers ServiceData and then queues actions CcmSetServiceConfig and CcmMigrateMessagingQueues.
Property(S): CcmSetServiceConfig_ActionText = Sets WMI ServiceRootDir and configures CCMEXEC service.
Property(S): CcmConfigDCOMInit_ActionText = Processes the CcmDCOMAplication table and checks to see if the DCOM Component is being updated. If so, passes that information to custom action CcmConfigDCOM.
Property(S): CcmConfigDCOM_ActionText = Configures registry key permissions for the DCOM Components passed from CcmConfigDCOMInit.
Property(S): CcmFixupServiceConfigInit_ActionText = Gathers the services or load ordering groups which must be started before ccmexec starts.
Property(S): CcmFixupServiceConfig_ActionText = Sets the services or load ordering groups which must be started before ccmexec can be started.
Property(S): CcmRemoveService_ActionText = Removes BITS jobs and deletes the messaging queues.
Property(S): CcmRemoveLanternDocuments_ActionText = Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority.
Property(S): CcmSetPortConfigInit_ActionText = This custom action specifies the port the client should use when communicating with the management point and the server locator point.
Property(S): CcmSetHttpsConfigInit_ActionText = This custom action configures the https port and http state.
Property(S): CcmPreserveLastStateSerialNum_ActionText = Custom action to preserve last state message serial number.
Property(S): CcmInitializePolicyInit_ActionText = Gather default policy information.
Property(S): CcmInitializePolicy_ActionText = Sets and initializes default policy.
Property(S): CcmMigratePolicySettingsInit_ActionText = Custom action to schedule the deferred execution of CcmMigratePolicySettings custom action.
Property(S): CcmMigratePolicySettings_ActionText = Compiles Mof file to migrate root\ccm\Policy namespace schema from Pre-V4 Beta2 to V4 and above.
Property(S): CcmMigratePolicySettingsCommit_ActionText = Just deletes the temporary MOF file.
Property(S): CcmMigratePolicySettingsRollback_ActionText = Just deletes the temporary MOF file. Actual Rollback is done by the rollback action that rollbacks root\ccm namespace.
Property(S): ExpandCcmExecFileKey_ActionText = Property action for setting CcmExec file key.
Property(S): CcmMinAppVersion = 5.00.7000.0000
Property(S): CcmMaxAppVersion = 5.00.9000.0000
Property(S): SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3 = C:\Windows\SysWOW64\
Property(S): System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3 = C:\Windows\system32\
Property(S): SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 = C:\Windows\SysWOW64\
Property(S): System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61 = C:\Windows\system32\
Property(S): USELEGACYSTATEMESSAGESTORE = 1
Property(S): CcmValidateCustomWebSite_ActionText = This custom action validates that either the custom website or default website (if a custom website is not specified) can be used.
Property(S): CcmValidateServerConfig_ActionText = Validates that IIS, BITS and WebDAV is installed and properly configured setup.
Property(S): CcmLookupIISAnonymousAccountName_ActionText = Looks up the IIS AnonymousUserName and then sets the IISAnonymousUserAccount property to this value.
Property(S): CcmSetServiceMPConfigInit_ActionText = Gathers Incoming and Outgoing directories and virtual directories for the MP. Queues the action CcmSetServiceMPConfig.
Property(S): CcmSetServiceMPConfig_ActionText = Sets Incoming and Outgoing directories and virtual directories in WMI.
Property(S): CcmSetServerDataRoot_ActionText = Property action for setting service data root folder.
Property(S): CcmSetServerDataRootInstallDir_ActionText = Property action for setting service data folder.
Property(S): CcmIncomingVDirName = CCM_Incoming
Property(S): SystemFolder.BFC13682_FB8F_4455_9724_4DDBBBF713D7 = C:\Windows\SysWOW64\
Property(S): System64Folder.BFC13682_FB8F_4455_9724_4DDBBBF713D7 = C:\Windows\system32\
Property(S): CCMSERVERDATAROOT = h:\Program Files\Microsoft Configuration Manager
Property(S): CcmSystemVDirName = CCM_System
Property(S): CcmSystemRegVDirName = CCM_System_WindowsAuth
Property(S): CcmSystemAltAuthVDirName = CCM_System_AltAuth
Property(S): SMSCACHEDIR = Default
Property(S): SMSCACHEFLAGS = Default
Property(S): DISABLESITEOPT = Default
Property(S): DISABLECACHEOPT = Default
Property(S): SMSCACHESIZE = 5120
Property(S): SmsShellNotify_ActionText = Notifies the shell for the file-association icon changes.
Property(S): CCMINSTALLMSMQ = FALSE
Property(S): CCMINSTALLMP = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): ARPNOREMOVE = 1
Property(S): ARPNOMODIFY = 1
Property(S): CCMENABLELOGGING_Default = FALSE
Property(S): CCMLOGLEVEL_Default = 1
Property(S): CCMLOGMAXSIZE_Default = 2000000
Property(S): CCMLOGMAXHISTORY_Default = 1
Property(S): SecureCustomProperties = CCMENABLELOGGING;CCMLOGLEVEL;CCMLOGMAXHISTORY;CCMLOGMAXSIZE;CCMDEBUGLOGGING;CCMOSINSTALLPATHS;CCMINSTALLMSMQ;CCMINSTALLMP;SMSUPGRADEPRODUCTS;CCMSERVERDATAROOT;SMSUPLEVELPRODUCTS;USESMSPORTS;SMSPORTS;CCMHTTPPORT;SMSSP1COLOCDOWNGRADE;USESMSSSLPORTS;SMSSSLPORTS;SMSSSLSTATE;CCMHTTPSPORT;CCMHTTPSCERTNAME;SMSFWKUPGRADEFROMPREV4;CCMFWKUPGRADEFROMPREV4;CLIENTFWKUPGRADEFROMCM2007;SMSCWS;CCMSHAREMODE
Property(S): AdminProperties = CCMENABLELOGGING;CCMLOGLEVEL;CCMLOGMAXHISTORY;CCMLOGMAXSIZE;CCMDEBUGLOGGING;CCMOSINSTALLPATHS;CCMINSTALLMSMQ;CCMINSTALLMP;CCMSERVERDATAROOT;CCMALLOWSILENTREBOOT;CCMHTTPPORT;CCMHTTPSPORT;CCMHTTPSCERTNAME;SMSCWS
Property(S): CcmDefaultPolicyAuthorityPriority = 10
Property(S): SmsDetectColocationDowngrade_Message = A newer version of the Configuration Manager Client is installed. Cannot continue installing this version of the management point.
Property(S): SmsDetectColocationDowngrade_ActionText = Detect if a newer version of the Configuration Management Client is installed before installing the Configuration Manager Management Point.
Property(S): SmsDetectDowngrade_ActionText = Check if a newer version of the Configuration Manager Client is already installed.
Property(S): SmsMpRepairSucceeded_ActionText = Sends a wmi event to indicate MP repair succeeded.
Property(S): SmsDetectMSXMLRebootRequired_ActionText = Tries to create an instance of SAXXMLReader to determine if a reboot is required.
Property(S): SmsMpSetDefaultPolicyAuthority_ActionText = Set default policy authority for the Configuration Manager Management Point.
Property(S): SmsMpSerializedKeyExist_ActionText = Wait for the Configuration Manager Management Point serialized key to exist.
Property(S): ButtonText_Next = &Next >
Property(S): ButtonText_Back = < &Back
Property(S): ButtonText_Cancel = &Cancel
Property(S): ButtonText_Finish = &Finish
Property(S): ButtonText_Install = &Install
Property(S): ButtonText_Close = &Close
Property(S): ButtonText_OK = &OK
Property(S): ButtonText_Abort = &Abort
Property(S): ButtonText_Ignore = &Ignore
Property(S): ButtonText_No = &No
Property(S): ButtonText_Yes = &Yes
Property(S): ButtonText_Retry = &Retry
Property(S): ButtonText_Exit = &Exit
Property(S): FilesInUse_Info = Setup has detected that it needs to update some files that are currently in use by other processes.
To prevent having to reboot the machine, please close the following applications:
Property(S): DefaultUIFont = DefaultDlgFont
Property(S): DialogBox_Title = ConfigMgr Management Point Setup
Property(S): WelcomeDialog_Info = This will install the ConfigMgr Management Point.
Property(S): InstallDialog_Title = Install
Property(S): InstallDialog_SubTitle = The product is now ready to install
Property(S): InstallDialog_Info = Click Next to proceed.
Property(S): ProgressDialog_Title = Please Wait
Property(S): ProgressDialog_SubTitle = Setup is configuring your system.
Property(S): CompleteDialog_Title = Setup Complete
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): SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\Windows\SysWOW64\
Property(S): System64Folder.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\Windows\system32\
Property(S): SMSSP1COLOCDOWNGRADE = {8864FB91-94EE-4F16-A144-0D82A232049D}
Property(S): MsiLogFileLocation = h:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): USESMSPORTS = TRUE
Property(S): SMSPORTS = 80
Property(S): USESMSSSLPORTS = TRUE
Property(S): SMSSSLPORTS = 443
Property(S): USESMSSSL = TRUE
Property(S): SMSSSLSTATE = 0
Property(S): CCMENABLELOGGING = TRUE
Property(S): CCMLOGLEVEL = 1
Property(S): CCMLOGMAXSIZE = 1000000
Property(S): CCMLOGMAXHISTORY = 1
Property(S): CURRENTDIRECTORY = H:\Program Files\Microsoft Configuration Manager\bin\x64
Property(S): CLIENTUILEVEL = 3
Property(S): MSICLIENTUSESEXTERNALUI = 1
Property(S): CLIENTPROCESSID = 6556
Property(S): MsiRestartManagerSessionKey = d8d0cefc1249514889002637bb750a41
Property(S): VersionDatabase = 200
Property(S): MsiSystemRebootPending = 1
Property(S): VersionMsi = 5.00
Property(S): VersionNT = 603
Property(S): WindowsBuild = 9600
Property(S): ServicePackLevel = 0
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): MsiNTSuiteDataCenter = 1
Property(S): WindowsFolder = C:\Windows\
Property(S): WindowsVolume = C:\
Property(S): System64Folder = C:\Windows\system32\
Property(S): SystemFolder = C:\Windows\SysWOW64\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\Windows\TEMP\
Property(S): ProgramFilesFolder = C:\Program Files (x86)\
Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(S): ProgramFiles64Folder = C:\Program Files\
Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\
Property(S): FavoritesFolder = C:\Windows\system32\config\systemprofile\Favorites\
Property(S): NetHoodFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(S): PersonalFolder = C:\Windows\system32\config\systemprofile\Documents\
Property(S): PrintHoodFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(S): RecentFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent\
Property(S): SendToFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo\
Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(S): CommonAppDataFolder = C:\ProgramData\
Property(S): LocalAppDataFolder = C:\Windows\system32\config\systemprofile\AppData\Local\
Property(S): MyPicturesFolder = C:\Windows\system32\config\systemprofile\Pictures\
Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(S): DesktopFolder = C:\Users\Public\Desktop\
Property(S): FontsFolder = C:\Windows\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): MsiAMD64 = 6
Property(S): Msix64 = 6
Property(S): Intel = 6
Property(S): PhysicalMemory = 5372
Property(S): VirtualMemory = 4017
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = SYSTEM
Property(S): UserSID = S-1-5-18
Property(S): UserLanguageID = 1033
Property(S): ComputerName = [servername]
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 23
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 20:50:23
Property(S): Date = 8/27/2014
Property(S): MsiNetAssemblySupport = 4.0.30319.33440
Property(S): MsiWin32AssemblySupport = 6.3.9600.16384
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): Privileged = 1
Property(S): DATABASE = C:\Windows\Installer\6257f6f.msi
Property(S): OriginalDatabase = h:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
=== Logging stopped: 8/27/2014 20:50:23 ===
MSI (s) (24:48) [20:50:23:717]: Note: 1: 1708
MSI (s) (24:48) [20:50:23:717]: Product: ConfigMgr Management Point -- Installation operation failed.
MSI (s) (24:48) [20:50:23:718]: Windows Installer installed the product. Product Name: ConfigMgr Management Point. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (24:48) [20:50:23:721]: Deferring clean up of packages/files, if any exist
MSI (s) (24:48) [20:50:23:721]: MainEngineThread is returning 1603
MSI (s) (24:FC) [20:50:23:725]: RESTART MANAGER: Session closed.
MSI (s) (24:FC) [20:50:23:725]: No System Restore sequence number for this installation.
MSI (s) (24:FC) [20:50:23:726]: User policy value 'DisableRollback' is 0
MSI (s) (24:FC) [20:50:23:726]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:FC) [20:50:23:726]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (24:FC) [20:50:23:726]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (24:FC) [20:50:23:726]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (24:FC) [20:50:23:727]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (9C:58) [20:50:23:728]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (9C:58) [20:50:23:728]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/27/2014 20:50:23 ===A newer version of the Configuration Manager Client is installed. Cannot continue installing this version of the management point.
Action ended 20:50:23: SmsDetectColocationDowngrade. Return value 3.
Action ended 20:50:23: INSTALL. Return value 3.
The installer certainly thinks that you still have a previous ConfigMgr client installed. Perhaps you haven't completely removed it. Use ccmclean.exe from the SMS 2003 tool kit.
If that fails, why not just rebuild the server - you've said that this is a fresh install. I don't like too much messing at the beginning. This can be difficult enough - you need to start with a clean installation of the product.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
All the xml and arrays are getting NULL Problem
Hello guys
I am working on a project which uses xml loading, e4x and array manipulation extensively, and it was going good but now I got stuck on a strange problem. Whole code was fine and application was working and responding in a desired way, but then mystourisly it stopped working and started to retun NULL values to almost all the actionscript (internal) Arrays and XML varibales.
Now Whenever i load xml file and assign the loaded values to internal xml variables, internal values get only NULL instead of data.
Same is the situation with Arrays, I created some components in mxml, and when i passed them to arrays by reference, code gets compiled successfully, but again Array has only null values [that code was working fine too]
I am wondering if Adobe Flex did a silenced update or something similar and it is the result of that things !
I am using Adobe Flex 3.2 with SDK 3.3 on windows Vista Ultimate.
Please check this attached project, Import it and see if you face the same problem
Thanks
Link to Problem Project
http://isolatedperson.googlepages.com/problemXperiment.zip
Problem Screenshot
http://isolatedperson.googlepages.com/xmlissue.JPGUse HTTPService to load the data. You'll have fewer problems.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application creationComplete="dataSvc.send();"
xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
<mx:Script>
<![CDATA[
import mx.collections.XMLListCollection;
import mx.rpc.events.ResultEvent;
[Bindable] private var xlc:XMLListCollection;
private function loadXML(evt:ResultEvent):void{
xlc = new XMLListCollection(evt.result.individual.@id as XMLList);
]]>
</mx:Script>
<mx:HTTPService resultFormat="e4x" result="loadXML(event)" url="alirazaTree.xml" id="dataSvc"/>
<mx:ComboBox id="cbx" dataProvider="{xlc}"/>
</mx:Application> -
Hi,
I'm a freshman in college and new to java. I am completely lost and really need help with a current assignment. Here are the instructions given by my teacher...
Building on provided code:
Loops and Arrays
Tracking Sales
Files Main.java and Sales.java contain a Java application that prompts for and reads in the sales for each of 5 salespeople in a company. Files Main.java and Sales.java can be found here http://www.ecst.csuchico.edu/~amk/foo/csci111/labs/lab6N/Main.java
and here http://www.ecst.csuchico.edu/~amk/foo/csci111/labs/lab6N/Sales.java It then prints out the id and amount of sales for each salesperson and the total sales. Study the code, then compile and run the program to see how it works. Now modify the program as follows:
1. (1 pts) Compute and print the average sale. (You can compute this directly from the total; no new loop is necessary.)
2. (2 pts) Find and print the maximum sale. Print both the id of the salesperson with the max sale and the amount of the sale, e.g., "Salesperson 3 had the highest sale with $4500." Note that you don't necessarily need another loop for this; you can get it in the same loop where the values are read and the sum is computed.
3. (2 pts) Do the same for the minimum sale.
4. (6 pts) After the list, sum, average, max and min have been printed, ask the user to enter a value. Then print the id of each salesperson who exceeded that amount, and the amount of their sales. Also print the total number of salespeople whose sales exceeded the value entered.
5. (2 pts) The salespeople are objecting to having an id of 0-no one wants that designation. Modify your program so that the ids run from 1-5 instead of 0-4. Do not modify the array-just make the information for salesperson 1 reside in array location 0, and so on.
6. (8 pts) Instead of always reading in 5 sales amounts, allow the user to provide the number of sales people and then create an array that is just the right size. The program can then proceed as before. You should do this two ways:
1. at the beginning ask the user (via a prompt) for the number of sales people and then create the new array
2. you should also allow the user to input this as a program argument (which indicates a new Constructor and hence changes to both Main and Sales). You may want to see some notes.
7. (4 pts) Create javadocs and an object model for the lab
You should organize your code so that it is easily readable and provides appropriate methods for appropriate tasks. Generally, variables should have local (method) scope if not needed by multiple methods. If many methods need a variable, it should be an Instance Variable so you do not have to pass it around to methods.
You must create the working application and a web page to provide the applications information (i.e., a page with links to the source code, the javadoc and an object model) to get full credit. You can use the example.html's from the last two labs to help you remember how to do this.
I'm not asking for someone to do this assignment for me...I'm just hoping there is someone out there patient and kind enough to maybe give me a step by step of what to do or how to get started, because I am completely lost from the beginning of #1 in the instructions.
Any help would be much appreciated! Thank you!
Message was edited by:
Scott_010
Message was edited by:
Scott_010First ask the person who gave this asignment as to why do you require two classes for this , you can have only the Sales.java class with main method in it . Anyways.
Let Main.java have a main method which instanciates a public class Sales and calls a method named say readVal() in Sales class.
In the readVal method of sales class define two arrays i.e ids and sales. Start prompting the user for inputting the id and sales and with user inputting values keep storing it in the respective arrays .. Limit this reading to just 5 i.e only 5 salesPerson.
Once both the arrays are populated, call another method of Sales class which will be used for all computations and output passing both the arrays.
In this new method say Compute() , read values from array and keep calculating total,average and whatever you want by adding steps in just this loop. You can do this in readval method too after reading the values but lets keep the calculation part seperate from input.
You must create the working application and a web page to provide the applications information (i.e., a page with links to the source code, the javadoc and an object model) to get full credit. You can use the example.html's from the last two labs to help you remember how to do this. I think this is ur personal stuff , but if you want to use web page , you probably will require to use servlet to read values from the html form passed to the server.
Maybe you are looking for
-
Configuring CCMS Alerts in Sol Man 4.0 CUA System
Hi Can anybody forward me some documents on how to add systems for CCMS Alerts on SolMan 4.0 System which is being used a CUA Especially, i need a document on the RZ20, RZ21, SCOT and SDCC TCodes during this process Immediate help would be greatly ap
-
When working on a NTSC project in FCP, if you import still image, does the images technically also have 525 scanlines? OR does this only apply to video?
-
How do I move all photos in an album to camera roll?
I want to move all photos in an album to themCamera Roll. But after hitting the share icon and selecting Camera Roll, the "All" option is grayed and not selectable. Am I missing something?
-
Can't view photo library in iMovie media pane
My photo library is on an external hard drive. I can open iPhoto and it works. I can't access the pictures through iMovie. I had the same problem with music until I put it back on the computers hard drive. I am very experienced with iMovie/iDVD/iPhot
-
My homepage is different after an update
I updated my computer and now my homepage is different. I can't figure out how to fix it. I'm sure it must be really simple, but I've never done it before. Help!