Spreadsheet Controls

Audit and Control Management Server 2013 - "The CREATE DATABASE statement failed" error

Zakir H - MSFT — Thu, 06 Apr 2017 23:44:01 GMT

During creation of the Audit and Control Management Server (ACM) database, you may run into the following error:

An error occurred creating the database: The CREATE DATABASE statement failed. The primary file must be at least 10 MB to accommodate a copy of the model database.

This error can when the model database in SQL Server is bigger than the initial size of the ACM database. When a new database is created, SQL server uses the model database as a template. Any database created that has a size smaller than the model database can cause this error. To fix the error, use the following steps to decrease the size of the model database and shrink it:

Open SQL Server Management Studio.
In Object Explorer, connect the SQL Server Database Engine, and then expand the instance.
Expand Databases > System Database and right-click the model database, and then click Properties.
In Database Properties, select the Files page.
Decrease the value in the Initial Size (MB) column for the file to 3 MB.
Click OK.
Right-click the model database and click on Tasks > Shrink > Database.
Configure the settings and click OK.

Audit and Control Management Server 2013 - Change Tracking Types

Zakir H - MSFT — Wed, 28 Dec 2016 04:43:47 GMT

The following is a list of the different Change Tracking Types that are shown on the Change History page for a file, as well as their definitions, used in Audit and Control Management Server 2013 for comparing versions of workbooks and Access databases.

ACM Change Tracking Type	Definition

Spreadsheet
Formula	Formula modifications are changes to an existing cell formula, and additions and deletions of formulas.
Entered Value	Entered value modifications are changes to a cell value that the user enters, and additions and deletions of a cell value by the user. These cells do not contain formulas.
Calculated Value	Calculated value modifications are changes to a calculated value in a cell. This cell contains a formula that calculates the resulting value.
Structural	Structural modifications are changes to sheets, including renames, deletions, additions, and moves, as well as row and column insertions and deletions.
Named Item	Named item modifications are changes to a named item, and additions and deletions of names.
Macro	Code module modifications are changes to a VBA code module or macro item.
Data Connection	Data connection modifications are changes to an external data connection, including databases, xml, text, etc., and additions and deletions of data connections.
Key Item	Key items are ranges with values that are tracked whether or not a value in the range was changed. This only tracks values, not formulas.
Format/Protection	Format/Protection modifications are changes to cell format, cell protection, workbook protection, sheet protection, or VBA protection.
Status	Status changes occur when 1) the first version of a file is processed to start the Change History and 2) there are no changes detected in a version.

Access Database
Table	Table modifications are changes to a database table.
Query	Query modifications are changes to a database query.
Module	Module modifications are changes to a database code module.
Macro	Macro modifications are changes to a database macro.
Report	Report modifications are changes to a database report.
Form	Form modifications are changes to a database form.
Page	Page modifications are changes to a database page.
Status	Status changes occur when 1) the first version of a file is processed to start the Change History and 2) there are no changes detected in a version.

Discovery and Risk Assessment Sever 2013 - Risk Criteria Overview for Access databases

Zakir H - MSFT — Tue, 16 Aug 2016 19:29:31 GMT

The Risk criteria for Access databases in Discovery and Risk Assessment Server 2013 are listed in the table below. These settings are fixed and cannot be changed, unlike the settings for workbooks which can be modified. These Risk settings are based on Complexity only. By default, all Access database files will be classified as “material” for the Materiality rating, so the Risk category is calculated from the Complexity. Complexity Scoring

Criteria	Operator	Value	Score
Tables	>	5	5
Tables	>	10	5
Tables	>	15	5
Queries	>	5	5
Queries	>	10	5
Queries	>	15	5
Forms	>	5	5
Forms	>	10	5
Forms	>	15	5
Modules	>	0	10
Modules	>	5	10
Modules	>	10	10

So, for example, if an Access database has greater than 5 tables, it will get 5 points. If it also has greater than 10 tables, it will get an additional 5 points toward complexity. Here is the scoring system used to determine Risk based on the total Complexity score of the Access database: Risk Definition

