Forum Discussion

Kevin Taber's avatar
Kevin Taber
Brass Contributor
Sep 21, 2021

Channel MonthlyEnterprise

The MonthlyEnterprise channel is not working with the latest ODT that is available as of today.   ODT: 16.0.14326.20404
manoth_msft's avatar
manoth_msft
Icon for Microsoft rankMicrosoft
The XML gave me an error initially, as it can't write data to C:\users\username\... When changing the SourcePath to C:\Temp it worked fine for me. Can you check if changing the sourcepath resolves your issue?

With C:\temp it worked fine for both updatechannel = MonthlyEnterprise and Current
kamesh_ss's avatar
kamesh_ss
Copper Contributor
Mar 02, 2023
Thanks, Martin. This is weird. We are behind a proxy. If I do the same on a VM without proxy, direct access to internet, it just works fine. But the error code still confuses me why it was showing me 0-2015 (2250), which is apparently related to wrong channel... Or because my network point is blocked, and it doesn't understand that there is a "MonthlyEnterprise" channel ?
    • kamesh_ss's avatar
      kamesh_ss
      Copper Contributor
      Mar 02, 2023

      manoth_msft 😐 It goes via proxy, we have the following endpoints whitelisted.

       

      activation.sls.microsoft.com
      crl.microsoft.com
      download.microsoft.com
      download.windowsupdate.com
      go.microsoft.com
      ntservicepack.microsoft.com
      sls.microsoft.com
      update.microsoft.com
      windowsupdate.microsoft.com
      wustat.windows.com
      www.microsoft.com

       

      I guess we also have to whitelist officecdn.microsoft.com.

       

      Thanks for the insight, Martin. I'll check further.

  • manoth_msft's avatar
    manoth_msft
    Icon for Microsoft rankMicrosoft
    Mar 02, 2023

    kamesh_ss 

    I want to add, for troubleshooting, do this:

     

    1. Delete all files from %temp%.
    2. Reproduce the issue.
    3. Go into %temp%, open the most recent file which is in the format of %computername%-%timestamp%.log.
    4. Search bottom-up for "unexpected". These are "hard" errors. Read the whole(!) line. Towards the end there are often human readable error messages. Also check the ~two lines above/below for cues.

     

    E.g. my failed test (because the specified sourcepath was not accessible) looks likes like this:

     

    03/02/2023 09:36:14.366 SETUP (0x1c0c8) 0x150d4 Click-To-Run Non Task Error brkp4 Unexpected wWinMain {"MachineId": "5f532c6cd3c0a8489e7b7bb286ebd715", "SessionID": "21003f8c-c0f6-4554-95ad-8c9e76c37d0e", "GeoID": 94, "Ver": "0.0.0.0", "C2RClientVer": "16.0.16026.20162", "ErrorCode": 5, "ErrorType": "5", "AppVErrorSource": "", "ErrorMessage": "ErrorCodeOnly (Failed to ensure a directory. , Error:0x5)", "ErrorDetails": "", "ContextData": "{\"message\":\"Installation failed (OException)\"}"}

     

    So, the logs hints me into the direction that my installation failed due to some issues with the directory I provided.

    • kamesh_ss's avatar
      kamesh_ss
      Copper Contributor
      Mar 02, 2023
      Thanks, that actually helped!
    • kamesh_ss's avatar
      kamesh_ss
      Copper Contributor
      Mar 07, 2023

      manoth_msft 

       

      Narrowing down the issue more

       

      03/07/2023 22:38:58.886	SETUP (0x2180)	0x2070		Click-To-Run Non Task Error	brkp4	Unexpected	wWinMain {"MachineId": "314c03f2e21e7f4f8b5f3ca279414f80", "SessionID": "04c4da1a-6d3a-4080-bd1b-ab8223fac50f", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "16.0.16026.20162", "ErrorCode": 30088, "ErrorType": "UnexpectedError", "AppVErrorSource": "", "ErrorMessage": "UnexpectedError (Error Parsing Json string.  , Error:0x7)", "ErrorDetails": "", "ContextData": "{\"message\":\"Installation failed (OException)\"}"}

      I'm getting the above error with the same XML file. We've added more endpoints to the proxy.

      The error is now Error Parsing Json String. No idea what that means in ODT. 

      • wygcuba's avatar
        wygcuba
        Copper Contributor
        Jul 25, 2024

        @ just downloaded from Internet the last version of the setup.exe installer for Office 365, and when I tried to tun it, it gave me the error code 0-2015 (2250). I don't have an xml file or similar, just the setup.exe file, downloaded directly from Office webpage. How is that even in 2024 this is not solved? 

Resources