The “The server could not be reached or validated” error below was prompted when starting the DriveLock Enterprise service. This usually happens when the connection pooling problems are related to “connection leaks.” The application did not close its database connections correctly and consistently.
There are different ways to fix this. For my specific environment, I was having connection issues with my DriveLock Enterprise Service (DES). Please see how to Resolve Account restrictions are preventing this user from signing in: User Account Password has expired.
For me, a restart of the services as shown here did not solve my issue.
Solution: Restarted my DES server and this issue was cleared. This solution was optimal because it is a test environment. To solve this correctly, follow the steps below.
Increase Max Pool Size connection string parameter value. Another way to get extra connections is to clear one or all of the pools. (This i did by restarting the server) ;)
That’s it for fixing “The server could not be reached or validated” DriveLock error. I hope you found this blog post helpful. Be sure to leave a comment or question.