![]() ![]() 13:34:44,155 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta. 13:34:44,155 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 13:34:39,122 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 13:34:34,106 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 13:34:29,084 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 13:34:24,042 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 13:34:19,009 DEBUG HttpUpload - transactionId parameter contained an invalid TCM URI string: meta.xml, processing as normal file request 13:34:15,463 DEBUG HttpUpload - Moving Tmp file to C:\inetpub\Deployment_Test\tcm_0.Content.zip is successful. 13:34:15,463 DEBUG HttpUpload - Storing incoming file in destination: C:\inetpub\Deployment_Test\tcm_0.Content.zip_tmp 13:34:15,463 INFO HttpUpload - Received incoming file with name: tcm_0.Content.zip Please find the cd_core.log file errors below i have successfully transported the package but unable to deploy it. At the time of publishing my pages has got stuck into the publishing queue with "waiting for deployment status". File sharing sites are blocked by corporate policy.I have configured 2013 sp1 into the environment. On CEP_llectionID=collections_g.collectionidīig thank you to everyone that helped me troubleshoot and best of luck to anyone else possibly having this issue.įigured copying a pasting long text files would be cumbersome for the comments, but happy to do so as you are requesting. If you find yourself in this situation, run the following SQL script against your SCCM database to identify the exact collection with this setting enabled.įrom CEP_CollectionExtendedProperties join collections_g Ultimately the issue came down to having a feature enabled we do not use, our lack of knowledge of the feature, and it accidentally being set on a collection. We found the correct collection and found this setting enabled causing issues with all devices inside. Groups" enabled in our environment and the feature accidentally got enabled on a random Device collection. The issue turned out being related to a (at this current time) Pre-Release feature called " Server WUAHandler 6:59:03 AM 8028 (0x1F5C)Īnyone have any ideas why these updates are not applying? Happy to provide some more logs as requested.įor anyone else that may stumble over this post, I ended up submitting a microsoft support case and we were able to resolve this issue. ![]() Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains '8C3FCC84-7410-4A95-8B89-A166A0190486') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'A38C835C-2950-4E87-86CC-6911A52C34A3')) WUAHandler 6:59:00 AM 8028 (0x1F5C)Īsync searching of updates using WUAgent started.Īsync searching completed. Scan results will include all superseded updates. Its a WSUS Update Source type () of content type: 2 WUAHandler 6:59:00 AM 8028 (0x1F5C) I can confirm these devices are online and reachable.īelow is the WUAHandler.log logs from an example PC starting on when these updates should have applied. As you said, we could click the view queue option to check. When you see the state:Waiting in the Deployment Queue, there should be unfinished deployment before this deployment. This means that you can only run release deployment one by one. Second, if I review the report "Maintenance windows available to a specified client" and enter several devices showing this status, the report consistently reports back no maintenance windows set on any device. By default, when you add a stage in release pipeline, the Maximum number of parallel deployments is 1. "Waiting for maintenance window before installing." The issue is that we do not use maintenance windows on these devices and never have.įirst, if I review the SUG deployment, deployment deadline was set to December 8th (edited), this past Sunday, and the option is checked to force both install and restart outside the maintenance window when the deadline is reached. I recently deployed a Software Upgrade group to our production collection for workstations. I have previously deployed the same SUG to test collections with no issue, but I am now seeing nearly all of devices "In Progress" with the status ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |