Skip to main content
spcooney
spcooney
Inspiring
January 4, 2024
Answered

API Error: Can not resolve PropertyFilter with id 'coldfusion.runtime.Struct'; no FilterProvider con

  • January 4, 2024
  • 3 replies
  • 2029 views

Hello All,

 

We have a collection of API calls that can successfully be called/run from several windows server instances of CF 2023.  A colleague on intel Mac CF 2018 and one on windows CF 2023 can also successfully call/run any of our API functionality.  On my local development instance of ColdFusion 2023 (ColdFusion 2023 MacBook Pro M2 macOS Sonoma) I consistently get the same error on every API call I try and leverage.

Can not resolve PropertyFilter with id 'coldfusion.runtime.Struct'; no FilterProvider configured

I have been unable to make any headway on figuring out why i am the only one getting this error message.

 

I am posting this discussion to hopefully find someone that may have some additional suggestions for me.

 

I can share more examples of some of the code but thought I would start with the error message and the explanation that this is only happening to me as the underlying CF code is working in all other environments.

 

Basic Code Same Error:

<cffunction name="getQuickTest" access="remote" output="false" returntype="Struct" restpath="test/outputValue/" httpmethod="get" produces="application/JSON">

		<cfset var myOneStruct = {Number:"1",Again:"2",More:"3",Lastly:"4"}>
		<cfset var returnStruct = StructNew()>
		<cfset variables.result  = "success" />

		<cfscript>
			myOneStruct = {Number:"1",Again:"2",More:"3",Lastly:"4"};
			returnStruct = StructNew();
			variables.result  = "success";
			returnStruct = myOneStruct;
		</cfscript>
		
	<cfreturn returnStruct>
</cffunction>

 

 

