Could not set ACL to allow access to IE EPM or Edge. about edge-diagnostics-adapter HOT 12 CLOSED

Hmmm. Honestly not sure what happened here. I believe that error code basically means it couldn't find the builtin name 'ALL APPLICATION PACKAGES' msdn. But that name should exsist on Win10 (and down to Windows 8). If you:

1. Find the proxy.dll and proxy64.dll
2. Right click on the dll and properties
3. Go to the Security panel
4. Edit
5. Add..
6. Make sure you have the location to your local machine name (and not a domain etc.)
7. Search for ALL APPLICATION PACKAGES (type it in the box)
8. Check Names this should resolve the name and underline it (if this fails we have a problem!)
9. Ok OK, OK
10. Now try it...

Fwiw and this is probably unrelated but the binaries should be somewhere local and not ran from a share.

from edge-diagnostics-adapter.

This happend to this guy cyrus-and/chrome-remote-interface#21

from edge-diagnostics-adapter.

@andysterland thanks, I'll try this ASAP.

from edge-diagnostics-adapter.

@andysterland Great, it works now!

But I had to use "TUTTI I PACCHETTI APPLICAZIONI" as my Windows is in Italian.

The error (message) persists though, I think because the adapter checks the non localized name:

ea.Trustee.ptstrName = L"ALL APPLICATION PACKAGES";

But it's just shameless speculation...

from edge-diagnostics-adapter.

@cyrus-and awesome! And thanks for looking at the code :). I must admit I don't think we ever tested on a non English machine :(. I didn't realize the name was localized though I should have known better. On the pluis side I think the fix is just to use the SID S-1-15-2-1 instead as I'm pretty sure they don't get localized :).

from edge-diagnostics-adapter.

@andysterland you're welcome!

On the pluis side I think the fix is just to use the SID S-1-15-2-1 instead as I'm pretty sure they don't get localized :).

I have no idea... but if I try to do the above with "S-1-15-2-1" it doesn't work: the name cannot be found.

Here's the list of all the possible choices that I have, maybe you might find it useful.

from edge-diagnostics-adapter.

Ah yea the SID I'll have to resolve to something in code. I think the change at:
https://github.com/Microsoft/edge-diagnostics-adapter/compare/fixIssue19?expand=1
I've uploaded an exe that isn't signed if you wanted to quickly test the fix:
https://onedrive.live.com/?id=65B2C5B13821FAB%21375901&cid=065B2C5B13821FAB
Just getting a non-English VM spun up to test it here.

from edge-diagnostics-adapter.

@andysterland unfortunately I don't have a Microsoft account so I cannot open that link, but if you find another way to provide me that file I'd be happy to give it a try.

from edge-diagnostics-adapter.

@cyrus-and sorry, it was marked as public which I guess isn't the same as anonymous. Try: https://1drv.ms/f/s!AqsfghNbLFsGlvhd9AV4QU15xSXPOA

from edge-diagnostics-adapter.

@andysterland yup the error message is gone now, here's what I get:

Edge Diagnostics Adapter
Proxy server listening on port 9222...
DEBUG MESSAGE: Attempting to attach to 64 bit tab
Client connection accepted for: /devtools/page/719BDAE6-1843-46E5-BCF3-26FD64DB947B as: 000000000001032A

from edge-diagnostics-adapter.

@cyrus-and .. and does it work? ;)

from edge-diagnostics-adapter.

@auchenberg yes it already worked after manually adding the security entities to the DLLs, I thought it was implicit. :)

Anyway yes, it also work with the original DLLs; after the execution the security entities are there.

P.S. I'm having some issues with the chrome-remote-interface but they are not related to this.
Edit: fixed in v0.12.1

from edge-diagnostics-adapter.