function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
BhuBhu 

Error : Email2Case set up : notification service userID.

I get the following error when I try to use email2case .
 
008-06-23 15:01:40,684 1828 [main] INFO  com.sforce.SalesforceAgent  - com.sforce.mail.EmailService  loaded as a timer service.
2008-06-23 15:01:44,137 5281 [Timer-0] INFO  com.sforce.mail.GenericClient  -    processing 3 messages
2008-06-23 15:01:54,153 15297 [Timer-0] ERROR com.sforce.mail.GenericClient  - Routing Addresses are not set up correctly to run Email To Case.
2008-06-23 15:01:54,153 15297 [Timer-0] ERROR com.sforce.mail.GenericClient  - com.sforce.exception.InvalidConfigurationException: Routing addresses are not setup correctly.
com.sforce.exception.InvalidConfigurationException: Routing addresses are not setup correctly.
 at com.sforce.mail.GenericClient.handleMessage(GenericClient.java:638)
 at com.sforce.mail.GenericClient.receive(GenericClient.java:409)
 at com.sforce.mail.EmailService$EmailWorker.run(EmailService.java:211)
 at java.util.TimerThread.mainLoop(Unknown Source)
 at java.util.TimerThread.run(Unknown Source)
2008-06-23 15:01:54,153 15297 [Timer-0] ERROR com.sforce.SalesforceAgent  - No configuration value has been provided for the notification service userID.
com.sforce.exception.InvalidConfigurationException: No configuration value has been provided for the notification service userID.
 at com.sforce.SalesforceAgent.processNotification(SalesforceAgent.java:368)
 at com.sforce.SalesforceAgent.processNotification(SalesforceAgent.java:447)
 at com.sforce.mail.GenericClient.handleConfigurationException(GenericClient.java:748)
 at com.sforce.mail.GenericClient.receive(GenericClient.java:416)
 at com.sforce.mail.EmailService$EmailWorker.run(EmailService.java:211)
 at java.util.TimerThread.mainLoop(Unknown Source)
 at java.util.TimerThread.run(Unknown Source)
2008-06-23 15:02:40,686 61830 [Timer-0] INFO  com.sforce.mail.EmailService  - Shutting down service...
 
Any pointers will be very helpful to resolve this issue
werewolfwerewolf
Did you not set up the notify section of sfdcConfig.txt?

    <notify>
        <notifyEmail>admin@your_company.com, E2CSupport@your_company.com</notifyEmail>
        <from>sample_user@your_company.com</from>
        <host>smtp.mail.your_company.com</host>
        <port>25</port>
        <user>sample_user</user>
        <password>123456</password>
        <service>com.sforce.mail.SMTPNotification</service>
    </notify>
BhuBhu

Yes , I have done all that correctly

email2case.txt

<configFile>
    <server1>
        <url>mail.mycompany.net</url>
        <protocol>imap</protocol>
        <userName>myaccount@your_company.com</userName>
        <password>***********</password>
        <interval>1</interval>
        <inbox>Inbox</inbox>
        <readbox>Inbox.Processed</readbox>
        <errorbox>Inbox.Error</errorbox>
    </server1>
</configFile>

sfdcConfig.txt

<configFile>
    <sfdcLogin>
        <url>https://www.salesforce.com/services/Soap/u/7.0</url>
        <userName>salesforcelogin</userName>
        <password>salesforce password</password>
        <loginRefresh>30</loginRefresh>
        <timeout>5000</timeout>
    </sfdcLogin>
    <notify>
        <notifyEmail>admin@your_company.com, E2CSupport@your_company.com</notifyEmail>
        <from>sample_user@your_company.com</from>
        <host>smtp.mail.your_company.com</host>
        <port>25</port>
        <user>sample_user</user>
        <password>123456</password>
        <service>com.sforce.mail.SMTPNotification</service>
    </notify>
    <attachments>
        <largeAttachmentDirectory> directory </largeAttachmentDirectory>
        <largeAttachmentURLPrefix> directory </largeAttachmentURLPrefix>
        <largeAttachmentSize>0.5</largeAttachmentSize>
    </attachments>
    <services>
        <com.sforce.mail.EmailService>email2case.txt</com.sforce.mail.EmailService>
    </services>
</configFile>

I get this error com.sforce.exception.InvalidConfigurationException: Routing addresses are not setup correctly.

Is there something I am missing here.

TIA

 

 

 
werewolfwerewolf
Did you actually set up any routing addresses in Setup->Customize->Cases->Email-to-case?  You need to do that.
BhuBhu

I did , however i got the issue resolved. The created a new routing address to an IMAP server account and it worked. I am not sure how  it works now.

Thanks
Joe_IpsenJoe_Ipsen

FYI, I have run into this error twice now:

 

2009-05-13 18:34:31,315 246730597 [Timer-0] ERROR com.sforce.mail.GenericClient  - Routing Addresses are not set up correctly to run Email To Case.
2009-05-13 18:34:31,315 246730597 [Timer-0] ERROR com.sforce.mail.GenericClient  - com.sforce.exception.InvalidConfigurationException: Routing addresses are not setup correctly.
com.sforce.exception.InvalidConfigurationException: Routing addresses are not setup correctly.
    at com.sforce.mail.GenericClient.handleMessage(GenericClient.java:644)
    at com.sforce.mail.GenericClient.receive(GenericClient.java:412)
    at com.sforce.mail.EmailService$EmailWorker.run(EmailService.java:211)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
2009-05-13 18:35:28,911 246788193 [Timer-0] INFO  com.sforce.mail.EmailService  - Shutting down service...
2009-05-13 18:35:28,911 246788193 [Timer-0] INFO  com.sforce.mail.EmailService  - Service: postinicc.pobox.corp.google.com
   User: postinicc
   Parent: com.sforce.mail.ImapSSLClient@8ffafa
2009-05-13 18:35:28,911 246788193 [Timer-0] INFO  com.sforce.SalesforceAgent  - Service postinicc.pobox.corp.google.com:0:postinicc:INBOX successfully de-registered                                           

 

 . . . and have found it was due to the Service Account that is performing all of the Email2Case work did not have access to a new Case Record Type.  Grant the service account access to all of the record types and restart the service and it did not have that problem any longer.
Joe_IpsenJoe_Ipsen

Oh, and I found the answer above here:

 

http://community.salesforce.com/sforce/board/message?board.id=JAVA_development&message.id=5332