Pivot reports fail when emailing or posting to teamspace

jeffadkisson · 2019-10-28 13:22:16

When sending a pivot report to a teamspace or email (via the UI or scheduler), the report fails with the following stacktrace. I don't see any other posts about this. Is this a defect or can you recommend a method to correct this? The function works fine for reports that do not use the pivot function.
Thank you.

The execution of a scheduled report has failed.

Error message: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Failed to execute report

Error-Details: net.datenwerke.scheduler.service.scheduler.exceptions.JobExecutionException: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Failed to execute report

at net.datenwerke.rs.scheduler.service.scheduler.jobs.report.ReportExecuteJob.doExecute(ReportExecuteJob.java:140)
at net.datenwerke.scheduler.service.scheduler.entities.AbstractJob.execute(AbstractJob.java:184)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeJob(SchedulerTask.java:646)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:208)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:103)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Failed to execute report

at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:218)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:119)
at net.datenwerke.rs.saikupivot.service.hooker.ExportTableCubeReport.executeReport(ExportTableCubeReport.java:54)
at net.datenwerke.rs.core.service.reportmanager.engine.ReportEngine.execute(ReportEngine.java:135)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:186)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:119)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:106)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:101)
at net.datenwerke.rs.scheduler.service.scheduler.jobs.report.ReportExecuteJob.doExecute(ReportExecuteJob.java:135)
... 9 more
Caused by: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorRuntimeException: Failed to execute report

at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.doExecute(SaikuReportEngine.java:117)
at net.datenwerke.rs.core.service.reportmanager.engine.ReportEngine.execute(ReportEngine.java:150)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:186)
... 17 more
Caused by: com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot access scoped object. Either we are not currently inside an HTTP Servlet request, or you may have forgotten to apply com.google.inject.servlet.GuiceFilter as a servlet filter for this request.

at net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer.class(SaikuSessionContainer.java:15)
while locating net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer
1 error

at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.doExecute(SaikuReportEngine.java:90)
... 19 more
Caused by: com.google.inject.OutOfScopeException: Cannot access scoped object. Either we are not currently inside an HTTP Servlet request, or you may have forgotten to apply com.google.inject.servlet.GuiceFilter as a servlet filter for this request.

at com.google.inject.servlet.GuiceFilter.getContext(GuiceFilter.java:135)
at com.google.inject.servlet.GuiceFilter.getRequest(GuiceFilter.java:121)
at com.google.inject.servlet.ServletScopes$2$1.get(ServletScopes.java:114)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)

eduardo · 2019-10-28 13:32:55

Hi jeffadkisson,

what reportserver version exactly are you using (rsversion.properties) ?

Regards,
Eduardo

jeffadkisson · 2019-10-30 04:05:31

Hello - Version is RS3.1.0-6015 (2019-10-19-15-14-01) - Thanks, Jeff

eduardo · 2019-10-30 09:19:29

Hi Jeff,

we had a similar problem with 3.1.0-6010 but it is corrected in 3.1.0-6015: https://forum.reportserver.net/viewtopic.php?id=1646 , release notes: https://reportserver.net/releasenotes/RS3.1.0.html
(RS-3732 Bug OutOfScopeException error while executing scheduled jobs in some cases)

Are you completely sure that you installed the 6015 version, not the 6010 version, and that all files were completely replaced if you previously had 6010? Can you please restart tomcat? Also, please post the contents of your RS_SCHEMAINFO table.

Regards,
Eduardo

jeffadkisson · 2019-11-04 14:06:00

