SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends

Hi
Configmgr 2007 sp2
Client versions : 4.00.6487.2000
On many of our servers (2003 SP2, 2008 R2 SP1) the SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends. The log gets full in
less then a second then another log opens and so on!
Here is an example of a small part of the log file:
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 06:00:00 6988 (0x1B4C)
Thanks for any help!
Daniel

Yes, I know this is an old post, but I’m trying to clean them up.
This is not normal, I would check the health of the server and I would also use WMIdiag to see if WMI is healthy.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

SCCM 2012 R2 C2 OSD deployments no logs when Applications fail

Hello,
Have Task Sequences with the Install Application step {as well as other steps for packages, etc.} that installs Applications when one of the Applications fail I usually see exactly what Application fails through the Console Status Message Query "All
Status Messages for a Specific Package at a Specific Site".
Troubleshooting: When I look in C:\Windows\CCM\logs. I see none of the logs: AppDiscovery.log(s), AppEnforce.log(s), AppIntentEval.log (s)?
Note: This only happens if there is an error in the Install Application step...normally the logs are there. Any ideas on how to fix this?
Thanks!

Here is a snippet of smsts.log There are 2 Install Applications steps the first one has 9 applications the 2nd has 1 application.
<![LOG[
Parsing step node: CCL Shipboard Applications]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
<![LOG[Description: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
<![LOG[ContinueOnError: true]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
<![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
<![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
<![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
<![LOG[Timeout: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
<![LOG[DefaultVarlist found]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_75fb5490-a490-4e64-9545-fcd0429bc135,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_848807ff-6527-4984-b789-315489b5d8fb,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_275df3b1-48df-49dd-8f4d-e739352e9da5,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_a5e881ca-e355-4119-ae4c-ecb0b809da1d,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b4ade0f0-0801-4772-a1b1-2f07b9e774d9,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_c57aedb5-5a8a-49a7-98ed-89b48fe78d12,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_01266b3d-f6cb-4dc4-b255-36c3244b998f,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b5d3c8f3-cb78-4e1a-8796-f8285128e315,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_83d05a3c-a613-40d7-88da-ceb0a07ef60e
/basevar: /continueOnError:True]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
<![LOG[Adding instruction at 56]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524">
<![LOG[
Parsing step node: CCL Shipboard Application Part 2]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
<![LOG[Description: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
<![LOG[ContinueOnError: true]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
<![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
<![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
<![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
<![LOG[Timeout: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
<![LOG[DefaultVarlist found]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_cdad2a4f-c0cc-4fd5-9833-0b273c8dca01 /basevar: /continueOnError:False]LOG]!><time="09:30:41.517+240" date="04-10-2015"
component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
<![LOG[Adding instruction at 57]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524">

SCCM 2012 R2: easy way to disable/enable MULTIPLE maintenance windows at once?

I have been racking my brain on this one for a while.
Scenario: you have an ADR set up that is deploying updates once a month. You have multiple collections set up that each have their own special maintenance window (example: 1st weekend - sat - 8-9pm)
Then, one week you are asked to not deploy updates for the upcoming weekend. Well, the ADR already ran and the machines for "1st weekend" are just waiting for the maintenance window to open. Now, at this point you can obviously go into EACH collection
associated with "1st weekend" and disable the maintenance window. But if you are asked to do this often and/or you have multiple collections with maintenance windows this could be a hassle.
Is there a way to easily enable and disable multiple maintenance windows at a time?
GUI: I have not found a way to select multiple collections and disable all MWs
PowerShell-module: set-CMMaintenanceWindow doesn't appear to have ability to modify "IsEnabled" property of MWs
PowerShell-WMI: Can't find in WMI where to modify "Isenabled" Property
Please see my other thread
regarding PowerShell
What other creative options are there? Disable a service via PowerShell on members of "1st Weekend" collections? Which service? Should I be looking in SQL? Where? Other options in GUI?
I may end up getting stuck doing this manually but I want to make sure I am not overlooking something first... it's such a simple task - just seems like there should be an easy way to accomplish this.
(And please, for the sake of my question, lets not get into the semantics of whether or not the ADR technically DEPLOYS the updates or not.)

I didn't even think about that.... so having one MW that is disabled or having no MW at all would allow the client to install at will? I guess I was thinking that if it had a MW but it was disabled it just wouldn't update.
The MWs on the collections are all different.
Perhaps I need to re-assess my approach...
The original plan was to have one ADR (patch tuesday) update 1 SUG (which is deployed to all machines) each month. Machines would then install based off MWs.
Now I'm thinking it might be best to have 2 ADRS:
ADR1- updates existing SUG which is already deployed to Dev/Test machines.
ADR2- creates new SUG - which I then manually deploy to Prod collections.
This would automate the deployment to Non-Prod machines but it would give me the power to withhold updates to Prod machines for the month if needed.

How to Print Project Edit Logs incl info on start and end of clips

I would also be interested in how to share these electronically.

If you are re-capturing then you must have used Capture Now to get the clip first time round or you would have run into the same trouble with pre-roll. You'll have to capture the clip again using the same method. Of course, the chances of getting the same start and end code using Capture Now are slim, but if you can get in earlier and out later then you should be able to manually re-connect the clip.
rh

Log page start and end process time.

Hi:
I want to trace my JSP/Servlet process time,who know how to set up
weblogic to log when the page start process and when it finish.
Thanks.
Jason
Shi([email protected])
2000/11/3

Jason Shi <[email protected]> wrote:
Hi:
I want to trace my JSP/Servlet process time,who know how to set up
weblogic to log when the page start process and when it finish.You can implement a common JSP superclass and specify it either using
<%@ page extends="foo.Super" %> directive, or -superclass jspc command-line
option. For example:
package foo;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
public abstract class Super implements HttpJspPage {
private ServletConfig config;
final public void init(ServletConfig config) throws ServletException {
this.config = config;
jspInit();
final public ServletConfig getServletConfig() {
return config;
public String getServletInfo() {
return "blah blah";
final public void destroy() {
jspDestroy();
final public void service(ServletRequest req, ServletResponse res)
throws ServletException, IOException {
long timeStarted = System.currentTimeMillis();
_jspService((HttpServletRequest)req, (HttpServletResponse)res);
System.out.println(((HttpServletRequest)req).getRequestURI() +
" took "
+ (System.currentTimeMillis()-timeStarted)
+ " milliseconds to execute");
abstract public void _jspService(HttpServletRequest request,
HttpServletResponse response) throws ServletException, IOException;
public void jspDestroy() {}
public void jspInit() {}
Dimitri

Custom text component with different start and end points for each line

I'm trying to create a custom component extending textArea in which each individual line in the textArea would have different start and end points. For example, the start/end points for line 1 might be 20 pixels in the front and 35 pixels at the end but start/end points for line 2 might be 25 pixels in front and 20 pixels at the end, etc. These boundary values would be passed in. The width of the entire textArea component would be a fixed size. The result would be something like this:
Jack and Jill
ran up the hill
to fetch a pail of water
depending on the boundary values of each individual line of course. The custom component would take a string and render it in the text component with the appropriate individual line start and end points. I'm trying to do this by adding the text component to the display with the passed in string and then adding in spaces in the beginning of each line and adding a "/n" at the end of the line wherever appropriate based on the start and end values for that line.
Just wondering if I'm on the right track and if anyone has any advice on this.

> Applying the marker places the same icon on all lines of the graph and I need a different one for each
What do you have selected when you assign the marker? It
shouldn't apply to all the markers on the whole graph unless you have all the existing markers selected when you apply the new one.
Assigning marker designs is exactly analogous to assigning bar graph designs.
If you have a single marker selected when you assign the new design, it will apply to only that graph data point.
If you use the group select tool (or option-click with the direct select tool) to reclick on an already-selected marker until all the markers for the same line are selected, and then assign a design, the new design will apply only to the selected line. (You can extend the graph by adding more rows, and the new data points will inherit the marker for the line they are on.)
The thread linked to below demonstrates in more detail how the marker designs are scaled:
http://www.adobeforums.com/cgi-bin/webx/.3bc10970/0

Can monitor SCCM agent health through SCOM, monitor logs like CCMeval and setup alerts

Can monitor SCCM agent health/inactive agents through SCOM, monitor logs like CCMeval and setup alerts

You can find some management packs here:
http://systemcenter.pinpoint.microsoft.com/en-US/applications/search/Operations-Manager-d11?q=
There are other sites as well but this is the MS page for hosting MP's. The default SCCM 2012 Management pack for SCOM 2012 is pretty functional, this page talks a little bit about it:
http://blogs.technet.com/b/kevinholman/archive/2012/12/11/monitoring-configmgr-2012-with-opsmgr.aspx
If I remember correctly, it does NOT include a lot of client monitoring but I could be wrong. It might take some custom monitor creation or management pack downloads to get exactly what you're wanting. If I can find something like that
I'll add it to this post.
A good rule of thumb that I live by with SCOM, in case the product is new to you, is to save all your changes and customizations to the SCCM management pack in a custom-created management pack.

SCCM Agent install failed - CcmUnloadWmiProviders. Unloading WMI providers

Hi I have a SCCM 2007 SP2 setup in native mode. I have sccm client problem on Exchange server with os 2008 sp2.
SCCM agent was working on this server few months back but it is not working now.
SCCM agent stops at "CcmUnloadWmiProviders. Unloading WMI providers" steps.
I tried below steps to resolve this but no luck.
1. Uninstall sccm setup using command "ccmsetup.exe /uninstall"
2. Run "Cccmclean.exe /all"
3. Run delcert.exe
4. Rename SMSCFG.ini file
5. Run ccmsetup.exe again with source folder path too
6. As agent installation failed i rebuild WMI repository
7. Re run setup but it failed at same step.
8. I rebooted server and rebuild Repository but same error.
Any Idea about problem
If needed i can provide Log files too
ccmsetup.log (Last few lines)
<![LOG[MSI:
Action 20:07:08: CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:08.980+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:08.980+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmCreateIISApplicationPoolsInit. ]LOG]!><time="20:07:09.385+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmCreateIISVirtualDirectoriesInit.
]LOG]!><time="20:07:09.479+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
RegisterUser. Registering user]LOG]!><time="20:07:09.572+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmFixupServiceConfigInit. ]LOG]!><time="20:07:09.572+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmSetObjectSecurityInit. Applying security
permissions]LOG]!><time="20:07:09.650+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:11:
CcmSetObjectSecurity. Applying security
permissions]LOG]!><time="20:07:11.429+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:11:
CcmSetupLoggingInit. ]LOG]!><time="20:07:11.429+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmSetupLogging. Initializing
logging...]LOG]!><time="20:07:13.176+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
SmsSwDistCacheConfigInit. ]LOG]!><time="20:07:13.176+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
SmsSwDistSetCacheConfig. Configuring Software Distribution
Cache]LOG]!><time="20:07:13.270+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterPerfCountersInit. Registering performance
counters]LOG]!><time="20:07:13.270+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterPerfCountersRollback. ]LOG]!><time="20:07:13.613+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterPerfCounters. Registering performance
counters]LOG]!><time="20:07:13.613+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterComponentsInit. ]LOG]!><time="20:07:13.613+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmRegisterComponentsRollback. ]LOG]!><time="20:07:14.159+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmRegisterComponents. Registering CCM
Components]LOG]!><time="20:07:14.174+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetLUAAccessPermissionsInit. Setting Access
Permissions]LOG]!><time="20:07:14.174+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetLUAAccessPermissions. Setting Access
Permissions]LOG]!><time="20:07:14.252+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
InstallServices. Installing new
services]LOG]!><time="20:07:14.252+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
WriteEnvironmentStrings. Updating environment
strings]LOG]!><time="20:07:14.315+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmSetServiceConfigInit. Configuring
service]LOG]!><time="20:07:14.315+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmSetServiceConfig. Configuring
service]LOG]!><time="20:07:14.393+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsMigrateInventoryInit. Migrating SMS Legacy Client inventory
settings]LOG]!><time="20:07:14.393+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsMigrateInventory. Migrating SMS Legacy Client inventory
settings]LOG]!><time="20:07:14.471+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmConfigDCOMInit. Configuring
service]LOG]!><time="20:07:14.486+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmConfigDCOM. Configuring service]LOG]!><time="20:07:14.564+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsShellNotify. Setting SMS
configuration]LOG]!><time="20:07:14.580+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetClientLookupConfigInit. ]LOG]!><time="20:07:14.580+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmInitializePolicyInit. Initializing
policy]LOG]!><time="20:07:14.642+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmInitializePolicy. Initializing
policy]LOG]!><time="20:07:14.736+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetClientConfigInit. Setting SMS
configuration]LOG]!><time="20:07:14.736+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetClientConfig. Setting SMS
configuration]LOG]!><time="20:07:14.970+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmMigrateDownloadSchemaInit. ]LOG]!><time="20:07:14.970+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmMigrateDownloadSchema. ]LOG]!><time="20:07:15.110+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmRegisterProduct. Registering
product]LOG]!><time="20:07:15.126+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmRegisterProductRollback. Registering
product]LOG]!><time="20:07:15.126+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsInstallPrepDrvrInitAMD64. ]LOG]!><time="20:07:15.126+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsInstallPrepDrvr. Installing Software Metering PREP
Driver]LOG]!><time="20:07:15.204+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
StartServices. Starting services]LOG]!><time="20:07:15.204+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmStartService. ]LOG]!><time="20:07:15.204+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsCleanupDesktopMigrationInfo. Deinstalling the SMS Legacy Client or
SMS 2.0 Client]LOG]!><time="20:07:15.220+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsClientInstallSucceeded. Sending status
message]LOG]!><time="20:07:15.220+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
InstallFinalize. ]LOG]!><time="20:07:15.220+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmStopServiceRollback. ]LOG]!><time="20:07:15.251+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
ProcessComponents. Updating component
registration]LOG]!><time="20:07:15.266+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmStopService. ]LOG]!><time="20:07:15.391+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
StopServices. Stopping services]LOG]!><time="20:07:15.563+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsUninstallPrepDrvrAMD64. Uninstalling Software Metering PREP
Driver]LOG]!><time="20:07:15.563+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Warning 25702. Failed to
uninstall PrepDrvr.Sys for Software Metering
Agent.]LOG]!><time="20:07:15.641+000" date="04-11-2014"
component="ccmsetup" context="" type="2" thread="9048"
file="msiutil.cpp:370">
<![LOG[MSI: Action 20:07:15:
SmsStopUIComponents. Stopping UI
Components]LOG]!><time="20:07:15.641+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
DeleteServices. Deleting services]LOG]!><time="20:07:15.734+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmUnloadWmiProviders. Unloading WMI
providers]LOG]!><time="20:07:15.734+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">

