VWNotify Killing the server CPU and a blocking SQL Process

[Neil]

VWNotify is running at 50% CPU and the service cannot be stopped (it just
said stopping the last time we tried, then rebooted the server to temporarily
fix it)

Also we have a SQL process blocking other processes, the program name is
Microsoft Project Server Views Notification Service
It has over 3000 exclusive locks on Rows and Pages on the
msp_view_proj_tasks_cf/ent/std tables

It says that the last TSQL command batch was
MSP_WEB_SP_QRY_ViewTasks_DeleteViewTable2;1

Does anybody have any ideas as to the SQL process and the vwnotify process
We have SQL2Ksp3 and Project server 2003 on the same serve, Sharepoint is on
a different server. We have not Service Packes Project Server to SP1 yet,
but will do tomorrow.

TIA

Neil.

 

[Ray McCoppin]

vwnotify process is the server side process that moves the data from the MSP
tables to the MSP_VIEW tables. As it does this it deletes the data in the
MSP_View tables and put a table lock on the table. The vwnotify process
does this as project are being published. If you look in the viewdrop folder
bin/viewdrop you might see xml files in this folder these are the project
publishes that are pending.

 

[Neil]

Thanks for the reply Ray,
I now understand the process, however do you have any idea why this process
cannot be stopped (it just says stopping) I cannot see any KB articles about
any issues with it.
The viewdrop folder has 174 XML files in it over the last 4 days

thanks

 

[Gary L. Chefetz [MVP]]

Neil:

The service is not stoppable because it's hung trying to process the xml
files in the queue. Move the xml files to a temporary directory and you
should be able to stop the service. You should probably reboot at this
point. Next, got the Server application event log and you're likely to see
somewhat of a bloodbath of errors. Post of some of these so that we might
help you figure out what's going wrong.

 

[Ray McCoppin]

If the SQL server gets into a blocking situation the service may not be able
to stop. doing a Gary said may work. But I have seen the service get lock
too the point it required a reboot to clear the blocking.

Good luck...
--
Ray McCoppin

http://www.randsmanagement.com
SRS gantt charts

 

[Shew]

My experience has been that just starting and stopping the service
won't do it either - a reboot is usually required. If the reboot
doesn't work, doing as Gary said (moving xml files to temp folder) then
rebooting should "unstick" the service from the last transaction it's
processing. Then add back the xml files - a few at a time - and they
will be processed.

J.J.