Recently we have been seeing this error:
Apex script unhandled exception by user/organization:
 
Visualforce Page: /apex/Case 
caused by: System.LimitException: Too many SOQL queries: 101
 
Class.AccountServices.rollupAssetAnnualSubscription: line 403, column 1
Trigger.AccountTrigger: line 11, column 1

The method is a rollup function designed to sum the asset values for Locations/Facilities (record type) to the parent Client (record type):

public static void rollupAssetAnnualSubscription(List<Account> accs){
      
      Set<Id> accIds = new Set<Id>();
      List<Account> accsToUpdate = new List<Account>();
      for(Account a : accs){
       if(a.ParentId != null && a.RecordTypeId == recordTypesNameMap.get(Constants.ACCOUNT_RECORD_TYPE_FACILITY).ID)
        accIds.add(a.ParentId);     
      }
      System.debug('**********accIds' + accIds);
      //A sub query has a limit of 200 records so I do not use one to query the related objects 
      //in place of a sub query I use a query of the objects based on the affected accounts
      Map<Id,Decimal> accountObjectSizeMap = new Map<Id,Decimal>();
      for(Account ob : [SELECT ParentId,Asset_Annual_Subscriptions__c FROM Account WHERE ParentId IN :accIds]){
       if(accountObjectSizeMap.containsKey(ob.ParentId)){
            Decimal i = accountObjectSizeMap.get(ob.ParentId);
            i = i + ob.Asset_Annual_Subscriptions__c;
            accountObjectSizeMap.put(ob.ParentId,i);
       }
       else
            accountObjectSizeMap.put(ob.ParentId,ob.Asset_Annual_Subscriptions__c);
      }
      System.debug('************accMap' + accountObjectSizeMap);
      //then query the accounts and set the count to the map value
      for(Account a : [SELECT Id,Locations_Asset_Annual_Subscriptions__c FROM Account WHERE Id IN :accIds]){
       a.Locations_Asset_Annual_Subscriptions__c = accountObjectSizeMap.get(a.Id);
       accsToUpdate.add(a);
      }

The issue seems to be that we now have some location record type accounts that have parents that are also locations (a recent change in protocol), so when this method tries to run it results in the SOQL query limit error. I'm trying to figure out if it's easier to just scrap this rollup entirely, or if it's possible to adjust to allow for locations to rollup to locations (or just prevent this error). 

Any info/direction would be much appreciated!

Thanks, 

Michael Pugliese