Problem in epm 11.1.1.3 configuration with websphere

hi there,
i am have installed epm 11.1.1.3 with websphere(ver 6.1) , but when i try to configure the workspace with websphere it asks me to give path for web server plug ins where mod_was_ap20_http.dll are installed .
i have also installed ibm http server(ver 6.0.1) but i am still not able to find that file .i chose the web server as ibm http server and apache but in both cases it is showing this problem.
thanks in advance.

So are you seeing this error when accessing only HFM? Do you have planning or Reporting,does those work fine? Provide more details like what documents have you followed.If you disable SSL does it work?
Thanks
Vivek

Similar Messages

  • I have a problem with Mail on my Macbook Pro. It is configurated with a gmail account, and now I can't access the mail. Is it possible to reboot the account or..? Please help:)

    I have a problem with Mail on my Macbook Pro. It is configurated with a gmail account, and now I can't access the mail. Is it possible to reboot the account or..? Please help:)

    The question mark means the computer cannot find a bootable volumes so can;t do anything, That, combined with annoying sounds, strongly suggests a failed hard drive.
    You can ask a "genius" at an Apple Rtail Store to test it but I'm pretty sure the drive is kaput. I'm hoping you had your data backed up.

  • Problem With Cutom Configuration with Object Type

    Dear Guru's
    I am working WebUI, I am facing a problem with Custom Configuration.
    1. The initial requirement to control the visibility for a dropdown event in ERP Quotation.
    2. To this i copied the default configuration to custom configuration with custom Object type and Subtype.
           CONFIG KEY: ZPJQTN
           OBJECT TYPE: ZOTYP_CONFIG
           OBJECT SUB TYPE:  ZSTYPE_CONFIG1
    3. I have created customm fields in enhancement.
    4. Now i chosen my new configuration (ZPJQTN,ZOTYP_CONFIG,ZSTYP_CONFIG1), when i click Show available fields, the custom fields are not showing. Instead the created fields are available at other configuration.
    5. I am able to control the visibility for the standard available fields.But i am not getting the custom created fields
    (Note:  I have created the Object type and Object sub type as follows: SPRO->CRM->UI Framework->Define Object Types
    Object type: ZOTYP_CONFIG Callback class: ZCL_CONFIG_CALLBACK
    Redifned the method: IF_BSP_DLC_OBJ_TYPE_CALLBACK~GET_OBJECT_SUB_TYPES
    Coded as below:
      data: lv_subtype type bsp_dlc_object_sub_type.
      lv_subtype = 'ZSTYP_CONFIG1'.
      append lv_subtype to result.
      lv_subtype = 'ZSTYP_CONFIG2'.
      APPEND lv_subtype to result.
    Now Please suggest me how to achieve this.
    Also please let me know, whether i am following the correct procedure for controlling the visibility.
    Thanks in Advance,
    S.Meganadhan.

    Hi Harshit,
    I added custom fields using AET only.
    I am able to see the field got added in the structure. I am able to access GET and SET methods of the field.
    But the problem is, it is not getting saved. Am i missed any configuration step?
    Please suggest me.
    Thanks in advance,
    Regards,
    S.Meganadhan.

  • Problem in Hibernate 3.0. while configuring with Oracle 9i

    Hi,
    I have a problem in Hibernate 3.0. while configuring with Oracle 9i.
    I make all necessary settings as per the requirement.
    My code successfully running with MYSQL,
    But if tried use Oracle 9i. then System generate the Following Exceptions.
    Please let me know the solution
    DEBUG - initializing class SessionFactoryObjectFactory
    DEBUG - registered: 2c9834f115ccc9360115ccc937600000 (unnamed)
    INFO - Not binding factory to JNDI, no JNDI name configured
    DEBUG - instantiated session factory
    INFO - Running hbm2ddl schema update
    INFO - fetching database metadata
    DEBUG - total checked-out connections: 0
    DEBUG - using pooled JDBC connection, pool size: 0
    ERROR - could not get database metadata
    java.sql.SQLException: ORA-00600: internal error code, arguments: [ttcgcshnd-1],
    [0], [], [], [], [], [], []

    Hi
    I alreay make all necessary chagens in cfg.file but still i have problem
    see the contenet fo .cgf file
    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE hibernate-configuration PUBLIC
    "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
    "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
    <hibernate-configuration>
    <session-factory>
    <property name="hibernate.cglib.use_reflection_optimizer">true</property>
    <property name="hibernate.connection.driver_class">oracle.jdbc.driver.OracleDriver</property>
    <property name="hibernate.connection.url">jdbc:oracle:thin:@sinpunap049:1521:esgdb</property>
    <property name="hibernate.connection.username">scott</property>
    <property name="hibernate.connection.password">tiger</property>
    <property name="connection.pool_size">1</property>
    <property name="hibernate.dialect">org.hibernate.dialect.Oracle9Dialect</property>
    <property name="show_sql">true</property>
    <property name="hbm2ddl.auto">update</property>
    <mapping resource="Student1.hbm.xml" />
    </session-factory>
    </hibernate-configuration>

  • EPM 11.1.2.4 configuration failed

    Hello Masters,
    I have 2 servers configured with EPM 11.1.2.4 planning,
    Server A
    Foundation services
    Planning
    EAS
    Provider services
    Server B
    Essbase server
    EAS
    Provider services
    In server A everything seems fine, post configuration all the URLs are up and running fine. But in server B, I am registering the apps with the same shared services in A.... all goes fine except the deploy to the application server (using the same weblogic domain in A) for EAS and Provider services is failing.
    Please your quick suggestions are highly appreciated.
    Thanks,
    Siva

    Hi John,
    I am sorry to ask you again.... but still... just to confirm.. as per the below installed components on server A & B,... the components that are there in B also configured with the same shared services and weblogic in A... so is there any way to make the Provider services in B work with this setup itself? or do we definitely need to configure this provider services with the webserver in B to get that work?
    Server A,
         -Foundation
              -Weblogic app server
              -Oracle HTTP
              -Static contents
              -Workspace Java web app
              -Foundation services java web app
         -Essbase
              -Provider services java web app
              -EAS Java web app
         -Planning
              -Planning Java web app
    Server B
         -Foundation
              -Static content files (by default it was selected)
              -Oracle HTTP - (I selected manually)
              -Weblogic app server (by default it was selected)
         -Essbase
              -EAS java web app
              -Provider services java web app
              -Essbase server
    Thanks,
    Siva

  • Problem to compile new configuration with imsimta

    After I patched 116568-53, iit was impossible to compile new configuration with "imsimta chbuild". The response is:
    13:57:09.20: Internal error in cl_init -- cannot open command definition file IMTA_BIN:pmdf.cld
    Any one know how to solve this problem?
    Thanks in advance.

    I checked the file as you suggested and i didn't find any tcp_lmtpss-daemon channel so i inserted the following lines:
    [CHANNEL=tcp_lmtpss*]
    master_command=IMTA_BIN:tcp_lmtp_server
    [CHANNEL=tcp_lmtpsn*]
    master_command=IMTA_BIN:tcp_lmtpn_server
    but i obtained the same errors.
    what's wrong? (i am new to sun one messaging server)
    thanks

  • J2ee agent 2.2 configuration problem with Websphere Portal 5.1

    Hi,
    I am trying to configure j2ee agent 2.2 with Websphere Portal server.
    I have followed the document "Sun Java SystemAccess Manager
    PolicyAgent 2.2 Guide for IBM WebSphere Portal Server 5.1.0.2"
    Please see the thread "Problem with Sun's SSO system and Websphere Portal Server integration" for environment related information.
    Also the security on app server has been enabled and is talking to LDAP.
    My aim here is to enable application server (portal server) to autheticate requests.
    I am getting following error when I log into the portal application.
    07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    AmFilter: now processing: SSO Task Handler
    07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    SSOTaskHandler: SSO Validation failed for null
    07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
    07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
    javax.net.ssl.SSLHandshakeException: unknown certificate
         at com.ibm.jsse.bs.a(Unknown Source)
         at com.ibm.jsse.bs.startHandshake(Unknown Source)
         at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
         at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
         at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
         at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
         at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
         at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
         at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
         at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
         at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
         at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
         at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
         at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
         at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
         at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
         at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
         at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
         at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
    07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    URLFailoverHelper: disconnected the connection for availability check
    07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    ERROR: URLFailoverHelper: No URL is available at this time
    07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
    [AgentException Stack]
    com.sun.identity.agents.arch.AgentException: No URL is available at this time
         at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
         at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
         at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
         at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
         at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
         at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
         at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
         at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
         at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
         at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
         at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
         at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
         at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
    07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    AmFilter: result =>
    FilterResult:
         Status      : FORBIDDEN
         RedirectURL     : null
         RequestHelper:
              null
         Data:
              null
    07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
    AmIdentityAsserter: result => TAIResult: status: 403, principal: null, subject: null
    From whatever analysis I have done so far, I believe this issue is related to the personal certificate for sun one webserver (on which access manager & LDAP are installed) not registered with the application server (portal server).
    I am not sure about the way I go by solving the issue.
    Please can anybody help me out.
    Thanks,
    Yaseer
    Message was edited by:
    yazee
    Message was edited by:
    yazee

    Ankush,
    I am getting error as follows in the webserver error log:-
    Error receiving request from 172.23.213.75 (SSL_ERROR_CERTIFICATE_UNKNOWN_ALERT: SSL peer had some unspecified issue with the certificate it received)
    Although I can get into am console but with https://apollo.maxnewyorklife.com/amconsole
    Tried the same thing, but couldnt resolve it. I will give it another go.
    Generally I am getting same error again and again.
    In my amWebsphere log file of j2ee agent (under root\am_wps_agent\agent_001\logs\debug) error I get.....
    07/15/2007 04:19:11:656 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    AmFilter: now processing: SSO Task Handler
    07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    SSOTokenValidator.validate(): Exception caught
    com.iplanet.sso.SSOException: Invalid sessionid formatjava.lang.IllegalArgumentException: Invalid server id in session id com.iplanet.services.naming.ServerEntryNotFoundException: Naming Service is not available.
         at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:205)
         at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:325)
         at com.sun.identity.agents.common.SSOTokenValidator.validateInternal(SSOTokenValidator.java:252)
         at com.sun.identity.agents.common.SSOTokenValidator.validate(SSOTokenValidator.java:157)
         at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:88)
         at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
         at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
         at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
         at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
         at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
         at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
         at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
         at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
         at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
         at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
    07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    SSOTaskHandler: SSO Validation failed for AQIC5wM2LY4SfcwoaNKFd01DvjYeNPbR3wXaa9sMVjcKtwo=@AAJTSQACMDE=#
    07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
    07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
    javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate found
         at com.ibm.jsse2.bw.a(Unknown Source)
         at com.ibm.jsse2.bx.a(Unknown Source)
         at com.ibm.jsse2.bx.a(Unknown Source)
         at com.ibm.jsse2.v.a(Unknown Source)
         at com.ibm.jsse2.v.a(Unknown Source)
         at com.ibm.jsse2.u.a(Unknown Source)
         at com.ibm.jsse2.bx.a(Unknown Source)
         at com.ibm.jsse2.bx.l(Unknown Source)
         at com.ibm.jsse2.bx.startHandshake(Unknown Source)
         at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
         at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
         at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
         at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
         at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
         at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
         at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
         at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
         at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
         at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
         at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
         at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
         at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
         at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
         at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
         at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
         at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
    Caused by: com.ibm.jsse2.util.g: No trusted certificate found
         at com.ibm.jsse2.util.f.b(Unknown Source)
         at com.ibm.jsse2.util.f.b(Unknown Source)
         at com.ibm.jsse2.util.d.a(Unknown Source)
         at com.ibm.jsse2.bn.checkServerTrusted(Unknown Source)
         at com.ibm.jsse2.z.checkServerTrusted(Unknown Source)
         ... 39 more
    07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    URLFailoverHelper: disconnected the connection for availability check
    07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    ERROR: URLFailoverHelper: No URL is available at this time
    07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
    ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
    [AgentException Stack]
    com.sun.identity.agents.arch.AgentException: No URL is available at this time
         at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
         at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
         at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
         at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
         at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
         at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
         at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
         at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
         at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
         at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
         at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
         at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
         at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
         at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
    Thanks,
    Yaseer

  • No wakelarm due to kernel configured with old "Enhanced RTC" options

    Hi,
    I am an Arch newbie building a mythtv box for the first time and it's going really well! Arch really let's me do what I want to do and doesn't hide stuff, thus letting me solve any problems quite easily. However, I have just encountered a bit of a snag so I need some advice.
    I want to have the machine start up in time for scheduled recordings, and so I need to use the RTC wakeup function of the motherboard. The Mythtv wiki suggests using the new /sys/class/rtc/rtc0/wakealarm interface, but Arch (kernel 2.6.23.14, x86_64) seems to be configured in a way that makes it impossible, here's the relevant text from the Mythtv wiki (http://www.mythtv.org/wiki/index.php/ACPI_Wakeup):
    Warning: The wakealarm interface is incompatible with the kernel's old "Enhanced Real Time Clock Support" and "Generic /dev/rtc emulation" options. If your kernel was built with these enabled your kernel log will contain messages such as
    rtc_cmos: probe of 00:03 failed with error -16
    The solution is to rebuild your kernel with the above two options excluded (find them under Drivers -> Character Devices) and the various RTC interfaces (found under Drivers -> Real Time Clock) included. From a .config point of view CONFIG_RTC and CONFIG_GEN_RTC must be unset and, at a minimum, RTC_INTF_SYSFS must be set.
    I get that exact error in my dmesg, and as a result /sys/class/rtc/rtc0/wakealarm does not exist. And since /proc is apparently deprecated I can't use the old option either.
    As far as I can see I have three options:
    * Wait for official updated kernel from Arch team and hope it is fixed
    * Compile my own kernel
    * Use nvram-wakeup or something like that
    Any suggestions on what to do? Other options? I would like to avoid recompiling the kernel if possible, but I guess that would be the quickest solution, right? I plan on reading up on ABS anyway
    Should I file this as a bug?
    Thanks/Johan
    Edit: added link to Mythtv wiki
    Last edited by infoball (2008-01-28 14:29:39)

    Configure the proper proxy server configuration using netsh.
    http://technet.microsoft.com/en-us/library/cc731131(v=WS.10).aspx#BKMK_5
    netsh set proxy proxy-server="http=myproxy;https=sproxy:88" bypass-list="*.contoso.com"
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    I had seen elsewhere that messing with these settings may break the connection to the EMC and EMS.
    If that happens, we will worse off than having an expiring certificate.
    How do we ensure that this does not happen?
    Can we just download the CRL file locally?

  • Error in Proxy configuration with SLM

    > Hello Experts,
    >
    > I am encountring some problems when configuring SLM with Solution Manager 7.01 SP06. I have applied all the settings required for SLM and described on the How-To documentation. I have also read all the forums regarding this issue, but nothing helpful. This issue is the configuration of the proxy settings. We are using SNC for our Saprouter, so I assume that I have to use also the sapserv3 for SLM configuration, with the port 8080.
    >
    > I have added also these entries on Web Service Container in VA:
    > Proxy Host: sapserv3
    > Proxy Port: 8080
    > Exclude List: myhost.mydomain
    > And Save
    >
    > When I execute the configuration check with the transaction "/n/tmwflow/mopzcfg", I have these errors:
    >
    >  <description>Check Proxy settings for download</description>
    > + <config-path>
    > <entry>Configuration path: SDT/SDT|cod-zeus|PS1/SDTExecutionService/DOWNLOAD</entry>
    >  </config-path>
    > - <input>
    >  <entry>Proxy use: true</entry>
    >  <entry>Proxy host: sapserv3</entry>
    >  <entry>Proxy port: 8080</entry>
    >  <entry>Use proxy authentication: false</entry>
    >  <entry>Check HTTP connection to: http://www.sap.com/index.epx</entry>
    >  </input>
    > - <output>
    > <entry>Test Result: FAILED</entry>
    >  </output>
    >- <error>
    >- <MESSAGE>
    >  <ID>java.net.UnknownHostException: BAEx.Failed</ID>
    >  <CREATOR>SLM: java.net.PlainSocketImpl: Line: 201</CREATOR>
    >  <TEXT>www.sap.com</TEXT>
    >  </MESSAGE>
    >  </error>
    >  </CheckResult>
    > - <CheckResult status="FAILED">
    >  <description>Check Proxy settings for web services</description>
    > - <config-path>
    >  <entry>Configuration path: WebServicessAddOn/HTTPProxy</entry>
    >  </config-path>
    > - <input>
    >  <entry>Proxy use: true</entry>
    >  <entry>Proxy host: sapserv3</entry>
    >  <entry>Proxy port: 8080</entry>
    >  <entry>Check HTTP connection to: http://www.sap.com/index.epx</entry>
    >  <entry>Set Proxy-Authorization</entry>
    >  </input>
    > - <output>
    >  <entry>Proxy user:</entry>
    >  <entry>Test Result: FAILED</entry>
    >  </output>
    >- <error>
    >- <MESSAGE>
    >  <ID>java.net.UnknownHostException: BAEx.Failed</ID>
    >  <CREATOR>SLM: java.net.PlainSocketImpl: Line: 201</CREATOR>
    >  <TEXT>www.sap.com</TEXT>
    >  </MESSAGE>
    >  </error>
    >  </CheckResult>
    > - <CheckResult status="FAILED">
    >  <description>Check SMP user and SP web service</description>
    >
    >  Configuration path: SDT/SDT|host|sid/SDTExecutionService/DOWNLOAD
    >
    > please tell me what should I do. Thank you
    Edited by: sapmoo on May 7, 2010 11:59 AM

    is Done...
    I have changed the 8001 Port, by 50100... :S
    this is my First Client with both instances in a same Server than I have to use this port... always I have used 800 + number of Instance...
    Regards

  • IPhone mail configured with Gmail alternate address

    I'm really stuck.. I have a Gmail account (through Google Apps for Business) that I have configured with Mail on my iPhone using Exchange to connect the account. Everything has been working flawlessly, until my employer made a change to our email addresses, so that we had to set up a new domain alias through Gmail as our "send from" account.
    My problem is that I can't for the life of me figure out how to send from this new address from my iPhone.
    Finally, I found a post on the web that seems to explain a way to do this, using the OTHER account setup (IMAP) on the iPhone (instead of either Gmail or Exchange): http://modernerd.com/post/535350679/solved-gmail-ipad-iphone-and-multiple-from  That seemed to do the trick, except then I realized I would no longer have Push email, which I have really come to rely on.
    I tried using the native iPhone Gmail app for a few days, as that seemed to be the only solution, but there's just so many things about that app that really make me miss my good 'ol Apple mail.
    Any other creative solutions out there? Thanks for any advice!

    yeah, it used to work fine because google was supported exchange on mobile devices up until the end of february or so. they let everyone keep their settings the way they were unless they changed them or deleted them, so that's totally expected. The thing with the push is that gmail no longer seems to be supporting that behavior through native apps on mobile devices because it's something they want their exchange customers to pay for

  • Hello i have a problem when i start woorksheet, my computer crash with blue screen sometimes.

    hello i have a problem when i start woorksheet, my computer crash with blue screen.
    OS: Win 2000 pack 2 and dasylab 7.00.05 ;ddi7.02 ;nidaq 7.0
    I hve this problem sometimes and need to reebot my computer.This worksheet is used to generate 4 signals to output and have an acquisition tooin this 4 channels.
    The error is in the blue screen:0x00000076 (0x00000000 , 0x81358300, 0x000001c2, 0x00000000).
    Thanks for your help.

    The DASYLab development team has read your message, and advises that there is insufficient information to be able to even start diagnosing the problem. We suggest that you send a note directly to [email protected], with your full contact information, DASYLab serial number, and the following technical information:
    -The Help-->Report information - this will tell us more about the computer, video and installed memory
    -Installed hardware - what DAQ devices are you using (exact models!)
    -The worksheet that crashes - we need to see how the timing is configured in the worksheet
    -What other programs are running at the same time?
    -Does the worksheet crash every time?
    -Does the NI-DAQ Test Panel work correctly for both inputs and outputs?
    Sorry that we cannot be more help in this forum; we do not have much experience with blue screen under Windows 2000. This is very hard to do, and is almost always related to a hardware problem - either a resource conflict, or problems with one of the installed hardware devices (DAQ, Video, Memory...).
    Regards,
    -cj
    - cj
    Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

  • Storedge 3510 failover configuration with 1 host

    I people.
    I'm new to the storedge configuration.
    I have a Sun storedge 3510 - 2 controllers with 2 x host port fc and 1x drive port each.
    I want to do a simple configuration - connect 1 host to the storedge with failover.
    It's correct to connect the 2 controllers using the drive port - because i want failover?
    It's possible to use only 1 pci single FC adapter in the machine?
    I will connect the machine with the storedge usinge 1 fibre cable,
    I will use the host port FC1. And to do the failover I will connect the 2 controllers
    using the drive port fc3 e fc2. - THIS IS CORRECT?
    My problem is who to connect the cables and who to configure the storedge. I'm
    already connected to the COM Port.
    Another thing i have in the first controller amber light - this is a hardware problem?
    And wath is the best configuration to use with 3510 storedge, one host, and failover?
    Thank you. I need this help for now.. Please.

    Isn't it wonderful when people respond?
    I, too, am running into the same scenario. We have a single 3510FC that is connected to a single host through two controller cards. The drives are configured as a single logical drive under RAID-5. We want to have this configuration multi-pathed for redundancy, not throughput, even though controller cards NEVER fail. [sarcasm] We will be using Veritas VxVM DMP for redundancy.
    Unfortunately, I can only ever see the logical drive/LUN on one controller. The main connection is channel 0 of the primary controller. Whenever I try to configure it to simultaneously be on channel 5 of the secondary controller, the 3510 won't let me do it. I can't figure out how to get the LUN to be assigned to two host channels when one is on the primary controller and one is on the secondary controller.
    I find this to be absurd. Controllers fail. That's all that there is to it. Yet the design of the 3510 (and the 3310 as well) seem to fight like hell whenever you want to spread the logical drives across physical controllers.
    What's the solution to this one, guys?

  • Integration with Websphere 5.0 (EJB 2.0) problems

    Hello all,
    Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
    Websphere 5.0 (using EJB 2.0).
    I have been basically binding a PersistenceManagerFactory into JNDI via
    start-up servlet, however got the exception bellow when I tried to create
    PersistenceManagerFactory (in setSessionContext of the EJB).
    <i>JDOFatalInternalException: Could not perform automatic lookup of EJB
    container's javax.transaction.TransactionManager implementation. Please ensure
    that you are running the application from within an <b>EJB 1.1</b> compliant
    EJB container, and then set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
    value to obtain the TransactionManager.</i>
    The reference to EJB 1.1 actually scared me a bit. Does this imply that
    Kodo (2.4) does not support J2EE 1.3?
    Would you know how to set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
    5.0?
    Thank you,
    Petr

    Petr-
    Is the integration with Websphere 5.0 application server officially
    supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
    Websphere. However, it should be noted that it is not as rigorously
    tested internally at SolarMetric as some other application servers (E.g.,
    JBoss and WebLogic). In short, integration is known to work, but it
    might be a little more rough around the edges than for other application
    servers (as shown in our misspelling of Websphere's TransactionManager
    implementation name).
    How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
    javax.jdo.option.ConnectionFactoryName property (see
    http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
    This is often more appropriate for applications server usage, since it
    allows you to configure pooling and other information from within the
    application server's centralized configuration.
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
    configuration we use for testing with IBM's drivers is:
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
    They shouldn't behave differently (I am guessing that the app driver is
    a type 2 driver or something), but it might be worth a shot to try using
    the net driver. If this fixes the problem, please let us know, because
    it will indicate that Kodo has a deficiency with one of IBM's drivers
    that we should look into resolving.
    Since I have been trying to integrate with App server, this is the
    initialization code that I use to bind PersistenceManagerFactory to JNDI.
    You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
    PM and start persistence operations. Note that you should also be able
    to deploy Kodo as a Resource Adapter (which allows Kodo configuration
    through the centralized Websphere configuration interface). However, I
    doubt this is part of the issue.
    So, in short, I recommend trying the following things:
    1. Using the ConnectionFactoryName to use the DataSource defined for the
    appserver, on the off chance this will fix it.
    2. Using the net driver instead of the app driver.
    3. Seeing if it will work with javax.jdo.option.Optimistic set to false
    If none of these work, please let us know, and we will continue to
    investigate other possible solutions.
    In article <[email protected]>, Petr Bulanek wrote:
    Hello Marc,
    Very good guess. Pretty much the same code worked well without App server.
    In that case, there obviously was no magic related to
    TransactionManagerFactory initialization (see bellow).
    Is the integration with Websphere 5.0 application server officially
    supported? Has anobody (that you know of) done it successfully yet?
    How do I tell Kodo to use existing Datasource managed by app server?
    Here is the basic configuration (URL, class, etc):
    javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2:snet
    javax.jdo.option.Optimistic=true
    javax.jdo.option.RetainValues=true
    javax.jdo.option.NontransactionalRead=true
    We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
    Since I have been trying to integrate with App server, this is the
    initialization code that I use to bind PersistenceManagerFactory to JNDI.
    You may find some funny stuff there.
    The new EESimpleConfiguration(true) construct seems to (by default) read
    the kodo.properties file that is part of the project.
    EEConfiguration conf = new EESimpleConfiguration(true);
    conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
    conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
    EEPersistenceManagerFactory pmf =
                        new EEPersistenceManagerFactory(conf);
    InitialContext ic = new InitialContext();
    ic.rebind(\"KodoPMF\", pmf);
    Thank you,
    Petr
    Marc Prud\'hommeaux wrote:
    Petr-
    It looks like DB2 doesn\'t like our attempt to close the connection
    without a rollback or commit. This is odd, since we have never
    seen this happen in our stand-alone DB2 tests. Can you let us know
    the connection details (driver, connectionURL, etc)?
    In the meantime, one possible workaround may be to turn off
    optimistic transactions (since this will cause the PM to
    only use a single Connection); can you try to specify:
    javax.jdo.option.Optimistic=false
    Also, have you tried to run this code in a non-managed environment
    (e.g., outside the application server)? I would be interested
    to know if it is related to running within an appserver.
    In article <[email protected]>, Petr Bulanek wrote:
    Hi Abe,
    Thank you for a speedo reply. You guys really are on the ball!!!
    As you suggested, the
    \\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
    did the job (for others, please note that the proper package name should
    contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
    Unfortunately, I got another problem. When running a method containing
    query (code bellow),
    I get SQLException complaining about \\\'Invalid transaction state\\\'.
    The method that executes the query is a stateless transactional Session
    bean.
    Thank you for your help,
    Petr
    --------------------------- DB2 - transaction state description
    CLI0116E Invalid transaction state.
    Explanation: There was a transaction in progress when SQLDisconnect was
    called.
    User Response: Call SQLTransact before calling SQLDisconnect.
    --------------------------- Exception ------------------------------------
    [2/01/03 16:34:19:050 EST] 563ddb8a SQL I
    com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
    D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
    PARENTX.JDOCLASSX FROM PARENTX
    [2/01/03 16:34:19:050 EST] 563ddb8a SQL I
    com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
    D:118283149 ] executing statement <369367952>: [reused=1;params={}]
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
    D:118283149 ] close:
    com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
    D:118283149 ] close connection
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
    exception when closing connection
    [2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
    com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
    was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
    Invalid transaction state. SQLSTATE=25000
    atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
    atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
    atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
    atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
    at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
    atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
    at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
    atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
    at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
    at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
    --------------------------- Failing code sample
    try {
                   PersistenceManager pm = factory.getPersistenceManager();
                   Extent ex = pm.getExtent(Parent.class, false);
                   Query q = pm.newQuery(ex, \\\"name==parName\\\");
                   q.declareParameters(\\\"String parName\\\");
                   Collection col = (Collection) q.execute(\\\"James\\\");
                   Iterator iter = col.iterator();
                   Parent pp;
                   Collection ch;
                   while (iter.hasNext()) {
                        pp = (Parent) iter.next();
                        System.out.println(pp);
                        ch = pp.getChildren();
                        Iterator it= ch.iterator();
                        while (it.hasNext()) {
                             System.out.println(it.next());
                   q.closeAll();
                   pm.close();
              } catch (Exception e) {
                   System.out.println(e);
                   throw new EJBException(e);
    Abe White wrote:
    The reference to EJB 1.1 actually scared me a bit. Does this imply that
    Kodo (2.4) does not support J2EE 1.3?
    EJB 2.0 is also supported. Sorry for the confusing error message.
    Would you know how to set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
    WSAD
    5.0?
    Try these settings:
    com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
         com.solarmetric.kodo.ee.InvocationManagedRuntime
    com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
         TransactionManagerMethod=\\\\
         com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
    Marc Prud\'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • Solution Monitoring configuration with solution manager 4.0

    Hi Friends,
    I have to the Solution Monitoring configuration with solution manager 4.0.
    Please provide steps or screen shot if any body having that.

    Hi,
    Check <a href="https://websmp108.sap-ag.de/sapidb/011000358700005479192006E.sim">this.</a> and <a href="https://websmp108.sap-ag.de/sapidb/011000358700006936062005E.sim">this</a>.
    This will solve your problem.
    Feel free to revert back.
    --Ragu
    Message was edited by:
            Raguraman C

  • Ewfmgr: Failed getting protected volume configuration with error 1

    Hello,
    I created a Windows 7-64 image for an Ivy-Bridge VME card. The image contains EWF with RAM-REG.
    The disk was divided into 2 partitions with the windows installer and the image was successfully installed.
    As I'm using RAM-REG, all
    the disk was allocated.  
    After the image was installed I tried to run "ewfmgr c:" and got the current status.
    Then I created a GHOST image and wrote the image on a new card with a clean disk.
    After Windows booted, running "ewfmgr c:" gave:
    Failed getting protected volume configuration with error 1
    I found few threads on this issue but failed to understand what is the right solution.
    Can you help ?
    Thanks,
    Zvika  

    The Problem is always Volumeid related (diskid)
    Explaination:
    Sysprep creates new bcd for the System. - Therefore it's recommended to use sysprep (and SID and so on..) but if you're lazy or don't have Domain Controller and so on or always use physical seperated (better not Internet connected) machines you would be
    totaly fine with non-syspreped Images. You only Need updated/new bcd.
    Captured wim has 'old' bcd (if there is no seperated MSR Partition) you can update this 3 entries within winpe and your Image will boot:
    bcdedit /store c:\boot\BCD /set {BOOTMGR} device boot
    bcdedit /store c:\boot\BCD /set {DEFAULT} device PARTITION=C:
    bcdedit /store c:\boot\BCD /set {DEFAULT} osdevice PARTITION=C:
    (boot could also be Partition=c: or all entries could be boot - and /store is not needed as in winpe bcdedit automatically Redirects the commands into the other/System (found) bcd. But i always recommand to specify the bcd store you want to edit, like in
    this lines)
    The definition of "C:" in this Parameter is 'translated' into volumeid/diskid. - So in the bcd is not "C:" it's some DiskID.
    Instead of the 3 entries you can just create a whole new bcd with updated volumeid/diskids. --> It would be enough to run bcdboot /s C:\ (or whatever the current boot (c:\) Partition is.
    EWF needs to be reconfigured as it also works with Volume/Diskids. So it needs additional command while running (online).
    ewfcfg /install-configuration for win7
    rundll32 ewfdll.dll,ConfigureEwf for win xpe/wes2009.
    Windows Embedded Developer and Scripting Guy //Germany (http://www.wesnext.com)

Maybe you are looking for