I have been working in an enviroment wich was working well unill last week. We found that the queue was not working at all. All the projects were getting enqueued but all of them were in state Waiting... After trying restarting all the services and see that was not a good solution we try to find the error.
Wen we create a new Shared Services Provider this will create two timer job definitions wich are needed for Projecct Server:
Shared Services timer job.
Project Server Synchronizing job for "SharedServicesprovidername".
If there is one of these Timer Jobs Definitions wich doesn't exists then project server sites will not work properly.
What's the solution? there are more than solution for this problem but the most easy is to create another Shared Services Provider, change the associations for the web applications to the new Shared Services Provider and delete the old one.
If you have properties defined in old Shared Services Provider (profiles, excel services, BDC, search....) you will need to configure it again in the new SSP.
Suscribirse a:
Enviar comentarios (Atom)
4 comentarios:
Muchas gracias, estoy probando la solución y veremos si resulta.
De todos modos, sería bueno comentar las otras posibilidades de solucionar este error.
Is there another solution to recreate the Project Server Synchronizing Job?? I have the same problem and don't want to recreate a new SSP.
Rgrds
nico
I haven't tested it yet, but I'm sure that you can recreate it programming.
To activate a job you should use a code like this:
// install a job
SPJobDefinition pojectJob = new SPJobDefinition("Project Server Synchronizing Job", site.WebApplication,server,SPJobLockType.None);
SPMinuteSchedule schedule = new SPMinuteSchedule();
schedule.BeginSecond = 0;
schedule.EndSecond = 59;
schedule.Interval = 5;
projectJob.Schedule = schedule;
projectJob.Update();
thanks carlos, I finally created a new SSP and it did the trick
Publicar un comentario