While working on a project to integrated Adobe LiveCycle and ColdFusion I ran into an odd issue. I was calling a LiveCycle service that returns a PDF document. That document is then written to the file system and then delivered to the client.

Everything was working fine then I started getting a strange error.

view plain print about
1AxisFault
2 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
3 faultSubcode:
4 faultString: coldfusion.xml.rpc.CFCInvocationException:
5 [coldfusion.tagext.io.FileTag$SingleFileOperationException : An error occurred when performing a file operation write on file \\serverpath\tempMarkup\C1E254134EE109A1D312B01C5A2F7EFA.pdf.][java.io.IOException : Insufficient system resources exist to complete the requested service]
6 faultActor:
7 faultNode:
8 faultDetail:
9 {http://xml.apache.org/axis/}stackTrace:coldfusion.xml.rpc.CFCInvocationException: [coldfusion.tagext.io.FileTag$SingleFileOperationException : An error occurred when performing a file operation write on file \\serverpath\tempMarkup\C1E254134EE109A1D312B01C5A2F7EFA.pdf.][java.io.IOException : Insufficient system resources exist to complete the requested service]
10 at coldfusion.xml.rpc.CFComponentSkeleton.__createCFCInvocationException(CFCo... ''

This error would happen directly after the web service ran at the point where the file would be written. What was actually written was a zero (0) byte file and an error message was displayed. I was sure that the error was not in the web service as the error was after the service ran and returned. But at the same time the error said it was an AxisFault which usually points to web services.

After doing some trial and error, contacting a few people that may have a solution, praying, and doing a quick chant I was able to figure it out. I changed the code to write the file locally then move it to the shared storage. (Notice the UNC path in the error message?).

I have no idea why this threw this error as I was able to move the file from local to remote. I have a feeling it has something to do with Windows and it's ability to write the file to the remote storage.

till next time,

--Dave