Thanks Mike and theinfraguys for your suggestions. My problem is resolved.
The solution which worked for me has no logic but it solved my issue.
When my installation stopps at “CcmUnloadWmiProviders. Unloading WMI providers” step client.msi.log file have incomplete entry as “C:\Windows\SysWOW64\C”
At this time I have to restart WMI service and service will not stop correctly so I have to forcefully kill Winmgmt process and setup will continue.
I have to follow same process for upgrading SCCM client. During client upgrade some time I have to kill ccmexec process too.

SCCM Agent 2007 Push not doing anything!!!

Hello,
- SCCM 2007 R3
I verified the boundaries.
I verified the Discovery Methods.
Everything looks okay.
When the SCCM Agent is deployed by GPO or from the SCCM Console I don't see anything on a lot of workstations.
8 machines on the same subnet, same OU, but only 2 received the SCCM Agent.
on the others I even do not see the CCMSETUP folder and no activity in the ccm.log...
Where to look now?
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

is this happen even I unchecked "Include only clients site's boundaries" ?
I verified the boundaries they are correct as well as the OUs. 2 out of 8 machines got the clients installed.
I checked the log file ClientLocation.log under
C:\Program Files (x86)\SMS_CCM\Logs on the server CONFIGMGRDTS for the DTS SIte and it is pointing to another server!!!
GetCurrentManagementPointEx ClientLocation
8/27/2014 12:37:05 PM 7200 (0x1C20)
Current Management Point is configmgrsrv.ad.medctr.ucla.edu with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
8/27/2014 12:37:05 PM 7200 (0x1C20)
this is wrong...
it should be CONFIGMGRDTS as the local server name is its own Management Point..
CONFIGMGRSRV MP for the site SRV is still in use for the servers environment... not linked to DTS used for the desktops... why this mixage?
Thanks,
DOm
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

