Title:
Bug 82775:When doing a cached FTP, then checking for an EXISTSFILE, returns the error Parser key cannot by null
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/
Reporter/Name(from Bugbase): Dan Madzia / Dan Madzia (Dmadzia)
Created: 04/29/2010
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: V9,0,0,251028 driverV 4.0(Build 0005) /
Priority/Frequency: Normal / Unknown
Locale/System: English / Win All
Vote Count: 0
Problem:
When doing a cached FTP, then checking for an EXISTSFILE, returns the error Parser key cannot by null. The initial connection is not set to secure. Works fine in v8 or under.
Method:
<cfftp action="open" server="myserver.domain.com" username="myusername" password="" connection="theTandem" stoponerror="Yes" result="ftp1"><cfftp action="EXISTSFILE" stoponerror="Yes" remotefile="myfile.txt" connection="theTandem" retrycount="3" result="ftp2">Error occurs here. "Parser key cannot be null". In previous versions <=8, the ReturnValue is ALWAYS False. I had to use the ErrorCode to work around it. (errorcode 226=file exists, errorcode 550=file not found). Now I can't use EXISTSFILE at all.
Result:
Parser key cannot be null
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3041388
External Customer Info:
External Company:
External Customer Name: Dan Madzia
External Customer Email: 075E28AB447C569B9920157F
External Test Config: 04/29/2010Attachments:
Comments: