Error Occurred While Processing Request

Seit gestern habe ich das Problem, daß eine Seite mit dem Titel "Error Occurred While Processing Request" aufgeht, wenn ich z.B. auf der ersten PC Welt-DownloadSeite den Weiterlink auf die 2. Seite anklicke. Was kann da passiert sein?

Error Occurred While Processing Request The system has attempted to use an undefined value, which usually indicates a programming error, either in your code or some system code.

Null Pointers are another name for undefined values.

The error occurred in /wwwroot/htdocs/idgwppcwelt/html-data/_datasource.cfm: line 14

12 : <!--- --------------------->
13 :
14 : <cfapplication name="idgwppcwelt" clientmanagement="Yes" sessionmanagement="Yes" CLIENTStorage="clientstorage" sessiontimeout="#CreateTimeSpan(0,12,0,0)#">

Please try the following:

* Check the ColdFusion documentation to verify that you are using the correct syntax.
* Search the Knowledge Base to find a solution to your problem.

Browser Mozilla/5.0 (Windows; U; Win 9x 4.90; de-DE; rv:1.0.2) Gecko/20030208 Netscape/7.02
Remote Address (wurde von mir entfernt)
Referrer http://www.pcwelt.de/downloads/heft-cd/
Date/Time 21-May-05 11:37 AM
Stack Trace
at cf_datasource2ecfm92098615.runPage(/wwwroot/htdocs/idgwppcwelt/html-data/_datasource.cfm:14) at cfApplication2ecfm281506398.runPage(/idg/apache/htdocs/idgwppcwelt/html-data/Application.cfm:13)

java.lang.NullPointerException
at coldfusion.runtime.ClientScopeKey.hashCode(ClientScopeKey.java:29)
at java.util.Hashtable.get(Hashtable.java:333)
at coldfusion.runtime.ClientScopeServiceImpl.GetClientScope(ClientScopeServiceImpl.java:168)
at coldfusion.tagext.lang.ApplicationTag.setupClientScope(ApplicationTag.java:571)
at coldfusion.tagext.lang.ApplicationTag.doStartTag(ApplicationTag.java:283)
at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1876)
at cf_datasource2ecfm92098615.runPage(/wwwroot/htdocs/idgwppcwelt/html-data/_datasource.cfm:14)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:147)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:357)
at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1876)
at cfApplication2ecfm281506398.runPage(/idg/apache/htdocs/idgwppcwelt/html-data/Application.cfm:13)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:147)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:357)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:62)
at coldfusion.filter.CfincludeFilter.include(CfincludeFilter.java:30)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:93)
at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:80)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:47)
at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:52)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:35)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:43)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.CfmServlet.service(CfmServlet.java:105)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:249)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:192)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:348)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:451)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:294)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

 

Meinst du den etwas schwarzen Humor des ersten Teiles der Signatur?

 

Deine Signatur ist zu lang !!
FORENREGELN lesen hilft !!

 

Ich habe meine Signatur angepasst.
Ich hoffe, daß damit einer Hilfestellung eurerseits nun nichts mehr im Wege steht, denn das beschriebene Problem besteht ja unabhängig von Signatur weiter.
Danke