I have below happening frequently. According to SQL DBA's, nothing wrong on SQL servers.. Does anyone know where the timeout mentioned is set? I'd like to up that a bit.
A transient error is preventing the execution of a SQL command. Enterprise Vault will try to run the command again.
Command: 'EVSqlCommand: DB: Data Source=server\instance,port;Initial Catalog=EVVSvaultstore;Integrated Security=True;Connect Timeout=180 - Command: uspu_RollbackCommittedWork'
Attempt: 1 of 40.
Last Error: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Solved! Go to Solution.
@GertjanA - I'm seeing these events in other 12.5.2 environments as well. I did come across an article stating this comes up during EV indexing processing and that it would be fixed in a later version?
We opened a case (210121-001034).
The indexing Engine changed. The article however describes some Stored Procedures causing this. One of the reasons I believe we are seeing this now is that we enabled Storage Expiry, and are expiring millions of items currently.
That last statement - 'it's fixed when it's fixed' :)
I am pretty sure EV engineering is aware of this, and the possible issues it causes, and are working on getting it fixed. I expect 12.5.3 (and/or 14.1) to be ready end of Q1, ealry Q2, and we'll apply 12.5.3 then.
the fix is programmatic to the stored procedures shipped with the product. best to upgrade to ensure support-ability and upgrade ability in the future. The good news is you have a great reason to upgrade.....