Thanks in advance Steve.

      Correct answer spcooney

      So I had a colleague also on an Apple Silicon macbook that needed to configure a local environment setup.  After we finished they also had the error above.  Because they still had their previous setup they went about comparing server settings and had a recollection of a past problem with mappings.

       

      After comparing the mappings they found that the mappings used for some universal rest functions had trailing slashes:

      /folder1/components/universal/

      But on their previous machine the mappings did not have a trailing slash.

      /folder1/components/universal

      After removing the trailing slash and restarting the CF server api calls resolved correctly without the previously stated error. Now I don't know if this is a Mac OS / Apple Silicon only type issue but I have observed that on our production windows systems the universal mapping does contain the trailing slash but does not error out like on a Mac.  Also of note on all tiers if you use the "Browse Server" button to add the path for your mapping it will add the trailing slash by default when you select a directory.  So the mappings behavior is consistent but the presence of that slash may or may not be detrimental based on the platform.

       

      I just wanted to add another possible solution here in case anyone else ran up against this.  This may still be a "bug" technically but I am not sure if I should submit it as one or not since it is possibly an edge case, I mean what weirdo codes CF on Mac OS/Apple Silicon in the year 2024 jeez....

      3 replies

      Charlie Arehart
      Community Expert
      Charlie ArehartCommunity Expert
      Community Expert
      July 22, 2025

      In case anyone finds this 2024 thread in the future (it was pointed to today in another thread), I want to share an observation not brought up here previously--especially since @pegarm reported that Steve's suggested solution had not worked for him. 

       

      Steve shared in one comment here that he had cleared the cfclasses and felix-cache folders. But he never mentioned clearing the rest-skeletons folder, a sibling of cfclasses. It's where classes specific to serving cf rest methods are saved, and like the others it will be rebuilt if emptied. As we've found with the others some problems are resolved by letting cf recreate those classes as they are subsequently called again--just as happens the very first time they're created. (In other words, you have nothing to lose in trying.)

       

      Also, do note with respect to all 3 folders while they're found within the default cfusion instance (which is always mentioned when discussing these folders), they are also in the folder for any cf" instance" you may create--and they would need to be cleared there, if your rest app is running within such a cf instance. 

       

      I'd be curious if anyone suffering this problem (now or in the future) might confirm (or deny) whether this helped. 

      /Charlie (troubleshooter, carehart. org)
      D
      davidc83157381
      Participating Frequently
      July 25, 2025

      We had the same issue on another thread. 

      REST API Error: Can not resolve PropertyFilter wit... - Adobe Product Community - 15423396

       

      We had 2 of our 4 production servers returning this error.

       

      We cleaned out just the rest-skeletons directory the first node and restarted and that was sufficent to get a proper resoponse.

       

      We went to do the same on the second bad node but that didnt fix it after we restared.  We then proceeded to delete cfclasses and restart and then it was working again.

       

      We didnt bother deleting felix-cache after they were working with out that step (but I guess why not while you are at it)

       

      So I guess no definitive answer on what directories should be cleaned and let CF recreate but cleaning those directories did work (at least for now)   Will report back if the fix is only temporary.

       

      Thanks again for all you do for the CF Community Charlie!

      BKBK
      Community Expert
      BKBKCommunity Expert
      Community Expert
      July 25, 2025

      One crucial point, in addition to @davidc83157381 's instructive comment:

      • If a method in a REST cfc calls 
         restSetResponse​()

        then the method should not return anything. It should have void return-type.

         
      spcooney
      spcooneyAuthorCorrect answer
      Inspiring
      April 4, 2024

      So I had a colleague also on an Apple Silicon macbook that needed to configure a local environment setup.  After we finished they also had the error above.  Because they still had their previous setup they went about comparing server settings and had a recollection of a past problem with mappings.

       

      After comparing the mappings they found that the mappings used for some universal rest functions had trailing slashes:

      /folder1/components/universal/

      But on their previous machine the mappings did not have a trailing slash.

      /folder1/components/universal

      After removing the trailing slash and restarting the CF server api calls resolved correctly without the previously stated error. Now I don't know if this is a Mac OS / Apple Silicon only type issue but I have observed that on our production windows systems the universal mapping does contain the trailing slash but does not error out like on a Mac.  Also of note on all tiers if you use the "Browse Server" button to add the path for your mapping it will add the trailing slash by default when you select a directory.  So the mappings behavior is consistent but the presence of that slash may or may not be detrimental based on the platform.

       

      I just wanted to add another possible solution here in case anyone else ran up against this.  This may still be a "bug" technically but I am not sure if I should submit it as one or not since it is possibly an edge case, I mean what weirdo codes CF on Mac OS/Apple Silicon in the year 2024 jeez....

      BKBK
      Community Expert
      BKBKCommunity Expert
      Community Expert
      April 4, 2024

      Handy information, @spcooney . Thanks for sharing it.

        spcooney
        spcooneyAuthor
        Inspiring
        January 5, 2024

        Just an update.  I was on ColdFusion HF 003 when I was having this error.  I took the shot and updated to ColdFusion 2023 Hotfix 006 from November of last year and after the update and restarting with a couple of extra class removal steps I was able to get the API calls working.  Just typing a post inspired me to try a few things so thanks for being here haha.

         

        Additional post hotfix steps:

        1. Stop the CF services.
        2. Navigate to ColdFusion2023\cfusion\wwwroot\WEB-INF\cfclasses and remove all files (would be regenerated)
        3. Navigate to ColdFusion2023\cfusion\bin\felix-cache and remove all files. (would be regenerated)
        4. Start CF services and check the scenario.
          spcooney
          spcooneyAuthor
          Inspiring
          March 19, 2024

          This solution appears to have been coincidence.  It may still work in your case but I have had the same error return. 

           

          Cannot resolve PropertyFilter with id 'coldfusion.runtime.Struct'; no FilterProvider configured (through reference chain: coldfusion.runtime.Struct[0])

           

          Again this happens on all calls to my APIs in the rest path. This is after the latest CF hotfix (2023 007) but I do not know if that had any impact.  Very frustrating issue to try and deal with esoecially when your post is the first result when yo search for solutions.  I just wanted to make sure the above was no longer the accepted answer even though there is a chance it can help.

          BKBK
          Community Expert
          BKBKCommunity Expert
          Community Expert
          March 20, 2024

          Looks like an issue in ColdFusion's REST engine. Report a bug.

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices