I have a client newly upgraded to SL2015CU2. They are a single user system, running on a Windows 10 environment and using SQL Server 2012 Standard for the database platform.
Each morning, when she logs in to SL, she receives a SQL Server Message 134. However, if she restarts (as opposed to reboots) her laptop, the error does not appear when she logs in to SL.
Anyone have any suggestions on what to look for? We've tried waiting 20 minutes after starting the laptop to start SL with the same results.
Thanks in advance!
Stuart Nottingham
