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

[spcooney]

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.

[spcooney]

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]

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]

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

[spcooney · Accepted solution]

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]

Handy information, @spcooney . Thanks for sharing it.

[pegarm]

@spcooney Thanks for the insight on this.  I'm also receiving this error.  The first "fix" is temporary for me as well.  Can you provide more information about how to resolve / find-and-fix the mapping trailing slash?

[cooney_sei]

For me I went into the ColdFusion Administrator mappings section and edited all mappings to make sure they did not contain a trailing slash.  Then made sure to do the same for my rest apis in the Administrator.

[pegarm]

That's what I suspected.  As it turns out, none of my mappings or API services have trailing slashes, but it's still dying on me randomly.

I've submitted a bug report to Adobe for it.  I hope I'm not screaming into a void.