Default Software Contents Download Job in error - Failed to commit

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

The "Default Software Contents Download Job" is in error

In C:\Program Files (x86)\CA\SC\CIC\logs\CIC*.log following error appears :

2026-01-14 10:22:12,108 INFO c.c.s.CCProcessingThread [prc-2] Extracting content messages from software_definition_link_0206.zip
2026-01-14 10:22:22,340 ERROR c.c.s.d.CCDBSession [prc-2] Failed to commit
2026-01-14 10:22:22,342 ERROR c.c.s.CCException [prc-2] Exception caught.  Stack Trace:
2026-01-14 10:22:22,342 ERROR c.c.s.CCException [prc-2] com.microsoft.sqlserver.jdbc.SQLServerException: The log for database 'mdb' is not available. Check the operating system error log for related error messages. Resolve any errors and restart the database.
2026-01-14 10:22:22,342 ERROR c.c.s.CCException [prc-2] com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:217)

In C:\Program Files\Microsoft SQL Server\MSSQL<version>.MSSQLSERVER\MSSQL\Log following error appears :

2026-01-14 11:46:36.00 spid17s     Error: 17053, Severity: 16, State: 1.
2026-01-14 11:46:36.00 spid17s     SQLServerLogMgr::LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.

2026-01-14 11:46:36.00 spid17s     Write error during log flush.
2026-01-14 11:46:36.00 spid17s     Error: 17053, Severity: 16, State: 1.
2026-01-14 11:46:36.00 spid17s     SQLServerLogMgr::LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
2026-01-14 11:46:36.00 spid16s     Write error during log flush.

2026-01-14 11:46:36.00 spid53      The log for database 'mdb' is not available. Check the operating system error log for related error messages. Resolve any errors and restart the database.
2026-01-14 11:46:36.01 spid76      Database mdb was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.

and also

2026-01-14 11:45:43.21 Server      Long Sync IO: Scheduler 2 had 1 Sync IOs in nonpreemptive mode longer than 1000 ms

Environment

Client Automation - All Versions
Domain Manager and SQL Server installed on a Virtual Machine

Cause

The machine has some delays to read/write data from file system.

Resolution

Hardware or Virtualization Layer Issues

• On VMware or Hyper-V, ensure the virtual disk controller is PVSCSI (VMware) or SCSI (Hyper-V).
• Update firmware and multipathing drivers on storage hosts.
• Confirm the host isn’t overcommitted — high disk latency at the hypervisor level can surface as SQL “Long Sync IO.”

A reboot of the VM host could also resolve the problem.

Additional Information

See following article :
SQL Server “Long Sync IO” Warning – What It Means and How to Fix It