installJavascriptPackages failed UNC paths not supported

Question

Hi, I'm trying to run install and run unity on my school's computers. All the user data is stored on the network. We are limited on data as we have a satellite connection, so I am installing from the files that were downloaded to a temporary directory.

Unity opens with a gray screen. It seems like it's having trouble using the appData directory on the server.

Here is the log file: Built from '5.3/release' branch; Version is '5.3.1f1 (cc9cbbcc37b4) revision 13409467'; Using compiler version '160040219' OS: 'Windows 8.1 (6.3.0) 64bit' Language: 'en' Physical Memory: 8910 MB BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 0 Initialize mono Mono path[0] = 'C:/Program Files/Unity/Editor/Data/Managed' Mono path[1] = 'C:/Program Files/Unity/Editor/Data/Mono/lib/mono/2.0' Mono path[2] = 'C:/Program Files/Unity/Editor/Data/UnityScript' Mono config path = 'C:/Program Files/Unity/Editor/Data/Mono/etc' Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,defer=y,address=0.0.0.0:56608 InstallEditorPackages failed, output: '\\IM-SERVER\Users\Joel_Page\Application Data\Unity\Packages'

 CMD.EXE was started with the above path as the current directory.
 
 UNC paths are not supported.  Defaulting to Windows directory.
 
 npm ERR! registry error parsing json
 npm ERR! registry error parsing json
 npm ERR! Windows_NT 6.3.9600
 npm ERR! argv "C:\\Program Files\\Unity\\Editor\\Data\\Tools\\nodejs\\\\node.exe" "C:\\Program Files\\Unity\\Editor\\Data\\Tools\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "unity-editor-home-0.0.7.tgz" "unityeditor-cloud-hub-0.0.1.tgz" "--cache=./.npm" "--json"
 npm ERR! node v0.12.7
 npm ERR! npm  v3.3.3
 
 npm ERR! Unexpected token <
 npm ERR! <!doctype html>
 npm ERR! <html lang="en">
 npm ERR! <head>
 npm ERR!   <meta charset="utf-8">
 npm ERR!   <title>unityeditor-cloud-hub-0.0.1.tgz</title>
 npm ERR! 
 npm ERR!     <meta name="description" content="">
 npm ERR!     <meta name="keywords" content="">
 npm ERR!     <meta name="twitter:url" content="https://www.npmjs.com/package/unityeditor-cloud-hub-0.0.1.tgz">
 npm ERR!     <meta name="twitter:title" content="npm: unityeditor-cloud-hub-0.0.1.tgz">
 npm ERR!     <meta name="twitter:description" content="">
 npm ERR! 
 npm ERR! 
 npm ERR!   <meta http-equiv="cleartype" content="on" />
 npm ERR! 
 npm ERR!   <meta name="apple-mobile-web-app-capable" content="no">
 npm ERR!   <meta name="description" content="npm is the package manager for javascript">
 npm ERR!   <meta name="viewport" content="width=device-width,minimum-scale=1.0,initial-scale=1,user-scalable=yes">
 npm ERR! 
 npm ERR!   <link rel="apple-touch-icon" sizes="57x57" href="/static/images/touch-icons/apple-touch-icon-57x57.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="60x60" href="/static/images/touch-icons/apple-touch-icon-60x60.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="72x72" href="/static/images/touch-icons/apple-touch-icon-72x72.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="76x76" href="/static/images/touch-icons/apple-touch-icon-76x76.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="114x114" href="/static/images/touch-icons/apple-touch-icon-114x114.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="120x120" href="/static/images/touch-icons/apple-touch-icon-120x120.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="144x144" href="/static/images/touch-icons/apple-touch-icon-144x144.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="152x152" href="/static/images/touch-icons/apple-touch-icon-152x152.png">
 npm ERR!   <link rel="apple-touch-icon" sizes="180x180" href="/static/images/touch-icons/apple-touch-icon-180x180.png">
 npm ERR!   <link rel="apple-touch-startup-image" media="(device-width: 768px) and (device-height: 1024px) and (orientation: landscape) and (-webkit-device-pixel-ratio: 1)" href="/static/images/touch-icons/apple-touch-startup-image-1024x748.png">
 npm ERR!   <link rel="apple-touch-startup-image" media="(device-width: 768px) and (device-height: 1024px) and (orientation: portrait) and (-webkit-device-pixel-ratio: 2)" href="/static/images/touch-icons/apple-touch-startup-image-1536x2008.png">
 npm ERR!   <link rel="apple-touch-startup-image" media="(device-width: 768px) and (device-height: 1024px) and (orientation: landscape) and (-webkit-device-pixel-ratio: 2)" href="/static/images/touch-icons/apple-touch-startup-image-2048x1496.png">
 npm ERR!   <link rel="apple-touch-startup-image" media="(device-width: 320px) and (device-height: 480px) and (-webkit-device-pixel-ratio: 1)" href="/static/images/touch-icons/apple-touch-startup-image-320x460.png">
 npm ERR!   <link rel="apple-touch-startup-image" media="(device-width: 320px) and (device-height: 568px) and (-webkit-device-pixel-ratio: 2)" href="/static/images/touch-icons/apple-touch-startup-image-640x1096.png">
 npm ERR!   <link rel="apple-touch-startup-image" media="(device-width: 320px) and (device-height: 480px) and (-webkit-device-pixel-ratio: 2)" href="/static/images/touch-icons/apple-touch-startup-image-640x920.png">
 npm ERR!   <link rel="apple-touch-startup-image" media="(device-width: 768px) and (device-height: 1024px) and (orientation: portrait) and (-webkit-device-pixel-ratio: 1)" href="/static/images/touch-icons/apple-touch-startup-image-768x1004.png">
 npm ERR!   <link rel="icon" type="image/png" href="/static/images/touch-icons/favicon-32x32.png" sizes="32x32">
 npm ERR!   <link rel="icon" type="image/png" href="/static/images/touch-icons/favicon-230x230.png" sizes="230x230">
 npm ERR!   <link rel="icon" type="image/png" href="/static/images/touch-icons/favicon-96x96.png" sizes="96x96">
 npm ERR!   <link rel="icon" type="image/png" href="/static/images/touch-icons/android-chrome-192x192.png" sizes="192x192">
 npm ERR!   <link rel="icon" type="image/png" href="/static/images/touch-icons/coast-228x228.png" sizes="228x228">
 npm ERR!   <link rel="icon" type="image/png" href="/static/images/touch-icons/favicon-16x16.png" sizes="16x16">
 npm ERR!   <link rel="manifest" href="/static/images/touch-icons/manifest.json">
 npm ERR!   <link rel="shortcut icon" href="/static/images/touch-icons/favicon.ico">
 npm ERR!   <link rel="yandex-tableau-widget" href="/static/images/touch-icons/yandex-browser-manifest.json">
 npm ERR!   <meta property="og:image" content="https://www.npmjs.com/static/images/touch-icons/open-graph.png">
 npm ERR!   <meta name="apple-mobile-web-app-capable" content="yes">
 npm ERR!   <meta name="msapplication-TileColor" content="#cb3837">
 npm ERR!   <meta name="msapplication-TileImage" content="/static/images/touch-icons/mstile-144x144.png">
 npm ERR!   <meta name="msapplication-config" content="/static/images/touch-icons/browserconfig.xml">
 npm ERR!   <meta name="theme-color" content="#cb3837">
 npm ERR! 
 npm ERR!   <link rel="canonical" href="https://www.npmjs.com/package/unityeditor-cloud-hub-0.0.1.tgz">
 npm ERR!   <link rel="stylesheet" media="all" href="/static/css/index.8340e1bc.css">
 npm ERR!   <link rel="search" type="application/opensearchdescription+xml" href="/opensearch.xml" title="npm">
 npm ERR!   <link rel="stylesheet" href="//fonts.googleapis.com/css?family=Source+Sans+Pro:300,400,600,700">
 npm ERR!   <!--[if lt IE 9]>
 npm ERR!     <script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.2/html5shiv.min.js"></script>
 npm ERR!   <![endif]-->
 npm ERR! 
 npm ERR! 
 npm ERR!   <script src="/static/js/index.min.e41ddaf7.js"></script>
 npm ERR! 
 npm ERR! </head>
 npm ERR! 
 npm ERR! <body itemscope itemtype="http://schema.org/WebSite" data-crumb="XixSi4v3H6xH9RXqHAlUupaavb68f4R6eXRSf8TWNoi">
 npm ERR!   <meta itemprop="url" content="https://www.npmjs.com/">
 npm ERR! 
 npm ERR!     <nav>
 npm ERR!         <a href="#" id="npm-expansions" data-event-trigger="click" data-event-name="npm-expansions">node package manager</a>
 npm ERR!         <a href="/npm/on-site">npm On-Site</a>
 npm ERR!         <a href="/npm/private-packages" data-event-trigger="click" data-event-name="private-modules-nav-link">npm Private Packages</a>
 npm ERR!         <a href="/npm/open-source">npm Open Source</a>
 npm ERR!         <a href="https://docs.npmjs.com">documentation</a>
 npm ERR!         <a href="/support">support</a>
 npm ERR!     </nav>
 npm ERR! 
 npm ERR!   <header>
 npm ERR!     <div id='npm-logo'>
 npm ERR!       <a href="/"><img src="/static/images/npm-logo.svg" alt="npm logo" /></a>
 npm ERR!     </div>
 npm ERR! 
 npm ERR! 
 npm ERR!       <div id="user-info" class="anonymous">
 npm ERR!           <a href="/login"><img alt="" src="/static/images/wombat-avatar-small.png" /></a>
 npm ERR!           <ul class="single">
 npm ERR!               <li><a href="/signup">sign up</a> or <a href="/login">log in</a></li>
 npm ERR!           </ul>
 npm ERR! 
 npm ERR!       </div>
 npm ERR! 
 npm ERR! 
 npm ERR!     <form id="npm-search" action="/search" method="get" itemprop="potentialAction" itemscope itemtype="http://schema.org/SearchAction">
 npm ERR!       <meta itemprop="target" content="https://www.npmjs.com/search?q={q}">
 npm ERR!       <div id="site-search-container">
 npm ERR!           <input name="q" value="" type="search" id="site-search" placeholder="find packages" tabindex="1" autocorrect="off" autocapitalize="off" itemprop="query-input" />
 npm ERR!       </div>
 npm ERR!       <input type="submit" id="site-search-submit" />
 npm ERR!     </form>
 npm ERR! 
 npm ERR!   </header>
 npm ERR! 
 npm ERR!     <div class="container content">
 npm ERR!       <div class="container">
 npm ERR!   <hgroup>
 npm ERR!     <h1>not found</h1>
 npm ERR!     <h2>
 npm ERR!         unityeditor-cloud-hub-0.0.1.tgz will be yours. Oh yes, unityeditor-cloud-hub-0.0.1.tgz will be yours.
 npm ERR!     </h2>
 npm ERR!   </hgroup>
 npm ERR! </div>
 npm ERR! 
 npm ERR! <div class="container narrow">
 npm ERR! 
 npm ERR! <pre><code>mkdir unityeditor-cloud-hub-0.0.1.tgz
 npm ERR! cd unityeditor-cloud-hub-0.0.1.tgz
 npm ERR! npm init
 npm ERR! # work your magic…
 npm ERR! npm publish
 npm ERR! </code></pre>
 npm ERR! 
 npm ERR!   <img class="roomy-and-flexible" src="/static/images/not-found.png">
 npm ERR! </div>
 npm ERR! 
 npm ERR!     </div>
 npm ERR! 
 npm ERR!   <footer>
 npm ERR! 
 npm ERR!     <div class="container">
 npm ERR! 
 npm ERR! 
 npm ERR!         <ul class="columnar">
 npm ERR!           <li>
 npm ERR!             <h3>You Need Help</h3>
 npm ERR!             <ul class="links">
 npm ERR!               <li><a href="https://docs.npmjs.com">Documentation</a></li>
 npm ERR!               <li><a href="/support">Support / Contact Us</a></li>
 npm ERR!               <li><a href="http://status.npmjs.org/">Registry Status</a></li>
 npm ERR!               <li><a href="https://github.com/npm/newww/issues">Website Issues</a></li>
 npm ERR!               <li><a href="https://github.com/npm/npm/issues">CLI Issues</a></li>
 npm ERR!               <li><a href="/security">Security</a></li>
 npm ERR!             </ul>
 npm ERR!           </li>
 npm ERR! 
 npm ERR!           <li>
 npm ERR!             <h3>About npm</h3>
 npm ERR!             <ul class="links">
 npm ERR!               <li><a href="/about">About npm, Inc</a></li>
 npm ERR!               <li><a href="/jobs">Jobs</a></li>
 npm ERR!               <li><a href="/npm-weekly">npm Weekly</a></li>
 npm ERR!               <li><a href="http://blog.npmjs.org">Blog</a></li>
 npm ERR!               <li><a href="https://twitter.com/npmjs">Twitter</a></li>
 npm ERR!               <li><a href="https://github.com/npm">GitHub</a></li>
 npm ERR!             </ul>
 npm ERR!           </li>
 npm ERR! 
 npm ERR!           <li>
 npm ERR!             <h3>Legal Stuff</h3>
 npm ERR!             <ul class="links">
 npm ERR!               <li><a href="/policies/terms">Terms of Use</a></li>
 npm ERR!               <li><a href="/policies/conduct">Code of Conduct</a></li>
 npm ERR!               <li><a href="/policies/disputes">Package Name Disputes</a></li>
 npm ERR!               <li><a href="/policies/privacy">Privacy Policy</a></li>
 npm ERR!               <li><a href="/policies/receiving-reports">Reporting Abuse</a></li>
 npm ERR!               <li><a href="/policies/">Other policies</a></li>
 npm ERR!             </ul>
 npm ERR!           </li>
 npm ERR!         </ul>
 npm ERR! 
 npm ERR! 
 npm ERR!     </div>
 npm ERR! 
 npm ERR!     <div class="container centered">
 npm ERR!       <a href="/" id="npm-loves-you">
 npm ERR!         npm loves you
 npm ERR!       </a>
 npm ERR!     </div>
 npm ERR! 
 npm ERR!   </footer>
 npm ERR!   
 npm ERR!   <script defer src="/static/js/vendor.min.76ac749e.js"></script>
 npm ERR!   <script defer async src="https://cdn.optimizely.com/js/3318080746.js"></script>
 npm ERR!   <script defer async src='//img.en25.com/i/elqCfg.min.js'></script><!-- Eloqua -->
 npm ERR! </body>
 npm ERR! </html>
 npm ERR! 
 npm ERR! <!-- pid=5756 8f45c66dfcf41ab0b94a9831fa5feb7ab10e4b39 https://www.npmjs.com www-12-west.internal.npmjs.com  -->
 npm ERR! 
 npm ERR! 
 npm ERR! If you need help, you may report this error at:
 npm ERR!     <https://github.com/npm/npm/issues>
 
 npm ERR! Please include the following file with any support request:
 npm ERR!     C:\Windows\npm-debug.log
 
 installJavascriptPackages failed
  
 (Filename: C:/buildslave/unity/build/Runtime/Utilities/Argv.cpp Line: 168)
 
 Error loading file:///%2F%2FIM-SERVER%2FUsers%2FJoel_Page%2FApplication%20Data%2FUnity%2FPackages%2Fnode_modules%2Funity-editor-home%2Fdist/index.html#/project/recent
 
  
 (Filename: C:/buildslave/unity/build/Editor/Platform/Interface/NativeWebViewWindow.cpp Line: 50)

