Microsoft Knowledge Base Email Alertz

You may experience a memory usage issue when you build an OLAP cube, publish a Project plan, or create or update an enterprise resource on the server that is running Project Server 2003

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 899482 - Last Review: September 18, 2011 - Revision: 3.0

You may experience a memory usage issue when you build an OLAP cube, publish a Project plan, or create or update an enterprise resource on the server that is running Project Server 2003

SYMPTOMS

You may experience a memory usage issue with the Project Server Views Notification Service (VWNotify.exe) on the server that is running Microsoft Office Project Server 2003. The memory usage issue may exist when any one of the following conditions is true:
  • When you build an Online Analytical Processing (OLAP) cube, the build is not completed.
  • When you publish a Project plan, the plan is not published as expected.
  • When you create or update an enterprise resource, the resource is not created or updated.

CAUSE

These issues may occur when the memory usage of a process in the Project Server Views Notification Service does not decrease after a process has been completed.

To determine whether the symptoms that you are experiencing are related to a memory usage issue in the Project Server Views Notification Service on the server that is running Project Server 2003, use Microsoft Windows Explorer to locate the following folder:
C:\Program Files\Microsoft Office Project Server 2003\BIN\Viewdrop
If the Viewdrop folder does not contain any .xml files, all the files have been processed. Therefore, memory usage in the Project Server Views Notification Service should not be an issue.

If the Viewdrop folder contains .xml files, not all the files have been processed. Press CTRL+ALT+DEL, and then click Task Manager. If VWNotify.exe is not listed on the Processes tab, or if VWNotify.exe is listed but there is no CPU usage, there is probably a memory usage issue with the Project Server Views Notification Service.

WORKAROUND

To work around this issue, stop and then restart the Project Server Views Notification Service on each server that is running the Project Server Views Notification Service. The files that are currently in the ViewDrop folder will be processed when the service is restarted.

To stop and then restart the Project Server Views Notification Service, follow these steps:
  1. Click Start, point to Administrative Tools, and then click Services.
  2. Right-click Project Server Views Notification Service, and then click Stop.
  3. Right-click Project Server Views Notification Service, and then click Start.
  4. Repeat these steps two times to make sure that the service is restarted.
Note If you suspect that the Project Server Views Notification Service is not responding or that the Project Server Views Notification Service is processing a task, run a task-killing tool before you restart the Project Server Views Notification Service.

For example, run a task-killing tool such as Kill.exe. Kill.exe may be available in the Microsoft Windows Resource Kit.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
171773  (http://kbalertz.com/Feedback.aspx?kbNumber=171773/ ) How to eliminate a process that is not responding without restarting the computer

APPLIES TO
  • Microsoft Office Project Professional 2003
  • Microsoft Office Project Server 2003
Keywords: 
kbtshoot kbprb KB899482
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate