Invalid cursor state

Problem with dsigning tables. when changing datatype, size
etc'
i get message:
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
cursor state
microsoft is reffering to: http://support.microsoft.com/?
kbid=831997
but there is nothing there that can fix the problem
what can i do to fix it?
Thankseran,shalom
Check out if the log file is full, what is recovery model of the log file?
<eranv@.gat.co.il> wrote in message
news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> Problem with dsigning tables. when changing datatype, size
> etc'
> i get message:
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> cursor state
> microsoft is reffering to: http://support.microsoft.com/?
> kbid=831997
> but there is nothing there that can fix the problem
> what can i do to fix it?
> Thanks|||Uri hi and thanks for responding,
The log file is not full and the mode is set to "simple"
this error occurs on all tables and in every database. I
think it has something to do with hotfix or patch that we
installed after sp3a
we are working around that problem by recreating the
tables everytime a change is needed. you can imagin how
hard it is to work like that.
thanks again
Eran
.
>--Original Message--
>eran,shalom
>Check out if the log file is full, what is recovery model
of the log file?
>
><eranv@.gat.co.il> wrote in message
>news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> Problem with dsigning tables. when changing datatype,
size
>> etc'
>> i get message:
>> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
>> cursor state
>> microsoft is reffering to:
http://support.microsoft.com/?
>> kbid=831997
>> but there is nothing there that can fix the problem
>> what can i do to fix it?
>> Thanks
>
>.
>|||Eran
I see, have you looked at http://support.microsoft.com/?kbid=821334
Do you have the same MDAC on the client and server?
<anonymous@.discussions.microsoft.com> wrote in message
news:acf101c48834$30264d70$a601280a@.phx.gbl...
> Uri hi and thanks for responding,
> The log file is not full and the mode is set to "simple"
> this error occurs on all tables and in every database. I
> think it has something to do with hotfix or patch that we
> installed after sp3a
> we are working around that problem by recreating the
> tables everytime a change is needed. you can imagin how
> hard it is to work like that.
> thanks again
> Eran
> .
>
> >--Original Message--
> >eran,shalom
> >Check out if the log file is full, what is recovery model
> of the log file?
> >
> >
> ><eranv@.gat.co.il> wrote in message
> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> Problem with dsigning tables. when changing datatype,
> size
> >> etc'
> >> i get message:
> >> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> >> cursor state
> >>
> >> microsoft is reffering to:
> http://support.microsoft.com/?
> >> kbid=831997
> >> but there is nothing there that can fix the problem
> >> what can i do to fix it?
> >>
> >> Thanks
> >
> >
> >.
> >|||yes the MDAC versions are the same. the error message
occurs also when working directly on the server.
a general search led me to http://support.microsoft.com/?
kbid=831997
and i think that the link discribes an issue somewhat
relevant, however i could not find a workaround or hotfix
to correct the problem.
>--Original Message--
>Eran
>I see, have you looked at http://support.microsoft.com/?
kbid=821334
>Do you have the same MDAC on the client and server?
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:acf101c48834$30264d70$a601280a@.phx.gbl...
>> Uri hi and thanks for responding,
>> The log file is not full and the mode is set to "simple"
>> this error occurs on all tables and in every database. I
>> think it has something to do with hotfix or patch that
we
>> installed after sp3a
>> we are working around that problem by recreating the
>> tables everytime a change is needed. you can imagin how
>> hard it is to work like that.
>> thanks again
>> Eran
>> .
>>
>> >--Original Message--
>> >eran,shalom
>> >Check out if the log file is full, what is recovery
model
>> of the log file?
>> >
>> >
>> ><eranv@.gat.co.il> wrote in message
>> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> >> Problem with dsigning tables. when changing datatype,
>> size
>> >> etc'
>> >> i get message:
>> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
Invalid
>> >> cursor state
>> >>
>> >> microsoft is reffering to:
>> http://support.microsoft.com/?
>> >> kbid=831997
>> >> but there is nothing there that can fix the problem
>> >> what can i do to fix it?
>> >>
>> >> Thanks
>> >
>> >
>> >.
>> >
>
>.
>|||Eran
You may want to delete the hotfix and re-install sp3.
<anonymous@.discussions.microsoft.com> wrote in message
news:ad1f01c4883a$cd180280$a601280a@.phx.gbl...
> yes the MDAC versions are the same. the error message
> occurs also when working directly on the server.
> a general search led me to http://support.microsoft.com/?
> kbid=831997
> and i think that the link discribes an issue somewhat
> relevant, however i could not find a workaround or hotfix
> to correct the problem.
> >--Original Message--
> >Eran
> >I see, have you looked at http://support.microsoft.com/?
> kbid=821334
> >Do you have the same MDAC on the client and server?
> >
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:acf101c48834$30264d70$a601280a@.phx.gbl...
> >> Uri hi and thanks for responding,
> >> The log file is not full and the mode is set to "simple"
> >> this error occurs on all tables and in every database. I
> >> think it has something to do with hotfix or patch that
> we
> >> installed after sp3a
> >> we are working around that problem by recreating the
> >> tables everytime a change is needed. you can imagin how
> >> hard it is to work like that.
> >> thanks again
> >> Eran
> >> .
> >>
> >>
> >> >--Original Message--
> >> >eran,shalom
> >> >Check out if the log file is full, what is recovery
> model
> >> of the log file?
> >> >
> >> >
> >> ><eranv@.gat.co.il> wrote in message
> >> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> >> Problem with dsigning tables. when changing datatype,
> >> size
> >> >> etc'
> >> >> i get message:
> >> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
> Invalid
> >> >> cursor state
> >> >>
> >> >> microsoft is reffering to:
> >> http://support.microsoft.com/?
> >> >> kbid=831997
> >> >> but there is nothing there that can fix the problem
> >> >> what can i do to fix it?
> >> >>
> >> >> Thanks
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Invalid cursor state