Any ideas? Is running Unity on a server possible?

Thanks for the help!

-Joel

Answer 1

Best Answer

Answer by turndapage · Jan 28, 2016 at 09:54 AM

Update:

I tried extracting the files manually and putting them in the "Application Data/Unity/Packages/node_modules/unity-editor-home/" and ran as administrator. The editor.log file now states

 Built from '5.3/release' branch; Version is '5.3.1f1 (cc9cbbcc37b4) revision 13409467'; Using compiler version '160040219'
 OS: 'Windows 8.1  (6.3.0) 64bit' Language: 'en' Physical Memory: 8910 MB
 BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 0
 Initialize mono
 Mono path[0] = 'C:/Program Files/Unity/Editor/Data/Managed'
 Mono path[1] = 'C:/Program Files/Unity/Editor/Data/Mono/lib/mono/2.0'
 Mono path[2] = 'C:/Program Files/Unity/Editor/Data/UnityScript'
 Mono config path = 'C:/Program Files/Unity/Editor/Data/Mono/etc'
 Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,defer=y,address=0.0.0.0:56612

But still had a gray screen.

Edit: Had to extract only the home package and unity worked now!

Edit 10-31-16: To sum up some other fixes I have found. An easier way to get the correct packages extracted is to log in as the local administrator and run unity, then copy the App Data to the user account.

