There is an authentication problem in Win 10 Insiders preview build 10.0.17035.1000. When I try to open Device Portal from Win 10 IoT Dashboard, Device Portal cannot recognize the set up password.
When I run PowerShell as admin and execute the command "Enter-PSSession –ComputerName xx.xxx.xx.xx–Credential xx.xxx.xx.xx\Administrator", the authentication again fails with the message: "Enter-PSSession : Connecting to remote server xx.xxx.xx.xx failed with the following error message : Access is denied...."
I just verified that the Win 10 IoT Core build 10.0.16299.15 does not have this problem. But, unfortunately it does not have the updates in the Insiders Preview build 10.0.17035.1000 I need to correctly run my application.
Please advise me how to solve this problem.
This is a known issue and is under investigation. The same issue has been posted in MSDN. If there is further update, i will let you know.
Related
I am able to get into SharePoint site using browser but not able to connect it using SSIS ODATA Connector. I have admin rights in that site. We have multiple imports successfully running using same SharePoint Server right now. Using SSDT2012. I tried another site successfully to confirm I don't have issue with SSDT. Any idea what I am missing.
Error msg:
TITLE: OData Connection Manager Editor
Test connection failed
ADDITIONAL INFORMATION:
The remote server returned an error: (401) Unauthorized. (System)
The logon attempt failed (System)
BUTTONS:
OK
What is the Service Document Location URL, you are giving in your case? Here is mine which works well.
Are you using basic authentication or Windows authentication?
If the former, double and triple-check that your userid and password are correct, and that the credentials have the proper access.
If the latter, check to see what user the package is running as. Also, I've found that when using Windows Authentication, you have to go back and double check what the Basic Authentication settings are, and zero them out before going back to Windows Authentication. It sounds crazy, but sometimes it works.
I am trying to setup openshift on ubuntu. When i ran rhc setup, asked for username and password, it throws username and password error message. I logged in using the github username. Please let me know.
Thanks
The rhc program is for the old OpenShift 2 and not the newer OpenShift 3 which is currently in developer preview for online and which it sounds like you are trying to use.
If you want the newer OpenShift version, ignore all documentation you find that talks about rhc. The command line client for OpenShift 3 is oc. Even when you use it, for the developer preview, the oc login doesn't take the login/password for GitHub. Instead you need to login into the web console after having logged into GitHub. You can then get access to a token you use to login from the command line.
For general usage of OpenShift 3, I would suggest perhaps you start out reading the free eBook at:
https://www.openshift.com/promotions/for-developers.html
Just ignore the bits about local VM and use the online developer preview version instead and take note of what I say above about how login works, as is different to what the book describes when using the VM.
General documentation for OpenShift 3 can be found at:
https://docs.openshift.com/online/welcome/index.html
When I try to sideload my Outlook add-in, created based on the last Ignite session by Andrew Salamatov, I get following error when I add the add-in from a URL (https://bulkpermissiondemo.azurewebsites.net/manifest-bulkpermission.xml): "The app can't be installed. This app isn't supported by the version of Exchange Server that your account connects to."
any idea what I'm doing wrong?
Thanks :-)
We’ve tried installing the manifest provided in the link but were unable to reproduce the error listed in the original post on recent builds. Could you try installing the manifest again and see if the same error occurs? If so, would you be willing to provide the email address for the account you are trying to install the add-in to? Then we can take a look at the server logs to see what the issue might be.
When I try to deploy a windows 10 app using remote debugger, I get this error "DEP0100 - deployment failed due to a developer licensing issue windows 10 while trying to remote a windows store app."
From what I understand, there is no concept of windows developer licensing in windows 10, all I have to do is to enable developer mode from settings.
I have still tried to renew developer license using powershell.
Is there any solution for this issue?
PS. Remote debugging was working earlier, it suddenly started giving this error.
Edit: This is happening only when remote debugger is running as a service.
This may seem like a really dumb solution, but I had the same issue and couldn't find what's wrong, until I enabled developer mode and it all worked.
To enable developer mode on Windows 10:
Click Start
Type "For Developers Settings"
Switch to "Developer Mode"
Not sure about this, but make sure the account you're using to run the service is allowed to do developer stuff on your machine.
Here's what I would do:
Generate an account on the machine with admin rights (e.g.
"myadminuser")
Log in as "myadminuser" and enable developer mode for
that account on the machine. (You might have to provide a Microsoft
account here) This will allow the account to install apps.
Configure the service to run with user "myadminuser".
I didn't try this, but this should work.
I have made an app for Windows Store Apps that needs the user to log in to facebook for it to make sense. I use the Authenticaiton Broker and it pops up as the first ting when the app launches.
When i run the developer tools WACK tool , it fails :
Error Found: The crashes and hangs test detected the following errors:
Application 20055S-Innovations.FacebookFanApp_1.0.0.6_neutral__z1vybpgpdtf9j was detected by Windows Error Reporting and experienced a crash or hang.
I dont know if thats related to it using the authentication broker ? Because if I run it myself it works fine and I just login and the app works.