Environment
Security Manager 6.x
Situation
Error:
CR={8F45C665-5351-4811-BB2B-93C9E0A1C34D}, PRG={869E1A11-35DE-4F91-9D49-BF9BFAA692EE} ComputerRuleToProcessRuleGroupInsertWithPKandTime Failed Error information has 2 rows and 6 columns. Err 0: op = 0, HRESULT = 80040e2f, Description = , SQL Native = 3641, SQL Description = 01000, Method Name = ComputerRuleToProcessRuleGroupInsertWithPKandTimeErr 1: op = 0, HRESULT = 80040e2f, DEscription = , SQL native = 547, SQL description = 23000, Method name = ComputerRuleToProcessRuleGroupInsertWithPKandTimeFound 2 errors, 0 were collisions.
or
CR={47D30E70-F72F-4229-BD97-B79B7184AFF3}, PRG={869E1A11-35DE-4F91-9D49-BF9BFAA692EE} ComputerRuleToProcessRuleGroupInsertWithPKandTime Failed Error information has 2 rows and 6 columns. Err 0: op = 0, HRESULT = 80040e2f, Description = , SQL Native = 3621, SQL Description = 01000, Method Name = ComputerRuleToProcessRuleGroupInsertWithPKandTimeErr 1: op = 0, HRESULT = 80040e2f, DEscription = , SQL native = 547, SQL description = 23000, Method name = ComputerRuleToProcessRuleGroupInsertWithPKandTimeFound 2 errors, 0 were collisions.
Resolution
Always make backups of your databases before making any changes!
- Open the MS SQL Server Management Studio.
- Connection to the database engine hosting the Security Manager Onepoint Database.
- Click on New Query.
- In the query box type the following:
--
--
Use Onepoint
select * from module
where name = 'Security Manager Self-Monitoring'
--
- Check the results of your query and verify the version is 6.5.1.68.
- To get the Module installer to install the module correctly, we need to roll back the version of the module. Using the following query to do this.
- If the existing version is below 6.5.1.68, you can proceed to the next step without running the following query.
--
--
Use Onepoint
update module
set version = '1.0.00.00'
where name = 'Security Manager Self-Monitoring'
--
- To verify which computer group is causing the issue you will need to lift the guid from the error you receive during the upgrade.
- This guid: CR={47D30E70-F72F-4229-BD97-B79B7184AFF3} is the default guid for the Windows 2008 Any Computer, Computer Group. The error will contain CR={GUID}. This is the guid we need.
- Once you have lifted the guid from the error, we can run a query against the Computer Rule table in the OnePoint database to be sure we've verified the correct group. See the following query:
--
--
Use Onepoint
select * from Computerrule
where idcomputerrule = '47D30E70-f72f-4229-BD97-B79B7184AFF3'
--
- Once you have verified the problematic computer group, we need to get is removed from the database. See the following steps:
- Open the Security Manager Development Console.
- Click on Computer Groups.
- Locate the Computer Group in question, right click on it, and delete it.
- Now that the customer group has been deleted, you can proceed with the module upgrade.
- Open the Security Manager Console Center.
- Click on Tasks and Launch the Module Installer.
- Update the Security Manager Self-Monitoring module.
Cause
If the expected guid does not match for certain computer groups during the upgrade of the Security Manager Self-Monitoring Module, it will cause the installation to fail with a constraint violation (Native SQL Error 547).
Additional Information
Please note that when you delete a computer group based on the error that you receive when you attempt to upgrade, it will be recreated after the module successfully installs.