If you are still getting the grey screen, ensure that the user has full access to their app data folder. If all else fails, open a saved scene file. The editor should launch, but you won't be able to save changes. If you open the Open Project window and close it again, an error should appear in the console pane saying what the problem is.

Please fix this Unity!

Add comment · Show 6 · Share

jammincomedy · Sep 29, 2016 at 07:11 PM 0

Share

Can you explain what you mean by you just extracted the home package? We are having the same issue at our school. Last year, we moved the appdata folder to the H drive of students so Game $$anonymous$$aker would work correctly. Now, Unity is looking for the appdata folder on the C drive. We'd rather not have to have the program utilize the C drive with students.

The tech director tried putting the entire Unity folder in individual student H drives where the appdata folder is located. That worked for a generic student user but is still bringing up the gray screen for specific students when they log in as themselves.

In the meantime, I have my students using a generic account we created for $$anonymous$$icrosoft testing exams that requires interaction with the C drive. Students are saving to the desktop of the particular computers with that setup. But, that account will only allow Internet access to non-authenticating sites. So, students have to log out of that user when done using Unity and back into their regular accounts to access the curriculum website. It's a hassle.

Another local school has both Unity and Game $$anonymous$$aker set up on the C drive and the programs can access the C drive when students are logged in to their H drives without the students having full rights to the C drive. But, our tech director hasn't yet made contact with that school's tech director to figure out what he did. Any ideas would be greatly appreciated. Thanks.

