Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Error in the forge log is Unable to determine the number of columns in the ODBC result: [Microsoft][SQL Native Client]Invalid cursor state
Endeca is a bit black-box, so I’m not sure exactly what sql call is causing this error
Glenn,
In SQLServer 2005 (and perhaps other SQLServer versions), calls to ODBC
SQLNumResultColshave been known to return invalid column counts or throw errors when the query is a call to a non-trivial stored procedure. If your query calls a stored procedure, see if you derive the same outcome using direct table or view reads, perhaps combined with logic in Forge.Brett