I have a customer who moved a MSSQL install from one server to another. After the server move, this error pops up at least once a day at random time:
Is there something i can do in the database connections configuration that can help?