[Microsoft][ODBC SQL Server Driver]Invalid cursor state
Having a few of these reported in our application logs as it calls a sql
server stored proc stemming from ODBC that references SQLFetch
The stored proc does not use a cursorPlease exhibit some patience and don't post the same question multiple
times.
What on earth does your stored procedure do? Should we guess? Do you have
any problems when you call the stored procedure directly (without using the
app)? How about if you use a different connection method (e.g. OLEDB
instead of ODBC)?
"Hassan" <hassan@.test.com> wrote in message
news:OUHYKlXUIHA.5160@.TK2MSFTNGP05.phx.gbl...
> [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> Having a few of these reported in our application logs as it calls a sql
> server stored proc stemming from ODBC that references SQLFetch
> The stored proc does not use a cursor|||Hi Hassan
My guess is that it is a DTC issue, but as Aaron points out all three of the
posts you have made since April 2007 for this give very little information.
John
"Hassan" wrote:
> [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> Having a few of these reported in our application logs as it calls a sql
> server stored proc stemming from ODBC that references SQLFetch
> The stored proc does not use a cursor
>

Invalid cursor state

[Microsoft][ODBC SQL Server Driver]Invalid cursor state
Having a few of these reported in our application logs as it calls a sql
server stored proc stemming from ODBC that references SQLFetch
The stored proc does not use a cursor
Please exhibit some patience and don't post the same question multiple
times.
What on earth does your stored procedure do? Should we guess? Do you have
any problems when you call the stored procedure directly (without using the
app)? How about if you use a different connection method (e.g. OLEDB
instead of ODBC)?
"Hassan" <hassan@.test.com> wrote in message
news:OUHYKlXUIHA.5160@.TK2MSFTNGP05.phx.gbl...
> [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> Having a few of these reported in our application logs as it calls a sql
> server stored proc stemming from ODBC that references SQLFetch
> The stored proc does not use a cursor
|||Hi Hassan
My guess is that it is a DTC issue, but as Aaron points out all three of the
posts you have made since April 2007 for this give very little information.
John
"Hassan" wrote:

> [Microsoft][ODBC SQL Server Driver]Invalid cursor state
> Having a few of these reported in our application logs as it calls a sql
> server stored proc stemming from ODBC that references SQLFetch
> The stored proc does not use a cursor
>