Project Server 2007 - Queue taking a long time to complete

J

Jay-pm

Hi,

We have recently implemented Project Server 2007 in the following config.

Project Server 2007 and PWA running on a Intel Xeon CPU 1.870Ghz 1.79Ghz
with 3.87GB RAM running Windows 2003 Enterprise SP2. It connects to a SQL
2005
server.

We never had Project Server before so there was no upgrade. We are only
creating new Project plans created in Project Pro 2007.

What we find strange and Project managers find very fustrating is that a
save or check in of a project is taking up to 12 hours. After doing one
publish job, we are unable to do anything further with that project plan, as
it allows only read mode till the job is completed. It shows Publish job 0%
complete waiting time 7 secs. But when I come in the morning (IST time)
around 09.30 am, all jobs are completed. The time for completion is exactly
12 hours from the time the queue was started.

Also I noticed that the Queue Cleanup takes up the first two positions, the
moment I start a job in the queue. All the other jobs then wait for the 12
hours as mentioned above. Each and every job takes the exact 12 hours. Can
you please help me as to why this is happening. I am able to cancel jobs.

Thanks in advance

Regards,

Jay
 
B

Ben Howard

This is just a thought...
Make sure your server is set to the right time, it sounds to me as though
you might be on AM when it should be PM, and the server is set to 12 hours
fast....
 
J

Jay-pm

Hi,

I checked the time. THe time on the server hosting project server is on EST,
The regional settings and the web application settings in the Sharepoint
administration all show the same EST settings. Our server is located in East
Coast and we work from india on the server using the internet.

Please guide me further in resolving the issue.

Thanks in advance

Regards,

Jay
 
J

Jay-pm

Hi,

We are 9 and half hours ahead in India. Thanks for the link. Will check the
time zones of the SQL Server and get back to you.

Regards,

Jay
 
J

Jay-pm

Hi,

Thanks a ton. Like you said it was the wrong time in the SQL Server.

Regards,

Jay
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top