Hololens Emulator app zzz - hololens

I have been following several tutorials from Microsoft on the Hololens, from the real basic 100 ( creating a Cube ) to the 101E.
However when deploying to the Hololens it doesn't troughs a error, all succeed, but when starting the App it shows a white screen and then zzz with a Moon "emoticon".
The only error i'm getting is the one attached. However developer license is active. And i also renewed it, but is that related? Don't know.
Log file:
>
3>------ Deploy started: Project: Origami, Configuration: Release x86 ------
3>Deploying to Phone Internal Storage...
3>Creating a new clean layout...
3>Copying files: Total 48 mb to layout...
3>Checking whether required frameworks are installed...
3>Framework: Microsoft.VCLibs.140.00/x86, app package version 14.0.24123.0 is not currently installed.
3>Framework: Microsoft.NET.CoreRuntime.1.0/x86, app package version 1.0.23819.0 is not currently installed.
3>Framework: Microsoft.VCLibs.140.00/x86, app package version 14.0.24123.0 is not currently installed.
3>Installing missing frameworks...
3>Registering the application to run from layout...
3>Deployment complete (0:00:05,557). Full package name: "Origami_1.0.0.0_x86__sx6pycx103f58"
========== Build: 2 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

There are several scenarios which produce this error. Here are a few ways, from my expetience, that may solve this issue:
In the Package.appxmanifest, find the line specifying TargetDeviceFamily and change Name="Windows.Universal" to Name="Windows.Holographic" and MaxVersionTested="10.0.10240.0" to MaxVersionTested="10.0.10586.0".
Go to the device portal and shutdown the instance of the app if it is running.
Try uninstalling the app from the emulator before installing it.
The hololens can be quite tedious to work with at first, but once you get the hang of it, it is a wonderful technology!

Related

Azure function failed to deploy with the error ERROR_CONNECTION_TERMINATED

Issue Description
I am trying to deploy the azure function using visual studio and getting the error: Web deployment task failed (Complete error logs are given below).
I have followed all the steps mentioned in the article http://techgenix.com/video-publish-azure-functions-azure-using-visual-studio-tools-azure-functions/ but still facing the issue.
Please help me as I have spent a lot of time on this issue and didn't get any solution.
Fiddler was not running when I deployed the azure function using visual studio.
Error logs
1>------ Build started: Project: TestFunction, Configuration: Release Any CPU ------
1>TestFunction -> C:\Repo\TestFunction\TestFunction\bin\Release\net461\bin\TestFunction.dll
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
Publish Started
TestFunction -> C:\Repo\TestFunction\TestFunction\bin\Release\net461\bin\TestFunction.dll
TestFunction -> C:\Repo\TestFunction\TestFunction\obj\Release\net461\PubTmp\Out\
C:\Program Files\dotnet\sdk\2.1.300-preview1-008174\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\PublishTargets\Microsoft.NET.Sdk.Publish.MSDeploy.targets(139,5): error : Web deployment task failed. (Web Deploy experienced a connection problem with the server and had to terminate the connection. Contact your server administrator if the problem persists. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CONNECTION_TERMINATED.) [C:\Repo\TestFunction\TestFunction\TestFunction.csproj]
C:\Program Files\dotnet\sdk\2.1.300-preview1-008174\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\PublishTargets\Microsoft.NET.Sdk.Publish.MSDeploy.targets(139,5): error : [C:\Repo\TestFunction\TestFunction\TestFunction.csproj]
C:\Program Files\dotnet\sdk\2.1.300-preview1-008174\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\PublishTargets\Microsoft.NET.Sdk.Publish.MSDeploy.targets(139,5): error : Web Deploy experienced a connection problem with the server and had to terminate the connection. Contact your server administrator if the problem persists. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CONNECTION_TERMINATED. [C:\Repo\TestFunction\TestFunction\TestFunction.csproj]
C:\Program Files\dotnet\sdk\2.1.300-preview1-008174\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\PublishTargets\Microsoft.NET.Sdk.Publish.MSDeploy.targets(139,5): error : Root element is missing. [C:\Repo\TestFunction\TestFunction\TestFunction.csproj]
Publish failed to deploy.

Unable to publish node.js app from VS2015 using VS publish