turndapage · Oct 25, 2016 at 06:40 PM 0

Share

In Response, I have found an easier solution. Log in as the Local Ad$$anonymous$$istrator for the computer and install and start Unity. After Unity has successfully loaded a project, copy the local ad$$anonymous$$istrator Application Data Unity folder to the network account Application Data folder. Unity should then start without errors.

This is an annoying bug that hasn't been fixed for a while and should be if they want schools or universities to learn this engine.

jammincomedy · Nov 02, 2016 at 01:55 PM 0

Share

I tried opening a saved scene via the folder of a saved project but still get the gray screen. I am trying to attach a picture but it won't actually upload. Basically, I found a file with a .unity extension and chose open with...Unity. It was an assets file. Thanks again.

turndapage jammincomedy · Nov 02, 2016 at 07:15 PM 0

Share

Have you tried opening a scene file?

jammincomedy turndapage · Nov 02, 2016 at 10:45 PM 0

Share

How do I open a scene from within the project folder? Thanks again.

jammincomedy · Nov 02, 2016 at 01:56 PM 0

Share

The students also have full ad$$anonymous$$ rights to the appdata folder that is now in their profiles.

Answer 2

Answer by jammincomedy · Oct 27, 2016 at 06:48 PM

We tried that to no avail. We are getting a message that the appdata folder in the Recycle bin is corrupted and then continue to get the gray screen. The appdata folder was previously moved to the students' individual H drives before this fix was suggested. We even tried moving it back to the admin profile, opening a project in Unity when logged in as the admin, and then copying the appdata folder back to the student profile. The gray screen persists.

Add comment · Show 1 · Share

turndapage · Nov 01, 2016 at 03:48 AM 0

Share

If you are still getting the grey screen, ensure that the user has full access to their app data folder. If all else fails, open a saved scene file. The editor should launch, but you won't be able to save changes. If you open the Open Project window and close it again, an error should appear in the console pane saying what the problem is.

installJavascriptPackages failed UNC paths not supported

2 Replies

Your answer

Follow this Question

Related Questions