Component attributes and render specific attributes
What should be considered as component's attributes while what should be considered as renderer specific attributes.
Is it correct to think that behavioural properties of a components have been abstracted out as components properties?
Is there any example or a link which points to this?
Thanks,
Chris
Yes, that's basically it. Note also that a custom subclass of a component can define JavaBean accessors for renderer-specific attributes, and that the Renderer can still safely use the getAttributes() Map to retrieve the attributes, because bean properties are automatically available as well in this Map. You might want to read:
http://forum.java.sun.com/thread.jsp?forum=427&thread=532578&tstart=15&trange=15
for more info on that.
-- Adam Winer (EG member)
Similar Messages
-
Howto render a UI component depending on a specific value
Hi all,
I'm using jdev 10.1.3.4 and built a small ADF BC / JSF application.
I try to render a UI component (selectmanylistbox) depending on a value of another UI component which is represented by a session bean attribute.
I implemented a class "public class OnPageLoadBackingBeanBase implements PagePhaseListener" and extended my backing bean from this class as described by Duncan Mills.
Further on I overwrote the method "onPagePreRender" and tried to get the value from one UI component by his getter and set the rendered value by using that getter.setrendered(...) method within the backing bean (request scope). Additionally I call "AdfFacesContext.getCurrentInstance().addPartialTarget(this.getPanelGroup2())" but I'm not sure if it's really necessary.
After a postback it works but not during the initial invocation of that page. It's seems like as the UI components are not reachable by their getter and setter in that moment?!
Does someone has an idea how to get it.
Thanks for advice.
Ralf
Edited by: user11987218 on Feb 15, 2010 7:34 AMHi,
why don't you use EL on the UI component "render" property and reference the session bean attribute. If this then returns false then the component doesn't render
Frank -
Composite component attribute scope
I'm implementing a master-detail screen on bicycles are shown for the bicycle category selected. When the user selects a bicycle category in the selectOneMenu, the change request is handled using ajax and the new list of bicycles is displayed.
<cc:interface>
<cc:attribute name="categoryHolder" required="true">
<cc:attribute name="selectedCategory" />
</cc:attribute>
<cc:attribute name="onSelectCategory"
method-signature="void action()" required="false" />
<cc:attribute name="showAllOption" required="false"
default="#{false}" />
<cc:attribute name="onChangeRender" required="false" default="@form" />
<cc:attribute name="rendered" required="false" default="#{true}" />
</cc:interface>
<cc:implementation>
<h:selectOneMenu value="#{cc.attrs.categoryHolder.selectedCategory}"
rendered="#{cc.attrs.rendered}">
<f:selectItem itemLabel="All" itemValue="#{null}" noSelectionOption="#{true}" />
<f:selectItems
value="#{bicycleCategoryListUiComponent.bicycleCategories}"
var="bicycleCategory" itemLabel="#{bicycleCategory.name}"
itemValue="#{bicycleCategory}" />
<f:ajax event="change" render="#{onChangeRender}" execute="#{cc.attrs.categoryHolder.check()}" />
</h:selectOneMenu>
</cc:implementation>I call the component like this:
<component:bicycleCategoryList
categoryHolder="#{selectBicyclePageBean}" onChangeRender="@form" />However, when I select a category I get the following error message:
serverError: class javax.faces.component.UpdateModelException /resources/component/bicycleCategoryList.xhtml @32,35 value="#{cc.attrs.categoryHolder.selectedCategory}": java.lang.NullPointerException
It seems like #{cc.attrs.categoryHolder} has run out of scope and this isn't available anymore.Therefore I'm wondering how I can manipulate the scope of composite component attributes? JSF 2 has elegent scopes for managed beans, but I could not find anything about this topic. When there is some other solution, also please enlighten me.
Thanks in advance!Did you find a solution to your problem? I too am trying to do something similar but rather than have an onChangeRender attribute, I was trying to find a way to nest <f:ajax> inside the call to the custom component. Using your code as an example, I was trying to do the following:
<component:bicycleCategoryList categoryHolder="#{selectBicyclePageBean}">
<f:ajax event="someCustomEvent" render="@form"/>
</component:bicycleCategoryList>However I get the following exception:
<f:ajax> Error: enclosing composite component does not support event someCustomEventIn the FacesComponent, I did implement ClientBehaviorHolder. The someCustomEvent would be fired after an internal <f:ajax> is called. For example:
<f:ajax onevent="handle_onevent"/>Then:
function handle_onevent(data) {
if (data.status == "success") {
var evt = document.createEvent("Events")
evt.initEvent("someCustomEvent", true, true);
this.dispatchEvent(evt);
}Any help would be very appreciated. Thanks! -
Persisting Declarative Component attributes using MDS
Hi,
I have created a Declarative Component with some custom attributes.
Is there a way to persist the component attributes using MDS or by some other means.
Thanks
PrahladHi Krithika,
Thank you for your answer. I decComp is null only if I try this code in the binding method. If I define a popupFetchListener and bind to a method in a managed bean, decComp is not nut. I don't know how to get attribute values and create my UIComponent programatically.
Does anyone know how to achive that?
Regards
Joseba -
Declarative component attribute binding
Hi,
I'm sure this is an easy one, but I can't find the answer on the forum.
using JDev 11.1.1.3
I have created a declarative component with text fields bound to attributes as described in the ADF Code Corner, created the ADF Component lib etc. When I use this component in a task flow in another project, I set the properties to fields in my managed bean which is declared in the task flow, however on submission I find that my text input fields (RichInputText objects) are null i.e. the binding didn't work. I'm not sure if I should be creating 'attribute bindings' in the page definition, or if teh managed bean should be declared in the ADF component library, or if this should just work and I have done something silly.
The examples usually bind the exposed attribute properties to a data control field, I'm not sure how it works for a managed bean, can anyone point me in the right direction?
thanks in advance
steveHi,
it should work for managed beans as well. If your managed bean exposes a setter/getter pair, then this can be bound to the declarative component attribute binding. However, keep in mind that if the managed bean is in request scope, the bean is refreshed and this re-setted for each request. So the bean should have a scope of at least viewScope
Frank -
How to copy the photo with file name at window 7 and search specific one in iphone 4s?
How to copy the photo with file name at window 7 and search specific one in iphone 4s?
Clendenen02 wrote:
2) It would be equally helpful if there was something that would take the name of the picture file and spotlight comment, copy and paste it to a movie file's comments with the same name but obviously has different extention. For an example
In a Pictures folder
Name: Dark Knight, The.jpeg Comment: (2008) Genre: Action... <- copy comment
In a Movie Folder
Name: Dark Knight, The.m4v Comment: <- paste
and do this for all 700 files
This Bash script will do it.
Edit "PicDir" and "MovDir" to the location of your Folders
(Note: The comment is written to the m4v file using xattr, so the Spotlight comment field appears blank in Finder, but the comment metadata is still indexed by Spotlight (If you add a Spotlight comment from Finder, it is stored both as an extended attribute and in a .DS_Store file)
#!/bin/bash
PicDir=$HOME/Desktop/Pictures
MovDir=$HOME/Desktop/Movies
for f in $PicDir/*
do
if [ ! -d "$f" -a "${f##*.}" == "jpeg" ]; then
comment=$(mdls -raw -name kMDItemFinderComment "$f")
if [[ $comment != "(null)" ]]; then
picname=${f##*/}
movname=${picname%.*}.m4v
if [ -e "$MovDir"/$movname ]; then
xattr -w com.apple.metadata:kMDItemFinderComment "\"$comment\"" "$MovDir"/$movname
fi
fi
fi
done -
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 -
Component binding and state saving
Hello,
I have a few questions in regards to component binding and state saving (specifically in regards to the reference implementation) when the saving method is client and backing-beans are in the request scope rather than in the session scope:
1) if a component instance is bound to a backing-bean property then does the state of that component get saved when the view state is saved?
2) for UIData component, if the component value is bound to a list, does the actual list (after being wrapped) serve as the local data for the component? If this is the case, when the state is saved and then subsequently restored, does the list get re-created with the original number of items?
Regards,
Len TakeuchiThanks for the quick response.
(2) The actual list is not saved; the list will be
re-queried on subsequent requests.The list composition may have changed by the time the list is re-queried. If the table being displayed is updatable then transfer of information from request back to the list (during Apply Request Values) may not happen properly. So does that pretty much mean that the original list has to be kept around (in the session)? If the state saving method is server then does the saved state maintain a reference to the original list across requests?
Len Takeuchi -
Difference between Component KB and Bulletin KB
Dear All,
I can able to see some of the Update has same Component KB and Bulletin KB, and some of them not and due to this when work on WSUS server im getting confusion, can you please help me out
with the differnce between Component KB and Bulletin KB and which one we need to take it for reference the wsus server.
Thanks
Balaji KHi Balaji,
In brief, Component KB.
A bulletin is an announcement that a new update has been issued. A bulletin might cover one or more updates and discusses the vulnerability fixed by the updates. Typically, a bulletin announces updates for several products within the same product family.
For example, a typical Windows security bulletin might include updates for Windows 8, Windows 7, Windows Server 2008 R2, Windows Vista, Windows 2003, Windows 2000, and Windows XP, and any other Windows products as appropriate.
Each update is product-specific and might replace other updates issued earlier for that product in another bulletin.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Can i use both Component video and HDMI?
Hi guys,
Im wondering if its possible to connect both Component video and HDMI on the ATV?
Its currently connected to HDMI on our main HD TV, however, the apartment we have has a strange setup in which you must send RF signals to a loop back in the main room to reach all other TV's.
We dont have the capital for either another flatscreen TV or a second Apple TV until next year - so currently we've got an older (see 2004) bulk of a CRT TV upstairs and my thought was i could route a signal to the RF loop back from the ATV and use my iphone remote to control what it plays to view upstairs.
For this id need a component to composite/rf convertor which ive found so sending the signal is no problem, but what would happen if i were to connect component cables as well as the HDMI, does the ATV output on both, or priortise the HDMI?When both types of cable are connected to the tv at the same time, the HDMI connection will be on by default but the component is turned off... and what happens if the source to the HDMI cable is off - eg its plugged in but its got no where to send the signal, would it still not send to the component?.. You mean if the tv was off, same thing, HDMI would take precedence.
Are you sure about this, Winston? I have only 2 component (and 2 HDMI) inputs on my Panasonic HDTV. For this reason I invested in an Audio Authority Component Switcher (Model 1154A) a few years ago. When the TV device arrived I connected it directly to the HDTV via my HDMI-2 HDTV input and also connected the component video and optical audio to the switcher. I have no problem using the HDTV's input selector to switch back and forth between component and HDMI lines. While I admit I cannot split the screen between an HDMI input and anything else for simultaneous viewing, I can leave both lines plugged in and switch between the two lines. In addition, the activity light on the switcher indicates there is a signal present on the switcher even when I am watching the HDMI line. (Of course, this may simply be triggered by the switcher's optical audio signal since I normally watch the TV video via the HDMI line (with HDMI audio muted) and use the optical audio line to drive my receiver's AC3 decoder so I can enjoy 5.1 audio with my latest conversions.) Am, therefore, wondering if the OP may have the same capability and could then simply switch to a different input mode to "de-negotiate" his HDMI connection and allow access to whatever component device he needs as long as he doesn't need simultaneous viewing on both TVs. -
I have been working on animating a scene in flash for a few weeks and recently I have encountered a problem with importing my images on to the stage where the images I import do not turn up, however the key frame that I attempted to import the image onto shows that it is occupied by an image and every frame previous to the key frame that just imported an image that does not show turns up as a red square that fills the original perimeters of the image, there is no solution to this problem any where on the forum and the adobe technical support staff will not help me find a solution to this problem what can I do to get Flash running normally again and fix this problem?????
Also after the first time i publish a preview after i begin using flash, flash renders the publishing and scene testing features as useless and claims that there is no HTML template found, or if the images if i import any images onto the stage that come up blank and render every image previous to that image as a red square and then try and publish a preview flash renders the publishing and scene testing features as useless and claims that there is no HTML template found. What can I do to fix this problem??? there is no solution on the web anywhere to this problem either.I don't know if Flash has a memory limit of its own. The memory for your Flash file is based on the available memory on your computer.
There is a limit on the number of frames that you can have in any given timeline. I think that it's about 15000 frames, but that's a guess. Flash does all of its work at runtime, this means that no part of your animation is pre-compiled like it is in a video file. So the more objects that you have on the stage, the more work Flash has to do. It follows that the more objects that there are to animate, the more work your processor and the video card have to do.
Here's a list of articles on memory management that might be useful:
Garbage collection internals for Flash Player and Adobe AIR | AdobeDeveloper Connection
actionscript 3 - What are good memory management techniques in Flash/as3 - Stack Overflow
AS3 Memory Management Tips -
How to Run a Request Set on specific days and at specific hours
Hi community,
The question is simple, how to rin a Request Set on Specific Days and at Specific hours?
Let me explain the scenario.
E-Business Suite, Release 11.5.9.
We have a request set under Sysadmin user. This Request set is running 24x7, during all year, and we want to restrict the execution from Monday to Friday since 08:00 a.m. to 20:00 p.m. in order to increase the productivity of our system and more over, to avoid the size increase of a table (OE_EXPOSURE_INTERFACE)
The Request Set includes 5 Requests:
10. Workflow Background Process.
20. GUZMAN: Cálculo metodo pago en pedidos.
30. GUZMAN: Exposición de crédito externo.
40. Credit Exposure Import.
50 Initialize Credit Summaries Table.
As you can see three of them are standar Oracle Order Management Processes and two of them are custom Oracle Order Management Processes; and the requests must be executed in that order.
We have just thinking about to create a Custom Manager with a workshift from Monday to Friday since 08:00 a.m. to 20:00 p.m., and include the requests as specialization rules or assigning those request to a Request Type and then include that Request Type as specializated rule, but this does not assure us that the request will be executed in that order.
Any suggestion?
Thanks a lot for your answer in advice.
Luis.Hi Anchorage,
It could be a solution, but not the exact solution that we want. Let me say why.
With the Request set we have the security that each concurrent request is executed when the prior one finishes; is that to say 20, does not begin till 10 finishes, and 30 does not begin till 20 finishes and so on. The most critical concurrent requests are 40 and 50, cause those are the ones that import an external credit exposure in the OE_EXPORURE_INTERFACE table (40) and are the ones that delete those external credit exposures imported (50). The problem is (and we do not know why) that these actions makes grow the size of the table and each time the 40 and 50 processes takes more minutes to finish. That's why we need to truncate the table in order to avoid the excesive grow of itself.
Making each process independent, with a begining time and hoping and expecting that the following one does not begin till the prior one ends is not an admisible or realizable solution due to the problem with the 40 and 50 processes.
So at the end, we need a request set in order to know that each one began when the prior one ends.
And Due to in order to truncate the table, as I said before, the processes that have a relationship whit it, must be stopped (just the 40 and 50 processes) prior to the truncation.
So as you see, it is difficult, very difficult.
Regards. -
Have deleted temp video, configured anti spam and firewall, and one specific video keeps giving me an error. Just tried downloading a previous episode of the show and it worked just fine. Always sunny in philly "Charlie rules the world" anyone else??
Have deleted temp video, configured anti spam and firewall, and one specific video keeps giving me an error. Just tried downloading a previous episode of the show and it worked just fine. Always sunny in philly "Charlie rules the world" anyone else??
-
How to find out the Target Component name and Target view name
Hi All Expert,
I want to know ,how to find out the target component and target view in WEB UI,when i click on a field which shows as a hyper link in WEB UI .At GUI level ,i know the how it will work.Any way to find out the component name and view name which is show the details of that field at GUI level .IF you go to transaction CRMD_ORDER then open the service contract id .then goto the item level value .there is 1 service data tab is available at item level.there is two button is available.first one is available time and second one is response time .if i click on any button then one popup is open which is shows the details of that button.I dont know how to find out the component name and view name from GUI level.
Thanks in Advance....
Vishwas SahuHi Vishwa,
The control would be something like this for navigation in Get_p_xxx method u mention as link and u mention a event name which gets triggered on the click of this hyperlink. So your GET_P_XXX method would have the following code:
CASE iv_property.
WHEN if_bsp_wd_model_setter_getter=>fp_fieldtype.
rv_value = cl_bsp_dlc_view_descriptor=>field_type_event_link.
WHEN if_bsp_wd_model_setter_getter=>fp_onclick.
rv_value = 'EXAMPLE'.
Now you have to create a method as EH_ONEXAMPLE at your IMPL class and within which you would give an outbound plug method. Within the outbound plug the target data would be filled in the collection and window outbound plug would be triggered.
This is a huge topic and i have just mentioned you basic things.
Regards,
Bharathy. -
Difference between component configuration and application configuration in webdynpro
what is the difference between component configuration and application configuration in webdynpro?
Hi Rohit,
With the component configuration, you can control the behavior of each individual component within a Web Dynpro application or the user interface of individual views. For each component, several records of configuration data can be created.
Using the application configuration, it is now possible to assign the configuration required in the current application to all the components used.
In short : Component Config belongs to WDP Component and Appl'n Config. belongs to WDP Appl'n.
Check this document for more information.
Web Dynpro for ABAP - Component and Application Configuration
Thanks
KH
Maybe you are looking for
-
IPod Mini No Longer Recognized by G5 10.2.8?
I connected an iPod Mini to a new iMac with 10.4.4 to charge it and now the Mini is not recognized by a G5 with 10.2.8. I read that 10.2.8 does not support USB 2.0. For some reason, the iPod was updated to USB 2.0 and the driver is not downward compa
-
Configurable dialog with timeouts and default capabilities
I would like to have a native LabVIEW dialog in the functions pallet that will allow you to set a default value and a time out feature. This allows a user to pick a desired behaviour if present but if not present the dialog times out and program con
-
Well, I'm currently on a Windows 7 based laptop (HP Pavilion dv6 2010). I like Windows and I've been using it all my life and I think it's great!!! But, there are features the the OS X has that Windows doesn't have (namley the Motion Gestures). Thing
-
Data web bean (chart) using a dynamic view object
Please I want a quick help. I read all forums concerning this subject but I still couldn't do it. - I create a view object which takes a proameter using the ? style parameter. - I passed the parameter from an html page and execute the query of the vi
-
GR against the Outbound Delivery
Hi If I MIGO Goods Receipt referencing the PO the Stock account is posted. But I MIGO Goods Receipt referencing the Outbound Delivery Order the stock account is not get posted. Basically, I am doing GR for the Intercompany STO (using NB P.O type). si