Unable to add new services in SOI with an error “Service Save Function Failed.”


Article ID: 209217


Updated On:


CA Service Operations Insight (SOI)


Error when trying to save a new service configuration

A popup windows opens with the text:

Save Service - Service Save Function Failed




The disk is 100% full and out of free space.

In this case the SQL transaction log was 82g.


Errors seen in the soimgr-debug.log:

2021-02-18 17:54:00,631 ERROR [JMS Alert SOICONNECTOR2] util.JDBCExceptionReporter.logExceptions(78)  - The transaction log for database 'SAMStore' is full due to 'LOG_BACKUP'.

2021-02-18 17:54:00,632 INFO  [JMS Alert SOICONNECTOR2] ?.?(?)  - Error creating Alert:

java.lang.Exception: Error writing com.ca.sam.manager.hibernate.Alert object. org.hibernate.exception.GenericJDBCException: could not insert: [com.ca.sam.manager.hibernate.Alert]


Release : 4.2

Component : Service Operations Insight (SOI) Manager


First we needed to make enough space to actually do anything.

We deleted some unrelated logs and moved a local SQL backup to another disk.

Once we had about 8g free on c:\

We had enough free space to actually do something.

browse to:

D:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA (your path may vary)

And we see that the SAMStore_log.ldf file is very large.

We used SQL management studio to ‘truncate’ the log file:

Open SQL Management studio and expand databases.

Highlight SAMStore and right click.

Select Tasks, select Shrink, Select Files.


In the new window, under File type, select log.

Under Shrink action, select Reorganize pages and set the Shrink file to: value at 0mb

In the screenshots, I used my lab, so the files are not that big



And validate the file size has changed in windows explorer:

D:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA (your path may vary)


Additional Information

The customer should be using a disk with enough space for the db, and they should be monitoring that disk for space issues.