DA Error

[Sortid]

We are running 2007 SP6.  An admin user went through Discovery Accelerator and deleted a lot of cases, highlighting 20 at a time and deleting a total of about 600.  Afterwards, he can no longer review results of cases.  He can create new cases, do searches, view results of the search and accept them, but when it comes time to review results of a case, the error below occurs.  Only he is affected by this.

Exception of type 'System.Web.HttpUnhandledException' was thrown. -

Missing first row in the

Dataset 'KVS.Accelerator.Search.SearchesDS'

of 'KVS.Accelerator.Web.BO.BO_Search'

Any ideas how to fix this?

Thanks.

[TonySterling]

You could try this:

1.Within IIS,locate the webctrl_client folder listed under Default Web Site

2. Right Click on webctrl_client and select Permissions

3. Ensure that Authenticated User's has full control set.

4. If Authenticated User's does not exist on the Security Tab add the account and give it Full Control.

5. Also then locate the EVBADiscovery site right click on this and choose properties.

6. Select Directory Security then select edit under the Authentication and Access control section

7. Ensure that Integrated Windows Authentication tick box is checked.

8. Ok and Apply

9. Restart IIS

10. Retest the search

This technote has your exact error:

Article URL http://www.symantec.com/docs/TECH65702

[Sortid]

Thanks Tony, that's the error I'm getting (I did do a search but didn't see this).  I ran through adding Authenticated users and confirming Windows Authentication but alas this did not fix the problem.  It's only for this one person which is strange.  Any other ideas?

Thanks.

[TonySterling]

Sorry for the delayed response, do you still have the issue?

If yes, I would suggest opening a case and having a tech take a look first hand.  I have not run across this before.

Regards,

Tony

[Kenneth_Adams · Accepted solution]

How did you get along with this issue?  Did you open a support case for it?  If you did, has it been resolved yet?

When deleting a Case in DA, the deletion first marks the case as 'To Be Deleted' to set off the rest of the processing.  The first thing you should notice is that the case is no longer displayed.  What happens next is all behind the scenes on the SQL Server hosting the DA Customer's database.  The database tables are scanned for any searches and exports or productions associated with the case.  Any searches found have their hits removed from the database (both accepted and pending acceptance searches).  The permissions to the case are also changed as nobody needs access to the deleted case any longer.

When a case with millions of hits is deleted, the SQL processing can take from minutest to hours to complete (depending on server resources and load).  If any deleted cases have legal hold enabled, they will take longer to complete as the holds must be removed first.  When 600 cases are deleted within a small time frame, the SQL Server can become overloaded with work to do.

Now, add in the fact that the permissions to cases are changing for the account that deleted those cases and you've got a condition where delays and failures to communicate properly can occur for that account (and any other account that had permissions to those cases).

If you don't have the issue resolved yet, you may need to stop the Enterprise Vault Accelerator Manager Service (EVAMS) and perform our recommended database maintenance (in order, backup the db, backup and truncate its transaction log, shrink the db, update the statistics and rebuild the table indexes).  Remember that deleting a case is removing data from the database, so shrinking the database can recover disk space.  There is no guarantee the db maintenance will resolve the issue, but it could help obtain the resolution.