Search Unity

  1. Calling all beginners! Join the FPS Beginners Mods Challenge until December 13.
    Dismiss Notice
  2. It's Cyber Week at the Asset Store!
    Dismiss Notice
FPS Beginners Mods Challenge Cyber Week Mega Sale

Package manager failed to start Unity 2018.2.3f1

Discussion in 'Package Manager' started by agwebberley, May 6, 2019.

  1. agwebberley

    agwebberley

    Joined:
    Dec 4, 2018
    Posts:
    5
    Package manager failed to start all of the sudden... It worked all the time but then it stopped for no apparent reason. There were no changes. I have attached the Editor.log

    LICENSE SYSTEM [201955 17:19:39] Next license update check is after 2019-05-07T00:12:42

    Built from '2018.2/release' branch; Version is '2018.2.8f1 (ae1180820377) revision 11407744'; Using compiler version '191225831'
    OS: 'Windows 7 (6.1.0) 64bit' Language: 'en' Physical Memory: 4094 MB
    BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 0
    [Package Manager] Server::Start -- Port 55047 was selected

    COMMAND LINE ARGUMENTS:
    C:\Program Files\Unity\Hub\Editor\2018.2.8f1\Editor\Unity.exe
    -projectpath
    C:/Users/Andrew/Documents/GitHub/Team_Project/Team_Poject
    -useHub
    -hubIPC
    -cloudEnvironment
    production
    -hubSessionId
    9f9d90d0-6f93-11e9-b232-df68873f7778
    Successfully changed project path to: C:/Users/Andrew/Documents/GitHub/Team_Project/Team_Poject
    C:/Users/Andrew/Documents/GitHub/Team_Project/Team_Poject
    Loading GUID <-> Path mappings...0.000161 seconds
    Loading Asset Database...0.035123 seconds
    Audio: FMOD Profiler initialized on port 54900
    AssetDatabase consistency checks...0.029194 seconds
    Refreshing native plugins compatible for Editor in 35.88 ms, found 2 plugins.
    Preloading 0 native plugins for Editor in 0.00 ms.
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #2

    [Package Manager] Server::Start -- Port 51813 was selected
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #3

    [Package Manager] Server::Start -- Port 54726 was selected
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #4

    [Package Manager] Server::Start -- Port 52392 was selected
    [Package Manager] Cannot connect to Unity Package Manager local server
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #5

    [Package Manager] Server::Start -- Port 53789 was selected
    [Package Manager] Cannot connect to Unity Package Manager local server
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #6

    [Package Manager] Server::Start -- Port 62987 was selected
    [Package Manager] Cannot connect to Unity Package Manager local server
    [Package Manager] Failed to start Unity Package Manager: operation timed out.

    LICENSE SYSTEM [201955 17:23:15] Next license update check is after 2019-05-07T00:12:42

    Built from '2018.2/release' branch; Version is '2018.2.8f1 (ae1180820377) revision 11407744'; Using compiler version '191225831'
    OS: 'Windows 7 (6.1.0) 64bit' Language: 'en' Physical Memory: 4094 MB
    BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 0
    [Package Manager] Server::Start -- Port 60107 was selected

    COMMAND LINE ARGUMENTS:
    C:\Program Files\Unity\Hub\Editor\2018.2.8f1\Editor\Unity.exe
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #2

    [Package Manager] Server::Start -- Port 60108 was selected
    C:/Users/Andrew/Documents/GitHub/Team_Project/Team_Poject
    Exiting without the bug reporter. Application will terminate with return code 1C:/Users/Andrew/Documents/GitHub/Team_Project/Team_Poject
    Loading GUID <-> Path mappings...0.000124 seconds
    Loading Asset Database...0.044781 seconds
    Audio: FMOD Profiler initialized on port 54900
    AssetDatabase consistency checks...0.030504 seconds
    Refreshing native plugins compatible for Editor in 38.22 ms, found 2 plugins.
    Preloading 0 native plugins for Editor in 0.00 ms.
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #3

    [Package Manager] Server::Start -- Port 63150 was selected
    [Package Manager] Cannot connect to Unity Package Manager local server
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #4

    [Package Manager] Server::Start -- Port 52758 was selected
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #5

    [Package Manager] Server::Start -- Port 53423 was selected
    [Package Manager] Cannot connect to Unity Package Manager local server
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #6

    [Package Manager] Server::Start -- Port 53424 was selected
    [Package Manager] Cannot connect to Unity Package Manager local server
    [Package Manager] Server::CheckExitCode -- Server stopped with exit code `1`
    [Package Manager] PackageManager Server::Start -- Process restart attempt #7

    [Package Manager] Server::Start -- Port 49323 was selected
    [Package Manager] Cannot connect to Unity Package Manager local server
    [Package Manager] Failed to start Unity Package Manager: operation timed out.
     
    agwebberley, May 6, 2019
    #1

  2. maximeb_unity

    maximeb_unity

    Unity Technologies

    Joined:
    Mar 20, 2018
    Posts:
    144
    Hi @agwebberley,

    Just to be sure, there were really no changes like a Unity update, a different user account being used, permissions/privileges of the user account changed, environment variables set/cleared/changed, antivirus/firewall updated...

    Is there a log file named upm.log next to the Editor.log? Does it seem to contain anything useful?

    Also, I couldn't help but notice that your Unity version is a bit outdated, the 2018.2 version has many patches on top of the version you used, 2018.2.21f1 being the latest for that release. You might want to try it as well. (As usual, make sure you use source control or make a backup of your project before trying a different version of Unity, for safety.)
     
    maximeb_unity, May 6, 2019
    #2

  3. agwebberley

    agwebberley

    Joined:
    Dec 4, 2018
    Posts:
    5
    There were no changes. I am working with a team of developers so updating is not an option at the moment. I don’t see upm.log. It doesn’t seem to exist. I have the latest 2018.2 version for other projects but that doesn’t work either.
     
    agwebberley, May 6, 2019
    #3

  4. maximeb_unity

    maximeb_unity

    Unity Technologies

    Joined:
    Mar 20, 2018
    Posts:
    144
    Hi @agwebberley,

    I looked at the version of the Package Manager shipped with that Unity version, and I noticed that we have fixed an issue with the logging which would cause the Package Manager to crash if it was unable to create a log file. Since you don't find a log file, I can only presume that for some reason, it's unable to do so.

    In your version, the log file should be created under 
    C:\Users\Andrew\AppData\Local\Unity
    if Unity is run with a regular user account (i.e. not a system account like LocalService or NetworkService). If that folder does not exist, or if the current user is otherwise unable to create the log file (e.g. it doesn't have the right permissions on that folder), then it could fail.

    Another possibility is that for some reason, Windows (or some security software) is refusing to let the Package Manager process start. You can verify this by checking if you can manually launch the program named 
    upm-win.exe
    located under 
    <path-to-Unity-install-directory>/Data/Resources/PackageManager/Server
    . If it properly launches, then you should see it running in the running processes displayed by the Task Manager window (which you can open by pressing the Ctrl-Shift-Esc keys together).
     
    maximeb_unity, May 6, 2019
    #4