BAQ Error - Local Activation permission for the COM Server application

The following Query Phrase from a BAQ which worked fine in 10.0 does not work after our 10.2.300.7 upgrade last weekend. It’s preventing several dashboards from working. Any ideas on where to dig next?

If we copy the SQL statement from the BAQ and paste it directly into SQL server management studio the query executes fine without errors.

Checking the server event logs we get the following error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{E0628A3F-D40D-4C78-87B9-98733CDF11F2}
and APPID
{347F1A3E-7950-45F6-8681-43C056BDE1BD}
to the user company/user SID (S-1-5-21-992154867-1173045178-1233803906-5666) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

select   [InvcHead].[InvoiceNum] as [InvcHead_InvoiceNum],
	[InvcHead].[InvoiceDate] as [InvcHead_InvoiceDate],
	[InvcHead].[OrderNum] as [InvcHead_OrderNum],
	[InvcHead].[TermsCode] as [InvcHead_TermsCode],
	[Customer].[CustID] as [Customer_CustID],
	[ShipHead].[PackNum] as [ShipHead_PackNum],
	[InvcHead].[InvoiceBal] as [InvcHead_InvoiceBal]
from Erp.InvcHead as InvcHead
inner join Erp.Customer as Customer on 
	InvcHead.Company = Customer.Company
	and InvcHead.CustNum = Customer.CustNum
inner join Erp.ShipHead as ShipHead on 
	InvcHead.Company = ShipHead.Company
	and InvcHead.OrderNum = ShipHead.OTSOrderNum
inner join Erp.OrderHed as OrderHed on 
	InvcHead.Company = OrderHed.Company
	and InvcHead.OrderNum = OrderHed.OrderNum
	and ( OrderHed.CreditCardOrder = true  )

where (InvcHead.InvoiceBal > 0)
group by [InvcHead].[InvoiceNum],
	[InvcHead].[InvoiceDate],
	[InvcHead].[OrderNum],
	[InvcHead].[TermsCode],
	[Customer].[CustID],
	[ShipHead].[PackNum],
	[InvcHead].[InvoiceBal]
order by InvcHead.InvoiceNum

What else did you upgrade besides just Epicor? OS, SQL, .NET?

Haso - We implemented a new server in September, running Microsoft Server 2016 and MSSQL 2016. We used for testing 10.2.300 before the final upgrade, and it’s now the server for LIVE.

The old environment that 10.0.700.4 LIVE was on was Server 2012 R1(?) and SQL 2014, I think… I can double check with our sysadmin if needed. Not sure about .NET

Replying to my own post… I added Criteria of ‘Company = Blah’ to the 1st BAQ table, and it ran quickly. Forgot about that little nugget… Odd error message initially didn’t get me thinking that way.