The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

UTILITIES_CONTAINER Error When Attempting to Add Email Filter

Discussion in 'E-mail Discussions' started by urantian, Apr 12, 2012.

  1. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    88
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    Greetings,

    I am attempting to add a filter, to discard messages with specific words in the subject or body. After setting the options and clicking "Create Filter", there is an error.

    INVALID ARGUMENT
    UTILITIES_CONTAINER.JS
    CODE: 0
    LINE: 11

    Is this a known issue? Is there anything I must do to resolve this?

    I have the following configuration:

    CENTOS 6.2 x86_64
    cPanel version 11.32.2 (build 18)
    Apache/2.2.22

    ---Michael
     
  2. royellis8679

    royellis8679 Registered

    Joined:
    Apr 27, 2012
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    I am getting the same error. The only workaround I have found so far is to use Google Chrome.
     
  3. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,381
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    I am seeing this error with cPanel version 11.32.2.28 as well. I am assuming that this was never fixed.

    The error appears to be specific to Internet Explorer, at least I am getting this error with IE8, not sure about other versions of Internet Explorer.
     
  4. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,458
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    This error is addressed in 11.32.3. For reference it is handled by case 59235.
     
Loading...

Share This Page