Report on "Status updates history"
Hi,
i need to check if resource are updating task from "My Task". Is it possible to estract a report on "Status updates history"?
I mean this type of data:
Approval Date
Action
Status
Info
Task Name
Project
Type
Start
Finish
Actual Work
Remaining Work
% Complete
Assigned To
Approved By
Thanks
Daniele
Hi Daniel,
You will probably have to create a join with the MSP_ASSIGNMENT_TRANSACTIONS Table.
See reference here:
http://blogs.msdn.com/b/project_programmability/archive/2008/01/03/statusing-transactions-partial-documentation.aspx
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS
Similar Messages
-
Status updates history period default
Hi
Is there any way to change the default status updates history date range from 3 months please? Currently as the status approver for a major change program I'm getting several hundred tasks to approve every day across multiple project plans; the problem
is that when I go in to clear down to run my weekly reports it lists every task submission for the last 3 months. The thing is, IE can take several minutes before it displays the page in full as it chews through all of the data which is annoying
to say the least.
I'd quite like it to show only the last 3 weeks, not the last 3 months.
Does anyone have any suggestions please?
Thanks.Hi,
As far as I tested, changing the default 3 months range from the date range feature will unfortunaltely not be kept in your IE cache next time you'll navigate to the status update history page. Thus you'll have to set it again every time you access
the page.
I guess this 3 months default value might be changed programmabily but I can't help on this.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS | -
PLD, Crystal Reports & Crystal Layout Update History
Dear Experts,
How can I get update history of PLD, Crystal Reports & Crystal Layout.
In RDOC table I get value of Last Update Date of any document but not get history & No of times updation.
SAP 8.8 PL:10
Waiting for your valuable reply.
Thanks,
Srujal PatelDear Srujal Patel,
There is no log to keep those changes in current design. You may export the table from time to time to have certain images as of historical records.
Thanks,
Gordon -
REPORT AND STATUS UPDATES - EXCHANGE
Hello
I have installed the Rollup 5 for Exchange 2010. So far so good. The issue is that
in "" Updates Needed "" point, tells me that the machine needs the Rollup 4 and 2 ...
Why can it be?? (I think It should not appear in the report ; NO need more updates )
(The report date is OK )
Regards and thnak you
MCITPHi,
As I referred in my last post, if you have another Exchange Server that needed rollup 2 or 4, you may see such a status report. So the point is that if it is the only Exchange
Server.
And another reason I could think is the server lose connection with WSUS server since it installed rollup 5. Check the computer report, notice the date of last report.
The status
needed means:
You have approved the update for installation but the client computers have not contacted the WSUS server since you approved it.
The update has already been downloaded and installed, but the client computer has not contacted the WSUS server since the update was installed.
The update has already been downloaded and installed, but the client computer must be restarted before changes go into effect. The client computer has not been restarted.
The update has been downloaded to the computer but has not been installed.
The update has not been downloaded or installed on the computer.
Hope this helps. -
Antimalware Overall Status and History - Report
Good morning,
I have setup a subscription to the default report in SCCM named "Antimalware Overall Status and History". When the report is sent out it sends a nice pie chart with categories underneath it. The categories are the following :-
- Protected
- At Risk
- Not yet Installed
- Client Not Supported
- Inactive
- Configuration Manager Client Not Installed
The report works great and it adds all of our clients in to the correct category. However my question is - How does SCCM determine which category clients are added to. Are there certain requirements that a client must meet before it is added to the "Protected"
category.
Also is it possible to edit the settings for these categories?
Regards,Hi,
Since it is related to SCCM, I recommend you to ask in the forum below for professional assistance:
http://social.technet.microsoft.com/Forums/en-US/home?forum=configmanagergeneral
I am really sorry that I moved it to this forum by mistake. Sorry for the inconvenience.
Best regards,
Susie -
Windows 2008 R2 Server not showing update history and not detecting new updates
Hi Sirs,
We have a Windows 2008 R2 server which is showing an empty windows update history, and is not detecting new updates from the WSUS server. It says that the windows is up to date, no error when trying to detect new updates, but I doubt it because when I checked
the installed updates menu, it shows that that the most recent update date installed was last 2013, it just stop detecting and installing updates. I've already tried the ff workarounds but to no avail:
1. restart wuauserv and bits service
2. rename/delete the software distribution folder
3. reinstalled the update agent/restarted the server
4. deleted the susclientid on the registry
Thanks in advanced for your help.
here's the windowsupdate.log:
2014-07-22 00:57:06:728 928 a34 AU #############
2014-07-22 00:57:06:728 928 a34 AU Successfully wrote event for AU health state:0
2014-07-22 00:57:06:728 928 a34 AU Featured notifications is disabled.
2014-07-22 00:57:06:728 928 a34 AU AU setting next detection timeout to 2014-07-21 20:50:56
2014-07-22 00:57:06:728 928 a34 AU Successfully wrote event for AU health state:0
2014-07-22 00:57:06:728 928 a34 AU Successfully wrote event for AU health state:0
2014-07-22 00:57:11:727 928 abc Report REPORT EVENT: {AF0753F1-F6F9-4583-87B0-A0B0AEA0C6A7} 2014-07-22 00:57:06:728+0800 1
147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows
Update Client successfully detected 0 updates.
2014-07-22 00:57:11:727 928 abc Report REPORT EVENT: {188957AA-577F-4DC5-9CDB-2D8CFEE96670} 2014-07-22 00:57:06:728+0800 1
156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting
client status.
2014-07-22 00:57:11:727 928 abc Report CWERReporter finishing event handling. (00000000)
2014-07-22 01:11:10:931 928 abc Report Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22 01:11:10:947 928 abc Report Reporter successfully uploaded 2 events.
2014-07-22 04:50:56:736 928 1130 AU #############
2014-07-22 04:50:56:736 928 1130 AU ## START ## AU: Search for updates
2014-07-22 04:50:56:736 928 1130 AU #########
2014-07-22 04:50:56:736 928 1130 AU <<## SUBMITTED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22 04:50:56:736 928 d08 Agent *************
2014-07-22 04:50:56:736 928 d08 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 04:50:56:736 928 d08 Agent *********
2014-07-22 04:50:56:736 928 d08 Agent * Online = Yes; Ignore download priority = No
2014-07-22 04:50:56:736 928 d08 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22 04:50:56:736 928 d08 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22 04:50:56:736 928 d08 Agent * Search Scope = {Machine}
2014-07-22 04:50:57:017 928 d08 Setup Checking for agent SelfUpdate
2014-07-22 04:50:57:017 928 d08 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22 04:50:57:017 928 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 04:50:57:017 928 d08 Misc Microsoft signed: Yes
2014-07-22 04:50:59:611 928 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 04:50:59:611 928 d08 Misc Microsoft signed: Yes
2014-07-22 04:50:59:611 928 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 04:50:59:611 928 d08 Misc Microsoft signed: Yes
2014-07-22 04:50:59:626 928 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 04:50:59:626 928 d08 Misc Microsoft signed: Yes
2014-07-22 04:50:59:626 928 d08 Setup Determining whether a new setup handler needs to be downloaded
2014-07-22 04:50:59:626 928 d08 Setup SelfUpdate handler is not found. It will be downloaded
2014-07-22 04:50:59:626 928 d08 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 04:51:01:095 928 d08 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 04:51:01:095 928 d08 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 04:51:01:110 928 d08 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 04:51:01:110 928 d08 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 04:51:01:142 928 d08 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 04:51:01:142 928 d08 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22 04:51:01:860 928 d08 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22 04:51:01:860 928 d08 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 04:51:01:891 928 d08 PT WARNING: Cached cookie has expired or new PID is available
2014-07-22 04:51:01:891 928 d08 PT Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22 04:51:01:891 928 d08 PT Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22 04:51:04:485 928 d08 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22 04:51:04:485 928 d08 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 04:51:04:875 928 d08 Agent * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22 04:51:04:875 928 d08 Agent *********
2014-07-22 04:51:04:875 928 d08 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 04:51:04:875 928 d08 Agent *************
2014-07-22 04:51:04:875 928 1278 AU >>## RESUMED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22 04:51:04:875 928 1278 AU # 0 updates detected
2014-07-22 04:51:04:875 928 1278 AU #########
2014-07-22 04:51:04:875 928 1278 AU ## END ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22 04:51:04:875 928 1278 AU #############
2014-07-22 04:51:04:875 928 1278 AU Successfully wrote event for AU health state:0
2014-07-22 04:51:04:875 928 1278 AU Featured notifications is disabled.
2014-07-22 04:51:04:875 928 1278 AU AU setting next detection timeout to 2014-07-22 00:38:28
2014-07-22 04:51:04:875 928 1278 AU Successfully wrote event for AU health state:0
2014-07-22 04:51:04:875 928 1278 AU Successfully wrote event for AU health state:0
2014-07-22 04:51:09:874 928 d08 Report REPORT EVENT: {FE398C01-75A1-4AD8-8C43-0894FCFCE13F} 2014-07-22 04:51:04:875+0800 1
147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows
Update Client successfully detected 0 updates.
2014-07-22 04:51:09:874 928 d08 Report REPORT EVENT: {CDA386AD-6392-4C34-859E-35307BCB5EA0} 2014-07-22 04:51:04:875+0800 1
156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting
client status.
2014-07-22 04:51:09:874 928 d08 Report CWERReporter finishing event handling. (00000000)
2014-07-22 05:05:09:109 928 d08 Report Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22 05:05:09:109 928 d08 Report Reporter successfully uploaded 2 events.
2014-07-22 08:38:28:883 928 1130 AU #############
2014-07-22 08:38:28:883 928 1130 AU ## START ## AU: Search for updates
2014-07-22 08:38:28:883 928 1130 AU #########
2014-07-22 08:38:28:883 928 1130 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22 08:38:28:883 928 53c Agent *************
2014-07-22 08:38:28:883 928 53c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 08:38:28:883 928 53c Agent *********
2014-07-22 08:38:28:883 928 53c Agent * Online = Yes; Ignore download priority = No
2014-07-22 08:38:28:883 928 53c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22 08:38:28:883 928 53c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22 08:38:28:883 928 53c Agent * Search Scope = {Machine}
2014-07-22 08:38:29:195 928 53c Setup Checking for agent SelfUpdate
2014-07-22 08:38:29:195 928 53c Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22 08:38:29:195 928 53c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 08:38:29:195 928 53c Misc Microsoft signed: Yes
2014-07-22 08:38:31:804 928 53c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 08:38:31:804 928 53c Misc Microsoft signed: Yes
2014-07-22 08:38:31:804 928 53c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 08:38:31:820 928 53c Misc Microsoft signed: Yes
2014-07-22 08:38:31:820 928 53c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 08:38:31:820 928 53c Misc Microsoft signed: Yes
2014-07-22 08:38:31:835 928 53c Setup Determining whether a new setup handler needs to be downloaded
2014-07-22 08:38:31:835 928 53c Setup SelfUpdate handler is not found. It will be downloaded
2014-07-22 08:38:31:835 928 53c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 08:38:33:241 928 53c Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 08:38:33:241 928 53c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 08:38:33:272 928 53c Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 08:38:33:272 928 53c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 08:38:33:288 928 53c Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 08:38:33:288 928 53c Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22 08:38:33:991 928 53c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22 08:38:33:991 928 53c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 08:38:34:038 928 53c PT WARNING: Cached cookie has expired or new PID is available
2014-07-22 08:38:34:038 928 53c PT Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22 08:38:34:038 928 53c PT Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22 08:38:36:616 928 53c PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22 08:38:36:616 928 53c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 08:38:37:022 928 53c Agent * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22 08:38:37:022 928 53c Agent *********
2014-07-22 08:38:37:022 928 53c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 08:38:37:022 928 53c Agent *************
2014-07-22 08:38:37:022 928 aa8 AU >>## RESUMED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22 08:38:37:022 928 aa8 AU # 0 updates detected
2014-07-22 08:38:37:022 928 aa8 AU #########
2014-07-22 08:38:37:022 928 aa8 AU ## END ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22 08:38:37:022 928 aa8 AU #############
2014-07-22 08:38:37:022 928 aa8 AU Successfully wrote event for AU health state:0
2014-07-22 08:38:37:022 928 aa8 AU Featured notifications is disabled.
2014-07-22 08:38:37:022 928 aa8 AU AU setting next detection timeout to 2014-07-22 04:15:53
2014-07-22 08:38:37:022 928 aa8 AU Successfully wrote event for AU health state:0
2014-07-22 08:38:37:022 928 aa8 AU Successfully wrote event for AU health state:0
2014-07-22 08:38:42:021 928 53c Report REPORT EVENT: {45B5AD35-C612-4C43-8FE0-DFC63B114FC9} 2014-07-22 08:38:37:022+0800 1
147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows
Update Client successfully detected 0 updates.
2014-07-22 08:38:42:021 928 53c Report REPORT EVENT: {BA606714-0153-41BA-ADC8-78520F678D97} 2014-07-22 08:38:37:022+0800 1
156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting
client status.
2014-07-22 08:38:42:021 928 53c Report CWERReporter finishing event handling. (00000000)
2014-07-22 08:52:41:224 928 53c Report Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22 08:52:41:240 928 53c Report Reporter successfully uploaded 2 events.
2014-07-22 12:15:53:027 928 1130 AU #############
2014-07-22 12:15:53:027 928 1130 AU ## START ## AU: Search for updates
2014-07-22 12:15:53:027 928 1130 AU #########
2014-07-22 12:15:53:027 928 1130 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22 12:15:53:043 928 a58 Agent *************
2014-07-22 12:15:53:043 928 a58 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 12:15:53:043 928 a58 Agent *********
2014-07-22 12:15:53:043 928 a58 Agent * Online = Yes; Ignore download priority = No
2014-07-22 12:15:53:043 928 a58 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22 12:15:53:043 928 a58 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22 12:15:53:043 928 a58 Agent * Search Scope = {Machine}
2014-07-22 12:15:53:308 928 a58 Setup Checking for agent SelfUpdate
2014-07-22 12:15:53:308 928 a58 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22 12:15:53:308 928 a58 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 12:15:53:324 928 a58 Misc Microsoft signed: Yes
2014-07-22 12:15:55:901 928 a58 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 12:15:55:901 928 a58 Misc Microsoft signed: Yes
2014-07-22 12:15:55:901 928 a58 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 12:15:55:917 928 a58 Misc Microsoft signed: Yes
2014-07-22 12:15:55:917 928 a58 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 12:15:55:917 928 a58 Misc Microsoft signed: Yes
2014-07-22 12:15:55:933 928 a58 Setup Determining whether a new setup handler needs to be downloaded
2014-07-22 12:15:55:933 928 a58 Setup SelfUpdate handler is not found. It will be downloaded
2014-07-22 12:15:55:933 928 a58 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 12:15:57:167 928 a58 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 12:15:57:167 928 a58 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 12:15:57:167 928 a58 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 12:15:57:167 928 a58 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 12:15:57:198 928 a58 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 12:15:57:198 928 a58 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22 12:15:57:917 928 a58 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22 12:15:57:917 928 a58 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 12:15:57:963 928 a58 PT WARNING: Cached cookie has expired or new PID is available
2014-07-22 12:15:57:963 928 a58 PT Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22 12:15:57:963 928 a58 PT Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22 12:16:00:572 928 a58 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22 12:16:00:572 928 a58 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 12:16:00:932 928 a58 Agent * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22 12:16:00:932 928 a58 Agent *********
2014-07-22 12:16:00:932 928 a58 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 12:16:00:932 928 a58 Agent *************
2014-07-22 12:16:00:932 928 1120 AU >>## RESUMED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22 12:16:00:932 928 1120 AU # 0 updates detected
2014-07-22 12:16:00:932 928 1120 AU #########
2014-07-22 12:16:00:932 928 1120 AU ## END ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22 12:16:00:932 928 1120 AU #############
2014-07-22 12:16:00:932 928 1120 AU Successfully wrote event for AU health state:0
2014-07-22 12:16:00:932 928 1120 AU Featured notifications is disabled.
2014-07-22 12:16:00:932 928 1120 AU AU setting next detection timeout to 2014-07-22 08:15:22
2014-07-22 12:16:00:932 928 1120 AU Successfully wrote event for AU health state:0
2014-07-22 12:16:00:932 928 1120 AU Successfully wrote event for AU health state:0
2014-07-22 12:16:05:931 928 a58 Report REPORT EVENT: {25E75367-1205-4F59-A812-02DA28BB3234} 2014-07-22 12:16:00:932+0800 1
147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows
Update Client successfully detected 0 updates.
2014-07-22 12:16:05:931 928 a58 Report REPORT EVENT: {FE1434F8-C6AF-4F87-B3DF-6E4D6C4B05FB} 2014-07-22 12:16:00:932+0800 1
156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting
client status.
2014-07-22 12:16:05:931 928 a58 Report CWERReporter finishing event handling. (00000000)
2014-07-22 12:30:05:116 928 a58 Report Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22 12:30:05:131 928 a58 Report Reporter successfully uploaded 2 events.
2014-07-22 14:05:29:584 928 10a0 AU Triggering AU detection through DetectNow API
2014-07-22 14:05:29:584 928 10a0 AU Triggering Online detection (interactive)
2014-07-22 14:05:29:584 928 1130 AU #############
2014-07-22 14:05:29:584 928 1130 AU ## START ## AU: Search for updates
2014-07-22 14:05:29:584 928 1130 AU #########
2014-07-22 14:05:29:584 928 1130 AU <<## SUBMITTED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22 14:05:29:584 928 8e0 Agent *************
2014-07-22 14:05:29:584 928 8e0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 14:05:29:584 928 8e0 Agent *********
2014-07-22 14:05:29:584 928 8e0 Agent * Online = Yes; Ignore download priority = No
2014-07-22 14:05:29:584 928 8e0 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22 14:05:29:584 928 8e0 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22 14:05:29:584 928 8e0 Agent * Search Scope = {Machine}
2014-07-22 14:05:29:584 928 8e0 Setup Checking for agent SelfUpdate
2014-07-22 14:05:29:584 928 8e0 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22 14:05:29:584 928 8e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 14:05:29:600 928 8e0 Misc Microsoft signed: Yes
2014-07-22 14:05:29:616 928 8e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22 14:05:29:631 928 8e0 Misc Microsoft signed: Yes
2014-07-22 14:05:29:631 928 8e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 14:05:29:631 928 8e0 Misc Microsoft signed: Yes
2014-07-22 14:05:29:647 928 8e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22 14:05:29:662 928 8e0 Misc Microsoft signed: Yes
2014-07-22 14:05:29:662 928 8e0 Setup Determining whether a new setup handler needs to be downloaded
2014-07-22 14:05:29:662 928 8e0 Setup SelfUpdate handler is not found. It will be downloaded
2014-07-22 14:05:29:662 928 8e0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 14:05:29:662 928 8e0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 14:05:29:662 928 8e0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 14:05:29:694 928 8e0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 14:05:29:694 928 8e0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22 14:05:29:709 928 8e0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22 14:05:29:725 928 8e0 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22 14:05:30:037 928 8e0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22 14:05:30:037 928 8e0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 14:05:30:053 928 8e0 PT WARNING: Cached cookie has expired or new PID is available
2014-07-22 14:05:30:053 928 8e0 PT Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22 14:05:30:053 928 8e0 PT Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22 14:05:35:630 928 8e0 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22 14:05:35:630 928 8e0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22 14:05:36:411 928 8e0 Agent * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22 14:05:36:411 928 8e0 Agent *********
2014-07-22 14:05:36:411 928 8e0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22 14:05:36:411 928 8e0 Agent *************
2014-07-22 14:05:36:411 928 1360 AU >>## RESUMED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22 14:05:36:411 928 1360 AU # 0 updates detected
2014-07-22 14:05:36:411 928 1360 AU #########
2014-07-22 14:05:36:411 928 1360 AU ## END ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22 14:05:36:411 928 1360 AU #############
2014-07-22 14:05:36:411 928 1360 AU Successfully wrote event for AU health state:0
2014-07-22 14:05:36:411 928 1360 AU Featured notifications is disabled.
2014-07-22 14:05:36:411 928 1360 AU AU setting next detection timeout to 2014-07-22 10:01:01
2014-07-22 14:05:36:411 928 1360 AU Successfully wrote event for AU health state:0
2014-07-22 14:05:36:411 928 1360 AU Successfully wrote event for AU health state:0
2014-07-22 14:05:41:410 928 8e0 Report REPORT EVENT: {6A2B180E-A95F-42F7-B775-5750DFFD6ECD} 2014-07-22 14:05:36:411+0800 1
147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows
Update Client successfully detected 0 updates.
2014-07-22 14:05:41:410 928 8e0 Report REPORT EVENT: {83041427-693D-4A42-AED0-E8E7BFB8E7E3} 2014-07-22 14:05:36:411+0800 1
156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting
client status.
2014-07-22 14:05:41:410 928 8e0 Report CWERReporter finishing event handling. (00000000)No Service Pack 1 installed. Does this mean that no updates will be detected if SP1 is not installed? thanks
That's exactly what that means!
Updates have not been available for Windows Server 2008 R2 *RTM* systems since April, 2013.
http://support.microsoft.com/lifecycle/?p1=14134
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
Status update for MeeGo on the N900
Here's a copy of the text sent by Harri Hakulinen from Nokia. He is the project lead for MeeGo on the N900. This message was sent to the MeeGo developer mailing list just now:
Hello MeeGos !
This is brief status update of "MeeGo to N900" project. This project is currently running as Nokia project, and I am Nokia project lead for it. The current closed mode of development is not the target for us at all, but rather transitional condition. As already discussed by Valtteri in TSG meeting, we are looking into going more open mode shortly. One reason why we have done this on this way is that at the same time we have been trying to handle opening of many currenly closed components that are needed in MeeGo and to build feasible MeeGo images for N900.
However, a lot of related work is already done completely open, you can find more info from places like ofono.org, connman.net and meego.gitorious.org . So if you are eager to contribute or want to closely follow whats happening, please work on those.
As you know, we have delivered working MeeGo images for N900 as part of first code drop in the end of March. At that state we were using older kernel version on N900 than on Atom side, as we used the same kernel (.28) than what is used in Maemo 5 based products today. We ended up doing that simply because lack of time to contribute and port all the drivers to the newer kernels.
Now, for the upcoming May release of MeeGo, we are going to use the same kernel version (.33) than Atom based devices are using. For that we need to submit number of ARM-architecture patches to MeeGo as well, because many of the required ones have just been contibuted upstream kernel and were not available in .33 version originally.
We have already enabled most of the main drivers, like LCD, GFX, Wlan and BT. Still, there is a lot to do in order to enable .33 on N900, like audio drivers, and modem subsystem including SSI buss driver, modem data and audio drivers etc. Our adaptation guys are in fact contributing those modem subsystem related drivers as we speak, and if you are following kernel mailing lists you can see how that goes on.
Besides of enabling the new kernel, we are working with number of smaller and bigger issues for N900. Starting from the beginning, we are now based on ARMv7 combiled code, so the code should be better optimised for N900 now. ARMv5 compilation that was in use for code drop will still be there, and it also seems to be used at least by community project that is planning to release MeeGo for good old N810 tablets
Also, we are planning to enable dual booting of Maemo 5 and MeeGo for the upcoming release. So that will be offered as 3rd way to setup MeeGo to N900, including the existing "native" MeeGo only on N900 and chroot based MeeGo on Maemo 5 setups. Taking the dual boot mode into use likely includes upgrade to Maemo5 kernel as well, but that should not be big issue in the process of enabling that.
As I don't want to go ahead of others working on MeeGo architecture and other issues I will stop now, but I will report again when we have more to tell about the subject.
Br,
// HarriHere's another update..
It seems that MeeGo on the N900 is not directly being driven by Nokia! It's an open project.. so the net result is MeeGo on the N900 may look and feel very different to Meego on the N900's sucessor
Either way, I'm certainly greatful for their efforts!
Hello Meego's,
As indicated in my previous mail about "MeeGo for N900" status, we were planning to open up our MeeGo work around N900. Now I am happy to announce, that we are there
First, to make it absolute clear for everybody: This is about open MeeGo adaptation to N900 device.
Like any other MeeGo project, it is open source project for all applicaple purposes, and does NOT directly have links to any potential Nokia product or potential product plans. So, based on this or any other of my posts, please do NOT start or continue speculation of upcoming Nokia MeeGo releases. That is practically not helpfull, and mostly only takes our time when we need to explain our words and actions in detail to various directions.
From our part, we are trying to implement the open development model that has been discussed now so many times around MeeGo. On practical terms, we are trying to work based on proposal by Carsten Munk, see
http://wiki.meego.com/Proposal_for_Best_Practices_for_working_in_a_MeeGo_team
We have already created some resources that will be used by the team, you can learn about those and the upcoming ones from http://wiki.meego.com/ARM/N900. We have IRC channel for realtime discussion, we will use meego-dev mailing list for normal discussions and announcements, and we will have Gitorius project for code.
We will evolve our practicies during the work, so if you are interested, stay tuned to those channels. I belive that soon we are also able to figure out, what is best way for community members to help us in development, and then effectively be part of the team.
I would also like to use this as opportunity to introduce the team behind this work (so far) and also thank them about their hard work and long hours. We have team that consist of some Nokia subcontractors and also growing team of Nokia personel:
"MeeGo for N900" team (so far)
- Cybercom Turku team; Marko Saukko, Jouni Peltonen, Sami Sirkiä, Jari Smura and Luka Milovanov.
- Cybercom Tampere team; Kalle Lampila,Teemu Tuominen,Tuukka Mäkinen and Ville Marjusaari.
- Carsten Munk via Nomovok
- Jarkko Nikula via Atomide
- Jan-Simon Möller from Linuxfoundation
- Nokia team; Alexander Kanevskiy, Felipe Contreras, Markus Lehtonen, Ameya Palande, Sakari Poussa, Roger Quadros and me.
In addition to official project team, many Nokia people have helped us despite their hectic daily work, even with their free time. Most of them are driven by the desire to open, repurpose and upstream all relevant sw that has been originally created for Maemo 5 based N900 product during previous years.
Marko, Jouni, Sami & Luka and Markus were working with me already on last year when we did prototypes and interoperability tests of Maemo & Moblin stuff combined in different ways. Based on those we had pretty good picture of what we are doing and why.
And of course, we have had very good and productive co-operation with various Intel teams since those times. Anas Nashif and many others from Intel's MeeGo team have done a lot for us by enabling ARM stuff in MeeGo OBS and repositories.
Last but not least, I want to give special thanks to Stskeeps (alias Carsten Munk . He has teached us how to operate on open, and he has also done respectable amount of this work since early days of Meego. In addition to that, I belive that his earlier work on Maemo community and on Mer project has in fact inspired all of us and shown a way to MeeGo alredy years ago.
Br,
//Harri -
Update showing as succeeded in update history but still pending installation (KB2975719)
I just installed September patches. KB2975719 is showing as downloaded but not installed in both the WSUS console, and the Windows Update control panel of servers.
The WindowsUpdate.log file shows the patch as successfully installed:
2014-09-20 19:10:07:325 704 a0c Report REPORT EVENT: {FE320875-D2A9-44A5-8F8F-5EEA2782EE27} 2014-09-20 19:09:50:763+0100
1 190 [AU_SCHEDULED_INSTALL_SUCCESS] 101 {756F8A5D-1588-4CFA-9B00-3DC89266CEE0} 204 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following update: Update for Windows Server 2012 R2 (KB2975719)
The WindowsUpdate control panel "View update history" also shows it as succeeded
And so does the event viewer - SYSTEM:
Source: WindowsUpdateClient; ID 19; Message: Installation Successful: Windows successfully installed the following update: Update for Windows Server 2012 R2 (KB2975719)
Despite these, the KB2975719 still shows as ready to install in the Windows Update control panel. "One important update is available" -> "Update for Windows Server 2012 R2 (KB2975719).
I installed the patch manually on one server and it did install correctly. I now have two lines showing success for KB2975719 in the "view update history".
I noticed this like in my update log and was wondering if it could be part of the problem:
2014-09-20 19:03:32:274 708 a18 Shutdwn user declined update at shutdown
It's not the first time I face patches that do not install. It seems to be a recurring issue on my servers. Not sure if I did something wrong with the configuration of WSUS. Each month I have 1-2 patches that do not install while other are installing properly.
Has anyone seen this already of have an idea of how I could troubleshoot this further?Please read the KB article for 2975719. It clearly lists update 2993651 as a pre-requisite.
Okay, so why are we having this conversation? It's a documented prerequisite. Having access to that information, it's then incumbent upon you to install the August KB2993651 Security Update, before the September KB2975719 Update Rollup as indicated
by the documentation for the update.
That's pretty much the way 99% of people are going to patch their systems anyway. (FWIW, I never encountered this issue on any of my systems because I always install Security Updates first and I installed the Update Rollup last.)
Yes, the Update Rollup does not detect that prerequisite. Fact is, there are a LOT of updates that do not have logic to detect for prerequisites, so in that this is not really unusual at all., albeit somewhat inconvenient if you're trying to throw months
of updates at a machine in a single pass.
What I'd say is more disconcerting, is not that the detection logic fails to detect the prereq, but that the "Update Rollup" didn't include the prerequisite update in the first place.
In any event, you're right, this is something for the Windows SE team to fix. That would be something to discuss with them in the Windows OS forum.
We use MDT to "build and capture" the fully-patched image that we then deploy with SCCM.
But that's not what I said. What I said was to patch the IMAGE (not patch a reference machine and recapture a patched image), so that the IMAGE is always up to date.
But even if you patch a reference machine, and recapture the image, and keep the reference machine up-to-date on a monthly basis, or only patch one-month-at-a-time of updates, you would have never encountered this issue. Fundamentally you
hit this issue because you're deploying multiple months of update simultaneously.
Patching the IMAGE as the update are released would completely avoid this issue (as well as eliminate the need to regularly recapture the image) as the August Security Updates would have almost certainly been applied prior to a September Update Rollup.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
Is there some way to check and see, either on your phone or on itunes, which apps were udpated most recently? A number of apps had updates from the app store this morning and I did the "Update All" and now one of those updated apps is killing my battery. But without a list of which apps were updated, there's no way to know which ones to delete and reinstall. I know that you have a purchase history in itunes but I haven't found any app update history.
I'm amazed that only six of us have this question. It seems like something we should be able to find without keeping a list ourselves.
I'm in a simliar situation in that suddenly my phone is sucking down between 1 and 2 GB of data around 2 AM, but I cant' figure out which app it is. It would be great if I could see what I updated recently to see if removing those from the phone would fix the (very expensive) problem, since anything that I've been running for months or years and not updated should not suddenly be causing me problems.
I'm suspicious of one app in particular, since others have reported problems that sound just like what I've experienced, but I'd like to have a little more data.
Maybe a little over a year after this original question was posted someone will have an idea or an answer? -
Certain MBAM agents not reporting compliance status
I have MBAM setup in a two computer configuration topology both servers running Windows Server 2008 R2.
The problem I have is that certain clients are not reporting back their compliance status to the MBAM servers and when I check the log files for these clients the MBAM Operational logs shows "The MBAM
policies were applied successfully." This event appears regularly within the 90min windows as expected which is fine.
When I check the MBAM Admin log files had absolutely no new entries since January this year so something is definitely not right. On working clients both the Admin and Operational logs should be updated at least once every 90min that's how it was configured
in GPO.
All clients are running version 1.0.2 of the MBAM agent on Windows 7 Enterprise SP1. The problem has to be client side because there are machines reporting back regularly with no problem on the same network.
Hi,
Please take a check to see if the following KB could help here:
MBAM Enterprise Reporting Not Getting Updated
Besides, questions related MBAM, please consider ask in the following forum:
http://social.technet.microsoft.com/Forums/en-US/home?forum=mdopmbam
Experts there might share some insights for the issue here.
Best regards
Michael Shao
TechNet Community Support -
CPH Reports for Status Attribute.
Using Central performance History (RZ23n), is it possible to create reports for Status attributes?
Eg: I want to create for number of abap dumps, dead locks for each day.
As per documentation it says we can create for performance values and we are able to create CPH reports for R3Dialog Response time...
http://help.sap.com/saphelp_nw70/helpdata/en/c2/49773dd1210968e10000000a114084/content.htm
Any help or ideas are appreciated.
Thanks,
Venkat.Thank you Shyam for so prompt reply,
We are using the same report. But its bit uneasy to go to change document of each and every ticket. Also in this report we could not find how much days the notification lay in New status or in In-process status. We require somewhat in following format.
Ticket number New Customer action In-process
000001 1Day 1.3 Days 1 Day
000002 1.3 Days 2.3 Days 1 Day
000003 3 Days 3.4 Days 1 Day
We are not bothered about days, week or hours etc. The purpose is to indentify how much time every ticket took stage wise. May be through ABAP this possible but we are looking for standard reports.
Thanks
Anand Rao -
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 -
STPPOD - DELVRY03 -GR Status Update in SNC
When we create an ASN in SNC with single material, mutiple line items corresponding to different PO's with a specific delivery date and when we post GR in ECC against this ASN and to send POD status update to SNC when RSMIPROACT batch job is run - We are noticing GR status update is happeing for the material in one line item with one PO but the other line item for the same material with different PO is not getting status update.
when we checked the ECC - DELVRY03 -Idocs they are getting generated only for single line item of ASN not for other line item.
Note : This scenario is with ASN with multiple line items here the Material is only one - Each line item has same material but different PO and whole of ASN would be with specific delivery date.
Can any one pls let me know if an ASN with multiple line items ( for single material) when GR is posted and when we send the GR status info (POD) to SNC thru Batch job - how it works.
I have checked PO history for the 2 PO's of same material - it is getting updated correctly.
Would appreciate your immediate help.
Regards,
MaheshHi Mahesh
I have created an ASN for the same material with specific delivery date, with mulitiple line items belonging to different PO.
I have posted a STPPOD idoc from ECC against the inbound delivery using VL32N.(Goods Reciept against inbound delivery)
It is posting to all the PO's and all are updated properly
Also can you check whether you DELVRY03 idoc has E1EDL24(Delivery Item) as many as your ASN line items????
Like if you three line items in ASN, then there should be three E1EDL24 segments carrying the info..
Best Regards
Vinod
Edited by: Vinod Kumar Pedapati on Sep 16, 2010 11:35 AM -
[WMI] QFE InstalledOn date property differs from GUI "update history", WMI bug?
Hello,
When I use get-hotfix (uses WMI under the hood) on a Windows 2012 box to retrieve the Installdate for windows hotfixes, there is a difference between the date Powershell reports and the date visible in the update history GUI.
http://i.imgur.com/HJVdsY4.png
The GUI shows an install date of July 11th, where the get-hotfix shows an install date of September 21st.
The hotfix is installed in July, not in September. it doesn't seem to be a date formatting issue.
Is this a known issue? if so is there a fix available?
thanks in advance,
SanderHello,
When I use get-hotfix (uses WMI under the hood) on a Windows 2012 box to retrieve the Installdate for windows hotfixes, there is a difference between the date Powershell reports and the date visible in the update history GUI.
http://i.imgur.com/HJVdsY4.png
The GUI shows an install date of July 11th, where the get-hotfix shows an install date of September 21st.
The hotfix is installed in July, not in September. it doesn't seem to be a date formatting issue.
Is this a known issue? if so is there a fix available?
thanks in advance,
Sander -
Reporting on service call history
I would like to create a report of service call history as can be seen on the service call tab. I know the ASCL table is the change log for service calls: is this my only option for getting a report? Is there a view for the Service call history?
My goal is to track the time it takes between changes in Call Status for some performance reporting. Any suggestions would be much appreciated.
LauraHi Laura,
If you need a report for service call history that can be seen on the service call tab, you may not need ASCL. ASCL only saves the header changes. Those data under each tab are saved in the SCLx sub tables.
Thanks,
Gordon
Maybe you are looking for
-
sir my printer is not printing the actual colours, for example when i want to print yellow colour, it is printing brown colour, what might be the problem with my printer? and what shoul i do? thanks..
-
Is there any reason photos in an album page created in iweb display small on the iPad, but normally on an iMac? And videos on a movies page don't play on the iPad, but are OK on the iMac?
-
My noctua d14 is running to fast on my p67a-g45-b3
ive just installed noctua d14 with the low noise adapter, but its still to noisy, its spinning around 920rpm how do i lower it more? and what exactly is smart fan target in bios?
-
SOA 11.1.1.5.0 Installation on W7-64 bit
What is the correct version of JDK for successfull installation of the following combination? DB 11.2.0.1 JDK 1.6.0_?? WLS 10.3.5 RCU 11.1.1.5.0 SOA 11.1.1.5.0 JDeveloper 11.1.1.5.0 Will JDK 1.6.0_30 64 bit work? Not for me. I have used JDK 1.6.0_30
-
Verizon data signup says card expiration is invalid
Is there a workaround to signing up for the data service aside from the iPad portal? My credit card expires in 2020, but when I enter all the information to sign up, it says that the expiration date is invalid.