I’ve got a node.js project which I’m using to publish to Azure. This worked fine the first couple of times I’ve published, but now when I try and publish it just fails with no error message. The output in the Azure Service Activity window in VS2015 is simply:
Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.
And the output from the ouput/build window is:
------ Publish started: Project: node, Configuration: Release Any CPU ------
Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
I don’t really know where to start diagnosing this as there is no error message per se.
Things I’ve tried thus far:
Full Clean and/or rebuild
Deleted all folders from the BIN directory
Deleted all folders from the obj directory
Tried both debug and release configurations
Deleting the publish profile from VS and re-adding it from scratch
None of the above has made any difference
Has anyone seen this issue before or could suggest where to start diagnosing the cause?
Thanks
Do you happen to have GhostDoc installed?
Uninstalling it fixed it for me after seeing this issue.
I had the same issue, and it was due to file paths getting long more than the allowed number of characters. use this module to make your file paths shorter, and it will fix this issue
https://www.npmjs.com/package/flatten-packages

How to set Node.js Windows Universal app as startup app on Windows 10 IOT Core

I have created the sample Hello, World Node.js Windows Universal Sample from the Microsoft IOT Github page, but now I want to set this background app to start.
I know I'm supposed to use iotstartup, but what is my app name? All I see is this:
[10.10.xx.xx]: PS C:\> iotstartup list
Headed : 0ea49cba-1455-4d46-82bf-e3500f805e6b_wzgz7s44cm19c!App
Headed : 135bb3b6-419d-4692-a777-c9131bc0a419_wzgz7s44cm19c!App
Headed : DefaultApp_cw5n1h2txyewy!App
Headed : IoTCoreDefaultApp_hz258y3tkez3a!App
Headed : Windows.MiracastView_cw5n1h2txyewy!Microsoft.Windows.MiracastView
Headed : ZWaveBackgroundService_6efsg6e0hggwa!App
Headless : ZWaveBackgroundService_1.0.0.0_arm__6efsg6e0hggwa
Headless : 0ea49cba-1455-4d46-82bf-e3500f805e6b_1.0.0.0_arm__wzgz7s44cm19c
Headless : 135bb3b6-419d-4692-a777-c9131bc0a419_1.0.0.0_arm__wzgz7s44cm19c
Found an at least partial answer. When you run the app on a "Remote machine" via Visual Studio, you can see the package name in the Build output window as the Full Package Name:
1>------ Deploy started: Project: Win10DropDoorScanner, Configuration: Debug ARM ------
1>Updating the layout...
1>Copying files: Total <1 mb to layout...
1>Deployment complete (7568ms). Full package name: "413be5f8-0fdf-4d23-a0dc-94eca103ac6b_1.0.0.0_arm__wzgz7s44cm19c"
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

Error 'result::failure -9' when porting android app to BlackBerry 10

I am trying to deploy my android app from eclipse on to my blackberry Z10 running 10.0.9.422 and i am unsuccessfull at it.
Here is the actual error that i am receiving.
Failed to deploy project XXXX
Info: Sending request: Install
Info: Action: Install
Info: File size: 8659959
Info: Installing ...
Info: Processing 8659959 bytes
Info: Progress 0%...
Info: Progress 49%...
Info: Progress 50%...
Info: Progress 100%...
actual_dname::com.xxx.xxxx.testEPPwDTJahv0UbAeaecXksgI
actual_id::testEPPwDTJahv0UbAeaecXksgI
actual_version::1.0.3.0
result::failure -9
After this error, I could see the app icon on my Z10, but when i try to access it, it says' Initializing. Please wait...' and the app crashes thereafter.
What does failure -9 indicate and any idea on what's the issue/resolution might be?
Any help is greatly appreciated.
I was able to fix my problem after doing little research and finding the unsupported libraries for my app. I figured out the unsupported libraries using the apkbarVerifier tool.
My app was using com.google.android.maps package. So, I edited the android manifest file to reflect the below line.
<uses-library android:name="com.google.android.maps" android:required="false" />
After this change, even though the 'Verify apk' option from eclipse is showing me the same warnings, I was able to deploy the app to my Z10 and had it to work.
Basically, failure -9 on deployment means that the app contains an unsupported library.

Why can't Web Publish/Deploy Find my Web.config?

I've just clone OrchardCMS from codeplex, built it and tried to deploy it to my web hosting service using Visual Studio's 'Publish' command.
No files get published and the publish fails with the following error:
1>------ Publish started: Project: Orchard.Web, Configuration: Release Any CPU ------
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(2352,5): Error : Could not open Source file: Could not find a part of the path 'C:\Users\Tim\targetsite.co.uk\src\Orchard.Web\Media\web.config;Media\web.config'.
1>
========== Build: 0 succeeded, 0 failed, 5 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
I've checked the source code, and the file is there and in the correct folder. So what's this error message actually trying to tell me? What's going on here and how do I fix it?
This is a bug. It's already been reported and is being addressed now:
http://orchard.codeplex.com/workitem/19264
http://orchard.codeplex.com/workitem/19282
The second report proposes a workaround that might help you out till this get fixed.

Resources