CFCONTENT and Windows error 232

[izibizi]

Hi,

I am usinf CF5.

I use CFCONTENT to send a pdf to the user. As soon as the browser loads acrobat inside it i get:

"Error","74288","12/22/08","13:49:35",,"Error number 232 occurred attempting to close connection to web server."
"Error","74288","12/22/08","13:49:35",,"Windows NT error number 232 occurred."

Any concern?
Can I do anything to prevent this?

[izibizi]

any body?

[Newsgroup_User]

> any body?

I did a search on Google y/day for "cfcontent windows error 232" (or
similar) and there were quite a few matches. So I figured you perhaps
haven't put much effort into trying to sort this out yourself: you
certainly don't indicate you've done any investigation.

What have you done to investigate this yourself? What have you eliminated
as being possible causes?

--
Adam

[izibizi]

well, guess what, I did do a lot of searches and all I found did not solve anything.

The best suggestion i found was that it relates to timeout on the IIS side which i checked and found to be not related.

what i did try is to comment out my cfcontent line and no more 232 error. this prooved to be the reason beyond any doubt.

[Newsgroup_User]

> well, guess what, I did do a lot of searches and all I found did not solve
> anything.
>
> The best suggestion i found was that it relates to timeout on the IIS side
> which i checked and found to be not related.
>
> what i did try is to comment out my cfcontent line and no more 232 error. this
> prooved to be the reason beyond any doubt.

That (all) probably would have have been good to mention.

What's the exact piece of code?

--
Adam

[izibizi]

I call this .cfm page from my main page using cflocation. like so:

<cflocation url="SendFile.cfm" addtoken="yes">

[Newsgroup_User]

> <cfheader name = "Expires" value = "#Now()#">
> <!--- <cfheader name = "Cache-Control" value = "no-cache">
> <cfheader name = "Pragma" value = "no-cache"> --->
> <cflock timeout="30" throwontimeout="no" type="readonly" scope="session">
> <cfset filename = session.file>
> </cflock>
> <cfif ucase(right(filename,3)) IS "AFP">
> <cfcontent deletefile="no" file="#filename#" type="application/afp">
> <cfelseif ucase(right(filename,3)) IS "PDF">
> <cfcontent deletefile="no" file="#filename#" type="application/pdf">
> </cfif>

All that seems OK, from a superficial assessment.

Have you used an HTTP sniffer to see if there's anything untoward being
sent down to the browser in these situations?

What happens if you factor this code back to a test rig:

<cfheader name = "Expires" value = "#Now()#">
<cfcontent deletefile="no" file="fullPathToFile" type="application/afp">

Are you sure the file you specify actually exists? What does
fileExists(filename) return.

I think you should be testing for the existence of the file as a matter of
course, when doing this sort of thing.

--
Adam

[izibizi]

the file is perfect. the browser opens pdf viewer (acrobat or foxit) and the file can be viewed with no problem.

but as soon as the file is sent to the browser i get the 2 error lines in system.log

the problem is not the file. i also applied the cfcontent hotfix of cf5 but no change.

i am quite sure the problem that acrobat is opened full screen in the ie window and this somehow changes the session to iis.