"Environment is not linked, exiting" when using command line after env refresh

microsoft / Dual-write-automations

MIT License

27 stars 5 forks source link

"Environment is not linked, exiting" when using command line after env refresh #14

Closed ReneVolkmer closed 1 year ago

ReneVolkmer commented 1 year ago

After env refresh (FO SUP db refresh from PROD db, CE PROD copied to SUP CE, Reset link done manually via DW portal UI) I am getting "Environment is not linked, exiting" (please find log scr attached bellow) when starting starting mappings via command line from DevOps. When same config us used via DW helper UI, mappings started ok. Any hints what could be wrong please?

ReneVolkmer commented 1 year ago

As Max advised (many thanks again!), this issue was caused by having "https://" in -e parameter (parameter's help also mentioning "Environment without https://www"), having just env url ("myenv.sandbox.operations.dynamics.com") there solved this issue