What is this error fatal: Write failed: Broken pipe in log of N7K

<186>: 2015 Mar 24 08:29:27 HKT: %DAEMON-2-SYSTEM_MSG: fatal: Write failed: Broken pipe .Client is 75.121.220.251,length of packet causing error 84 84 - sshd[684]
what is this error fatal: Write failed: Broken pipe in log of N7K
i find many brute force guessing login,
what can we do next?
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23714]
[7m--More--[27m
2015 Mar 24 07:17:25 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23714]
[7m--More--[27m
2015 Mar 24 07:17:28 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23715]
[7m--More--[27m
2015 Mar 24 07:17:28 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23715]
[7m--More--[27m
2015 Mar 24 07:17:28 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23715]
[7m--More--[27m
2015 Mar 24 07:17:31 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23717]
[7m--More--[27m
2015 Mar 24 07:17:31 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23717]
[7m--More--[27m
2015 Mar 24 07:17:31 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23717]
[7m--More--[27m
2015 Mar 24 07:17:33 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23718]
[7m--More--[27m
2015 Mar 24 07:17:33 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23718]
[7m--More--[27m
2015 Mar 24 07:17:34 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23718]
[7m--More--[27m
2015 Mar 24 07:17:36 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23719]
[7m--More--[27m
2015 Mar 24 07:17:36 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23719]
[7m--More--[27m
2015 Mar 24 07:17:36 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa

Restrict your vty line logins with an access-list to prevent Internet origin login attempts.

SCCM Agent upgrade 2007 to 2012 Problem. UAC in ..\CCM\Cache folder

During the migration to SCCM 2012 R2 from 2007, i am using Software Update SUP to deploy the new agent, which will uninstall the old sccm 2007 agent from machines, and install the new SCCM 2012 R2 agent.
I test it in two or three machines and everything just works fine. The machine gets a software update (SCCM 2012 R2 Agent), uninstall sccm 2007, and install the new agent.
When i start testing in larger scale, i notice that some machines are not getting the new agent, and hanging in the removal of the old agent. The CCMSETUP.LOG file is stuck in (MSI: Action 9:09:35: SmsSwDistCacheDirDelete), while the (client.msi_uninstall.log)
shows :
[9:14:18] ERROR: Unable to enumerate files in C:\Windows\SysWOW64\CCM\Cache\7f2916ad-688e-4497-87fa-6e31d3d0d631.1.System (0x80070003)
[9:14:18] Unable to delete folder C:\Windows\SysWOW64\CCM\Cache\7f2916ad-688e-4497-87fa-6e31d3d0d631.1.System (0x80070002). Retry after 1 seconds
and that's it.
Hint: if i go to that machine and manually tried to open C:\Windows\SysWOW64\CCM\Cache folder, it prompts me for admin credentials (UAC prompt), if i deleted that folder, the SCCM Agent 2007 gets removed successfully, and the new SCCM 2012 R2 Agent gets
installed successfully.
Question: since i cannot do this for all machines in the organization, and i need the deployment to go smooth without any actions, why CCMSETUP is unable to elevate to admin right to get rid of the UAC prompt when opening that cache folder?
ammarhasayen

I can't imagine this being a UAC issue as the Windows Update Agent runs as local System which is not subject to UAC and effectively has God rights on the system. I suspect something else is preventing the folder from being deleted like your AV. You should
run procmon during an installation to see exactly what is stopping the folder from being deleted.
Jason | http://blog.configmgrftw.com | @jasonsandys

Sccm Agent will not install via push on SCCM 2012 to computers that have sccm 2007 agents

I can not install the sccm 2012 agent on client computers via the push method or selecting the computers in a collection and clicking on install client nothing happens on the clients.
Also another problem is when i install the clients manually on the machines there is no site code and i can not "find site"
in both cases teh machines did have the sccm 2007 agent and were working fine on that.

1.make sure you have created the boundary group first. if you cant push the agent via push method, check the log files.
2. also make sure that in your environment if you have a firewall then there are port need to be open for agent push.
3. also if you have installed MacAfee agent on your client machine make sure the policies are not blocking file and print sharing.
4. also the windows firewall need to open for file and print sharing of you are using push method.
did you try to push the agent via GPO?
IF not try to run the following script in one of the client machine. use this command in the command prompt.
in my case smssitecode is BLL
MP is the management point.
ccmsetup.exe SMSSITECODE=BLL /mp:sccmserver.contoso.com /source:\\sccmserver.contoso.com\sms_bll\client
run the above command in the command prompt of one of the client machine which you cant install the agent and see.

SCCM Agent Not Initializing

I saw this one off case on a re-imaged computer where the SCCM agent is not initializing after installation. Usually it takes roughly 10 min after installation for the agent to download the different actions, policies, etc... but for some weird reason the
agent seems to be stuck. The Configuration Manager Properties window is displaying the default tabs (general, components, actions, site..) without the additional Configurations tab which usually appears there after initialization. Also Software Center shows
"IT Organization" on the top right corner instead of the actual organization name, and no communication showing in the console since before it was re-imaged. No obvious errors in ccmsetup.log. Any ideas how this can be further troubleshooted?

Hi,
In which we search far and wide to bring you the best of the Microsoft blogs. Here's one from the J.C. Hornbeck's SCCM Blog.
Troubleshooting issues where clients are not reporting
http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

What is labview digital write-to-line logic high voltage?

i'm using a pci-6503 daq hardware and cb-50lp.I'm currently doing a project to interface a labview vi to a programmable chip(downloaded with a vhdl program),using the daq hardware.The chip must function according to the labview program.I'm using 2 digital write-to-lines and 6 digital read-from-lines to interface to the chip.
Problem:
the 6 digital read-from-lines are able to read from the chip,but the 2 digital write-to-lines are unable to reach a logic high of 5v.This means that the labview vi can only read and unable to write to the chip to function(only one way communication).In the daq wizard,when using the test panel to test the individual lines of port a,b and c,it is able to write a good
logic low and good logic high(5v),even when all the lines are being used altogther.But when the labview vi is being run, the write-to-line cannot write a good logic high,thus unable to interface completely with the chip.
Please advise.Urgent!
grays

LabVIEW does not do anything different to the PCI-6503. NI-DAQ outputs the same 5V from MAX and LabVIEW. Are you sure the FPGA isn't driving 0V on the same line? You could test this by putting a small resistor between the FPGA and the DAQ card. See what the voltage is across the resistor.
Even at 2.5mA, the 6503 should output 3.7V.

How to config the digital write-to-line so it would independent when more than one is being used

when one digital wirte-to-line is used in the labview vi, a good logic high(5v) can be read using a voltmeter,but when two or more digital write-to-lines are being using at the same time,the logic high seemed to have split voltages and thus having a bad logic high.how to make sure that in the labview program,that when many digital write-to-lines are used at the same time,all of them can abtain a good logic high (around 5v).
I need the solutions urgently.
grays
np

Hello,
The probable reason you are seeing the behavior you are is due to a reconfiguration of the digital port. The Write to Digital Port VI is setup to configure the entire port, then write to one line (default settings). If you reconfigure the port it will reset all the lines, and then write your new value. You will want to use the iteration input on the Write to Digital Line so you can avoid the reconfiguration issue.
The first time the Write to Digital Line is executed in your code wire a 0 to the iteration (or leave it unwired). This will configure the port for write and write your first value. The next time you use the write to digital port VI wire an integer greater than 0. This will bypass the configuration step and simply write the new value to the
line. You can open the Write to Digital Line VI to see how the iteration input effects the execution and configuration of the digital ports.

SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends

Similar Messages

Maybe you are looking for