Quantcast
Channel: ProjectWise Design Integration Wiki
Viewing all articles
Browse latest Browse all 1890

Distribution Services does not work with the set file enabled

$
0
0
Current Revision posted to ProjectWise Design Integration Wiki by Dana Guthrie on 11/11/2022 7:58:18 PM

 Product(s):ProjectWise Dynamic Composition Server (Distribution Services)
 Version(s):08.11.11.559
 Area: PDF
 Original Author:Mantas Nauseda, Bentley Technical Support Group

Problem Description

When trying to run the Distribution Service job that has the set (InterPlot Settings file) enabled it gives the error (when using Bentley Navigator as a print engine):
Failed -- IPARMENG, The MicroStation IPARM engine did not complete successfully.
- Milepost code: 0

And error (when using MicroStation as a print engine):
Failed -- CMDERR, executed ipmstnsrvm, which failed

When trying to use the same ProjectWise document and the same settings file in the InterPlot Organizer it worked fine without any errors.

Reason

When the set file is used in the Distribution Job the Print Engine process is started with the Current Directory that is the Distribution service working directory (a shared folder on the network, for example: \\ server_name.domain.com\ds_working\1\282_35)

User had the system Path added that syntax was not correct. One of the paths was added like: \c:\windows. This way when the print engine (MicroStation or Navigator) was locating the required dll files it was trying to load the dll from the path: \\ server_name.domain.com\ds_working\1\282_35c:\windows
The syntax of the path is not correct and it failed to load the dll. The whole process stopped at this stage.

Steps to Resolve

To resolve the issue the System Path was fixed (backslash was removed from: \c:\windows to: c:\windows)

Tags: PDF, ProjectWise Dynamic Composition Server, path, Distribution Services, SELECTsupport, Problem Solving

Viewing all articles
Browse latest Browse all 1890

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>