no locks exist

We have an application running on SQL 7 which we just made changes to. Since
then we've been getting intermittant error message saying "no locks exist for
the table: cddegree. Unable to reset the lock status.." This happens about
25% of the time when we try to enter information into a table that has
nothing to do with cddegree. Any ideas would be greatly appreciate.
Thanks.
PatPat
What kind of changes did you do?
"PatW" <PatW@.discussions.microsoft.com> wrote in message
news:6766EC59-5E07-4741-870D-BA116E1E31B0@.microsoft.com...
> We have an application running on SQL 7 which we just made changes to.
Since
> then we've been getting intermittant error message saying "no locks exist
for
> the table: cddegree. Unable to reset the lock status.." This happens
about
> 25% of the time when we try to enter information into a table that has
> nothing to do with cddegree. Any ideas would be greatly appreciate.
> Thanks.
> Pat|||Is this a SQL Error message or an application message?
--
Andrew J. Kelly SQL MVP
"PatW" <PatW@.discussions.microsoft.com> wrote in message
news:6766EC59-5E07-4741-870D-BA116E1E31B0@.microsoft.com...
> We have an application running on SQL 7 which we just made changes to.
> Since
> then we've been getting intermittant error message saying "no locks exist
> for
> the table: cddegree. Unable to reset the lock status.." This happens
> about
> 25% of the time when we try to enter information into a table that has
> nothing to do with cddegree. Any ideas would be greatly appreciate.
> Thanks.
> Pat|||Most of the changes are in the front end app, which is in Visual FoxPro. In
SQL, we added some fields to two test score tables and modified some stored
procedures to update one of those tables with information from the other
table. Neither table is dependent on the table referred to in the error
message and vice versa.
"Uri Dimant" wrote:
> Pat
> What kind of changes did you do?
>
> "PatW" <PatW@.discussions.microsoft.com> wrote in message
> news:6766EC59-5E07-4741-870D-BA116E1E31B0@.microsoft.com...
> > We have an application running on SQL 7 which we just made changes to.
> Since
> > then we've been getting intermittant error message saying "no locks exist
> for
> > the table: cddegree. Unable to reset the lock status.." This happens
> about
> > 25% of the time when we try to enter information into a table that has
> > nothing to do with cddegree. Any ideas would be greatly appreciate.
> >
> > Thanks.
> >
> > Pat
>
>|||I can't tell - it's in the SQL Server log, but I haven't been able to find
anything like it on the SQL web site.
"Andrew J. Kelly" wrote:
> Is this a SQL Error message or an application message?
> --
> Andrew J. Kelly SQL MVP
>
> "PatW" <PatW@.discussions.microsoft.com> wrote in message
> news:6766EC59-5E07-4741-870D-BA116E1E31B0@.microsoft.com...
> > We have an application running on SQL 7 which we just made changes to.
> > Since
> > then we've been getting intermittant error message saying "no locks exist
> > for
> > the table: cddegree. Unable to reset the lock status.." This happens
> > about
> > 25% of the time when we try to enter information into a table that has
> > nothing to do with cddegree. Any ideas would be greatly appreciate.
> >
> > Thanks.
> >
> > Pat
>
>|||I haven't seen that one before. This google search brings up a number of
potentials and it is probably worth a look:
site:support.microsoft.com Unable to reset the lock status
Andrew J. Kelly SQL MVP
"PatW" <PatW@.discussions.microsoft.com> wrote in message
news:339B7DF0-30F3-498B-9C94-A5625F18DD84@.microsoft.com...
>I can't tell - it's in the SQL Server log, but I haven't been able to find
> anything like it on the SQL web site.
> "Andrew J. Kelly" wrote:
>> Is this a SQL Error message or an application message?
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "PatW" <PatW@.discussions.microsoft.com> wrote in message
>> news:6766EC59-5E07-4741-870D-BA116E1E31B0@.microsoft.com...
>> > We have an application running on SQL 7 which we just made changes to.
>> > Since
>> > then we've been getting intermittant error message saying "no locks
>> > exist
>> > for
>> > the table: cddegree. Unable to reset the lock status.." This happens
>> > about
>> > 25% of the time when we try to enter information into a table that has
>> > nothing to do with cddegree. Any ideas would be greatly appreciate.
>> >
>> > Thanks.
>> >
>> > Pat
>>