Skip to main content
Participant
June 29, 2006
Answered

Error with CFGRIDUPDATE after installing CFMX 7 Updaters

  • June 29, 2006
  • 1 reply
  • 16648 views
I installed ColdFusion MX 7 Updater (7.0.1) and ColdFusion MX 7 Updater 2 (7.0.2). Now I'm geting the following errors when using CFGRIDUPDATE:

Error casting an object of type coldfusion.sql.CFNoResultSetTable to an incompatible type. This usually indicates a programming error in Java, although it could also mean you have tried to use a foreign object in a different way than it was designed.
coldfusion.sql.CFNoResultSetTable

<cfgridupdate datasource="#request.dsn#" grid="thisGrid" tablename="MY_TABLE">

Is anyone else getting this? I'm going to handle the SQL manually until I can use CFGRIDUPDATE again.
    This topic has been closed for replies.
    Correct answer danwparker
    I don't know if this will help you guys, but I solved my problem last night by disabling debugging on the CF server. I was the only one getting the error message "Error casting an object of type to an incompatible type. This usually indicates a programming error in Java, although it could also mean you have tried to use a foreign object in a different way than it was designed."
    My machine was the only IP setup to receive debugging output. I turned off debugging and problem went away...weird.

    sbrehm,

    You are absolutely right. Turning debugging off solved the problem. In this case, you can leave debugging on but uncheck the "Database Activity" checkbox. Something must be getting confused between the DB debugging and the CFGRIDUPDATE call. Hopefully Adobe will fix this glitch.

    By the way, I tried using <cfsetting showdebugoutput="no"> on the .cfm file in question, but that didn't work. I had to physically disable to "database activity" debugging completely.

    Thanks for the suggestion!

    1 reply

    Participant
    July 24, 2006
    Did you ever solve this one? I'm experiencing something similar and getting nowhere... --Steve
    Participant
    July 25, 2006
    I never solved this one. I submitted a bug report. I'm handling the SQL manually until its fixed.
    Inspiring
    July 26, 2006
    Whats the bug number on this issue? I am having this problem too and am reverting back to 7.0.1.