13:25:15.422 SETUP (0xbdc) 0xad8 Click-To-Run aqdco Monitorable Tr圜heckNetworkCost::HandleStateAction: Failed to initialize NetworkCostManager for. 13:25:15.407 SETUP (0xbdc) 0xad8 Click-To-Run aoh85 Medium AdminConfigure::HandleStateAction: Configuring an install/crosssell scenario. I believe "Network cost manager" is whatever checks if there's a metered connection in use and the cab file it refers to ( v32_.1029.cab) does exist - C:\odt\Office\Data\v32_.1029.cab - it's not clear to me from this log if it succeeds or fails to find this file, which appears to be the crucial step: Timestamp Process TID Area Category EventID Level Message Correlation I believe this is the relevant segment, because everything after this (around 350 lines) appears related to trying to get network access and it appears to have already concluded that it needs to run. Here are the first few lines of a sample log file. I figured out how to access log files for ODT. I've also tried using the setup.exe /packager command, specifying a valid config file and an output folder, in case the package I have needs to be re-packaged somehow, but it has the exact same problem and error. I've also tried switching Branch to Business which I see is an allowed value in the reference. I've also tried adding the version number from the package files to the XML as a fixed version, in case MS support gave me a version that is not the latest and it's rejecting it for that reason. I get the same result if I add the correct SourcePath ( SourcePath="C:\odt\Office") as no SourePath, which is the expected result because according to the config XML documentation, with no source path added it looks for "Office" in the directory it's in. The error code I get is also identical to the one I get if I rename the Office folder or add a non-existant path to SourcePath (e.g. I've established that it is finding the correct XML file, and that the XML is valid, because if I give a deliberately incorrect config path or deliberately borked XML file it gives a different error code (Error Code: 0-1008 (0)). Please make sure you're connected to the internet or connect to a difference network, then try again. We're sorry, we can't continue because we weren't able to download a required file. From research it seems the "required file" it vaguely alludes to is the 1.06GB installation bundle, which it is (seemingly needlessly) trying to re-download: Couldn't install It gives this error, which indicates that it is trying to download a file. I'm in a country with poor quality internet connections and the MS downloader is both extremely sensitive to momentary losses in connection and unable to resume downloads that are interrupted: re-downloading the files is not an option. it ignores the existing files and tries to download the bundle again. My problem is, when I run setup.exe as an administrator using a command like this. The files Microsoft Support gave me were named Office 365 Business 2016 which appears to correspond. I've confirmed that O365BusinessRetail is one of the supported Product IDs for the ODT and that it is the appropriate ID for my subscription. I have the ODT setup.exe file in C:\odt\Office and a Configuration.xml file with the appropriate settings, for example: Microsoft Support have supplied me with the 1.06GB installation package, which I have downloaded and placed in a directory C:\odt\Office so that the paths to the data files look like this: C:\odt\Office\Data\.1029\ and C:\odt\Office\Data\.1029\ I'm trying to install Office 2016 (business subscription) using the Office Deployment Tool 2016 (ODT) from a pre-downloaded install package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |