V
Victor
Problem: The scheduled OLAP cube build does not work sometimes.
Background: Windows Server 2003, Project Server 2003 SP1, SQL Server
2000 SP3, Analysis Services SP3. Project Server is on one machine and
SQL Server is on another.
I noticed this by checking in PWA on the Admin tab and see when the
last build had happened. Initially, we thought it was just a glitch
and just bounced the server. However, what we have found is that the
service Project Server Scheduled Process Service (PJSCHSVC.EXE)
appeared to be hung and was taking up a lot of memory resources. Most
of time, we cannot stop the service the traditional way and we would
have to go through task manager to kill the process.
We have tried changing the scheduled start time. We did this because
we thought there was a conflict with database backups or possibly virus
scanning. Every time we change the start time or restart the service,
the build seems to be fine for some period of time (it varies from 1
day to maybe 14 days. I had not been keeping metrics. I am now) and
then it just stops. I have not noticed any errors in the event viewer
that state something went wrong with the OLAP build. Also the DBA did
not notice anything on the SQL Server box stating there was a problem.
The problem only seems to exist with the scheduled build. There has
never been a problem if we just do a manual build.
I know this is somewhat vague. What I am looking for are just
suggestions on things to look at or possibly a suggestion on how to
monitor the system in an effective manner. The key here is that most
of the time the build is fine. This means to me that there aren't
problems with the accounts we are using or permissions, or anything
else that is typically the problem. Once I stop and start the service,
the build works fine again (for awhile).
It almost seems as if the service is kicked off and it is trying to do
the build, but the service never gets a response back stating the build
is finished so it just hangs which then causes it to not build the next
scheduled time. Not sure how to track that down though.
Any thoughts would be much appreciated.
Victor
Background: Windows Server 2003, Project Server 2003 SP1, SQL Server
2000 SP3, Analysis Services SP3. Project Server is on one machine and
SQL Server is on another.
I noticed this by checking in PWA on the Admin tab and see when the
last build had happened. Initially, we thought it was just a glitch
and just bounced the server. However, what we have found is that the
service Project Server Scheduled Process Service (PJSCHSVC.EXE)
appeared to be hung and was taking up a lot of memory resources. Most
of time, we cannot stop the service the traditional way and we would
have to go through task manager to kill the process.
We have tried changing the scheduled start time. We did this because
we thought there was a conflict with database backups or possibly virus
scanning. Every time we change the start time or restart the service,
the build seems to be fine for some period of time (it varies from 1
day to maybe 14 days. I had not been keeping metrics. I am now) and
then it just stops. I have not noticed any errors in the event viewer
that state something went wrong with the OLAP build. Also the DBA did
not notice anything on the SQL Server box stating there was a problem.
The problem only seems to exist with the scheduled build. There has
never been a problem if we just do a manual build.
I know this is somewhat vague. What I am looking for are just
suggestions on things to look at or possibly a suggestion on how to
monitor the system in an effective manner. The key here is that most
of the time the build is fine. This means to me that there aren't
problems with the accounts we are using or permissions, or anything
else that is typically the problem. Once I stop and start the service,
the build works fine again (for awhile).
It almost seems as if the service is kicked off and it is trying to do
the build, but the service never gets a response back stating the build
is finished so it just hangs which then causes it to not build the next
scheduled time. Not sure how to track that down though.
Any thoughts would be much appreciated.
Victor