Unable to start File Listener from SMA


I have created a file listener rule. When clicked on the Test Connectivity button, it is showing as sucsess. But it is giving the following error when I am tring to start the listener from SMA:


Start Listener Status
Listener 'Data-Admin-Connect-FileListener:CSVFileListener.(com.pega.pegarules.integration.engine.internal.services.file.FileListener)/0' failed to start because of the following error:
   Failed to launch listener, com.pega.pegarules.pub.PRException: Failed to start listener: File.CSVFileListener From: (BB6B44B76021A465A1D2FAC4D1EEDE5BB:(MBean Access))


Can anyone please help?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

May 29, 2014 - 5:58pm

By looking at the error it seems that its failed because of Service that  mentioned in File Listner: "CSVFileListener"

In order to better understand the issue, you may diagnose the issue to see what exacly happening while you are starting the listner from SMA.


Two ways that you can Add diagnosing details.

1.On the Listner Rule Form, at Properties tab




The Remote Logging feature streams the contents of the Process Commander log file to the LogFactor5 application installed on your workstation. When you add your workstation as an active logger through the Logging and Tracing > Remote Logging menu item in the System Management application, your workstation receives all messages for all processes running on the server. To view only those log messages that are about the service rule this listener listens for, complete the fields in this section. Remember to start the LogFactor5 window on your workstation before using this form to identify your workstation as a logger.

Remote Host

Optional. Enter the network name of your computer. See How to install and use remote logging.


Optional. Enter the TCP/IP port number that the log4j package on your computer listens on. By default this port is 8887.

,save the instance


OR at SMA:

Select  one of the JVM on the left hand side, Under Logging and Tracing, Click on Remote Logging

and fill in the Remote Host(Your computer host name) and Remote Port (8887)


and then Click on Add.

Also download and install the SocketServer

Monitor the activity log using SocketServer(LogFactor 5) when you are starting the Listner.


One More thing we can try out is:

Change the Start Up Option, like if it is currently configured to Run on All Nodes,change it to either Node Based Start Up or Host Based Start Up and Click on Button: Reset Start Up and Save.

And see if that help anything.

February 4, 2015 - 12:20am

Hi All,


I am also facing same issue while starting Emaillistener from SMA ,What is solution for this ,can some body guide on this.




February 4, 2015 - 9:50am

Shiva, Plese bounse the JVM once and see if that helps.

February 20, 2015 - 11:07am

On service file just uncheck authentication. Your listener will work.

May 13, 2015 - 11:57am

1. Goto SMA (System Management Application).

2. Click on the node in which you want to run the File Listener.

3. Expand the 'Advanced' option available on the Left Pane.

4. Upon expanding, click on the 'Authorization Management'.

5. Check which Access Group is pointing to the Application Version in which your listener's Service File is created.

  • e.g. Your Service File rule is created in Ruleset- XYZ:03.28.01.
  • Ruleset XYZ:03.28.01 is present Application ABC:03.28.01.
  • Access Group AG1 is pointing to Application ABC:03.28.01.
  • So, check if AG1 is available or not in the list which appears at Step 5.

6. If, AG1 is available in the list, then update the Access Group of your Service Package of the Listener to AG1 and Save and try Starting the File Listener again.

This should work.




April 27, 2016 - 11:15am

Hello All ,


I tried all the above solution .But none of them is working . PRPC 7.1..7




July 11, 2016 - 10:35am

Provide Requester login details in File Listener Rule . This worked for me

Requestor log-in

These two fields are used as user name and password if the Service File rule requires requestors to be authenticated.



User Name

Optional. Select the Operator ID that this listener uses to log in. The Operator ID determines the access group (and so the RuleSet list) of the listener.


Optional. Enter a password for this Operator ID.