https://forge.codesys.com/forge/talk/Runtime/thread/6d00354db7/2021-12-13T23:51:44.369000ZRecent posts to Cannot log into Windows Controller2021-12-13T23:51:44.369000Z2021-12-13T23:51:44.369000Zdferbashttps://forge.codesys.com/u/dferbas/https://forge.codesys.com1b6b103a12420d3e78f51fd83930ec43e5986731

<div class="markdown_content"><p>SOLVED. Default project is generated with Control Win V3, but installed is Control Win V3 x64. Once I "updated" the device, everything started to work.</p></div>

2021-12-13T22:17:57.631000Z2021-12-13T22:17:57.631000Zdferbashttps://forge.codesys.com/u/dferbas/https://forge.codesys.com3dfacc12c76c3aee0910b30b9ab07525dd31a28c

<div class="markdown_content"><p>Probably the issue can be tight to the Codemeter licensing? Or to a fact, I already installed PLCnext Engineer on the same PC?</p></div>

2021-12-13T21:39:45.542000Z2021-12-13T21:39:45.542000Zdferbashttps://forge.codesys.com/u/dferbas/https://forge.codesys.com9feae1a4719bc0cd449ccb98ba23cabc9d1d3f75

<div class="markdown_content"><p>I get familiar with the Gateway.cfg file. Tried to add interfaces, configuration parameters via IDE, tried to delete and recreate the gateway. Still no success - Gateway not configured properly.<br/> When I scan network with License manager, the device is immediately found. I restarted PC, nothing helped.</p></div>

2021-12-13T20:05:37.010000Z2021-12-13T20:05:37.010000Zdferbashttps://forge.codesys.com/u/dferbas/https://forge.codesys.com47cc133f75b04799e0dbcf07ab240dd1d2033e4d

<div class="markdown_content"><p>I followed the <a href="https://forge.codesys.com/forge/talk/Runtime/thread/c75cd203e2/">https://forge.codesys.com/forge/talk/Runtime/thread/c75cd203e2/</a>, deleted 5 files and attempted to do the first time login again. It did not help. I forced to disable user management as per the <a href="https://faq.codesys.com/display/CDSFAQ/Device+UserManagement." rel="nofollow">https://faq.codesys.com/display/CDSFAQ/Device+UserManagement.</a></p> <p>Now I am not asked for a name and a password, but the message 'Setting the active path has been aborted.' is still there.</p> <p>Any advice what to check next?</p></div>

2021-12-13T19:12:29.678000Z2021-12-13T19:12:29.678000Zdferbashttps://forge.codesys.com/u/dferbas/https://forge.codesys.com8d8ba958047038794207a7bde158429520ffde23

<div class="markdown_content"><p>I just installed the V3.5 SP17 dev environment. Everything fine, I am able to build simple Modbus master program but when I tried to test it on a Windows controller I am unable to log into it.</p> <p>I passed the first time login procedure with user name 'Codesys' and a password. When I now try to log into the controller, I get the 'Setting the active path has been aborted' message (see attached scrshot). When I attempt to use a different name or password, I get the 'No device is responding to the scan request' message, so I assume I am matching the correct name and password.<br/> As this seems to be a new feature of the V3.5 SP17, I was unable to google out a solution. Please advise what to check and where or how to pass this.</p></div>