tracker issue : CF-3916195

select a category, or use search below
(searches all categories and all time range)
Title:

CFFTP not working, CF10 Update 15

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/

Reporter/Name(from Bugbase): Chris Morbitzer / Chris Morbitzer (Chris Morbitzer)

Created: 01/05/2015

Components: Net Protocols, FTP

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final /

Priority/Frequency: Normal / Unknown

Locale/System: English / Win 2008 Server

Vote Count: 0

Problem Description:
We updated our CF10 installation to Update 15 and now our cfftp tags are throwing the error: "The tag handler ftp does not have a setter for the attribute parserKey specified in the Tag Library Descriptor." I made a one line file with the code below to reproduce the error.

Steps to Reproduce:
<cfftp action="open" connection="My_query" server="xxx" username="xxx" password="xxx" stopOnError = "No">

Actual Result:
The tag handler ftp does not have a setter for the attribute parserKey specified in the Tag Library Descriptor. 

Expected Result:
FTP connection opened. 

Stack trace viewable here: https://forums.adobe.com/message/7039909

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3916195

External Customer Info:
External Company:  
External Customer Name: cmorbitzer
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Adobe, This is likely related to #CF-3849151. The parserkey attribute was renamed to systemtype before CF11u3 was released. FWIW, I was unable to repro this on CF10u14 and CF11u3. Thanks!, -Aaron
Comment by External U.
9130 | January 06, 2015 06:52:15 AM GMT
Hi Chris, Could you let us know the build number that you are getting this error on, because for the update 15 with the build number #292620 I am unble to repro the issue. Thanks, Preethi
Comment by S P.
9131 | March 16, 2015 02:28:06 AM GMT
Since there has been no response, closing the bug for now. If you still are facing issues the bug will be reopened.
Comment by S P.
9132 | May 11, 2015 12:22:43 AM GMT