I retrieved the windows 8 developer license on my laptop successfully. But when I tried to retrieve another one from another windows located in VirtualBox I got an error message said
[Content]
Error 0x80004005: Unspecified error
Something different on this windows 8 virtual machine:
It is running as a virtual machine.
It communicate to internet through CNTLM on my host machine (windows 7). But I had set the IE proxy, devenv.exe.config proxy as well as the PowerShell proxy.
I logged in this windows 8 with a local account while my laptop was logged as my windows account.
Can anyone give me some suggestion?
Working under a proxy I stumbled on the same error. I managed to activate VS developer license by doing the following:
1 - On Windows 8 Start search for Services (under settings)
2 - After that stop Network Location Awareness
3 - Try to activate again and you will be prompted a live ID request.
I got the solution from: http://social.msdn.microsoft.com/Forums/en-US/toolsforwinapps/thread/112c6b04-9eda-49f2-95d8-62e0a169f99e/
I commonly change networks and the auto-detect options for my proxy weren't working when I was on a network that wasn't behind a proxy. When I manually turned off the proxy settings I could then get the prompt for a live sign-on.
Related
We are encountering Kerberos and/or NTLM authentication failures in custom application packages orinally designed for Windows 7 using the WISE packaging Installer. On Windows 7 they work fine but they now fail on Windows 10. They fail both during installations on Windows 10 using the Microsoft SCCM tool, and they fail specifically when using Kerberos authentication to an SMB Share on the network durign the installation process. We can see inside the network trace that the client application fails over to NTLM from Kerberos durign the authentcation transaction. We are unsure why. We have a large scale Active Directory environment. Because the WISE package is comiled we cannot look into it. On successful Windows 7 machines, it appears the computer requires access to the Share while the package is being executed and the loggged-in user must have read and execute access on the SMB Share. We are able to access the same SMB Share using the Windows 7 system account but not when using the Windows 10 system account. Very odd! Is this a code issue inside the package? This may be important: The SMB share is using an DNS alias, not sure if this makes any difference. The real name of the host is different. When using the real name of the host instead of the alias the access issue appears to be resolved.
The network share wouldn't happen to be hosted by a non-Windows server by any chance, would it? If so, see if this article applies:
SMB file server share access is unsuccessful through DNS CNAME alias
Basically there was a change in the security model of Windows 10. Windows 10 by default won't request a Kerberos ticket for a DNS alias, but Windows 7 will. The SMB server is basically saying since you're not using my actual name (as shown by the service ticket), I won't allow the connection. Create a new SPN using the name that the successful Windows 7 machines are connecting with, but in SPN form. For example, if a Windows 7 is using something like this:
\servername.domain.com\sharename
..then find that name of the AD computer object representing the host and add a secondary SPN to that AD object like so:
HOST/servername.domain.com
I am using 2 computers and both are running fedora 23. In computer A I have installed ovirt engine 4.0 and in computer B I installed ovirt node 4.0.3 on a virtual machine manager and both the computer are in a same network.
When I login to the engine admin account using web interface, I tried to setup a host, but always gives error as install failed as shown below, any idea whats going wrong here?
Engine Host setup error picture
I thought it might be due to node storage issue, I tried to setup a node shared storage, again it gives error. Can anyone help how to setup a shared storage for node?
Node storage setup issue
in the lower panel you can see a message telling you that it failed to verify power management configuration.
You can see more messages if you'll go to the events tab.
For full details you can check the host installation log.
I have installed odoo 9 on a windows 7 machine..
All working well when i try to access like localhost:8069 or 192.168.1.11:8069
But the same dosnt work when i try to access from locally connected computers.. I am trying to access odoo from computers connected through lan..
trying to access 192.168.1.11:8069
However If I try to access Xampp Server using the ip it works well..
when I ping 192.168.1.11:8069 from any network computers it shows 'unknown host'
I am relatively new to this kind of network config thing.. Hope if anyone had similar issue and have sorted it out??
PS. Same thing happens when I install odoo on an Ubuntu 14.04 based computer..
Looking Forward to a solution.
Thanks in Advance.
VJ
There is a number of reasons that can cause this. What you are describing is a network issue and not a odoo issue. You cannot ping xxx.xxx.xxx.xxx:port number. I would start with some of the obvious tests:
Disable the firewall and anti-virus
If it is the firewall, set it up to open port 8069 and make sure that the firewall allows connections from other computers.
I'm working on a Windows Phone 8 app. I'm developing this app on a Windows 8 Pro machine. My app is successfully hitting my back-end server. I need to do some debugging though. I turned on Fiddler and noticed no traffic was being logged (even though I know that some traffic should have been logged.) I then followed the instructions found here: http://www.spikie.be/blog/post/2013/01/04/Windows-Phone-8-and-Fiddler.aspx.
Unfortunately, traffic is still not being logged. I'm not sure where else to look to fix this error. I can see that traffic in my web browser on my desktop is being logged. However, any network traffic within the emulator is NOT being logged. How can I get this resolved?
I've ensured that "Allow remote computers to connect" is checked.
I used the prefs set command with my machine name.
Thank you
See the details about how to use Fiddler with Windows Phone 8 emulator
http://blogs.msdn.com/b/wsdevsol/archive/2013/06/05/configure-the-windows-phone-8-emulator-to-work-with-fiddler.aspx
I have installed windows phone 8 SDK and tried running a simple app which embeds a WebBrowser on a page. When I try to run the app in emulator the emulator does not get internet connection. It displays an error message saying "You don't have permission to modify internal Hyper-V network adapter settings required to run the emulator". Im sure my login has admin permissions. My machine is 64bit, hyper v is enabled and Hyper v manager is running, hardware virtualization is enabled in the BIOS settings, DHCP is enabled and its connected to a wired network. I have checked all the system requirements. What ever I do it keeps on giving the same error message. I setup everything in a different machine and tried running the app in that machine. The same error message is displayed in the that machine also. Can anyone tell me how to get it working.
DHCP is enabled and its connected to a wired network
Can you run ipconfig /all on your host machine and post it here please?
seems you have problem with your DHCP or maybe multiple DHCP and conflict.
You need to add your user account as a member of the "Hyper-V Administrators" group on the machine.
Detailed steps:
Hit Windows key + Q and search for "local users and groups". Change the search scope to "Settings". Click "Edit local users and groups".
Expand the "Groups" section. Right-click on "Hyper-V Administrators" and select "Add to group".
Add your user account.
Some connection tools on the host can have negative effects when used with the emulator; I found having cisco VPN client installed on the host prevented the emulator from finding the internet. Other VPN clients may have similar side-effects. I simply uninstalled cisco (the inbuilt windows VPN is fine for what I need) and it worked perfectly.
I've also seen problems where it won't find the internet after the host has been suspended / resumed. In that scenario, it turned out to be bad network drivers. I installed a dedicated Intel NIC (rather than the on-board NIC on the motherboard) - problem solved.
Basically, Hyper-V is a bit fussy.
try refreshing the hyper-v by unchecking and then checking it again,this worked for me.
Steps:
1.control panel>>programs>>Programs and features>>turn windows features on and off>>hyper-v
2.uncheck it and restart the pc.
3.again go to control panel an check hyper-v and restart the pc again.
the try to run the emulator,should work..
another possible reason is that you did not start vs2013 as admin