Hi Eduardo,
thanks for your response. I double checked and I have replaced all the files (I followed this tutorial https://reportserver.net/en/tutorials/upgrade-30/). I have replaced all the files that I was supposed to (I deleted all the old ones and copied the new ones in to make sure none of the old files remain). I went back to our logs and the version in it changed on the next tomcat startup from RS3.1.0-6010 to RS3.1.0-6015.
I looked at the table in the DB and it still shows the old version:
1 created 2019-10-11 19:45:50
2 version RS3.1.0-6010
3 schemaversion RS3.0-14

Also I have noticed that no upgrade scripts ran after the first tomcat startup like it shows in the tutorial.
I should also mention that we upgraded from the community edition to the enterprise edition - not sure if it's related or not.
Thanks for your help.

eduardo · 2019-11-04 15:04:56

Hi jeffadkisson,

your installation seems correct. The schema_info table only shows the upgrades where the schema (db) has been changed, so it is normal that you have RS3.1.0-6010. Between 6010 and 6015 there were no schema changes.

Have you deleted your browser's cache completely *including temporary files*?

"When sending a pivot report to a teamspace or email (via the UI or scheduler), the report fails with the following stacktrace. I don't see any other posts about this. Is this a defect or can you recommend a method to correct this? The function works fine for reports that do not use the pivot function."

--> Does this happen *every time* you try to send a pivot report ? Or sporadic (sometimes yes, sometimes no). And the same for dynamic list reports: does this never happens during sending dynamic list reports or does it happen sporadically?

--> Can you try with a new schedule job after your double-check? Is this still happening?

"I should also mention that we upgraded from the community edition to the enterprise edition - not sure if it's related or not."
--> But do you have the reportserverenterprise.jar inside your WEB-INF/libs, correct?

Regards,
Eduardo

jeffadkisson · 2019-11-04 16:13:56

Thanks for the clarification on the DB.
Yes I have deleted the browser's cache completely. I have tried multiple browsers (Chrome, Opera, Mozilla) on multiple machines. It fails every time and other reports succeed every time. I have not observed any randomness in it. I also checked for the jar file and it is present on my server.
I have noticed another error in the logs that appears after an execution fails.
04-Nov-2019 11:01:52.933 WARNING [ajp-nio-8009-exec-12] net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute Failed to execute report
net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorRuntimeException: Failed to execute report
at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.doExecute(SaikuReportEngine.java:117)
at net.datenwerke.rs.core.service.reportmanager.engine.ReportEngine.execute(ReportEngine.java:150)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:186)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:119)
at net.datenwerke.rs.saikupivot.service.hooker.ExportTableCubeReport.executeReport(ExportTableCubeReport.java:54)
at net.datenwerke.rs.core.service.reportmanager.engine.ReportEngine.execute(ReportEngine.java:135)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:186)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:119)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:106)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:89)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl.exportViaMail(ReportExportRpcServiceImpl.java:185)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.CGLIB$exportViaMail$1(<generated>)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8$$FastClassByGuice$$4eece8ad.invoke(<generated>)
at com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at com.google.inject.persist.jpa.JpaLocalTxnInterceptor.invoke(JpaLocalTxnInterceptor.java:66)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:109)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.exportViaMail(<generated>)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:333)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.CGLIB$processCall$7(<generated>)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8$$FastClassByGuice$$4eece8ad.invoke(<generated>)
at com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:109)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.processCall(<generated>)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:303)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.CGLIB$processCall$8(<generated>)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8$$FastClassByGuice$$4eece8ad.invoke(<generated>)
at com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:109)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.processCall(<generated>)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.CGLIB$service$21(<generated>)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8$$FastClassByGuice$$4eece8ad.invoke(<generated>)
at com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:109)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor.invoke(CatchStacktraceInterceptor.java:38)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at net.datenwerke.rs.core.server.reportexport.ReportExportRpcServiceImpl$$EnhancerByGuice$$ce7a99e8.service(<generated>)
at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)
at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)
at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)
at com.google.inject.persist.PersistFilter.doFilter(PersistFilter.java:89)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:526)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:678)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:394)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:860)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1589)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.io.EOFException: No content to map to Object due to end of input
at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2775)
at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)
at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)
at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.createQuery(SaikuReportEngine.java:133)
at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.doExecute(SaikuReportEngine.java:84)
... 95 more

eduardo · 2019-11-05 07:52:53

Hi jeffadkisson,

does this also happen if you make a *new* schedule for *another* pivot report?

Regards,
Eduardo

jeffadkisson · 2019-11-07 15:42:22

