FileNet p8 content edition:WSE839

Nov 29, 2007 | Tags: none

FileNet p8 content edition
I installed the content engine, then i tried to logon and connect to the enterprize manager, i found this problem "Unexpected exception was detected WSE839: an http response was received that used the following content type:application/soap+xml the following content type was expected: multipart related; type=application/xop+xml."
So what should i do..
I'm using this application server:IBM WebSphere Application Server, 6.0.2.15
I attached printscreen for the error message

Thanks

Attachments

• •  
  • attachment_14019513_Error.bmp 
  • 1.2 MB 
  • Download

• Log in to reply.

Updated on Jul 21, 2009 at 5:47 AM by SystemAdmin

• 
  

  

  SystemAdmin

  693 Posts

  Re: FileNet p8 content edition:WSE839

  Dec 22, 2007  in response to SystemAdmin

  Hi Nasser,
  
  Ah this brings back fond memories of the internal Alpha program! 8o)
  
  There are several web services endpoints that Enterprise Manager can use to connect to the Content Engine in P8 4.0. The two you'll be interested in are:
  
  http://ceserver:9080/wsi/FNCEWS40SOAP/
  and
  http://ceserver:9080/wsi/FNCEWS40MTOM/
  
  MTOM is a SOAP protocol but which uses some cleverness with regards to large binary objects.
  
  I've seen your problem before with early versions of Enterprise Manager when the MTOM url was used, but only the SOAP one would work. Try changing this connection parameter in Enterprise Manager and try again.
  
  Regards,
  
  Adam.

  • Log in to reply.
  • 
    

    

    SystemAdmin

    693 Posts

    Re: FileNet p8 content edition:WSE839

    Apr 5, 2008  in response to SystemAdmin

    Hi Adam,
    
    I encountered the same problem trying to connect to CE from FEM. I tried your advice, change the MTOM to SOAP endpoint. But it gave “The user is not authenticated. Web services login failed: no login modules succeeded.”
    
    Please kindly advice.
    
    Regards,

    • Log in to reply.
    • 
      

      

      SystemAdmin

      693 Posts

      Re: FileNet p8 content edition:WSE839

      Apr 9, 2008  in response to SystemAdmin

      Hi
      
      I have exactly the same error on was 6.0.2.13,
      
      If anyone have found an issue please let me know,
      
      HAKIM

      • Log in to reply.
    • 
      

      

      SystemAdmin

      693 Posts

      Re: FileNet p8 content edition:WSE839

      Jun 20, 2008  in response to SystemAdmin

      Hello,
      
      Ensure you're not using Windows integrated login when logged in as a local machine account (E.g. local machine's Administrator) as the server is trying to authenticate you to the configured directory server.
      
      If that's not your issue, please reply with a screenshot / copy-paste of your WAS server LTPA configuration, as this is most likely the issue (E.g. wrong LDAP search criteria)
      
      Regards,
      
      Adam Fowler
      UKISA ECM Tech Sales, P8 4.0 Specialist

      • Log in to reply.
      • 
        

        

        SystemAdmin

        693 Posts

        Re: FileNet p8 content edition:WSE839

        Jul 21, 2009  in response to SystemAdmin

        fist of we have to check in websphere applycation server on FNGCD and FNGCDXA testconnection.after that u have tobe login filenet enterprise manager snap-in 4.0 on p8 domain Administrator dy deafault ceadmin or we have allredy content engine data base user name and pass word on MSSQL SERVER.

        • Log in to reply.
        • 
          

          

          Priyangi

          1 Post

          FEM error

          Aug 21, 2014  in response to SystemAdmin

          I am also facing the same issue. Is there anyone who was able to resolve the issue. The error is

          
          

          "The user is not authenticated. Web services login failed: no login modules succeeded." Please help !!

          • Log in to reply.
• 
  

  

  hamgem

  111 Posts

  Re: FileNet p8 content edition:WSE839

  Aug 21, 2014  in response to SystemAdmin

  Please check the following in the WebSphere Admin Console.  Content Engine 4.x and higher requires that Application Security be enabled
  within WebSphere in order for the various JAAS login modules to work.

  1. Launch the WebSphere Admin console
  2. Navigate to Security - Global Security (Security - Secure administration, applications and infrastructure in WebSphere 6.1)
  3. Make sure that the "Enable administrative security" and "Enable application security" checkboxes are checked and that the "Use Java 2 security" checkbox is not checked)
  4. Click Apply and save changes
  5. Restart WebSphere when prompted

  If that fixes the issue, switch back to the FNCEWS40MTOM endpoint and see if that works also.

  • Log in to reply.

  Updated on Aug 21, 2014 at 10:24 AM by hamgem