Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CFSET/COM Error

Status
Not open for further replies.

Argus

Programmer
Mar 10, 2000
8
GB
Hi guys

I've got a COM object which takes a SQL statement, creates an excel spreadsheet, saves it, then throws back the path. I've got it working on a dev server fine but when I copy it to a live server I get the following message:-

Disk or network error

The error occured while processing an element with a general identifier of (CFSET), occupying . . . etc etc

Here's the CFOBJECT tag and the offending CFSET:-

<CFOBJECT CLASS=&quot;ClientSQL.ClientXLGen&quot;
ACTION=&quot;CREATE&quot;
NAME=&quot;XLTest&quot;>

<CFSET Test1 = XLTest.GenXL('#MyVBSQL#', '#Form.ReportName#', #Session.UserID#, &quot;Office97&quot;)>

I can't see any difference between the dev server and the live server - the code is the same, the directory structure is the same, the exe is the same and is viewable through oleview (ie. it seems to have been installed ok).

What I don't understand is why I'm getting a 'disk or network error' rather than a COM error?

Anything spring to mind that I might be overlooking?

I've had a look at which is a good resource for ColdFusion/COM, but to no avail.
 
It sounds to me like the com object is getting an error when it tries to write the file out to disk. I would guess that CF is somehow catching the specific COM error message and returning it instead of a CF error message. I would expect a &quot;COM Error&quot; if the object wasn't registered correctly.

I would comment out any code in the COM object that checks or writes to the disk and see if that makes a difference. If it runs without an error, I would comment sections back in until you find the guilty line. At that point, I suspect you'll find it's a bad file path or has something to do with NT permissions. If not, post what line is giving you the error and I'm sure someone in the forums can help you pinpoint the problem.

Hope this helps,
GJ
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top