SQL Server 2019 Lab issue about sqlworkshops

[rgward]

Thanks for these comments. Hmmm, I never saw anything like this when I ran the lab over and over several times. The job should be run immediately not when the CPU is idle. I don't think having less cores is an issue. Can you post the output of the screen you get with these problems as the containers are run not in the background

[kevchant]

OK, laptop is being upgraded today however was still able to test. Here's a copy of the Synchronization Status when the containers are up and running but replication not completed. Let me know if you need anything more. I will try and replicate the xpstar.dll freeze later but I suspect the Docker reset may have resolved that one

[kevchant]

Here's a copy of the docker-compose output, the SQl Server Log and the SQL Server Agent history for the Publisher instance as well
dclog.txt
20190806 instance 1 SQL Agent History.log
20190806 instance 1 SQL Server log.log

[rgward]

I'm not sure about the config of our laptop but it looks like it is taking a very long time to startup the SQL Server containers. The db-init.sh script which is located in the db1 and db2 directory has a command of sleep 45s to allow both the SQL Server containers to startup. As a test can you change those to 120s to see if that gives plenty of time for the servers to startup and run the repl agent jobws?

[rgward]

Closing due to no repro and inactivity. Please reopen if you have more details and can try to change the sleep timings