Is it possible that you are using SQL server and the db owner is set to something different than the norm?
The query at the root of the error does not seem to have #application.dbowner# prefixed against the table name. There could be an exception that is not being handled correctly by CF, perhaps... Just a thought On Tue, Nov 17, 2009 at 6:10 AM, Chris Roth <[email protected]> wrote: > I grabbed the latest core (4891). > > Updates app, and I still have the problem on this one node. It appears > that all the other dmNvaigation nodes work just fine. > > I duplicated the FUs used by production (they are the same as dev) to > see if a sub node would work and I get the same error. > > Im not sure wherre else to look for a reason why this entire node > would blow up. > > > > > > > On Nov 13, 9:54 pm, modius <[email protected]> wrote: > > On Nov 14, 7:48 am, Chris Roth <[email protected]> wrote: > > > > > hmm. FUs are working for all the other nodes, and the one thats not > > > working has a defult object (dmhtml), and FUs assigned to it. > > > > 5.2.7 was only released today. It may be that the HEAD of the > > maintenance branch was unstable when you grabbed it. Let us know if > > you are still encountering the problem. > > > > -- geoffhttp://www.daemon.com.au/ > > -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: > [email protected]<farcry-dev%[email protected]> > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry > -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
