microsoft / microsoft/Dual-write-automations

Problem "Deploy map"

Open
#63 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
47
Forks
12
Avg merge
4d 4h
Merged PRs (30d)
3

Description

hello Max,

thanks a lot for your sofware, he is great ! (and I love the UI !)
to export a mapping, it's fine
but as soon as we want to deploy to a new environment, we have this error :
Get access token, opening Edge


2025-10-06 15:45:09: ERROR
2025-10-06 15:45:09:       System.ComponentModel.Win32Exception (5): **Accès refusé**.
2025-10-06 15:45:09:          at System.Diagnostics.Process.Kill()
2025-10-06 15:45:09:          at DWLibary.EdgeUniversal.checkKillEdgeDriver() in C:\Users\**maxhentschel**\source\repos\Dual-write-automationsv2\DWLibary\EdgeUniversal.cs:line 54
2025-10-06 15:45:09:          at DWLibary.EdgeUniversal.getToken() in C:\Users\**maxhentschel**\source\repos\Dual-write-automationsv2\DWLibary\EdgeUniversal.cs:line 87
2025-10-06 15:45:09:          at DWHelper.AppExecution.checkEdgeVersionAndRetrieveToken() in C:\Users\maxhentschel\source\repos\Dual-write-automationsv2\DualWriteHelper\AppExecution.cs:line 179
2025-10-06 15:45:09:          at DWHelper.AppExecution.run() in C:\Users\maxhentschel\source\repos\Dual-write-automationsv2\DualWriteHelper\AppExecution.cs:line 89
2025-10-06 15:45:09:       Application is shutting down...

we have tested on 2 differents PC, with latest version of DWhelper & latest .NET 9
it only worked 1 time, after that we always have the same error "access refused" with the local path of your edgeuniversal.cs

I'm not sure where is the problem here ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Deploy map flow and follow the reported stack trace in DWLibary/EdgeUniversal.cs at lines 54 and 87, then DWHelper/AppExecution.cs at lines 179 and 89. Confirm the access-denied failure occurs during Edge startup and verify that deployment completes without the error on the affected setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.