- Solutions
-
- File Server: Ransomware Protection
- File Server: File Copy
- File Server: Audit File Access
- File Server: Storage growth reporting
- Licensing/Pricing
- Contact
This error often involves a kerberos authentication failure.
If you are using one of our products (PA Server Monitor for example), the problem can often be fixed by going into the Console application, to the Settings > System Settings menu, and entering the service username and password - the same ones you might have already entered in services.msc. This helps because it allows the product to capture the password (and store encrypted!) and then pass it along with the WMI or Powershell request.
If you are seeing this error on servers monitored by Satellites, the same thing (re-enter credentials) will need to be done on the affected Satellites. Note that there is a Bulk Config operation to help make this easier, "Satellites: Set Service Run As Account".
Other things to check:
This error sometimes happens and causes database connection failures. The monitoring service or Satellite will automatically restart up to once per day in an effort to fix the problem.
UPDATE: According to some forum posts, this is fixed in the Microsoft SQL Server ODBC driver versions 17.4.2 or newer. Updates can can be downloaded from Microsoft here.
Also note that starting with version 18, encryption is on by default, which might cause problems if you haven't been using encryption before. See Microsoft's note about this.
Microsoft has released a document about the problem available here: https://support.microsoft.com/en-us/topic/fix-setting-of-connection-attribute-fails-when-you-use-connection-pooling-for-the-sql-server-odbc-connection-978a4bf3-a950-1738-1633-05e8d9667e22.
Essentially, do NOT use a data source name for the connection string, but rather use an actual connection string. OR turn off connection pooling. You can turn off connection pooling by setting:
HKEY_LOCAL_MACHINE\software\ (PAServerMonitor, PAStorageMonitor or PAFileSight)
DB_ODBC_CONNECTION_POOLING = 0
The above value should be changed on the Central Server, and it will get synced to the Satellites after a little while.
After making the above change, restart the monitoring or Satellite service.
“Very very good job!”
Fabrizio B., BESTIT s.r.l., Italy