"DEP0700 : Registration of the app.." & "...windows.licensing failed ..."

Answered "DEP0700 : Registration of the app.." & "...windows.licensing failed ..."

  • Saturday, August 11, 2012 3:15 PM
     
     

    I've all of a sudden lost the capacity to create a default project (eg. blank) and run it, with both "...DEP0700 : Registration of the app..." and "...windows.licensing failed to start WSService..." errors.

    Curiously, some of my apps still deploy (hence I can continue to develop them) yet others don't. [PS Now none of them work :(]

    I've also run the Powershell cmdlet get-windowsdeveloperlicense and the expiration date is two weeks in the future, with the IsValid value returning as True.

    I've looked at every page in Google that comes up, even those which refer to the task scheduler (my xml is well formed) but to no avail.

    (For me this is around £400 pound a day loss until I can carry on.)

    Any suggestions?

        Error 1 Error : DEP0700 : Registration of the app in the layout folder "C:\Users\Anthony\Desktop\ProxyServer\ProxyServer\bin\Debug\AppX" failed. ProxyServer

    and

        Error 2 error 0xC0020012: windows.licensing failed to start WSService while installing 97D8F4A2-992E-4502-BAE2-A1A4C73F6DAC_1.0.0.0_neutral__bkvjexddj2nfj.  Try again and contact the package publisher if the problem persists. ProxyServer



All Replies

  • Sunday, August 12, 2012 9:22 AM
     
     Answered

    Hi,

    Dont worry,I too faced this problem yesterday.When I run the solution in different developer machine,it worked properly.

    Registration of app failed error usually occurs when you try to re-deploy an app with the same package ID from visual studio if it is already installed by a different user.

    Solution- change the Package Identity (open the manifest, go to the package tab and modify the identity).


    Subramanian Muthukrishnan Microsoft Student Partner iLink Systems General Secretary,Rockcity Dot Net User Group Windows 8 Trainer,DPE Program for Windows 8,Microsoft.

    • Proposed As Answer by BlakeJ Monday, August 20, 2012 11:13 PM
    • Marked As Answer by XQuirrel Sunday, October 21, 2012 6:26 PM
    •  
  • Friday, January 11, 2013 11:20 AM
     
     
    I agree with Subramanian. Another option is to just restart your system. Though not an ideal solution, it works.