Sequence passfail status
The TS code I need to modify needs to have a subsequence and the subsequence will have about 5 or 6 verify steps. What is the standard method for rolling up the results of all these Verify statements to give an overall pass/fail value for the subSequence? From other code I have looked at it looks like this can be passed up many levels: ie a sub-sub-sequence passes pass/fail up to the subsequence and it passes its pass/fail up to the main sequence.
Seems strange that I have been maintaining a lot of VIs in this suite for several months but never had to deal with TS's interpretation of pass/fail data before.
thanks,
jvh
Solved!
Go to Solution.
jvh,
a sequencecall in TestStand has a quite simple result in the default settings: If one step of the subsequence fails, the calling step also returns "Failed".
You can change this on steplevel of the subsequence by disabling the option "Step Failure causes Sequence Failure" found in the run options of the step you want to modify.
This is the easiest way to change this behavior. There are other ways (e.g. customized sequence call step) as well if this is not the feature you are looking for.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Similar Messages
-
Status sequence: exclude status from the middle of the min/max range
Dear Experts!
I have customized status schema and determined the status sequence. Etherything works well, but I need to exclude status from the range of statuses that user can set from the current status. For example, I have statuses:
10 status1 min-20 max-40
20 status2 min-10 max-30
30 status3 min-20 max-40
40 status4 min-40 max-40
And I need to let user set from "status1" only statuses "status2" and "status4", but not "status3". How can I do it without changing positions of statuses? Hope for your help.
Regards,
VladimirThank you for your reply, Robert!
But how exactly can I do this? Should I use an exception NOT_ALLOWED of the method BEFORE_CHANGE? When I was trying to debug this method, I could operate only with one status (from importing parameters) defined by the filter of BADi CRM_ORDER_STATUS. Hope for your reply.
Regards,
Vladimir -
Status Sequence not letting to change to other status
Hi All,
I have a question regarding status change using sequence.
I am trying to add sequence to statuses for a status profile, it is like below:
01 Z001 Open 01 99
02 Z002 In Process 01 99
03 Z003 Approve 03 99
04 Z004 Complete 03 99
05 Z005 Closed 04 99
Now my issue:
Once I set the status Z003 (Approve), the system does not allow me to set to status Z002 (In Process) though a program. Is there any way I can set the status Z002 or Z001 without changing the sequence.
Thank you for your quick reply.
Regards,
AbhayHi Abhay,
I doubt you can achieve this using a BAdi.(May be I'm wrong but I doubt) It may need standard modification after you find the place where system performs this check.
As Arden Stricke mentions, you can achieve this by changing Low High values. This will enable you to do it manually as well. And if a certain thing can be done manually on WebUI/GUI it can be automated. But if it cannot be done manually, then normally you cannot automate it.
If you cannot change the configuration for any reason, then look for the place where SAP checks for an allowed status and modify it according to your custom logic.
Cheers,
Niraj -
Change KANBAN Status Sequence in Control Cycle
Hi guys,
Can anyone please detail which are the implications if I should change the status sequence for a control cycle, which is in use now?
Regards,
IleanaHi
In the kanban process the actual sequence is
Wait>Empty>In process > Intransit> Full > In use>Empty.This is complete cycle
If ur present kanban bin status is "In use" then then u changed the sequence in the control cycle.
When ever u trigger the kanban card, then system move to control cycle and checks the kanban sequence by referring the standard sequence it move to next status.
Eg: Ur present sequence is like
Empty>In process> In -transit --> Full --> Empty
Now ur bin status is "Full" then u have changed the sequence in the control cycle.
New sequence is like
"Empty--> In process > Full> In use -->Empty"
Now u triggered the kanban card of " Full" status bin, then system refer first sequence in the control cycle and then standard sequence then status is changing to " In use"
Means when ever u change the sequence in the control cycle system checks the sequence in the control cycle by reference of standard sequence it will changes the bin status.
So if ur bin is in the "In -use " status, then what ever the next status in the sequence is taken when u trigger the kanban signal -
KAMBAN: Change Status Sequence in Control Cycle
Hi guys,
Can anyone please detail which are the implications if I should change the status sequence for a control cycle, which is in use now?
Regards,
IleanaHi
In the kanban process the actual sequence is
Wait>Empty>In process > Intransit> Full > In use>Empty.This is complete cycle
If ur present kanban bin status is "In use" then then u changed the sequence in the control cycle.
When ever u trigger the kanban card, then system move to control cycle and checks the kanban sequence by referring the standard sequence it move to next status.
Eg: Ur present sequence is like
Empty>In process> In -transit --> Full --> Empty
Now ur bin status is "Full" then u have changed the sequence in the control cycle.
New sequence is like
"Empty--> In process > Full> In use -->Empty"
Now u triggered the kanban card of " Full" status bin, then system refer first sequence in the control cycle and then standard sequence then status is changing to " In use"
Means when ever u change the sequence in the control cycle system checks the sequence in the control cycle by reference of standard sequence it will changes the bin status.
So if ur bin is in the "In -use " status, then what ever the next status in the sequence is taken when u trigger the kanban signal -
Are there any issues with starting a task sequence one day and finishing it up days later?
Hello,
We have a few techs who, for whatever reason, will sometimes start a deployment task sequence (from boot media, USB) and then finish the task sequence the next day or days later. For example, I had a recent one where the smsts log file had all of the
PXE steps taking place on Friday, but then everything after the first reboot took place today, on Monday.
The log was full of messages like below, and no software was installed:
reply has no message header marker TSManager 3/3/2014 7:46:36 AM 1452 (0x05AC)
Failed to send status message (80004005) TSManager 3/3/2014 7:46:36 AM 1452 (0x05AC)
Error calling message lib Send(). Code 0x80004005 TSManager 3/3/2014 7:46:36 AM 1452 (0x05AC)
Non fatal error 0x80004005 in sending task sequence execution status message to MP TSManager 3/3/2014 7:46:36 AM 1452 (0x05AC)
So obviously something is wrong, but I'd like to know a little detail as to why. Is there a timing issue when communicating with the MP?I need the complete smsts.log. Only part of them does not help.
Anyway, the TS can run up to 24 hours if I have not remembered wrong. So, if you have too many steps in a TS and need to spend too much time to finish, this will cause the TS failed.
Juke Chou
TechNet Community Support -
SCCM 2012 monitoring - Site Status - Reporting Services Point - Status Critical
Hi all,
I have noticed that the Site Status under Monitoring shows Reporting services point as in Critical state though we do not see anything wrong with SCCM as such (at least we haven't been reported any problems thus far). There is nothing in the event viewer
on SQL Server. Just wanted to know how to resolve this issue. Could you help?
When I try to open status messages for Reporting Services (for any days) it does not return anything as if there are no status messages for this role. Also, could you let me know the log file locations/names for Reporting services point?Here it is... I have replaced server names with a dummy name.
=================
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.588-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.596-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.616-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.641-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.713-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.715-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.339-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.336-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.347-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.357-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.377-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.404-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.478-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.480-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.160-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.159-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.168-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.188-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.237-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.264-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.539-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.541-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.796-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.795-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.804-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.813-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.834-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.859-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.904-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.905-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.940-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.942-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.724-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.726-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.723-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.731-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.752-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.776-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.813-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.954-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.956-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.728-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.730-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.727-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.738-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.747-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.769-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.799-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.875-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.496-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.494-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.503-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.512-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.534-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.563-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.646-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.648-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.653-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.654-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.352-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.351-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.361-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.370-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.393-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.432-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.484-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.485-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.520-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.522-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.530-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.531-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.268-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.277-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.286-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.308-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.334-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.380-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.381-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.421-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.423-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
Confirmed the configuration of SRS role [ConfigMgr Report Users]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.088-60><thread=6072 (0x17B8)>
Confirmed the configuration of SRS role [ConfigMgr Report Administrators]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.098-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.700-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.736-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.758-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.791-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.815-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.849-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.870-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.906-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.929-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.961-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.998-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.033-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.067-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.099-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.127-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.155-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.192-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.221-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.265-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.303-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.326-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.362-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.381-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.413-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.432-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.470-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.495-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.529-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.551-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.585-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.609-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.642-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.666-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.700-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.724-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.755-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.778-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.815-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.835-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.867-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.888-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.924-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.952-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.985-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.007-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.042-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.073-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.096-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.132-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.156-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.189-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Users]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.209-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.243-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.268-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.298-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.320-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.349-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.367-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.397-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.418-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.458-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.492-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.511-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.542-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.571-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.599-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.632-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.656-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.689-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.709-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.742-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.767-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.800-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.822-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.856-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.880-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.911-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.932-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.966-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.988-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.020-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.045-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.078-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.113-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.137-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.170-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.193-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.227-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.247-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.280-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.306-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.339-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.361-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.395-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.415-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.445-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.467-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.497-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.518-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.550-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.570-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.602-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.625-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.655-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.676-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.710-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.731-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.762-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.785-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.821-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.852-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.878-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.899-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.933-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.967-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Users]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.994-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.027-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.052-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.084-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.106-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.135-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.153-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.186-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.209-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.250-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.284-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.304-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.338-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)> -
UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012
This is kind of long, but here goes...
We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images. We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002 during what appears to be the "Use Toolkit Package" step. This is after the OS image has already been laid down and after the ConfigMgr
client has been installed/configured. The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x8007002" Among other errors...I will post the entire log below...
After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure.
Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment. We have a few OSD task sequences built without UDI and those all still work just fine.
So, I am at a loss for where the root problem lies. Any suggestions or assistance would be greatly appreciated.
Here is the entire SMSTS.log and BDD.log...
https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
Thanks
Richie Tenhetyour failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
Use Toolkit Package step...
"Starting Task Sequence Engine . . . "
"Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
"Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
"unknown host (gethostbyname failed)"
"sending with winhttp failed; 80072ee7"
"Tried all the available http based locations. SMB based locations will be attempted now."
"Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
"Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"
that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
around the time of the failure.
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady -
Document Status -- Authorization group?
Hi,
I defined new status values for document in the IMG SolMan project. In addition, i created the document Status schemes with sequence number (Status values). The workflow sequence is working after testing in the Business Blueprint. The problem is, how can I or other users unlock the document if the Status is locked. How can I manage this problem; Should i define a group of user with authorization, where?
Thanks!
Blaise
Edited by: Blaise Vincent Havanaby on Mar 26, 2009 10:31 AMcan u pls explain the steps u tried?
-
Can't switch standby logfiles to status=active
Hi DBA's
I'm trying to create logical standby on 10.2 on fedora 6 on manual http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
I can't create proper working standby redo logs.
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4
('/u01/app/oracle/oradata/ORCL/onlinelog/log4a.log',
'/u01/app/oracle/flash_recovery_area/ORCL/onlinelog/log4b.log') SIZE 50M;
then create the rest of standby redos and switch logfile:
ALTER SYSTEM SWITCH LOGFILE;
when:
SQL> SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;
GROUP# THREAD# SEQUENCE# ARC STATUS
4 0 0 YES UNASSIGNED
5 0 0 YES UNASSIGNED
6 0 0 YES UNASSIGNED
What to do?
Edited by: val75 on Jun 21, 2009 11:08 PMtry switch log at primay
please try to run this Command and then open the primary database.
alter database set standby database to maximize performance;
alter database open; -
Background : In TMS project IDOC interface is used to send out data from SAP to the external transportation planning systems. This interface includes sending of information related to outbound deliveries, which is performed with specific message type ZVXX_TMS1_TPSDLS. As soon as external system receives outbound delivery data from SAP it generates response messages with technical acknowledgment (message type STATUS) and sends it back to SAP. Then external system process data received from SAP and as data is processed, message with Functional acknowledgement (message type STATUS) is generated and sent out to SAP through XI.
In SAP STATUS messages update outbound delivery messages ZVXX_TMS1_TPSDLS with new statuses received from external system. In this way it is possible to have information in SAP regarding outbound delivery processing in External system.
The problem related to status update process is found. In some cases even STATUS IDOCs are created in correct order in SAP, they update ZVXX_TMS1_TPSDLS messages in incorrect order. And it makes not possible to track actual processing status of outbound deliveries in external system with message ZVXX_TMS1_TPSDLS status record.
Requirements
Basic requirement is to have status for outbound message TMS_TMS1_TPSDLS which reflects progress of data processing in external system.
The right sequence of status scheme is to process technical acknowledgment before the functional acknowledgment.
Can any one help ?Hi,
One more method is to provide Milestone timing for critical loads/availability of reports.
For eg consider you have one chain loading data into a few critical targets. Depending on the data volume, load timings and post processing identify a critical milestone time by which everyday the chains should be complete. say 9.00 AM in clients time zone (normal beginning of business day when clients may expect a report).
Only in the scenario where its delayed you have to inform client through a mail with the reason for delay and expected time of availability. Otherwise when there is no delay its understood that data is available.
Hope this helps.
Thanks,
JituK -
Status profile - Quality Info record
Hi,
Pls explain about status profile: QM_P_DOL -
Status check DOL.
Waht is DOL?
Why is required?
Reg,
RPV.Hi,
Status profile is created by the user in general status management and used to control user statuses
In a status profile you can:
Define the sequence in which user statuses can be activated
Define initial statuses
Allow or prohibit certain business transactions
Status Profile Assigned to Quality Info Record:
Use : The supply relationship can run through a sequence of statuses that you define in a status profile. The sequence of statuses for the supply relationship is updated whenever inspection lots are accepted in the usage decision.
If you assign a status profile that has a mandatory sequence of statuses to a vendor relationship, the system creates inspection lots for origin 01 with an inspection type appropriate to the status of the vendor relationship.
supply relationship : A business link with vendor or customer.
Quality Management information for these business links are managed in the SAP system using the following master data:Vendor master record and Info record with reference to vendor, material and plant.
SAP standard User profiles starts with QM_P for supply relationship. In your case
QM_P stands for supply relationship and DOL might be User notation.
Hope it is clear to you.
Regards
Venkat.V -
Hi,
Explain the use of status profile - DOL in Quality Info record
RP VeluchamyHi,
Status profile is created by the user in general status management and used to control user statuses
In a status profile you can:
Define the sequence in which user statuses can be activated
Define initial statuses
Allow or prohibit certain business transactions
Status Profile Assigned to Quality Info Record:
Use : The supply relationship can run through a sequence of statuses that you define in a status profile. The sequence of statuses for the supply relationship is updated whenever inspection lots are accepted in the usage decision.
If you assign a status profile that has a mandatory sequence of statuses to a vendor relationship, the system creates inspection lots for origin 01 with an inspection type appropriate to the status of the vendor relationship.
supply relationship : A business link with vendor or customer.
Quality Management information for these business links are managed in the SAP system using the following master data:Vendor master record and Info record with reference to vendor, material and plant.
SAP standard User profiles starts with QM_P for supply relationship. In your case
QM_P stands for supply relationship and DOL might be User notation.
Hope it is clear to you.
Regards
Venkat.V -
WE-19 Inbound Idoc Process - Status Code 51
Hi,
I generated Outbound idoc COND_A successfully to send it out to XI. I used same Idoc again in WE19 and changed partner details and tried Inbound Processing. Its giving me error code 51 ("ISO Currency USD can not be converted unambiguously to SAP currency for E1KOMG" )
Any Idea how to fix this error. basically I did not changed anything.
Message was edited by: Ram KrishAppana,
Thank you very much for your reply.
I did setup all parameters as Iam getting this Idoc as an Inbound to R3 as well. Thsi Idoc will be both Outbound and Inbound to R3.
I successfully sent this Idoc to XI. and then as I wanted to test the same Idoc for inbound, I changed Paramters according to my setup.
Sequence of status are
74 - created with test transaction
50 - Idoc added
64 - Idoc ready to be transferred to Application
62 - Idoc Passed to Application
51 - ISO currency USD can not be converted unambiguously to SAP currency for KOMG
I looked at several fields in E1KOMG segment and changed one of the currency field to USD which didn't help to fix this error.
I really appreciate any help to fix this error. -
Newb question - group by sequence number range
Hi - I'm a newb to pl/sql but am pretty familiar with t-sql and sql server.
Here's my question:
I have a database table with ~1.6M records, call it "a". a has two columns, id (a sequence) and status. status has three possible values: null, error and success.
I want to write a query that will group the sequence numbers into sets of 100k and give the the count of nulls, errors and successes for that set. The output should be something like:
set null error success
1-100,000 x y z
100,001-200,000 x y z
200,001-300,000 x y z
Can anyone point me in the right direction?I scaled it down with a factor 1000, and here is the idea:
SQL> create table a
2 as
3 select level id
4 , decode(mod(level,3),1,'error',2,'success',null) status
5 from dual
6 connect by level <= 1600
7 /
Tabel is aangemaakt.
SQL> select trunc((id-1)/100)*100 + 1 lb
2 , trunc((id-1)/100)*100 + 100 ub
3 , count(decode(status,'error',1)) err
4 , count(decode(status,'success',1)) success
5 , count(decode(status,null,1)) "NULL"
6 from a
7 group by trunc((id-1)/100)
8 /
LB UB ERR SUCCESS NULL
1 100 34 33 33
101 200 33 34 33
201 300 33 33 34
301 400 34 33 33
401 500 33 34 33
501 600 33 33 34
601 700 34 33 33
701 800 33 34 33
801 900 33 33 34
901 1000 34 33 33
1001 1100 33 34 33
1101 1200 33 33 34
1201 1300 34 33 33
1301 1400 33 34 33
1401 1500 33 33 34
1501 1600 34 33 33
16 rijen zijn geselecteerd.Regards,
Rob.
Maybe you are looking for
-
How can I change my bank details on my iTunes account?
I can't change my bank details on my iPad??
-
How to put data into a array element in the BPEL
Hi, I have a element in the WSDL which is of type Array. (i.e accepts unlimited data for the same element). How should i put a data into a array in the BPEL. Example: The below Example gives u an idea about wht iam asking:pasting a piece of my requir
-
I have Nokia E6 and my bluetooth was not working fine so I reset the factory default settings and before that I took the back up, but once I restore all the settings everything was restored except msgs in which I made several folders. It say zero (0)
-
Binding an object to Listbox.SelectedItem
I have this code: Binding ContactBinding = new Binding("Conversation"); ContactBinding.Source = lstContacts.SelectedItem; BindingOperations.SetBinding(txtRecieve, TextBlock.TextProperty, ContactBinding); Is there a way to set the Cont
-
Nokia N8 - RAM memory full at video playback
Hello.Every now and then when i watching som videos on my Nokia N8 it will stop and display a message that says something like "General! The Phone memory is full, try to close som apps and try again". The thing is that i have even close the "menu ap