/t5/coldfusion-discussions/cf-8-0-1-administrator-broken/td-p/4763356Jan 21, 2013
Jan 21, 2013
Copy link to clipboard
Copied
Coldfusion sites are running just fine. However, accessing the CF Administrator in our produciton environment generates error. Appears to have occured after installing hotfix "APSB09-12". This same hotfix has been applied to our development environment with out causing CF Administrator to break. I use the term "appears" because I don't think other changes were made to the environment in relation to the time we found out CF Admin was broken. Please help!
See below information:
Server Info:
Running CF 8.0.1
on Windows Server 2008 R2 Datacenter (Service Pack 1)
x64 OS
Error Message:
Browser
DateTime
Diagnostics
Could not find the ColdFusion Component or Interface CFIDE.adminapi.accessmanager. Ensure that the name is correct and that the component or interface exists. <br>The error occurred on line 95.
GeneratedContent
[empty string]
HTTPReferer
[empty string]
Mailto
[empty string]
Message
Could not find the ColdFusion Component or Interface CFIDE.adminapi.accessmanager.
QueryString
[empty string]
RemoteAddress
RootCause
struct
Detail
Ensure that the name is correct and that the component or interface exists.
Message
Could not find the ColdFusion Component or Interface CFIDE.adminapi.accessmanager.
StackTrace
coldfusion.runtime.CfJspPage$NoSuchTemplateException: Could not find the ColdFusion Component or Interface CFIDE.adminapi.accessmanager. at coldfusion.runtime.TemplateProxyFactory.getResolvedFile(TemplateProxyFactory.java:1142) at coldfusion.runtime.TemplateProxyFactory.getTemplateFileHelper(TemplateProxyFactory.java:1315) at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:1258) at coldfusion.cfc.ComponentProxyFactory.getProxy(ComponentProxyFactory.java:28) at coldfusion.runtime.ProxyFactory.getProxy(ProxyFactory.java:65) at coldfusion.runtime.CFPage.createObjectProxy(CFPage.java:4688) at coldfusion.runtime.CFPage.CreateObject(CFPage.java:4533) at cfApplication2ecfm1439570487._factor2(E:\cf8_final\cfusion\wwwroot\CFIDE\administrator\Application.cfm:95) at cfApplication2ecfm1439570487._factor7(E:\cf8_final\cfusion\wwwroot\CFIDE\administrator\Application.cfm:4) at cfApplication2ecfm1439570487.runPage(E:\cf8_final\cfusion\wwwroot\CFIDE\administrator\Application.cfm:1) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.CfincludeFilter.include(CfincludeFilter.java:33) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:214) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:86) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.CfmServlet.service(CfmServlet.java:198) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89) at jrun.servlet.FilterChain.doFilter(FilterChain.java:86) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at jrun.servlet.FilterChain.doFilter(FilterChain.java:94) at jrun.servlet.FilterChain.service(FilterChain.java:101) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:284) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543) at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203) at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428) at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
TagContext
array
1
struct
COLUMN
0
ID
CF_CFPAGE
LINE
95
RAW_TRACE
at cfApplication2ecfm1439570487._factor2(E:\cf8_final\cfusion\wwwroot\CFIDE\administrator\Application.cfm:95)
The article you listed does not apply in my case. Infact, our CF Administrator was working previously. It broke recently and the root cause we have not been able to identify.
Let's start with the obvious. The error says "Could not find the ColdFusion Component or Interface CFIDE.adminapi.accessmanager. Ensure that the name is correct and that the component or interface exists. <br>The error occurred on line 95.". Does that file exist on your server in that location?
This is the location where our IIS site for the ColdFusion Administrator site is on. This one does not have the accessmanager file. However, our dev environment matches this setup too. Dev CF Admin works just fine.
In terms of permissions I am almost sure nothing changed from the time when it was working.
I'm guessing that your dev ColdFusion administrator is running from the CFIDE\adminapi that contains the file and production is not. If your CFIDE directory is not in the default location you must update those files manually when you apply hotfixes/patches. The installation instructions generally tell you to expand the ZIP file to your CFIDE directory. Which directory did you apply the fix? That page I referred you to intially mentions you can just copy the files to the appropriate directory.
I think your problem will go away if you update the correct CFIDE directory.
8
Replies
AdChoices