Possible Reasons a Job May Fail or Not Finish
- The job may fail if you try to use an unsupported application (or an unsupported version of a supported application) as the i-model publishing engine.
- The job may fail if you do not use a file's native application as the i-model publishing engine.
For example, using OpenBuildings Designer as the i-model publishing engine might cause the job to fail if your job contains Bentley OpenPlant Modeler files.
- The job may fail if the application you selected as the i-model publishing engine is reporting errors.
In some cases these errors do not affect publishing, yet they still cause the job to fail. To force Bentley Automation Service to ignore these errors, create an environment variable called PowerPlatformProcessor_IgnoreErrors and set the value to 1, then restart the computer.
(To create the variable, go to .)
- The job may not finish if you turn off one of the computers on which Bentley Automation Service components are installed.
In this case, the job will appear to be running indefinitely (job status is Queued or In Progress) when in fact nothing is happening. The job will resume processing where it left off when the offline computer is turned on again. The job does not need to be resubmitted in this case.
- A file may not finish processing and the job may never return to a finished state if the MicroStation processor has to bounce (shut down and restart) during the processing of a file, and it bounces more than is currently allowed by the processor's Maximum
Attempts to Process Message setting.
The job should continue to run and other files in the job may (or may not) process successfully.
- The MicroStation processor may bounce if it exceeds the current value of processor's Maximum Memory Usage (after
processing message) setting.
If this is the case you can increase the memory setting to accommodate the file in question. It may also bounce if something has caused an extension to the MicroStation processor to fail.