Value string (primary key) could not pass to entity bean

database server 3.23.57
application server Jboss 3.07
ide jbuilder8
i am using session bean to wrap entity bean where it calls for entity bean to lookup the databse.
value entered in client application could not be passed from session bean to entity bean.
it is a jtextfield thta capture string as input which is the customer id. it is also the primary key. session bean managed to get the value but it was then became null when i pass to entity bean.
may i know wat could be the problem that is causing this?
application server not suporting this feature???? or it is th elogic problem .. or i have miss ot some code somewhere.?

Sounds like a code problem.

Similar Messages

  • Primary Key could not be changed without dropping the index

    I want to change the primary key in the "alter table modus". I don't see any INDEX. I refresh the DATA and get the following error:
    ORA-01785: ORDER BY-Angabe muss Positionsnummer von Ausdruck der SELECT-Liste enthalten
    Version: 3.0.03 Build-03.97
    Edited by: mesch181 on Apr 17, 2011 12:31 PM

    That error message has nothing to do with dropping an index.
    There is a bug in current versions of sql developer where the query used to populate the data grid is stored and if the table structure changes the query can be invalid. Try closing the table and re-opening it.

  • Composite Primary Key in M:N CMP Entity Bean Relationship

    Dear Sir/Madam,
         We are creating an Enterprise Application for our institute using EJB 2.0 specifiactions. In the course of developement, we are facing a problem in writing the CMP Entity Beans with EJB Relationships.
         We are having many to many relationship between two beans such that the primary key of one Entity Bean (let's call it A), serves as the foreign key of another Entity Bean (let's call it B). Further, this primary key of A as foreign key in B, participates in the composite key of B.
         The EJB Specifications require that the primary key field(s) of any bean (B, in our case) declared in the Primary Key class should be the subset of the 'cmp-field' declared in the deployment descriptor for that bean. As I said earlier, we have many to many relationship at play. Hence, we require to keep the foerign key in the 'cmr-field' in lieu of 'cmp-field'. In short, the component of primary key is in 'cmr-field' while, it is needed in both 'cmp-field' and 'cmr-field'. That's perfect from Database point of view but illogical from CMP Entity Bean's view.
         How can we write the deployment descriptor for such a CMP (BMP is working fine for above scenario) Entity Bean? Also, how can we write the Primary Key class? The problem is not just to find the solution, but find under the hood of EJB 2.0 specifications.
         Please help.

    I think you should realise that it would not be convenient to use CMP for everything. It is difficult to define complex relations using CMP. Mostly BMP os preferd since it gives the flexibility for the bean developer.
    Regards
    xH4x0r

  • Cannot modify value of primary key field after lookup.

    I realize this could be a WebSphere problem, but I don't know if it is an EJB problem or what? So I'm posting anyway, and adding Duke Dollars in the hopes someone out there has encountered this.
    Okay, I'm using WebSphere Studio Application Developer 4.0.3.
    I am using an EJB that has three primary key fields.
    I use the primary keys to lookup the bean.
    I then want to update the value of one of the primary keys.
    So I create a setter and getter method for that primary key field.
    I then can call the set method, but it does nothing.
    I get no errors.
    It compiles.
    I rebuild, regenerate access beans, and redeploy and rmic.
    I can use ctrl-space to see the functions in the JSP editor.
    However, the set function never gets called for some reason, and I get no runtime exception either.
    For example, if I do this in my code:
    MyBeanFactory myBean = new MyBeanFactory();
    MyBeanKey myBeanKey = new MyBean(name,age,city);
    MyBean myBean = myBeanFactory.findByPrimaryKey(myBeanKey);
    // this function doesn't do anything, because it's a primary key field
    // but it does compile and I get no runtime errors
    myBean.setCity("Orlando");
    // this function works fine, presumably because it isn't a primary key
    myBean.setState("Florida");Questions;
    Is there a restriction that says I can't update the value of a field if it is marked as a primary key?
    If not, what could I be doing wrong?

    Looks like your appserver is working as per the specification.
    Check this out:
    Question
    How can I update the primary key field in a CMP Entity Bean?
    Derived from
    A question posed by Shanks75 shanks75
    Topics
    Java:API:EJB:EntityBean:CMP, Java:API:EJB:2.0
    Author
    Tim Duggan
    Created
    Oct 9, 2001
    Answer
    You cannot change the primary key field of an Entity bean. Refer to page 130 of the EJB 2.0 specification, it states "Once the
    primary key for an entity bean has been set, the Bean Provider must not attempt to change it by use of set accessor methods
    on the primary key cmp-fields. The Bean provider should therefore not expose the set accessor methods for the primary key
    cmp-fields in the component interface of the entity bean."
    A work around to update a primary key field, would be to remove and then an re-create the bean.
    taken from here:
    http://www.jguru.com/faq/view.jsp?EID=515864

  • Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.

    html,body{padding:0;margin:0;font-family:Verdana,Geneva,sans-serif;background:#fff;}html{font-size:100%}body{font-size:.75em;line-height:1.5;padding-top:1px;margin-top:-1px;}h1{font-size:2em;margin:.67em 0}h2{font-size:1.5em}h3{font-size:1.16em}h4{font-size:1em}h5{font-size:.83em}h6{font-size:.7em}p{margin:0
    0 1em;padding:0 .2em}.t-marker{display:none;}.t-paste-container{;left:-10000px;width:1px;height:1px;overflow:hidden}ul,ol{padding-left:2.5em}a{color:#00a}code, pre{font-size:1.23em}
    I get this message on two different machines installing SQL2014 developer edition, a Windows 7 and a Windows 8 machine. Both machines have SQL2005 through SQL2012 developer machines installed and working great. I have tried uninstalling all SQL2014 stuff and
    installing again making sure I was running as an Administrator to no avail. 
    How do I look at sys.key_encryptionswhen the server will not start to finish installation?
    The links in the log only provide the  "We're Sorry" message.
    This is the first error dialog info
    TITLE: Microsoft SQL Server 2014 Setup
    The following error has occurred:
    Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%25400x4BDAF9BA%25401306%254026
    The SQL Server error log has the message in the title.
    2014-04-04 17:02:17.49 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
     Feb 20 2014 20:04:26 
     Copyright (c) Microsoft Corporation
     Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    2014-04-04 17:02:17.49 Server      UTC adjustment: -4:00
    2014-04-04 17:02:17.49 Server      (c) Microsoft Corporation.
    2014-04-04 17:02:17.49 Server      All rights reserved.
    2014-04-04 17:02:17.49 Server      Serverprocess ID is 9236.
    2014-04-04 17:02:17.49 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'HP EliteBook8760w'.
    2014-04-04 17:02:17.49 Server      Authentication mode is MIXED.
    2014-04-04 17:02:17.49 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Log\ERRORLOG'.
    2014-04-04 17:02:17.49 Server      The service account is 'NT Service\MSSQL$SQL2014'. This is an informational message; no user action is required.
    2014-04-04 17:02:17.49 Server      Registry startup parameters: 
      -d C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\DATA\master.mdf
      -e C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Log\ERRORLOG
      -l C:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\DATA\mastlog.ldf
    2014-04-04 17:02:17.49 Server      Command Line Startup Parameters:
      -s "SQL2014"
      -m "SqlSetup"
      -Q
      -q "SQL_Latin1_General_CP1_CI_AS"
      -T 4022
      -T 4010
      -T 3659
      -T 3610
      -T 8015
    2014-04-04 17:02:17.79 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2014-04-04 17:02:17.79 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-04 17:02:17.79 Server      Detected 8142 MB of RAM. This is an informational message; no user action is required.
    2014-04-04 17:02:17.80 Server      Using conventional memory in the memory manager.
    2014-04-04 17:02:17.92 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english1033)
    2014-04-04 17:02:17.95 Server      Perfmoncounters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-04 17:02:17.96 Server      Query Store settings initialized with enabled = 1, 
    2014-04-04 17:02:17.97 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-04 17:02:17.97 Server      This instance of SQL Server last reported using a process ID of 8760 at 4/4/2014 5:02:08 PM (local) 4/4/2014 9:02:08 PM (UTC). This is an informational message only; no user action is required.
    2014-04-04 17:02:17.97 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-04-04 17:02:17.97 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-04-04 17:02:18.00 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-04 17:02:18.00 spid7s      Warning ******************
    2014-04-04 17:02:18.00 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-04 17:02:18.01 spid7s      Starting up database 'master'.
    2014-04-04 17:02:18.02 Server      Software Usage Metrics is disabled.
    2014-04-04 17:02:18.07 Server      CLR version v4.0.30319 loaded.
    2014-04-04 17:02:18.11 spid7s      8 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2014-04-04 17:02:18.24 spid7s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2014-04-04 17:02:18.25 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-04-04 17:02:18.26 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-04 17:02:18.34 spid7s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
    2014-04-04 17:02:18.40 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-04 17:02:18.40 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-04 17:02:18.44 spid7s      SQL Trace ID 1 was started by login "sa".
    2014-04-04 17:02:18.44 spid7s      Server name is 'TOMGROSZKO-HP\SQL2014'. This is an informational message only. No user action is required.
    2014-04-04 17:02:18.46 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-04 17:02:18.46 spid16s     Initializing the FallBackcertificate failed with error code: 1, state: 20, error number: 0.
    2014-04-04 17:02:18.46 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-04-04 17:02:18.46 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-04 17:02:18.46 spid16s     TDSSNIClientinitialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-04 17:02:18.46 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-04 17:02:18.46 spid16s     TDSSNIClientinitialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2014-04-04 17:02:18.46 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-04 17:02:18.46 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-04-04 17:02:18.46 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-04 17:02:18.46 spid16s     SQL Server could not spawn FRunCommunicationsManagerthread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    And a copy of the install log.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893606
      Start time:                    2014-04-04 16:23:39
      End time:                      2014-04-04 17:06:25
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  TOMGROSZKO-HP
      Machine processor count:       8
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2005      SQL2005              MSSQL.1                        Database Engine Services            
        1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005      SQL2005              MSSQL.1                        SQL Server Replication              
        1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005      SQL2005              MSSQL.1                        Full-Text and Semantic Extractions for Search 1033      
              Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005      SQL2005              MSSQL.1                        SharedTools                
                 1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005      SQL2005              MSSQL.2                        Analysis Services              
             1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005      SQL2005              MSSQL.3                        Reporting Services - Native            
     1033                 Developer Edition (64-bit) 9.00.1399.06    No         Yes       
      SQL Server 2005                                                          DTS        
                                 1033                 Developer Edition (64-bit) 9.4.5069        No        
    Yes       
      SQL Server 2005                                                          Tools        
                               1033                 Developer Edition (64-bit) 9.4.5069        No         Yes
      SQL Server 2005                                                          ToolsClient      
                           1033                 Developer Edition (64-bit) 9.4.5069        No         Yes    
      SQL Server 2005                                                          ToolsClient\Connectivity  
                  1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005                                                          ToolsDocument      
                         1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005                                                          ToolsDocument\BOL    
                       1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005                                                          ToolsDocument\Samples    
                   1033                 Developer Edition (64-bit) 9.4.5069        No         Yes       
      SQL Server 2005                                                          NS          
                                1033                 Developer Edition (64-bit) 9.4.5069        No         Yes
      SQL Server 2008 R2   SQL2008R2            MSSQL10_50.SQL2008R2           Database Engine Services                 1033          
          Developer Edition    10.51.2550.0    No         Yes       
      SQL Server 2008 R2   SQL2008R2            MSSQL10_50.SQL2008R2           SQL Server Replication                   1033        
            Developer Edition    10.51.2550.0    No         Yes       
      SQL Server 2008 R2   SQL2008R2            MSSQL10_50.SQL2008R2           Full-Text and Semantic Extractions for Search 1033                 Developer
    Edition    10.51.2500.0    No         Yes       
      SQL Server 2008 R2   SQL2008R2            MSAS10_50.SQL2008R2            Analysis Services                        1033  
                  Developer Edition    10.51.2500.0    No         Yes       
      SQL Server 2008 R2   SQL2008R2            MSRS10_50.SQL2008R2            Reporting Services - Native              1033          
          Developer Edition    10.51.2550.0    No         Yes       
      SQL Server 2008 R2                                                       Management Tools - Basic      
              1033                 Developer Edition    10.51.2550.0    No         Yes       
      SQL Server 2008 R2                                                       Management Tools - Complete    
             1033                 Developer Edition    10.51.2500.0    No         Yes       
      SQL Server 2008 R2                                                       Client Tools Connectivity      
             1033                 Developer Edition    10.51.2500.0    No         Yes       
      SQL Server 2008 R2                                                       Client Tools Backwards Compatibility  
      1033                 Developer Edition    10.51.2500.0    No         Yes       
      SQL Server 2008 R2                                                       Client Tools SDK        
                    1033                 Developer Edition    10.51.2500.0    No         Yes       
      SQL Server 2008 R2                                                       Integration Services      
                  1033                 Developer Edition    10.51.2550.0    No         Yes       
      SQL Server 2012      SQL2012              MSSQL11.SQL2012                Database Engine Services                 1033  
                  Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012      SQL2012              MSSQL11.SQL2012                SQL Server Replication                   1033
                    Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012      SQL2012              MSSQL11.SQL2012                Full-Text and Semantic Extractions for Search 1033            
        Developer Edition    11.1.3000.0     No         Yes       
      SQL Server 2012      SQL2012              MSSQL11.SQL2012                Data Quality Services                    1033
                    Developer Edition    11.1.3000.0     No         Yes       
      SQL Server 2012      SQL2012              MSAS11.SQL2012                 Analysis Services                    
       1033                 Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012      SQL2012              MSRS11.SQL2012                 Reporting Services - Native              1033  
                  Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012                                                          BIDS        
                                1033                 Developer Edition    11.1.3128.0     No         Yes  
      SQL Server 2012                                                          SQL Server Data Tools - Business
    Intelligence for Visual Studio 2012 1033                                      11.1.3402.0     No         Yes       
      SQL Server 2012                                                          Integration Services    
                    1033                 Developer Edition    11.1.3128.0     No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3128.0     No         Yes    
      SQL Server 2012                                                          Master Data Services    
                    1033                 Developer Edition    11.1.3000.0     No         Yes       
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Downloads\SQL2014\SQL\x64\setup\
      Installation edition:          Developer
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 NT Service\SQLAgent$SQL2014
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\SQLData\MSSQL\SQL2014\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.SQL2014\OLAP\Config
      ASDATADIR:                     C:\SQLData\MSSQL\SQL2014\OLAP
      ASLOGDIR:                      C:\SQLData\MSSQL\SQL2014\OLAP
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSOLAP$SQL2014
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            TomGroszko-HP\Tom Groszko
      ASTEMPDIR:                     C:\SQLData\MSSQL\SQL2014\OLAP
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140404_162339\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, MDS
      FILESTREAMLEVEL:               3
      FILESTREAMSHARENAME:           SQL2014
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQL2014
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              c:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           c:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQL2014
      INSTANCENAME:                  SQL2014
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SQL2014
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  C:\SQLData\MSSQL\SQL2014\Backup
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQL2014
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           TomGroszko-HP\Tom Groszko
      SQLTEMPDBDIR:                  C:\SQLData\MSSQL\SQL2014\Engine
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  C:\SQLData\MSSQL\SQL2014\Engine
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  true
      TCPENABLED:                    0
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140404_162339\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Master Data Services
      Status:                        Passed
      Feature:                       Integration Services
      Status:                        Passed
      Feature:                       Data Quality Client
      Status:                        Passed
      Feature:                       Analysis Services
      Status:                        Passed
      Feature:                       Reporting Services - SharePoint
      Status:                        Passed
      Feature:                       Reporting Services Add-in for SharePoint Products
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140404_162339\SystemConfigurationCheck_Report.htm
    Any suggestions for what step to take next will be appreciated.
    Thanks
    Tom G.

    Hi Tom,
    Sorry for the delay. We can exclude the media factor since you were able to install it on VM with this media.
    If I understand correctly, Shanky said “Abve message can also appear due to corrupt profile so deleteting old profile and creating new one and using this to install would also help.Make sure you always RK on setup.exe and select run as administrator” which
    means your user account may be corrupted rather than the Virtual account. You can create a new Windows user account and use it to log into the system. Then, re-try the installation.
    Additional information:
    http://windows.microsoft.com/en-us/windows/create-user-account#create-user-account=windows-8
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Null in Composite Primary Key and "Primary keys must not contain null"

    Hello all.
    I'm a newbie concerning to JPA/EJB3, but I was wondering if toplinks doesn't support composite primary keys with null in some field (something perfectly right in any RDBMS).
    I used JDeveloper (I'm using Oracle 10g database and JDeveloper 10.1.3.2.) wizards to generate JPA classes and I checked out generated files (with annotations), so they should be right (by the way, other O-R mappings for my model are working right, but this one).
    I'm getting the next error:
    Exception Description: The primary key read from the row [DatabaseRecord(
         TSUBGRUPOSLDI.CD_GRUP => 01
         TSUBGRUPOSLDI.CD_SUBGRUP => null
         TSUBGRUPOSLDI.CG_POBL => 058
         TSUBGRUPOSLDI.CG_PROV => 28
         TSUBGRUPOSLDI.DSCR => Sanidad)] during the execution of the query was detected to be null. Primary keys must not contain null.
    Compound primary key is (CD_GRUP, CD_SUBGRUP). No foreign keys, no joins (only a NamedQuery: "select o from ..."). It's the simplest case!
    I checked out that everything runs ok if there's no "null" value in CD_SUBGRUP.
    After some research (this and other forums) I'm beginning to believe that it's not supported, but not sure.
    Am I doing sth wrong? If not, what is the reason to not support this? Will it be supported in the future?
    Thanks in advance.

    Null is a special value and in many databases is not comparable to another null value (hence the isNull operator) and may pose problems when used to uniquely identify an Entity. TopLink does not support null values within a composite PK. As the nullable column is most likely not designated as a PK within your database table (many databases do not allow this) I recommend updating the Entity PKs to match that of the database.
    --Gordon                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • While updating my ipad to ios7, I could not pass the terms and conditions screen where I had to agree or disagree. It just didn't move pass that screen. I can't do anything to go forward or back. It's just stuck there.

    While updating my ipad to ios7, I could not pass the terms and conditions screen where I had to agree or disagree. It just didn't move pass that screen. I can't do anything to go forward or back. It's just stuck there.

    Try to reset the device:
    Device Reset (won't affect settings/data/music/apps/etc)
    1. Press and hold (& continue to hold) BOTH the Sleep/Wake button & the Home button.
    2. Continue to hold BOTH (ignoring any other messages that may show) until you see the Apple logo on the screen.
    3. Release BOTH buttons when you see the Apple logo and allow the device to boot normally.

  • License Key could not be installed , Invalid user or password

    Hello,
    My HANA studio working fine before 2 days. But after installing one CISCO VPN client software on my PC ,I am not able to connect to our HANA box.
    Sometime it gives License Key could not be installed(though we have valid license) and sometime Invalid user or password (though my collegues are able to login into system with same user id details from their machine).
    I have already reinstalling the HANA studio but no luck. I am able to ping the HANA box as well.
    Any hint will be much appreciable.
    With Regards,
    Rafikul Hussain

    Hi,
    Thanks for your reply.
    No, there is no mismatch between the HANA Studio and the HANA DB server. As both of them are in SPS3 (rev 21).
    I asked my colleagues to reset my password and after that from my PC, studio->properties when I put my initial password it will ask to change the password ,i have entered my new password but once its over it shows me the message that the invalid user & password.
    regards,
    Rafikul Hussain

  • Named query, primary keys must not contain null

    We have an question on the named query. Here is the scenario:
    Class JoinClassC (id, name, desc, comment) is mapped to two tables Join_Table_A (id, name, description) and Join_Table_B (id, name, comments); Join_Table_A is the primary table; two tables are associated via primary key.
    Defined a named query (findByName, ReadAllQuery/SQL) for JoinClassC descriptor. The sql is:
    SELECT a.ID,a.NAME,a.DESCRIPTION,b.COMMENTS FROM JOIN_TABLE_A a, JOIN_TABLE_B b WHERE a.NAME=#name AND a.ID=b.ID AND a.NAME=b.NAME
    Getting QueryException while executing the query. Here is the trace:
    [3/2/05 13:50:24:795 EST] f8b62aa SystemOut O 2005.03.02 01:50:24.795--ServerSession(738697921)--Thread[Servlet.Engine.Transports : 4,5,main]--Connection(1095574161)--SELECT a.ID,a.NAME,a.DESCRIPTION,b.COMMENTS FROM JOIN_TABLE_A a, JOIN_TABLE_B b WHERE a.NAME='persistence' AND a.ID=b.ID AND a.NAME=b.NAME
    2005.03.02 01:50:24.835--ClientSession(1127670417)--Thread[Servlet.Engine.Transports : 4,5,main]--Exception [TOPLINK-6044] (OracleAS TopLink - 10g (9.0.4.4) (Build 040627)): oracle.toplink.exceptions.QueryException
    Exception Description: The primary key read from the row [DatabaseRow(
         USER04.JOIN_TABLE_B.ID =&gt; 2
         USER04.JOIN_TABLE_A.NAME =&gt; persistence
         USER04.JOIN_TABLE_A.DESCRIPTION =&gt; FJF Persistence Fram
         USER04.JOIN_TABLE_B.COMMENTS =&gt; The Persistence Fram)] during the execution of the query was detected to be null. Primary keys must not contain null.
    Query: ReadAllQuery(com.ford.it.persistence.unittest.dom.JoinClassC)Local Exception Stack:
    Exception [TOPLINK-6044] (OracleAS TopLink - 10g (9.0.4.4) (Build 040627)): oracle.toplink.exceptions.QueryException
    Exception Description: The primary key read from the row [DatabaseRow(
         USER04.JOIN_TABLE_B.ID =&gt; 2
         USER04.JOIN_TABLE_A.NAME =&gt; persistence
         USER04.JOIN_TABLE_A.DESCRIPTION =&gt; FJF Persistence Fram
         USER04.JOIN_TABLE_B.COMMENTS =&gt; The Persistence Fram)] during the execution of the query was detected to be null. Primary keys must not contain null.
    Query: ReadAllQuery(com.ford.it.persistence.unittest.dom.JoinClassC)
         at oracle.toplink.exceptions.QueryException.nullPrimaryKeyInBuildingObject(QueryException.java:542)
    Adding b.ID to the sql select will solve the problem.
    Question: does the primary key must be present in the sql select to run this kind of query? Any way to work around the restriction?
    Your help would be greatly appreciated.
    Haiwei

    The problem is that you need to select both primary keys for the multiple table descriptor.
    i.e.
    SELECT a.ID,a.NAME,a.DESCRIPTION,b.ID, b.COMMENTS FROM JOIN_TABLE_A a, JOIN_TABLE_B b WHERE a.NAME=#name AND a.ID=b.ID AND a.NAME=b.NAME
    Your SQL needs to return the same data that TopLink would have selected, which includes the primary key for both tables. TopLink expects both a.ID and b.ID fields in the select, because your only select one and the field names are the same TopLink thought the ID field was for b.ID not a.ID, if you select both it will be ok.

  • Unexpected error;Primary key does not exist:CmscdomPK version=2,name=J2E

    Hi I am getting the following error when i try to access the CMS related WebDynpro application.
    First time i am able to access the CMS.I created the domain and track.after that i edited the Domain tab with new domain name J2E.During that time i tried to save the domain,its throughing the Primary key does n't exist error.I closed the application.Again when i tried to access the CMS.Its throughing the following error.
    <b>Error stacktrace:
    com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException: Unexpected error; inform your system administrator - Primary key does not exist: CmscdomPK version=2,name=J2E
         at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseMessageInternal(MessageManager.java:254)
         at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseMessage(MessageManager.java:964)
         at com.sap.cms.ui.wl.Custom1.hasTracks(Custom1.java:860)
         at com.sap.cms.ui.wl.Custom1.wdDoInit(Custom1.java:277)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdDoInit(InternalCustom1.java:990)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.doInit(DelegatingCustomController.java:73)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.initAttributeMapping(AttributeInfo.java:596)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:456)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:373)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:252)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)</b>
    What causing the problem.I am not finding the way,where can i rectifything problem
    Regards
    Usman

    Hi Usman,
    Domain ID and CMS Server ID are also stored in the SLD when you create these for the first time. As of now you can just create one Domain and One CMS Server id.
    If you have to edit it you may have to do the following.
    1. Delete all the tracks under the domain id and the CMS server id.
    2. Then in SLD. go to HOME -> CONTENT BROWSER -> SUBSET = LANDSCAPE DESCRIPTION
    In the CLASS dropdown please select Change Management Domain. Select the domain that you had created and delete it.
    Again in the CLASS dropdown select Change management Server. Select it and delete.
    Note: Please ensure that all the tracks have been deleted before you delete SLD entries.
    Now login to CMS again and create the Domain and CMS server again.
    If possible please try this some where on a test machine if possible and then try in actual scenario.
    Hope this helps.
    Regards
    Sidharth

  • The key could not be obtained. You may need to use the -keystore argument with the specified keystor

    I am getting this error: "The key could not be obtained. You may need to use the -keystore argument with the specified keystore type." when trying to create an apk file using adt. I am following the steps mentioned here: http://blogs.adobe.com/ria/2010/10/28/creating-an-apk-file-using-flashbuilder-4-0/

    Could a self save from premiere cause the problem? By this i don't mean the autosave.
    Autosave is the only kind of 'self save', and is not likely to 'cause' project corruption.
    thnx for your reply. My first question came from a remark of Gakhue:
    "I'm using CS6 and I got that warning, I copied my project file on usb stick and re-opened in a different computer using CS5, it then gave me a few warnings about changing the name and saving it to auto save fault, I clicked away and said yes to each one"
    So i wondered how he did it
    The second question came from the fact that my last save was from 17 minutes after i left my studio. And i am not talking about an autosave. It was the main save of the corrupted videofile. And since i did not do it myself, the only option left is that Premiere did it? Or that premiere does not use the internal Mac clock and is on a different time. Which is not the case (just tested).

  • MOM Setup key could not be opened

    I'm having problems deploying SCOM 2012 SP1 Agents to a 2008 R2 Server.  below ports are open.  I pushed the agent install to the target server and the momagentservice installed and is running as well as the files for the install are pushed but
    the Agent does not automaticlly install.  The only error message I see is MOM is unable to open Key in the momagentmangemnt.log
    Any help would be appricated.  Thank you
    12:18:59 PM : CServiceModule::Init : m_bService is set to true. HResult: 0
    12:18:59 PM : CServiceModule::Start : Service flag is set
    12:18:59 PM : CServiceModule::SetServiceStatus : State: 2, Error: 0
    12:18:59 PM : CServiceModule::SetServiceStatus : State: 2, Error: 0
    12:19:00 PM : IsCurrentMOMServerInstalled : MOM Setup key could not be opened.
    12:19:00 PM : CServiceModule::_RegisterFile : Before LoadLibrary
    12:19:00 PM : CServiceModule::_RegisterFile : After LoadLibrary
    12:19:00 PM : CServiceModule::_RegisterFile : Before GetProcAddress
    12:19:00 PM : CServiceModule::_RegisterFile : After GetProcAddress
    12:19:00 PM : CServiceModule::_RegisterFile : After FreeLibrary
    12:19:00 PM : CServiceModule::RegisterFile : Success return
    12:19:00 PM : CServiceModule::RegisterFile : WaitForSingleObject return  HResult: 0
    12:19:00 PM : CServiceModule::SetServiceStatus : State: 4, Error: 0
    01:22:40 PM : CServiceModule::SetServiceStatus : State: 3, Error: 0
    01:22:40 PM : CServiceModule::SetServiceStatus : State: 3, Error: 0
    01:22:41 PM : IsCurrentMOMServerInstalled : MOM Setup key could not be opened.
    01:22:41 PM : CServiceModule::_RegisterFile : Before LoadLibrary
    01:22:41 PM : CServiceModule::_RegisterFile : After LoadLibrary
    01:22:41 PM : CServiceModule::_RegisterFile : Before GetProcAddress
    01:22:41 PM : CServiceModule::_RegisterFile : After GetProcAddress
    01:22:41 PM : CServiceModule::_RegisterFile : After FreeLibrary
    01:22:41 PM : CServiceModule::RegisterFile : Success return
    01:22:41 PM : CServiceModule::RegisterFile : WaitForSingleObject return  HResult: 0
    01:22:41 PM : CServiceModule::SetServiceStatus : State: 1, Error: 0
    Source                 
    Dest                     
                  Protocol                              
    Port
    SCOM                         
             Target Server                       TCP/UDP                             
    135
    SCOM                                  
    Target Server                       UDP    
    137
    SCOM                                  
    Target Server                       UDP    
    138
    SCOM                                  
    Target Server                       TCP     
                                  139
    SCOM                                  
    Target Server                       TCP                                       
    445
    SCOM                                  
    Target Server                       TCP     
                                  5723
    Target                                  
    SCOM                  
    TCP                                       
    5723
    Target                                  
    SCOM                  
    TCP                                       
    51906
    Target                                  
    SCOM                  
    TCP                                       
    51909

    Hi,
    I recommend you disable firewall and antivirus on the server and install the agent again.
    Also, I recommend you to post it at SCOM forum for further help:
    System Center - Operations Manager forums
    http://social.technet.microsoft.com/Forums/en-US/home?category=systemcenteroperationsmanager
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • I got problem on installing iTunes. When I clicked iTunes out, two windows popped out. One said the procedure entry point CFAttributed String Create Mutable could not be located in the dynamic link library Core Foundation.dll.

    I got problem on installing iTunes. When I clicked iTunes out, two windows popped out. One said the procedure entry point CFAttributed String Create Mutable could not be located in the dynamic link library Core Foundation.dll. and one just said *Itunes was not installed correctly.  Please re install I Tunes Error 7 (windows error 127) . I've tried uninstalling and reinstalling it. But either way cant work. I really need some of your help! PLS HELP ME!

    For general advice see Troubleshooting issues with iTunes for Windows updates.
    The error shares a similar pattern to that in the third box, so a similar approach should work. Look for CoreFoundation.dll in C:\Program Files (x86)\Common Files\Apple\Apple Application Support, delete it, then repair Apple Application Support.
    The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down page in case one of them applies.
    Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
    tt2

  • ApEx BIP report using webservice: could not convert null to bean field

    Seems like a pretty straightforward problem but I don't manage to find a solution.
    I have a BI Suite implementation on one server.
    And a database with ApEx on another server.
    I want to call a BIP report from within my ApEx application using the webservices (runReport) available in BIP 11g.
    I used soapUI to test my webservice. Result : OK
    When called from within ApEx, ApEx gives me a succes message but the report isn't generated. Instead the console on the BIP server shows the following error:
    <Sep 12, 2012 10:28:37 PM BST> <Error> <org.apache.axis.encoding.ser.BeanPropert
    yTarget> <BEA-000000> <Could not convert null to bean field 'sizeOfDataChunkDown
    load', type int>
    'sizeOfDataChunkDownload' is a field of the webservice that is left empty.
    That indeed is the only difference between my soapUI test and the ApEx situation.
    In soapUI I removed all empty fields. In ApEx this does not seem possible...
    Some extra information:
    - the webservice is created on this WSDL : /xmlpserver/services/v2/ReportService?wsdl
    - it's defined as a SOAP v2
    - no basic authentication
    - the reports are defined in the BIP environment; not in ApEx
    Edited by: kcaluwae on 13-sep-2012 3:19

    I overlooked a not nillable field...

  • Why Interceptors are not used in Entity beans?

    Why Interceptors are not used in Entity beans?
    Interceptors can be used in MDB, Session bean but not in Entity bean....why so?
    Thanks,
    Rahul.

    Hi,
    why batch updations are not prefered in entity beansPlease refer the specification of ejb and find out what the entity bean is meant for.In short the emtity bean represents the object state which can be persisted.
    Talking regarding the batch updations does not make sense , also the entity bean represents the row of the table mapped to the Object(java Object).
    Regards
    Vicky

Maybe you are looking for