Security Compliance
ARM Exchange Scan job fails with unspecific Error
ARM Exchange Scan Job failed without any specific error message
First published date
6/28/2019 10:13 PM
Last published date
12/18/2020 3:31 PM
Overview
When you perform an exchange scan with on premise exchange servers, the job fails with the message.
Error 1:
And in Logs you may find this kind of error (in ARM9.2.619and below)
Error 2:
In some cases, exchange online scans are stuck and you see following errors in pnjob.log
Error 3:
In another case a different was seen in pnjob log file in ARM version 19.4.0.129
Error 1:
And in Logs you may find this kind of error (in ARM9.2.619and below)
[ 61871|AVARM |pnServer |384.1| 33|ABCD\svcarm |pn.database.msSql.M…lDataBaseTransaction|190627|11:04:34.605|Error ] DataBaseHelper.HandleDataBaseSqlException(Object source, SqlException exception, String sqlCommand): System.Data.SqlClient.SqlException (0x80131904): Die CREATE UNIQUE INDEX-Anweisung wurde beendet, weil ein doppelter Schlüssel für den Objektnamen "ex._user_and_group_relations_27" und den Indexnamen "PK__user_and_group_relations_27" gefunden wurde. Der doppelte Schlüsselwert ist (900002303, 900002304). [ 61872|AVARM |pnServer |384.1| 33|ABCD\svcarm |pn.database.msSql.M…lDataBaseTransaction|190627|11:04:34.605|Error ] DataBaseHelper.HandleDataBaseSqlException(Object source, SqlException exception, String sqlCommand): -- If needed this script can be used to check if a column exists Error in Log: JobStatus.addInfo(Object source, MultiLingualString info): Fehler beim beenden des Scans - Datenbank oder Transaktionslog ist voll Checked DB Server: no Problems visible and enough Space for Transaction Log and Drive.you verified the SQL DB and ARM DB transaction log file is not full and neither it is running out of space i.e ARM DB is healthy.
Error 2:
In some cases, exchange online scans are stuck and you see following errors in pnjob.log
[ 769|ARMSERVER|pnJob |9488.1| 22|COMPANY\SVC_SolarWinds_ARM|libPowerShellConnec….PowerShellDataReady|200330| 9:57:51.448|Error ] PowerShellDataReady.ErrorDataReady(Object sender, DataAddedEventArgs e): Error while executing (Preloading PublicFolders): No active public folder mailboxes were found. This happens when no public folder mailboxes are provisioned or they are provisioned in 'HoldForMigration' mode. If you're not currently performing a migration, create a public folder mailbox. CategoryInfo: NotSpecified: (:) [Get-PublicFolder], ObjectNotFoundException
Error 3:
In another case a different was seen in pnjob log file in ARM version 19.4.0.129
[ 10293|SRV123 |pnJob |4120.1| 20|city administration\sysarm-mail|pn.exchange.scanner...ScanResultSerializer|200122| 6:07:26.602|Error ] ExchangeScanResultSerializer.saveExchangeMailBoxAccessControlList(List`1 aces): Double ACE entry found: Sid: S-1-5-21-3175823995-2929372599-3136817829-xxxx, AccessRights: 2, Deny: False, IsInherited: False, IsValid: True ConnectorScanHumster`6th ExecuteJob(Boolean isInteractive, JobConfiguration jobConfiguration, ManualResetEvent cancelEvent): END -> Failed (448757 ms) [ 10370|SRV123 |pnJob |4120.1| 1|city administration\sysarm-mail|pn.jobs.JobControlImplementation |200122| 6:08:14.632|Error ] JobStatus.addError(Object source, MultiLingualString error): Job failed without any specific error message[ 4453|SRV015 |armServer |472.1|104|ABCD\SYSTEM |pn.database.msSql.M…lDataBaseTransaction|200204|14:54:24.410|Error ] DataBaseHelper.HandleDataBaseSqlException(Object source, SqlException exception, String sqlCommand): System.Data.SqlClient.SqlException (0x80131904): String or binary data would be truncated.
Product section
Access Rights Manager
Cause
- Bug was fixed in ARM 9.2.619
- Bug as of 2019.24.2.4 - The category table does only work with 200 character lengths. If an OU string is longer the prepareData script fails.
Resolution
For Error 1:
1. Apply ARM 9.2.619 update by downloading it from your SolarWinds Customer Portal.
2. Run the scan again to verify
3. If issue persists, zip ARM logs folder and log a ticket with SolarWinds support.
For Error 2:
No active public folder mailboxes were found. This happens when no public folder mailboxes are provisioned or they are provisioned in 'HoldForMigration' mode. If you're not currently performing a migration, create a public folder mailbox or exclude the public folder scan option within exchange scan configuration.
For Error 3:
Confirmed as bug as of ARM 2019.4.2.4 and will be fixed in future version.
Please keep an eye on the latest ARM release notes page quarterly.
Workaround:
1. Update the pnServer.config.xml file located in %ProgramData%\protected-networks.com\8MAN\cfg to include the following block
3. Re-run the scan
1. Apply ARM 9.2.619 update by downloading it from your SolarWinds Customer Portal.
2. Run the scan again to verify
3. If issue persists, zip ARM logs folder and log a ticket with SolarWinds support.
For Error 2:
No active public folder mailboxes were found. This happens when no public folder mailboxes are provisioned or they are provisioned in 'HoldForMigration' mode. If you're not currently performing a migration, create a public folder mailbox or exclude the public folder scan option within exchange scan configuration.
For Error 3:
Confirmed as bug as of ARM 2019.4.2.4 and will be fixed in future version.
Please keep an eye on the latest ARM release notes page quarterly.
Workaround:
1. Update the pnServer.config.xml file located in %ProgramData%\protected-networks.com\8MAN\cfg to include the following block
<exchange> <scanBlockwise type="System.Boolean">true</scanBlockwise> <publicFolderScanDepth type="System.Int32">1000</publicFolderScanDepth> <makeMailBoxCategories type="System.Boolean">true</makeMailBoxCategories> <makeMailBoxOUCategories type="System.Boolean">false</makeMailBoxOUCategories> </exchange>2. Restart the ARM service
3. Re-run the scan