Well it seems to have done everything that that flowchart is showing.
Looking at the ConfigMgrSetup.log there is one odd thing in there…
Cannot create
S:\SCCM\EasySetupPayload\c43a89e4-b642-4fc8-abf0-255bf5d88d82\redist\LanguagePack\\AutoUpgradeScripts\PostUpgradeScripts,
[error code: 123, error message: The filename, directory name, or volume label
syntax is incorrect.]. Configuration Manager Setup 23/11/2016 3:08:24 PM
26900 (0x6914)
ERROR(3): Failed to iterate cab file. Configuration Manager Setup
23/11/2016 3:08:24 PM 26900 (0x6914)
ERROR: Failed to expand the data file
AutoUpgradeScripts\PostUpgradeScripts\PostUpgrade0.sql. Error: 3
Configuration Manager Setup 23/11/2016 3:08:24 PM 26900 (0x6914)
Seems to me like there is a file with a \\ which seems odd…
In the EasySetupPayload folder I can see that there are 5 subfolder with guid
names, only one of them has content and that is the one that had stuff
downloaded on the 23/11/2016
Nothing else seems out of place…
Oh and I just realised I used the script ‘EnableFastUpdateRing1610.ps1’ at the
time to try to get the update sooner…
________________________________
Magnus Tveten
Server Engineer
Infrastructure oN demand
IAG labs
From: [email protected] [mailto:[email protected]] On
Behalf Of Niall Brady
Sent: Wednesday, 11 January 2017 6:02 PM
To: [email protected]
Subject: Re: [mssms] 1610 update issue
ok can you please go through this workflow and see does it help
https://docs.microsoft.com/en-us/sccm/core/servers/manage/download-updates-flowchart
On Tue, Jan 10, 2017 at 10:51 PM, Magnus Tveten
<[email protected]<mailto:[email protected]>> wrote:
Yup I did try that… but tried again now got good measure.. no luck..
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Niall Brady
Sent: Tuesday, 10 January 2017 4:49 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] 1610 update issue
have you tried restarting smsexec ?
On Tue, Jan 10, 2017 at 4:36 AM, Magnus Tveten
<[email protected]<mailto:[email protected]>> wrote:
HI All,
In my Lab SCCM environment I seem to have an issue with the
1610 update replicating from the CAS(yes I know...it just ended up we needed a
CAS) to the primary server.
[cid:[email protected]]
(yes I also realise that this happened quite some time ago now.. but the update
just popped up on prod recently as available and that made me think to check in
lab)
My problem is that there does not seem to be any way to make it retry…. The
Distmgr.log has nothing relevant to this anymore,
Docs seem to indicate I should be able to retry..
https://github.com/Microsoft/SCCMdocs/blob/master/sccm/core/servers/manage/install-in-console-updates.md#bkmk_retry
however there is no re-try.. only run Prerequisite check.
[cid:[email protected]]
Anyone seen this happen and have any ideas for a fix ?
________________________________
Magnus Tveten
Server Engineer
Infrastructure oN demand
IAG labs
_____________________________________________________________________
The information transmitted in this message and its attachments (if any) is
intended
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance
upon this information, by persons or entities other than the intended recipient
is
prohibited.
If you have received this in error, please contact the sender and delete this
e-mail
and associated material from any computer.
The intended recipient of this e-mail may only use, reproduce, disclose or
distribute
the information contained in this e-mail and any attached files, with the
permission
of the sender.
This message has been scanned for viruses.
_____________________________________________________________________
_____________________________________________________________________
The information transmitted in this message and its attachments (if any) is
intended
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance
upon this information, by persons or entities other than the intended recipient
is
prohibited.
If you have received this in error, please contact the sender and delete this
e-mail
and associated material from any computer.
The intended recipient of this e-mail may only use, reproduce, disclose or
distribute
the information contained in this e-mail and any attached files, with the
permission
of the sender.
This message has been scanned for viruses.
_____________________________________________________________________
_____________________________________________________________________
The information transmitted in this message and its attachments (if any) is
intended
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance
upon this information, by persons or entities other than the intended recipient
is
prohibited.
If you have received this in error, please contact the sender and delete this
e-mail
and associated material from any computer.
The intended recipient of this e-mail may only use, reproduce, disclose or
distribute
the information contained in this e-mail and any attached files, with the
permission
of the sender.
This message has been scanned for viruses.
_____________________________________________________________________
