September 19, 2002 at 4:38 am
hello,
when trying to view the current activities on one of our servers (SQL2K SP1) via Enterprise Manager we get a 1222 timeout error. Checked for lock-timeout setting which is '-1'. We never had problems before - did not change server-settings (but we migrated to new version of application using this server). When re-starting the server all will be ok for a while - then the problem occurs again and will only be solved by restarting the server. sp_who & sp_lock show no clues. Did anybody else face similar problem?
Greetings from Germany,
Kerstin
September 19, 2002 at 7:24 pm
Do you have any job that can be causing this problem. Did you tried with sp_who2. This one shows more info.
With sp_lock, did any spid had an exclusive lock?
September 20, 2002 at 1:30 am
the only jobs running are maintenance-plan jobs. when viewing the existing locks there are some exclusive ones - but they are released in quite reasonable times. the interesting thing is that people working on this server are doing this exclusively via application (which is Navision) - and they should not touch other than user-tables, as far as i understood this from my colleague in charge there for Navision administration. of course we cannont look inside their code - so we cannot be sure what's going on. We will run Profiler today to watch the actions inside that db.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply