- Error: "The scheduler component failed the object identified by 46971. The job associated with the object was unresponsive" in the Event Viewer when scheduling a specific Webi report off BEx query.
- Adaptive Job Server log records the following:
# A fatal error has been detected by the SAP Java Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000005b37c7a, pid=3900, tid=2404
# faulting address (tried to read): 0x0000000000000010
# JRE version: 6.0_37-b06
# Java VM: SAP Java Server VM (6.1.044 21.1-b06 Oct 31 2012 10:44:56 - 61_REL - optU - windows amd64 - 6 - bas2:182728 (mixed mode) compressed oops)
# Problematic frame:
# C [DestinationWrapper.dll+0x7c7a] (sp=0x000000000749e778) (pc=0x0000000005b37c7a)
# Failed to write core dump. Minidumps are not enabled
# If you would like to submit a bug report, please visit:
# Please save the hs_err file(s) and the written dmp file for further error analysis
# See SAP note 1500116 for further information on collecting core dumps after SAPJVM crashes
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Aborting thread stack check for pointers at address 0x000000006619f2c8 because of too many pointers (found 51 pointers).
- SAP BusinessObjects Business Intelligence Platform (BI) 4.0
EXCEPTION_ACCESS_VIOLATION, DestinationWrapper.dll , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BI-BIP-PUB , Publishing and scheduling in InfoView/BI launch pad , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.