---
title: "AppEnhancer 25.4: Troubleshooting Indexing Service Logging and Page Failures"
description: "AppEnhancer 25.4: Troubleshooting Indexing Service Logging and Page Failures"
---

[Skip to content](https://knowledgebase.metasource.com/appenhancer-25.4-troubleshooting-indexing-service-logging-and-page-failures#main-content)

[![2026 MetaSource Logo - Light Background](https://knowledgebase.metasource.com/hs-fs/hubfs/Images/Logos/2026%20MetaSource%20Logo%20-%20Light%20Background.png?width=226&height=29&name=2026%20MetaSource%20Logo%20-%20Light%20Background.png)](https://www.metasource.com/)

Open main navigation

Close main navigation

- [Go to Customer Portal](https://clientsupport.metasource.com/tickets-view)

[Go to Customer Portal](https://clientsupport.metasource.com/tickets-view?hsLang=en)

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [MetaSource Knowledge Base](https://knowledgebase.metasource.com/?hsLang=en)
2. [OpenText AppEnhancer (ApplicationXtender)](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en)

# AppEnhancer 25.4: Troubleshooting Indexing Service Logging and Page Failures

## When AppEnhancer 25.4 customers move from Xplore Full Text to IDOL Fulltext, you may see document indexing failures that are difficult to troubleshoot through the Windows Event Log alone. This article explains the current behavior, what to verify first, and how to respond when customers ask about verbose logging or page-level failure handling.

 **Symptoms**

You may hear one or more of these issues from customers:

- Documents fail during full-text indexing after the upgrade to IDOL Fulltext
- Multiple document pages fail, but the available logging is difficult to parse in Windows Event Log
- The indexing service appears to stop processing after the first error instead of reporting every failed page
- Teams want verbose logging written to a file to make troubleshooting easier

 Environment

- Product: OpenText AppEnhancer
- Version: 25.4
- Area affected: Indexing service / full-text processing

**Current Guidance**

Based on the support case, there is **no known pre-check option** to validate documents before processing. Troubleshooting is currently somewhat hit-or-miss when problem documents contain low-quality images, blank pages, unsupported files, or other page-level issues that cause indexing to fail.

There is also **no confirmed setting** from this case that allows the indexing service to skip problem pages, treat them as blank, continue indexing the rest of the document, or log all failed pages after the first error. If a problematic page causes a failure, the result may be that the whole document is not fully searchable.

**Known Limitation**

At the time of this case, the requested behavior was not available: if the service encounters a page-level problem, it may fail the document rather than skip the bad page and continue OCR or full-text indexing on the rest.

**Enhancement Request**

An enhancement request was submitted asking for the indexing service to continue indexing usable pages even when one page fails, so part of the document can still be full-text searchable instead of failing the entire document.

- [Tungsten (Kofax)](https://knowledgebase.metasource.com/tungsten-kofax?hsLang=en#main-content)

    - [Installation and Setup](https://knowledgebase.metasource.com/tungsten-kofax?hsLang=en#installation-and-setup)
    - [Troubleshooting](https://knowledgebase.metasource.com/tungsten-kofax?hsLang=en#troubleshooting)
    - [Updates](https://knowledgebase.metasource.com/tungsten-kofax?hsLang=en#updates)
- [OpenText AppEnhancer (ApplicationXtender)](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en#main-content)

    - [Installation and Setup](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en#installation-and-setup)
    - [Basic Features](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en#basic-features)
    - [Troubleshooting](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en#troubleshooting)
    - [Updates](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en#updates)
    - [System Requirements](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en#system-requirements)
    - [Security](https://knowledgebase.metasource.com/opentext-appenhancer-applicationxtender?hsLang=en#security)
- [OpenText Intelligent Capture (Captiva)](https://knowledgebase.metasource.com/opentext-intelligent-capture-captiva?hsLang=en#main-content)

    - [Installation and Setup](https://knowledgebase.metasource.com/opentext-intelligent-capture-captiva?hsLang=en#installation-and-setup)
    - [Troubleshooting](https://knowledgebase.metasource.com/opentext-intelligent-capture-captiva?hsLang=en#troubleshooting)
- [PaperVision](https://knowledgebase.metasource.com/papervision?hsLang=en)
- [OpenText OTS (Output Transformation Server)](https://knowledgebase.metasource.com/opentext-ots-output-transformation-server?hsLang=en#main-content)

    - [OTS](https://knowledgebase.metasource.com/opentext-ots-output-transformation-server?hsLang=en#ots)
- [FileBound](https://knowledgebase.metasource.com/filebound?hsLang=en)

[![2026 MetaSource Logo - Light Background](https://knowledgebase.metasource.com/hs-fs/hubfs/Images/Logos/2026%20MetaSource%20Logo%20-%20Light%20Background.png?width=226&height=29&name=2026%20MetaSource%20Logo%20-%20Light%20Background.png "2026 MetaSource Logo - Light Background")](http://www.metasource.com)

[getsupport@metasource.com](mailto:getsupport@metasource.com)

[(888) 634-7684](tel:18886347684)

<https://www.linkedin.com/company/metasource/> <https://x.com/MetaSource> <https://www.facebook.com/MetaSource/> <https://www.instagram.com/metasource/>

© 2025 MetaSource, LLC. All rights reserved.