Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Command line -P path not working in PEGA BIX

SA-27617

Summary



The user has configured PEGA BIX and created Extract rule to generate XML file.

The issue is when they try to run the extract rule from windows command line and even after mentioning the path using command line parameter "-P" , the extract rule not placing XML file in mentioned path.


Error Messages



The following errors are triggered in the bix logs

ERROR - Path: =D_PRM_GlobalResourceSettings.DLLBixFileLocation mentioned in the output directory is invalid
ERROR - Unable to process DLL-US-Leasing-PRM-Work-DApp: Path: =D_PRM_GlobalResourceSettings.DLLBixFileLocation mentioned in the output directory is invalid


Steps to Reproduce



1. Create one Extract rule with output format XML.
2. Update prconfig.xml with necessary changes.
3. Update RunBix.bat file with necessary changes and do mention a network shared directory which has restricted access.

Root Cause



Issue is with the directory which is being used, as the machine from which extract is being executed, does not seem to have adequate access to write files to the specified directory.

Resolution



A different path has been provided and verified using Windows explorer if it has access to write and read file from the directory provided.

​BIX extraction is successful when a valid path has been provided.

Using "-P" as command line parameter, will override the configuration provided for schema directory and XML extract directory in the rule, as both of them would be extracted to the directory mentioned using "-P".

 

Published September 14, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us