I
irish_archer68
Hello, thank you in advance for replying to this posting...
I am in a frustrating situation and am seeking for any wisdom
possible.
I have a project server 2007 environment, connected to SQL Server
2005, running WSS 3.0 and sitting on a Windows server 2008 OS.
In the project server environment, I have an IMS (integrated master
schedule) with about 14-15 inserted projects. One of the projects,
with 2100 tasks and interlinked with other schedules that are part of
the IMS, is taking an eternity to save. It literally will say '95%'
saved and will take over an hour to save. Now, the project will not
even save. It times out and fails in the Queue. It never gets above
the 95% saved state.
This same schedule saved in about 8-10 minutes yesterday.
I have tried to restart the MS Project Services, restarted the queue,
ensured other projects can still be saved and published, and I am
still having the issue.
Has anyone seen this before?
Is this IMS and the size of this schedule too large for the small -
virtual server environment we have installed?
What does Microsoft consider a 'large' schedule vs a small or
medium?
Will special characters in the task name cause this issue?
I am in a frustrating situation and am seeking for any wisdom
possible.
I have a project server 2007 environment, connected to SQL Server
2005, running WSS 3.0 and sitting on a Windows server 2008 OS.
In the project server environment, I have an IMS (integrated master
schedule) with about 14-15 inserted projects. One of the projects,
with 2100 tasks and interlinked with other schedules that are part of
the IMS, is taking an eternity to save. It literally will say '95%'
saved and will take over an hour to save. Now, the project will not
even save. It times out and fails in the Queue. It never gets above
the 95% saved state.
This same schedule saved in about 8-10 minutes yesterday.
I have tried to restart the MS Project Services, restarted the queue,
ensured other projects can still be saved and published, and I am
still having the issue.
Has anyone seen this before?
Is this IMS and the size of this schedule too large for the small -
virtual server environment we have installed?
What does Microsoft consider a 'large' schedule vs a small or
medium?
Will special characters in the task name cause this issue?