000029853 - Unable to save records warning in RSA Archer: An unexpected error occurred while calculating field values for this record.  Your previously stored field values, if any, have been retained for this record.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on May 16, 2018
Version 11Show Document
  • View in full screen mode

Article Content

Article Number000029853
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
IssueThe following error message is displayed:
 
Warning: An unexpected error occurred while calculating field values for this record.  Your previously stored field values, if any, have been retained for this record.  Please contact your Archer administrator for assistance.



User-added image
 

The Archer log files that have w3wp in the file name ( e. g., w3wp.20171207 - 2.xml, where the file name is a time stamp of when the error occurred) will have the following messages around the time of the warning:


<Message>The specified network name is no longer available</Message>



<Message>An unexpected error occurred while calculating field values for this record.  Your previously stored field values, if any, have been retained for this record.  Please contact your Archer administrator for assistance.</Message>



<Message>A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)  SQL statement: usp_get_object_content_numeric @userToken = …..


CauseThe Archer web server is unable to communicate with the SQL server or file repository.  Most likely, Windows is having a system issue like low resources and the errors/warnings are the side effects.  The Windows event logs may contain additional information.
ResolutionReboot the Archer web server that is experiencing the issue so that Windows can recover from itself.  If there are multiple web servers, the exception in the Archer log files will provide the machine name in the <Computer> XML element.

If a reboot does not resolve the problem, resetting the Services Account password in the Archer Control Panel has also proved to resolve the issue.

It was also found the following configurations on the database can resolve the issues as well:

1. Adjust degree of parallelism to 1. 
Microsoft SQL Server Management Studio -> <server name> -> Right click and select Properties -> Advanced tab -> Parallelism section -> Set "Max. Degree of Parallelism" to 1

2. Setting database autogrowth appropriately. 

Microsoft SQL Server Management Studio -> <server name> -> Databases -> <database> -> Right click and select properties -> Files tab -> Database Files. For each of the files, select "Autogrowth / Maxisize" and set values according. Example:
   For File Type of "Rows Data": File Growth -> In Megabytes, select 64MB; Maximum File Size, select Unlimited
   For File Type of "Log": File Growth -> In Megabytes, select 64MB; Maximum File size, select 2097152

3. Setting compatibility level according to the SQL server version

Microsoft SQL Server Management Studio -> <server name> -> Databases -> <database> -> Right click and select properties -> go to "Options" tab -> Compatibility level. Example:
   SQL Server 2012 = 110
   SQL Server 2014 = 120
   SQL Server 2016 = 130

Attachments

    Outcomes