Hi Eduardo,
I've been playing with the reports for the past couple days and this is what I found out:
The email function will fail when you open the report and DON'T preview it first. If I open a report that's already setup and I click send it will fail. If I open the same report again, click Pivot/Preview, let it finish, and then click email then it will succeed. The scheduling feature doesn't work either way. I guess there is something in the preview function that "prepares" the report which doesn't occur when it is scheduled. I tried setting up other reports and the same thing occurs - it will fail if it hasn't been previewed first.
For now, we have decided to create pivot queries on the SQL server itself and just use the regular reporting function of the RS. If you have any information regarding this that would be great, but as of right now we can't spend more time on trying to get the pivot schedule to work.
Thanks for your help.

eduardo · 2019-11-07 18:05:17

Hi jeffadkisson,

thanks for testing and for this detailed error description. You are correct, now I see the errors you mention. This seems to be a bug.
I will post here when I have more information.

Regards,
Eduardo

eduardo · 2019-11-08 08:01:15

Hi jeffadkisson,

I raised tickets RS-3770 and RS-3771 for both issues.

Regards,
Eduardo

eduardo · 2019-11-11 08:05:21

Hi jeffadkisson,

RS-3770 is corrected (error when sending to email/to teamspace if preview is not activated) and will be fixed in the next reportserver versions 3.1.1 and 3.1.0-LTS.

We will look into RS-3771 as well and I will keep you updated on this.

Regards,
Eduardo

eduardo · 2019-11-12 12:26:11

Hi jeffadkisson,

we corrected RS-3771 as well ( OutOfScopeException when scheduling pivot / Mondrian reports ). Both bugs will be fixed in the next reportserver versions 3.1.1 and 3.1.0-LTS.

Regards,
Eduardo

jeffadkisson · 2019-11-12 14:54:31

Hi Eduardo,
Thanks for you status report and for quickly resolving these issues. Do you know the ETA for next release of the RS?

eduardo · 2019-11-12 15:42:32

Hi Jeff,

the next 3.1.0-LTS version should be finished either by next week or in 2 weeks at the most. The LTS version is available for our support customers. As I see by your email, you are a support customer We will write you in the support portal with more information as soon as the version is available.

The 3.1.1 version, available for all, should be ready by the end of the year.

Regards,
Eduardo

eduardo · 2019-11-29 17:39:59

Hi Jeff,

we decided to release the 3.1.0-6016 version for all users. You can download it from our homepage or from the support portal. For a list of all changes please refer to the Release Notes.

Regards,
Eduardo

jeffadkisson · 2019-11-30 14:25:30

Hi Eduardo,
thanks for letting me know about the new release. We will upgrade soon.

ReportServer Forum

#1 2019-10-28 13:22:16

Pivot reports fail when emailing or posting to teamspace

#2 2019-10-28 13:32:55

Re: Pivot reports fail when emailing or posting to teamspace

#3 2019-10-30 04:05:31

Re: Pivot reports fail when emailing or posting to teamspace

#4 2019-10-30 09:19:29

Re: Pivot reports fail when emailing or posting to teamspace

#5 2019-11-04 14:06:00

Re: Pivot reports fail when emailing or posting to teamspace

#6 2019-11-04 15:04:56

Re: Pivot reports fail when emailing or posting to teamspace

#7 2019-11-04 16:13:56

Re: Pivot reports fail when emailing or posting to teamspace

#8 2019-11-05 07:52:53

Re: Pivot reports fail when emailing or posting to teamspace

#9 2019-11-07 15:42:22

Re: Pivot reports fail when emailing or posting to teamspace

#10 2019-11-07 18:05:17

Re: Pivot reports fail when emailing or posting to teamspace

#11 2019-11-08 08:01:15

Re: Pivot reports fail when emailing or posting to teamspace

#12 2019-11-11 08:05:21

Re: Pivot reports fail when emailing or posting to teamspace

#13 2019-11-12 12:26:11

Re: Pivot reports fail when emailing or posting to teamspace

#14 2019-11-12 14:54:31

Re: Pivot reports fail when emailing or posting to teamspace

#15 2019-11-12 15:42:32

Re: Pivot reports fail when emailing or posting to teamspace

#16 2019-11-29 17:39:59

Re: Pivot reports fail when emailing or posting to teamspace

#17 2019-11-30 14:25:30

Re: Pivot reports fail when emailing or posting to teamspace

Board footer