Status/Resolution/Reason: Closed/Withdrawn/Duplicate
Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)
Created: 08/22/2014
Components: Hot Fix Installer
Versions: 10.0
Failure Type:
Found In Build/Fixed In Build: Final /
Priority/Frequency: Major / Some users will encounter
Locale/System: English / Platforms All
Vote Count: 0
Duplicate ID: CF-3577840
This is a new install of CF10, and I'm trying to apply the updates I need to make it secure.
When I got to Server Update > Updates, after some seconds I get this:
The following information is meant for the website developer for debugging purposes.
Error Occurred While Processing Request
A timeout occurred while attempting to lock updatecheck.
The error occurred in index.cfm: line 92
Called from index.cfm: line 37
Called from index.cfm: line 1
Called from index.cfm: line 92
Called from index.cfm: line 37
Called from index.cfm: line 1
-1 : Unable to display error's location in a CFML template.
Resources:
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 NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36
Remote Address 127.0.0.1
Referrer http://127.0.0.1:8501/CFIDE/administrator/navserver.cfm
Date/Time 22-Aug-14 12:52 PM
Stack Trace
at cfindex2ecfm510158214._factor4(C:/work/cf10_updates/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm:92) at cfindex2ecfm510158214._factor7(C:/work/cf10_updates/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm:37) at cfindex2ecfm510158214.runPage(C:/work/cf10_updates/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm:1)
at cfindex2ecfm510158214._factor4(C:/work/cf10_updates/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm:92) at cfindex2ecfm510158214._factor7(C:/work/cf10_updates/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm:37) at cfindex2ecfm510158214.runPage(C:/work/cf10_updates/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm:1)
I'm not so concerned about the fact that it's erroring as it cannot reach the outside world, and is timing out.
But how amateur are you guys to not have an onError() in place to present a decent error message here?!
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3810506
External Customer Info:
External Company:
External Customer Name: Adam Cameron.
External Customer Email:
External Test Config: My Hardware and Environment details:
Attachments:
Comments: