Build 1707 causes PivotTableCache.Refresh() to throw protected memory error

Copper Contributor

We have a Com Add-In for Excel as part of our product, used by thousands, that has caused havoc since Version 1707 arrived, begining with build 8326.2058 and still a problem with build 8326.2087 

 

We have used this code untouched for a few years without fail, and works thru build 8229.2103 (last build of Version 1706)

 

For now a rollback satisfies customers, but it prevents anybody from using our demo product, as we can find no workaround.

 

The issue:

In short we declare/load/change variables to contain sql statements which change upon user choices, etc. and run thru a connection string "OLEDB;DSN=QQubeUser"


When we now run this command:
oInteropPivotTableCache.Refresh()

We get this error:

System.Reflection.TargetInvocationException occurred
  HResult=-2146232828
  Message=Exception has been thrown by the target of an invocation.
  Source=mscorlib
  StackTrace:
       at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
       at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
  InnerException:
       HResult=-2147467261
       Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
       InnerException:
System.AccessViolationException occurred
  HResult=-2147467261
  Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
  Source=mscorlib
  StackTrace:
       at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
  InnerException:

We saw another post that you guys fixed for 1707, and it may be relevant: https://techcommunity.microsoft.com/t5/Get-and-Transform-Data/Analysis-Services-connector-ruined-in-...    You fixed their issue in build 8326.2073 but it didn't fix our situation (again through build 8326.2087)

 

Can you please advise on what we can do to get this bug fixed?  This is is very painful for our business, and the second bug affecting our business in the last several months. (and yes we just survived Hurrican Harvey in Houston).

 

 

 

 

 

0 Replies