Mehadi_Hasan
New Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: TestComplete Stuck on "Synchronization <internal>"
Thank you, I guess, I figured out the issue. In the TestComplete I used a shared azure drive as a log location. I think the concurrent access of the same location from different agents caused the forced shutdown of the TextExecutes. And Thus raise synchronization error.3.7KViews3likes0CommentsRe: TestComplete Stuck on "Synchronization <internal>"
Thank you for your reply. I already check the above-mentioned documentation but found no luck. Beside individual agents work fine when I run them from network suites individually. But when I run the whole network suites for some of the agents the above error logged. And this error was logged in random agents for each run. Is there anything I missed in setting or anywhere for parallel agents running. Coz the error mainly logged when network suites job starts the machine concurrently.3.7KViews0likes2CommentsTestComplete Stuck on "Synchronization <internal>"
Recently I added 20 agents in network suites for distributed testing. I checked the individual machines to verify and run a test routine from the script successfully. But when I run the whole network suites for some of the agents an error message is logged on. The message is Cannot run the remote project And those agents stopped and the other agents get stuck on "synchronizing <internal>". "Cannot run the remote project" error is completely random for the agents. TestComplete version is: 14.20 TestExecute version is 14.10 for some agents and 14.0 for some others. Can anyone please help to resolve this issue?Solved3.8KViews0likes6Comments