Operator	Complexity Score	Complexity	Risk
<	5	Rudimentary	Low
<=	10	Light	Low
<=	20	Intermediate	Medium
>	20	Advanced	High

Audit and Control Management Server 2013 - Low disk space due to large Temp directory

Zakir H - MSFT — Thu, 21 Jul 2016 21:51:13 GMT

When using Microsoft Audit and Control Management Server (ACM) 2013, you may run into a situation where an application server has low disk space due to many files in the Temp directory. The Temp directory becomes large because Windows uses it as temporary storage for files that are being processed by ACM on the application server, and in some cases, the files may not be deleted after they are processed. The Temp directory location is typically in the following location:

C:\Users\\AppData\Local\Temp

A temporary solution is to delete all the files in the Temp directory. However, the same issue could reoccur in the future. If the server has another hard disk drive that has more free space, follow these steps to move the Temp directory to that drive:

1. Log on to the application server as the ACM service account.2. Stop all application services on the application server by opening ACM Service Manager and clicking the Stop All Services button. 3. Create a new directory on the second drive that will be used as the Temp directory. 4. Click Start , right-click My Computer and select Properties. 5. Click Advanced System Settings. 6. Select the Advanced tab. 7. Click Environment Variables. 8. Under User Variables for select TEMP and then click Edit. 9. In the Variable Value field, type the name of the path of the new Temp folder (for example, D:\Temp) and then click OK. 10. Repeat step 8 and 9 for the TMP variable. 11. Restart all ACM services by clicking the Start all Services button in ACM Service Manager.

Another solution is to create a batch script that will periodically delete all files from the Temp folder by scheduling it to run on a regular basis using Task Scheduler. The following is a sample command:

del /q C:\Users\\AppData\Local\Temp\*.*

Audit and Control Management Server 2013 - Reprocessing files that have thrown an error

Zakir H - MSFT — Thu, 23 Jun 2016 20:23:01 GMT

In Audit and Control Management Server (ACM) 2013, some files may not get processed due to an error. There are many different causes of processing errors, such as password protected workbooks, large or complex workbooks causing timeouts, corrupted workbooks, etc. Many of these errors can be fixed by changing a setting in ACM, such a the timeout setting, or updating workbooks, and then reprocessing the files that are already in the processing folder in error status. You can determine whether or not a file is in error status by looking for an error.txt in the processing subfolder. The text in the error.txt file gives the error message that is preventing the file from getting processed. There are 2 ways to reprocess files after fixing the issue with the file. One is to click the Acknowledge Errors button on the Site Settings > Event Log page. This reprocesses all files that are in error status in the processing folder by automatically deleting the error.txt from all processing folders. You should use this method if you have fixed the issue with many of the files. If there are a lot of files in error status but only one or a few have been fixed, then deleting the error.txt manually from those particular processing subfolders is a better option. ACM will then reprocess only those files which you remove from error status by deleting the error.txt file, instead of reprocessing all the files, since any files which are not fixed would just go back into error status, causing ACM to use up unnecessary resources.

Audit and Control Management Server 2013 and Discovery and Risk Assessment Server 2013 - Updates List

Zakir H - MSFT — Tue, 26 Apr 2016 21:51:44 GMT

The following is a list of updates for Audit and Control Management Server 2013 (ACM) and Discovery and Risk Assessment Server 2013 (DRA). The list will be updated each time a new hotfix is released for these products. You can compare the KB numbers in this list with the updates installed on your machine to make sure you have all the updates by going to Control Panel > Programs and Features > View installed updates and entering KB in the top-right search box with the format KBxxxxxxx. KB2863865 - ACM Service Pack 1 (February 25, 2014) https://support.microsoft.com/en-us/kb/2863865 KB2837623 - April 8, 2014 update for ACM https://support.microsoft.com/en-us/kb/2837623 KB2881010 - October 14, 2014 update for ACM https://support.microsoft.com/en-us/kb/2881010 KB2899503 - May 12, 2015 update for ACM https://support.microsoft.com/en-us/kb/2899503 KB2881006 - May 12, 2015 update for DRA https://support.microsoft.com/en-us/kb/2881006 KB3039793 - April 5, 2016 update for ACM https://support.microsoft.com/en-us/kb/3039793 KB3172512 - September 5, 2017 update for ACM https://support.microsoft.com/en-us/help/3172512/septebmer-5-2017-update-for-microsoft-audit-and-control-management-ser KB3172484 - September 5, 2017 update for DRA https://support.microsoft.com/en-us/help/3172484/september-5-2017-update-for-microsoft-discovery-and-risk-assessment

