Skip to main content
K
keith_6356
Participant
August 12, 2025
Answered

Cfindex not indexing .docx word documents files

  • August 12, 2025
  • 3 replies
  • 5120 views

On Thursday, the error below began appearing after the last 2023 coldfusion update on my cfindex code that is atleast 10 years old. I found removing the .dot file extension from my extensions list stopped the error from occurring. However, .docx files will not index now.

 

I tried to uninstall the update 15, although this did not solve the error or the indexing issue 

 

Message

com.zaxxer.sparsebits.SparseBitSet not found by poi-5.4.1 [36]

StackTrace

java.lang.ClassNotFoundException: com.zaxxer.sparsebits.SparseBitSet not found by poi-5.4.1 [36] at org.apache.poi.xslf.usermodel.XSLFSheet.<init>(XSLFSheet.java:89) at org.apache.poi.xslf.usermodel.XSLFSlideMaster.<init>(XSLFSlideMaster.java:64) at org.apache.poi.ooxml.POIXMLFactory.createDocumentPart(POIXMLFactory.java:61) at org.apache.poi.ooxml.POIXMLDocumentPart.read(POIXMLDocumentPart.java:671) at org.apache.poi.ooxml.POIXMLDocument.load(POIXMLDocument.java:165) at org.apache.poi.xslf.usermodel.XMLSlideShow.<init>(XMLSlideShow.java:126) at coldfusion.tagext.search.MSDocument.readPPTX(MSDocument.java:206) at coldfusion.tagext.search.SolrUtils.getSolrDocument(SolrUtils.java:817) at coldfusion.tagext.search.SolrUtils.addDocument(SolrUtils.java:1439) at coldfusion.tagext.search.IndexTag.doUpdate(IndexTag.java:683) at coldfusion.tagext.search.IndexTag.doStartTag(IndexTag.java:352) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:5083) at cffile_index_intranet2ecfm1052529286.runPage(D:\tasks\file_index_intranet.cfm:38) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:251) at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:749) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:578) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:613) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:43) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:162) at coldfusion.filter.IpFilter.invoke(IpFilter.java:45) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:97) at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:81) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:60) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62) at coldfusion.CfmServlet.service(CfmServlet.java:231) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:311) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:46) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:762) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359) at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:447) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:935) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1826) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1189) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:658) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) at java.base/java.lang.Thread.run(Thread.java:833)

    Correct answer Charlie Arehart

    After restarting the server, getting this error again will all six downgraded one version, 

     

    void org.apache.xmlbeans.XmlOptions.put(java.lang.Object)' null


    Keith, please now try to see if that remaining problem goes away with stopping cf, deleting the felix-cache folder (in cfusion/bin), then restarting cf. 

    3 replies

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    August 18, 2025

    To help those who may find this thread (such as if searching brings them here), I want to offer a summary. There was the initial problem reported, then others discovered. It's a very long thread.

     

    • First, what Keith reported originally was that as of the July 2025 CF updates (in his case, of cf2023), his use of cfindex would no longer work for .docx files
    • He also reported that uninstalling that July update did NOT resolve the problem
    • For the first couple of days we pursued a couple of lines of consideration, including whether it may be due to an error in the update process
    • But I later confirmed not only that I could recreate the problem, but that it was true also for those on CF2025 and CF2021 who applied the July Update. I also filed an Adobe bug report
    • BKBK then proposed downgrading the search package, which proved to solve the problem of .docx files not being indexed
    • But Keith later reported that he now found also .xlsx files would not index
    • I proposed he downgrade the spreadsheet package. He reported at first that didn't work, but then I reminded him to clear the felix-cache, and then he reported now it worked:  he could now use cfindex to process .docx and .xlsx files, along with the others that had been working

     

    While that takes care of his cfindex problems (and it would work for those who apply the July update and then uninstall it), it still didn't explain why uninstalling the July update left things in this seemingly broken state.

     

    And for that I had (in the midst of all the dozens of replies) also identified and reported here a different problem that expands WELL BEYOND this one matter of cfindex.  Indeed, it can explain many, many problems that some (not all) people have had with recent updates and unusual package management problems.  It has to do with what I've documented is a seeming misconfiguration in the bundlesdependency.json file which is downloaded from Adobe when one performs a CF update (or CF package updates).  For now, check out that message I just linked to. I will eventually create a new bug report (at tracker.adobe.com).

     

    For now, I have updated that other bug report (about this cfindex problem) to also summarize both the workarounds and note this new, different (but related) problem.  So while Keith's original problem seems resolved, for now, this really is just the start of a new journey related to this other issue. I think we will want to create a new thread on that, and let this one close. Maybe I'll do that after I create the Adobe bug report. I'll also do a blog post, as that new info seems important news to share well beyond this one forum thread on cfindex.

     

    But I hope this summary of things helps put a nice bow on this one, for now. If I missed or forgot anything, let me know. 

    /Charlie (troubleshooter, carehart. org)
      Charlie Arehart
      Community Expert
      Charlie ArehartCommunity Expert
      Community Expert
      August 14, 2025

      Keith, I realize you may suspect still this is some bug in cf, but I still would contend you should confirm if there was not some failure in the update process.

       

      I'd raised multiple diagnostic questions in my first reply.  You've still not answered 2b and 2c. Please take time to do that, as it seems you're not getting to resolution with the other back and forth you guys have been having since then.

       

      I have more for you/us to consider if that doesn't find the problem. Let's go one step at a time. 

      /Charlie (troubleshooter, carehart. org)
      K
      keithm99725152
      Participating Frequently
      August 14, 2025

      2) And if "that didn't help", please then confirm for us a) are you doing the update within the CF Admin or via the command line (and the "java -jar" approach or using the cfpm tool)?

      Answer: update within the CF Admin

       

      Also b) what is the value in your CF Admin for the "packages url" (available via the the "settings" tab on the "package manager" page, where you can see CF updates). I can explain later, if needed, why I ask those questions.

       

      Answer: https://www.adobe.com/go/cf2023_packages

      BKBK
      Community Expert
      BKBKCommunity Expert
      Community Expert
      August 15, 2025
      @Charlie Arehart wrote:

      What I have NOT yet confirmed is whether it happened with earlier updates or not. I presume you're feeling it WAS working before you did update 15 of 2023, right? You say it was "working for 10 years", but it's not clear a) what update you were on before this and b) whether you or anyone there had definitly run that code while on some that update.)  It might help to confirm for us.

       

      I know the indexing was functioning correctly prior to the update. I have an application that compares directory files to indexed files daily. Missing indexed files generate a ticket in our ticketing system for my review. This ticket was generated the day after the update installation.

       


      quote

      I know the indexing was functioning correctly prior to the update. I have an application that compares directory files to indexed files daily. Missing indexed files generate a ticket in our ticketing system for my review. This ticket was generated the day after the update installation.

       


      By @keith_6356

       

      From your description of when the error occurred and from researching the POI namespace error online, I think it is caused by the library xmlbeans-5.3.0.jar. Update 15 introduced this new XmlBean library. The version in Update 14 and Update 13 is xmlbeans-3.1.0.jar.

       

      So I assume that the error does not occur with  xmlbeans-3.1.0.jar. But your installation may now be using xmlbeans-5.3.0.jar instead. It would have been imported when you installed Update 15, but remained in your installation when you reverted to Update 13 or 14. This idea is the basis for a workaround.

       

      Possible workaround:

      1.  Open the ColdFusion Administrator and go to the page Package Manager > Packages > Installed Packages.
      2.  Click on the search package. You should then see the settings for the Search package. Confirm that xmlbeans-5.3.0.jar is in the Required Jars list. Our idea is that that is the cause of the problem.
      3.  In the Available Versions dropdown, select the previous version and click on the Downgrade button. Click on OK to accept the change.
      4.  Return to the page Installed Packages. You will see a red flag, symbolizing the downgraded package. Click once again on the search package. You should now see xmlbeans-3.1.0.jar in the Required Jars list.
      5.  Restart ColdFusion.
      6.  Test to see whether cfindex works as before.
      Charlie Arehart
      Community Expert
      Charlie ArehartCommunity Expert
      Community Expert
      August 12, 2025

      Keith, I'm unaware of that being a known issue with update 15...but then again you found that in uninstalling that the problem remains. So the issue may or may not be about the specific "update" but rather about something amiss during your update process. I will elaborate. (Maybe someone else may know something about this .docx matter if it's a known one.)

       

      1) First, though, can you just stop CF, delete the cfusion/bin/felix-cache folder, then start CF and test again? That has been a workaround for many recent problms people have experienced after an update.  If that helps while you are on u14, THEN try going to u15 and after that update is done, REPEAT THAT STEP of deleting the felix-cache.  For now, don't ask about it or contemplate whether it could/should help. 🙂 FWIW it's mentioned in some of the update technotes as a thing to do to solve "known issues".

       

      If you'll just please try it and let us know how it goes, we can go to another step if it does NOT work.

       

      2) And if "that didn't help", please then confirm for us a) are you doing the update within the CF Admin or via the command line (and the "java -jar" approach or using the cfpm tool)? Also b) what is the value in your CF Admin for the "packages url" (available via the the "settings" tab on the "package manager" page, where you can see CF updates). I can explain later, if needed, why I ask those questions.

      Finally, c) did you confirm in your update log that there was a count of 0 for "fatalerrors" and "nonfatalerrors"? I elaborate on that last point in a post here. BTW, that log is created both for an install AND for an uninstall of any CF update.

       

      There's still more I and others could share, but let's see how things go. Hope something above here helps you.

      /Charlie (troubleshooter, carehart. org)
      K
      keithm99725152
      Participating Frequently
      August 13, 2025

      I googled this error and found posable solutions, In my test environment i tried

      1.  Deleting the cfusion/bin/felix-cache folder, then start CF and testing again 
      2. Deleting the ColdFusion2023\cfusion\bin\jvm.config, then start CF and testing again 
      3.  adding JVM Arguments

       

      Refresh are being being done with cfindex command using a path in .cfm files with CF admin scheduled tasks

       

      There are no errors in the log, it seems it is skipping over the files as if there were not included in the extensions.

       

       

      Charlie Arehart
      Community Expert
      Charlie ArehartCommunity Expert
      Community Expert
      August 13, 2025

      Please consider and reply to  point 2 in my initial reply here.

       

      Also,. If you are saying you found other online discussions of your specific issue, please share links to any in case it could help others here, either facing or helping with this problem.

       

      Finally, you mention deleting the jvm config. That's frankly a shocking idea, which I've never heard proposed. If you can share any link to a discussion suggesting that, I'd be very interested to know of it. 

      /Charlie (troubleshooter, carehart. org)
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices