Products > PSOP > Documentation How come P3e isn't responding to PSOP's scheduling request? After exporting the current P3e schedule PSOP must invoke the P3e scheduler. It uses the Primavera job service component to do this. If the job service component does not respond to PSOP's leveling request, PSOP will provide a warning, shown in blue in this screen shot: This can occur for several reasons: The Job Service component may not be installed. In client/server environments there must be one job service component installed on the network. In a stand-alone installation the job service component should be installed on the computer running P3e. For information on installing the job service component refer to the Primavera Administrator's Guide. The job service component may be installed but may not be running. The job service runs as a windows service and should be started at boot time, but it may have crashed or been manually stopped. Ensure that the job service is running. The machine where the job service is running may not have network access to the database. If network connectivity between the job service machine and the P3e database has been interrupted the job service component will be unable to respond to service requests. The job service may be busy handling other requests. Note that while the PSOP progress dialog indicates the number of pending job service requests (in the example above it says, "1 pending; 0 in progress; 0 complete"), this refers only to the number of pending requests submitted by PSOP. There may be many other jobs pending that were submitted by other programs. If this is the case, the job service component will eventually work through all the pending requests and service PSOP's schedule request. In this case no fix is necessary, you need only wait for the job service to get through the queue of pending jobs. If this happens often, you may want to consider installing the distributed job service which allows multiple machines on the network to service job requests. Back to FAQ