Database Compare - "Could not load file or assembly 'Microsoft.ReportViewer.WinForms.Version =9.0.0.0' " error

Zakir H - MSFT — Fri, 05 Feb 2016 22:44:00 GMT

When using Microsoft Database Compare, you may receive the following error:

Could not load file or assembly 'Microsoft.ReportViewer.WinForms.Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. They system cannot find the file specified."

The error may occur if Microsoft Report Viewer Redistributable 2008 is not installed. It is a prerequisite for Database Compare.

To fix the error, install Microsoft Report Viewer Redistributable 2008, available here:

https://www.microsoft.com/en-us/download/details.aspx?id=6576

Discovery and Risk Assessment Server 2013 - "An error has occurred initializing record manager: SQL exception generated..."

Zakir H - MSFT — Fri, 24 Apr 2015 20:53:00 GMT

When launching Discovery and Risk Assessment Server 2013, you may see the following error:

An unexpected error has occurred: An error has occurred initializing record manager: SQL exception generated by SELECT COUNT(*) FROM UDKDEFINITION WHERE AccountID = @accountId and UDKType = @udkType. Details: Invalid object name 'UDKDEFINITION'.

This error occurs if Audit and Control Management Server 2013 (ACM) is not installed and configured. The installation of ACM creates a database in SQL Server, which is the same database used by Discovery. As stated in the install documentation, ACM must be installed and configured before installing Discovery:

https://technet.microsoft.com/en-us/library/jj612857.aspx

Audit and Control Management Server 2013: "Exception has been thrown by the target of an invocation" error while processing files or with Spreadsheet Compare

Warren_R_Msft — Mon, 09 Mar 2015 08:43:00 GMT

Overview: Audit and Control Management Server (ACM) 2013 or Spreadsheet Compare may show this error:

Exception has been thrown by the target of an invocation.

Cause: ACM and Spreadsheet Compare use MD5 encryption which is not compliant with the National Institute of Standards and Technology (NIST) as compliant with the Federal Information Processing Standard (FIPS). If FIPS enforcement is turned on, ACM and Spreadsheet Compare will not work. The FIPS enforcement setting can be accessed in the Local Security Policy or in the registry. To view the setting in Local Security Policy, go to Administrative Tools > Local Security Policy > Security Options and look for System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing. In the example below, it shows that it is Enabled: To check the Registry setting, look for the value for: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy\Enabled If the value is 1, FIPS enforcement enabled. Workaround: To use Local Security Policy to change the setting, open Administrative Tools > Local Security Policy > Security Options, right click System cryptography: Use FIPS compliant algorithms... and select Properties. Click Disabled, and then click OK. To use the Regsitry instead, open it using regedit.exe and set this value to 0: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy\Enabled You will need to restart the Spreadsheet Processor in ACM or the Spreadsheet Compare client for the changes to take effect. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.

Audit and Control Management Server 2013 - "Index was out of range. Must be non-negative and less than the size of the collection." error

Zakir H - MSFT — Wed, 25 Feb 2015 11:46:30 GMT

You may see the following error in the SharePoint processor log file in Audit and Control Management Server 2013:

Index was out of range. Must be non-negative and less than the size of the collection.

This error may occur when a SharePoint document is currently at version of 0.1 and is checked out by a user. The SharePoint processor throws the above error when trying to process this file, and as a result, ACM is unable to track changes for this file.

To fix this error, apply the update described in this article on the ACM application server:

https://support.microsoft.com/kb/2837623