Datatargets not finding in infopackage level.

hi ,
    i can see the datatargets in infopackage but in processing tab i cant find psa and datatargets parallel.so please give solution for this.

Please make sure that the transfer rules are set to "PSA" and not "IDOC". (R/3 to BIW)
Also, are you going from 1 BIW target to another? If so, you need to do some data mart setup. (BIW to BIW)
Cheers!
/smw

Similar Messages

  • Warning: Could not find the customization level value for document

    Hi All,
    I am trying to upload the translation for one of the page at responsibility level.
    I am getting following warning when running the below command.
    java oracle.jrad.tools.trans.imp.XLIFFImporter $APPL_TOP/xmci/12.0.0/fr-CA/Translated/ARIACCTDETAILSPAGE.xlf -username apps -password apps -dbconnection "$AD_APPS_JDBC_URL"
    Warning: Could not find the customization level value for document "/oracle/apps/ar/irec/accountDetails/webui/customizations/responsibility/51688/ARIACCTDETAILSPAGE".
    The same is working fine if the translation is for some attribute at site or function level.
    Did anyone faced this kind of issue.
    Thanks,
    Anoop

    Anoop,
    I am sure you would have verified the responsibility id in the target instance is 51688(may be source instance your resp id is 51688 and in target it is different).
    Have a look at this below notes, it might help.
    1077267.1 - Unable To Move Resp Level OA Personalization From 1 Env To Another
    848851.1 - Attempting To Upload XML File Generates Error: Could not find the customization level value for document
    Thanks.
    With Regards,
    Kali.
    OSSI.

  • Selection field not coming at Infopackage level

    Hi All,
    I am facing a strange problem.There is one field which is marked for selection at the datasource level.In the R/3 side we are getting that field as selection if we go for t-code RSA3.
    But in the BW system when we create an Info-package we do not get the same field under Data selection tab.We have tried to change the data type of that field and replicated the datasource but still it didnt worked.
    Please suggest on this issue as it a very high priority issue for us.
    Thanks in advance.
    Regards,
    Kshitij

    Hi Naveen,
    1) This is not a standard datasource.
    2) In RSA2 that field is marked for selection and it is showing for selection if we go for RSA3.
    3) Could you please elobrate more on what do you mean by 'attribute column'.???
    In R/3 system we have the same field for selection ( this field is related to 'no of days'=zdays[info object name]) but at Info package level in BW system it does not appear for selection.
    If you have time can we call you.Please pass on your number to me.
    Regards,
    Kshitij

  • Infopackage Idocs in status 2 - could not find code page for receiver system

    Hi,
    We just migrated our production system from BW 7.01 non unicode to BW 7.4 on HANA.
    We now encounter issues with idocs while loading data into bw from our ECC5 source. When we analyze idocs in the source system it appears with the message "could not find code page for receiver system"
    One weird thing is that the idoc seems to have been created before we started the infopackage in bw.. We controlled system time and AS time and everything seems ok.
    We did not encounter this issues on our previous migration test runs..
    Hope someone can help
    Christophe

    Hi,
    Thanks for responding. We finally found out what the problem was.
    We have two applications servers on our ECC with 2 different OS. One of them could not reach the new BW HANA server.
    Regards
    Christophe

  • Why I can not find field:Level in Project Hierarchy in BAPI_BUS2054_NEW?

    Dear experts,
        Why I can not find the field of "Level in Project Hierarchy" in structure BAPI_BUS2054_NEW?
    I only define the data to upload wbs:
    PROJECT DEFINITION
    PROJECT DESCRIPTION
    PROJECT PROFILE
    WBS Element
    WBS description
    Can you tell me which fields must to upload?
    Looking forward to your reply.
    Many thanks.
    Merryzhang

    Anyone can help me ?I need the field "Level" in BAPI_BUS2054_NEW,But I can not find it.

  • Not able to find out invoice level for customer collection

    Hi Experts,
    We are not able to find out  invoice level payment details for the collection
    They are provided collection amount and reference no, but here problem is customer have more than 20 company codes and they cleared in multiple co.codes , also user not maintained any reference while clearing the invoice, so we only able to find out the collection amount but we dont know for which invoice it is cleared.
    can any one help us,

    The given link take to the window where CPU patch for all the quarter available.
    The Critical Patch Updates released to date are listed in the following table.
    Critical Patch Update Latest Version/Date
    Critical Patch Update - October 2012 Rev 1, 16 October 2012
    Critical Patch Update - July 2012 Rev 1, 17 July 2012
    Critical Patch Update - April 2012 Rev 2, 19 July 2012
    If I click on Critical Patch Update - October 2012 its takes to the window for selectin the database version (11.2.0.3). From there it goes to the Patch Set Update and Critical Patch Update October 2012 Availability Document [ID 1477727.1] which I had already checked.
    There for the database products it shows the below option.
    Table 9 Patch Availability for Oracle Database 11.2.0.3
    +*<moderator edit - deleted MOS Doc content - pl do NOT post such content - it is a violation of your Support agreement>*+
    It doesnt have the sepreate CPU patch. The below CPU patch is for the OC4J. I had a check.
    Thanks
    SHIYAS M

  • Change the packet size at infopackage level

    Hi, Experts:
    All loads (full or delta) in the system can split data into small packets expect for one full load, which has almost 2 million records into 1 packet. It overflows the memory and fails.
    I found the following settings for this datasource when click from menu "Scheduler"->"DataS. Default Data Target":
    "Maximum size of a data packet in kByte" = 20000
    "Number of Data Packets per info-IDoc" = 10
    "Number of Data Packages per Delta Request" = 0
    "Update Method" - full Upload
    It seems to me that the load should split data into small packets.
    Can someone please tell me why only this load still puts all 2 million records in one big packet?
    Thanks,
    Jenny

    Some update on more information:
    The datasource is 0FI_GL_8, a standard SAP datasource for transaction data. I think it is an old datasource because I can not find any on-line document for its details from SAP help website. I was told that this datasource is not Delta capable. That is why full load is used.
    I also tried to reduce the package size settings for this datasource from "Scheduler"->"DataS. Default Data Target". But whatever I changed did not affect the way that this load is putting all records in one big data package.
    I assume the set up in Transaction RSCUSTV6 is for every infopackage across the whole system unless setup differently at infopackage level? I checked in RSCUSTV6, it is set up as the following:
    FrequencyStatus-IDOC = 10
    Package size = 30000
    Partition size = 1.000.000
    I also checked in ECC system with transaction SBIW for the control parameters for data transfer from the source system. It has the following set up for the source system:
    Max. (kB) = 20000
    Max. lines = 0
    Frequency = 10
    Max. Proc. = 3
    Max. DPs = 0
    From all the checked results, I still don't get why every other datasource loading can split data into small data packages, but only this one datasource can not. And why whatever I changed from the infopackage to reduce the size did not affect how it is splitting the data package.
    Any more inputs?
    Thanks,
    Jenny

  • Can not find Save botton in log configure.

    Hi,
    I want to change the log severity level from some application. I went to log configuration and I clicked the button for "change on selected node". However, I could not find any "Save" or "Apply" button. When I exit the page, system showed me "you will lost the unsaved data". Does anybody know how to save it? Thank you.

    Hi,
    Which SP level you are on? If you are on NW04 SPS12 or NW04s SPS02 or below upgrade that to NW04 SP 13 of the J2EE Engine 6.40 or NW04s SPS 03 of the J2EE Engine 6.40s or higher level.
    If it is not possible due to any reason apply sap.com_tclmwebadminlog_configwd.sda
    by following  the note 656711.
    Reward points for useful answers
    Regards,
    Phani

  • Org.hibernate.PropertyNotFoundException: Could not find a getter for id in

    [skumar@aithdell3 events]$ java EventManager
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment <clinit>
    INFO: Hibernate 3.2.3
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment <clinit>
    INFO: hibernate.properties not found
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment buildBytecodeProvider
    INFO: Bytecode provider name : cglib
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment <clinit>
    INFO: using JDK 1.4 java.sql.Timestamp handling
    May 15, 2008 8:39:42 PM org.hibernate.cfg.Configuration configure
    INFO: configuring from resource: /hibernate.cfg.xml
    May 15, 2008 8:39:42 PM org.hibernate.cfg.Configuration getConfigurationInputStream
    INFO: Configuration resource: /hibernate.cfg.xml
    May 15, 2008 8:39:42 PM org.hibernate.cfg.Configuration addResource
    INFO: Reading mappings from resource : Event.hbm.xml
    May 15, 2008 8:39:43 PM org.hibernate.cfg.HbmBinder bindRootPersistentClassCommonValues
    INFO: Mapping class: Event -> EVENTS
    May 15, 2008 8:39:43 PM org.hibernate.cfg.Configuration doConfigure
    INFO: Configured SessionFactory: null
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: Using Hibernate built-in connection pool (not for production use!)
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: Hibernate connection pool size: 1
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: autocommit mode: false
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: using driver: org.hsqldb.jdbcDriver at URL: jdbc:hsqldb:sql://localhost
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: connection properties: {user=sa, password=****}
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: RDBMS: HSQL Database Engine, version: 1.8.0
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC driver: HSQL Database Engine Driver, version: 1.8.0
    May 15, 2008 8:39:44 PM org.hibernate.dialect.Dialect <init>
    INFO: Using dialect: org.hibernate.dialect.HSQLDialect
    May 15, 2008 8:39:44 PM org.hibernate.transaction.TransactionFactoryFactory buildTransactionFactory
    INFO: Using default transaction strategy (direct JDBC transactions)
    May 15, 2008 8:39:44 PM org.hibernate.transaction.TransactionManagerLookupFactory getTransactionManagerLookup
    INFO: No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Automatic flush during beforeCompletion(): disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Automatic session close at end of transaction: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC batch size: 15
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC batch updates for versioned data: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Scrollable result sets: enabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC3 getGeneratedKeys(): disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Connection release mode: auto
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Default batch fetch size: 1
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Generate SQL with comments: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Order SQL updates by primary key: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory createQueryTranslatorFactory
    INFO: Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
    May 15, 2008 8:39:44 PM org.hibernate.hql.ast.ASTQueryTranslatorFactory <init>
    INFO: Using ASTQueryTranslatorFactory
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Query language substitutions: {}
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JPA-QL strict compliance: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Second-level cache: enabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Query cache: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory createCacheProvider
    INFO: Cache provider: org.hibernate.cache.NoCacheProvider
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Optimize cache for minimal puts: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Structured second-level cache entries: disabled
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Echoing all SQL to stdout
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Statistics: disabled
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Deleted entity synthetic identifier rollback: disabled
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Default entity-mode: pojo
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Named query checking : enabled
    May 15, 2008 8:39:45 PM org.hibernate.impl.SessionFactoryImpl <init>
    INFO: building session factory
    Intial session factory creation failed org.hibernate.PropertyNotFoundException: Could not find a getter for id in class Event
    Exception in thread "main" java.lang.ExceptionInInitializerError
    at HibernateUtil.<clinit>(HibernateUtil.java:18)
    at EventManager.main(EventManager.java:11)
    Caused by: org.hibernate.PropertyNotFoundException: Could not find a getter for id in class Event
    at org.hibernate.property.BasicPropertyAccessor.createGetter(BasicPropertyAccessor.java:282)
    at org.hibernate.property.BasicPropertyAccessor.getGetter(BasicPropertyAccessor.java:275)
    at org.hibernate.tuple.PropertyFactory.getGetter(PropertyFactory.java:168)
    at org.hibernate.tuple.PropertyFactory.buildIdentifierProperty(PropertyFactory.java:44)
    at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:123)
    at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434)
    at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109)
    at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55)
    at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
    at HibernateUtil.<clinit>(HibernateUtil.java:14)
    How can i fix this exception
    Please help me.
    Thanks in advance

    [skumar@aithdell3 events]$ java EventManager
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment <clinit>
    INFO: Hibernate 3.2.3
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment <clinit>
    INFO: hibernate.properties not found
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment buildBytecodeProvider
    INFO: Bytecode provider name : cglib
    May 15, 2008 8:39:41 PM org.hibernate.cfg.Environment <clinit>
    INFO: using JDK 1.4 java.sql.Timestamp handling
    May 15, 2008 8:39:42 PM org.hibernate.cfg.Configuration configure
    INFO: configuring from resource: /hibernate.cfg.xml
    May 15, 2008 8:39:42 PM org.hibernate.cfg.Configuration getConfigurationInputStream
    INFO: Configuration resource: /hibernate.cfg.xml
    May 15, 2008 8:39:42 PM org.hibernate.cfg.Configuration addResource
    INFO: Reading mappings from resource : Event.hbm.xml
    May 15, 2008 8:39:43 PM org.hibernate.cfg.HbmBinder bindRootPersistentClassCommonValues
    INFO: Mapping class: Event -> EVENTS
    May 15, 2008 8:39:43 PM org.hibernate.cfg.Configuration doConfigure
    INFO: Configured SessionFactory: null
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: Using Hibernate built-in connection pool (not for production use!)
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: Hibernate connection pool size: 1
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: autocommit mode: false
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: using driver: org.hsqldb.jdbcDriver at URL: jdbc:hsqldb:sql://localhost
    May 15, 2008 8:39:43 PM org.hibernate.connection.DriverManagerConnectionProvider configure
    INFO: connection properties: {user=sa, password=****}
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: RDBMS: HSQL Database Engine, version: 1.8.0
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC driver: HSQL Database Engine Driver, version: 1.8.0
    May 15, 2008 8:39:44 PM org.hibernate.dialect.Dialect <init>
    INFO: Using dialect: org.hibernate.dialect.HSQLDialect
    May 15, 2008 8:39:44 PM org.hibernate.transaction.TransactionFactoryFactory buildTransactionFactory
    INFO: Using default transaction strategy (direct JDBC transactions)
    May 15, 2008 8:39:44 PM org.hibernate.transaction.TransactionManagerLookupFactory getTransactionManagerLookup
    INFO: No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Automatic flush during beforeCompletion(): disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Automatic session close at end of transaction: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC batch size: 15
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC batch updates for versioned data: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Scrollable result sets: enabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JDBC3 getGeneratedKeys(): disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Connection release mode: auto
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Default batch fetch size: 1
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Generate SQL with comments: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Order SQL updates by primary key: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory createQueryTranslatorFactory
    INFO: Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
    May 15, 2008 8:39:44 PM org.hibernate.hql.ast.ASTQueryTranslatorFactory <init>
    INFO: Using ASTQueryTranslatorFactory
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Query language substitutions: {}
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: JPA-QL strict compliance: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Second-level cache: enabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Query cache: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory createCacheProvider
    INFO: Cache provider: org.hibernate.cache.NoCacheProvider
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Optimize cache for minimal puts: disabled
    May 15, 2008 8:39:44 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Structured second-level cache entries: disabled
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Echoing all SQL to stdout
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Statistics: disabled
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Deleted entity synthetic identifier rollback: disabled
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Default entity-mode: pojo
    May 15, 2008 8:39:45 PM org.hibernate.cfg.SettingsFactory buildSettings
    INFO: Named query checking : enabled
    May 15, 2008 8:39:45 PM org.hibernate.impl.SessionFactoryImpl <init>
    INFO: building session factory
    Intial session factory creation failed org.hibernate.PropertyNotFoundException: Could not find a getter for id in class Event
    Exception in thread "main" java.lang.ExceptionInInitializerError
    at HibernateUtil.<clinit>(HibernateUtil.java:18)
    at EventManager.main(EventManager.java:11)
    Caused by: org.hibernate.PropertyNotFoundException: Could not find a getter for id in class Event
    at org.hibernate.property.BasicPropertyAccessor.createGetter(BasicPropertyAccessor.java:282)
    at org.hibernate.property.BasicPropertyAccessor.getGetter(BasicPropertyAccessor.java:275)
    at org.hibernate.tuple.PropertyFactory.getGetter(PropertyFactory.java:168)
    at org.hibernate.tuple.PropertyFactory.buildIdentifierProperty(PropertyFactory.java:44)
    at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:123)
    at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434)
    at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109)
    at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55)
    at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
    at HibernateUtil.<clinit>(HibernateUtil.java:14)
    How can i fix this exception
    Please help me.
    Thanks in advance

  • Text data is not displaying at Report level for an Infoobject Item name

    Hi All,
    Texts data is maintained at Info object level but text information is not displaying at Report level for an object.  I have set the property at query level as "Text", but at report level it is displaying key values of the object, not displaying texts information.  This problem occured in QA(Quality) system but not replicated in Production system.  I have checked all properties at backend and query level and compared the same between QA and Production system didn't find any difference.
    Please suggest what might be the cause: at report level it is displaying key values instead of the textual information even text data is mainintained at backend.  In production it is displaying textal data for the IO.
    Thanks in advance.

    Hi All,
    Thanks for your valuable information.  I have changed the setting under Advanced tab as "Master data" for Access type for results values, but didn't solved the problem still it showing key information for the IO.
    In Production system the report displaying texts information for the IO, but in QA its displaying key information. The problem exits only in QA, its working fine in DEv and Production.
    As per my understanding might be the issue with Patches will be checking with Basis team on the same.
    Please suggest if you have any alternatives to fix the issue.

  • Office Web Apps - "Could not find trace string in ULS logs" unhealthy?

    I have reviewed everything I could find on unhealthy WAC clusters as my problem seems unrelated to certificate or missing components.  I've already digested
    http://www.wictorwilen.se/office-web-apps-server-2013---machines-are-always-reported-as-unhealthy (Thanks Wictor).
    The particular configuration is an Office Web Apps 2013 ([X-OfficeVersion, 15.0.4551.1005]), running on top of Windows Server 2012, configured for http access (SSL offloaded NLB cluster) and finally linked to Exchange 2013, Lync 2013 and SharePoint
    2013.  Everything works as expected from client side after setting IIS ARR to handle all reverse proxy bits.
    FarmOU                            :
    InternalURL                       : https://officeapps.fqdn/
    ExternalURL                       : https://officeapps.fqdn/
    AllowHTTP                         : True
    SSLOffloaded                      : True
    CertificateName                   :
    EditingEnabled                    : True
    LogLocation                       : C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS
    LogRetentionInDays                : 7
    LogVerbosity                      : Unexpected
    Proxy                             :
    CacheLocation                     : C:\ProgramData\Microsoft\OfficeWebApps\Working\d
    MaxMemoryCacheSizeInMB            : 75
    DocumentInfoCacheSize             : 5000
    CacheSizeInGB                     : 15
    ClipartEnabled                    : False
    TranslationEnabled                : False
    MaxTranslationCharacterCount      : 125000
    TranslationServiceAppId           :
    TranslationServiceAddress         :
    RenderingLocalCacheLocation       : C:\ProgramData\Microsoft\OfficeWebApps\Working\waccache
    RecycleActiveProcessCount         : 5
    AllowCEIP                         : False
    ExcelRequestDurationMax           : 300
    ExcelSessionTimeout               : 450
    ExcelWorkbookSizeMax              : 50
    ExcelPrivateBytesMax              : -1
    ExcelConnectionLifetime           : 1800
    ExcelExternalDataCacheLifetime    : 300
    ExcelAllowExternalData            : True
    ExcelWarnOnDataRefresh            : True
    OpenFromUrlEnabled                : False
    OpenFromUncEnabled                : True
    OpenFromUrlThrottlingEnabled      : True
    PicturePasteDisabled              : True
    RemovePersonalInformationFromLogs : False
    AllowHttpSecureStoreConnections   : False
    Machines                          : {WAC15PD-02, WAC15PD-01}
    The problem however is an incessant logging on the WAC cluster nodes of event 1204,2204 followed almost immediately by 1004,2004.  This repeats every 4min or so...
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">1204</EventID>
      <Level>2</Level>
      <Task>1</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:37.000000000Z" />
      <EventRecordID>3043246</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage>
    <ComponentOwner>ServicesInfrastructure</ComponentOwner>
    </HealthReport></Data>
      </EventData>
     </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">2204</EventID>
      <Level>2</Level>
      <Task>1</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:37.000000000Z" />
      <EventRecordID>3043247</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in
    C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage> <ComponentOwner>ServicesInfrastructure</ComponentOwner>
    </HealthReport></Data>
      </EventData>
      </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">1004</EventID>
      <Level>2</Level>
      <Task>10002</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:39.000000000Z" />
      <EventRecordID>3043266</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
    AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
      </EventData>
     </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">2004</EventID>
      <Level>2</Level>
      <Task>10002</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:39.000000000Z" />
      <EventRecordID>3043267</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
    AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
      </EventData>
      </Event>
    Further exploration of ULS log files (C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS) did not yield particularly much, except the following;
    02/04/2014 20:48:04.48  UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Uls Controller Watchdog        ajbam Assert 
     We're about to trace a string for category MsoSpUlsControllerWatchdog at level Info and we expect to find in the log later, but it appears that the category has been throttled. We will never be able to find the string and this watchdog will always fail.
    StackTrace:   at Microsoft.Office.Web.UlsControllerWatchdog.Program.CheckServiceInstance(ServiceInstance serviceInstance)     at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.GetHealthResults(WatchdogExecutionContext
    context, ServiceInstance si)     at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.WatchingThreadMethod(Object o)     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback
    callback, Object state, Boolean preserveSyncCtx)     at System.Threading.ExecutionContext.Ru... 345fbec5-e958-4f1f-bf56-d65c1c0d472a
    02/04/2014 20:48:04.48* UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Uls Controller Watchdog        ajbam Assert 
     ...n(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)     at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()    
    at System.Threading.ThreadPoolWorkQueue.Dispatch()   345fbec5-e958-4f1f-bf56-d65c1c0d472a
    02/04/2014 20:48:05.52  UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Services Infrastructure Health adhog Unexpected Health report
    by UlsControllerWatchdog: Agent: UlsController, eventId: 1204, eventType: Error, categoryId: 1, eventMessage: <?xml version="1.0" encoding="utf-16"?>  <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">    <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported
    status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage>    <ComponentOwner>ServicesInfrastructure</ComponentOwner>  </HealthReport> 345fbec5-e958-4f1f-bf56-d65c1c0d472a
    02/04/2014 20:48:05.52  UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Services Infrastructure Health adhoh Unexpected Health report
    by UlsControllerWatchdog (persistent): Agent: UlsController, eventId: 2204, eventType: Error, categoryId: 1 345fbec5-e958-4f1f-bf56-d65c1c0d472a
    I suspect these might be related, but can't seem to find any logical explanation why this should cause the Get-OfficeWebAppsMachine to report HealthStatus of Unhealthy.  If related, is there a way to disable this check or remove throttling in a safe
    way?  Alternatively if this is some coding issue (I've not found any other blog/QA dealing with this particularly) it would be nice to get confirmation of this and potentially a fix/solution.
    Any help would be greatly appreciated. Thank you!

    Hi ChristiaanB,
    You get this ULS error because you change the log verbosity of the OWA farm. I wrote an article for this on my blog : OWA unhealthy uls issue
    Regards,
    Wes

  • Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

    I tried to install ,deleted and re-installed several times and no help at all.
    visual studio 2013 with update 2 rc and adk installed in my computer.
    error code: 0x851a0019
    error messege in setup: could not find the database engine startup handle
    edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
    logs:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 13:53:29
      End time:                      2014-04-03 14:47:48
      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:                  ARIELUBA-PC
      Machine processor count:       8
      OS version:                    Windows 8
      OS service pack:               
      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 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             Database Engine Services                 1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             SQL Server Replication                   1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    Database Engine Services            
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    SQL Server Replication              
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3412.0     No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
      Installation edition:          Evaluation
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Hebrew_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            ARIELUBA-PC\Arie Luba
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   
      CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
      CLTSTARTUPTYPE:                Manual
      CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               Manual
      CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     ARIELUBA-PC\Arie Luba
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
      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:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Hebrew_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           ARIELUBA-PC\Arie Luba
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Master Data Services
      Status:                        Passed
      Feature:                       Distributed Replay Client
      Status:                        Passed
      Feature:                       Distributed Replay Controller
      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:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
    2014-04-03 14:14:28.01 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    2014-04-03 14:14:28.01 Server      UTC adjustment: 3:00
    2014-04-03 14:14:28.01 Server      (c) Microsoft Corporation.
    2014-04-03 14:14:28.01 Server      All rights reserved.
    2014-04-03 14:14:28.01 Server      Server process ID is 7148.
    2014-04-03 14:14:28.01 Server      System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
    2014-04-03 14:14:28.01 Server      Authentication mode is WINDOWS-ONLY.
    2014-04-03 14:14:28.01 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-04-03 14:14:28.01 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2014-04-03 14:14:28.01 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-04-03 14:14:28.01 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "Hebrew_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2014-04-03 14:14:28.28 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-03 14:14:28.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-03 14:14:28.28 Server      Detected 8099 MB of RAM. This is an informational message; no user action is required.
    2014-04-03 14:14:28.28 Server      Using conventional memory in the memory manager.
    2014-04-03 14:14:28.31 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2014-04-03 14:14:28.34 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-03 14:14:28.36 Server      Query Store settings initialized with enabled = 1, 
    2014-04-03 14:14:28.36 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-03 14:14:28.36 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-03 14:14:28.38 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-03 14:14:28.39 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-03 14:14:28.39 spid8s      Warning ******************
    2014-04-03 14:14:28.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-03 14:14:28.40 spid8s      Starting up database 'master'.
    2014-04-03 14:14:28.42 Server      Software Usage Metrics is disabled.
    2014-04-03 14:14:28.48 Server      CLR version v4.0.30319 loaded.
    2014-04-03 14:14:28.56 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-03 14:14:28.62 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.63 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.64 spid8s      SQL Trace ID 1 was started by login "sa".
    2014-04-03 14:14:28.64 spid8s      Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
    2014-04-03 14:14:28.65 spid16s     Password policy update was successful.
    2014-04-03 14:14:28.66 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-04-03 14:14:28.66 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-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization 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-03 14:14:28.66 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-03 14:14:28.66 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-03 14:14:28.67 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-03 14:14:28.67 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    ________________________________________________________________________________________________

    Is it okay? (see below)
    ;SQL Server 2014 Configuration File
    [OPTIONS]
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 
    ACTION="Install"
    ; Detailed help for command line argument ROLE has not been defined yet. 
    ROLE="AllFeatures_WithDefaults"
    ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 
    ENU="True"
    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 
    UIMODE="Normal"
    ; Setup will not display any user interface. 
    QUIET="False"
    ; Setup will display progress only, without any user interaction. 
    QUIETSIMPLE="False"
    ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 
    UpdateEnabled="True"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 
    ERRORREPORTING="False"
    ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 
    USEMICROSOFTUPDATE="False"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
    will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 
    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
    ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
    or a Windows Update service through the Window Server Update Services. 
    UpdateSource="MU"
    ; Displays the command line parameters usage 
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console. 
    INDICATEPROGRESS="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 
    X86="False"
    ; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 
    INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 
    INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
    (RS). 
    INSTANCENAME="MSSQLSERVER"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 
    SQMREPORTING="False"
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 
    INSTANCEID="MSSQLSERVER"
    ; The computer name that the client communicates with for the Distributed Replay Controller service. 
    CLTCTLRNAME="SQLDRC"
    ; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 
    CTLRUSERS="ARIELUBA-PC\Arie Luba"
    ; The account used by the Distributed Replay Controller service. 
    CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
    ; The startup type for the Distributed Replay Controller service. 
    CTLRSTARTUPTYPE="Manual"
    ; The account used by the Distributed Replay Client service. 
    CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
    ; The startup type for the Distributed Replay Client service. 
    CLTSTARTUPTYPE="Manual"
    ; The result directory for the Distributed Replay Client service. 
    CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
    ; The working directory for the Distributed Replay Client service. 
    CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
    ; RSInputSettings_RSInstallMode_Description 
    RSINSTALLMODE="DefaultNativeMode"
    ; RSInputSettings_RSInstallMode_Description 
    RSSHPINSTALLMODE="SharePointFilesOnlyMode"
    ; Specify the installation directory. 
    INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
    ; Agent account name 
    AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
    ; Auto-start service after installation.  
    AGTSVCSTARTUPTYPE="Manual"
    ; Startup type for Integration Services. 
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account. 
    ISSVCACCOUNT="NT Service\MsDtsServer120"
    ; The name of the account that the Analysis Services service runs under. 
    ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
    ; Controls the service startup type setting after the service has been created. 
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services. 
    ASCOLLATION="Hebrew_CI_AS"
    ; The location for the Analysis Services data files. 
    ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files. 
    ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files. 
    ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files. 
    ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files. 
    ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process. 
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned. 
    ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 
    ASSERVERMODE="MULTIDIMENSIONAL"
    ; CM brick TCP communication port 
    COMMFABRICPORT="0"
    ; How matrix will use private networks 
    COMMFABRICNETWORKLEVEL="0"
    ; How inter brick communication will be protected 
    COMMFABRICENCRYPTION="0"
    ; TCP port used by the CM brick 
    MATRIXCMBRICKCOMMPORT="0"
    ; Startup type for the SQL Server service. 
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express. 
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine. 
    SQLCOLLATION="Hebrew_CI_AS"
    ; Account for SQL Server service: Domain\User or system account. 
    SQLSVCACCOUNT="NT Service\MSSQLSERVER"
    ; Windows account(s) to provision as SQL Server system administrators. 
    SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express. 
    ADDCURRENTUSERASSQLADMIN="True"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol. 
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol. 
    NPENABLED="0"
    ; Startup type for Browser Service. 
    BROWSERSVCSTARTUPTYPE="Automatic"
    ; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 
    RSSVCACCOUNT="NT Service\ReportServer"
    ; Specifies how the startup mode of the report server NT service.  When 
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled 
    RSSVCSTARTUPTYPE="Automatic"
    ; Add description of input argument FTSVCACCOUNT 
    FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

  • Delivery address at Item Level and not at the Header Level

    Hello Experts,
    We are facing an issue as described below:-
    We are in SRM 7.0 using classic scenario.
    After approval of multi line Shopping Cart in SRM ,PR's are getting
    automatically created in backend R/3 system.After converting PR's into
    POs in backend R/3,we are observing that the delivery address for these
    PO'are getting printed at Item level and not at the Header Level
    inspite of the delivery address being same for all the Item level.
    As desired,the delivery address in the PO's should have the delivery
    address at the header level if the the delivery address is identical
    for all the Item Levels.
    However,if we create a PR directly in R/3 system and then convert these
    PR's into PO's in the backend R/3 system,we find that the deliver
    address are getting printed at the Header Level if the delivery address
    is same for all the item level(which is as desired)
    Any pointers will be highly appreciated.
    Thanks & Regards,
    RKS

    It is standard process only.
    In Po delivery address is maintained at item level because to which address perticular material to be delivered,
    this may change from material to material or may not change

  • Could not find the policy in WMI for package

    Hi,
    I am trying to deploy a language pack to a windows 8.1 machine and it is not installing. According to the execmgr.log it cannot find the policy in WMI? I have tried running the machine policy update within CFG MGR but no change. Is there something else
    I can check?
    <![LOG[Policy is updated for Program: InstallEN, Package: LIA002A0, Advert: LIA2011A]LOG]!><time="09:47:18.345+300" date="01-28-2015" component="execmgr" context="" type="1" thread="980"
    file="execreqmgr.cpp:7063">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="LIA002A0",ProgramID="InstallEN", actionType 45l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="09:47:18.347+300"
    date="01-28-2015" component="execmgr" context="" type="1" thread="980" file="event.cpp:405">
    <![LOG[Mandatory execution requested for program InstallEN and advertisement LIA2011A]LOG]!><time="09:47:19.220+300" date="01-28-2015" component="execmgr" context="" type="1" thread="3684"
    file="execreqmgr.cpp:3527">
    <![LOG[Creating mandatory request for advert LIA2011A, program InstallEN, package LIA002A0]LOG]!><time="09:47:19.220+300" date="01-28-2015" component="execmgr" context="" type="1" thread="3684"
    file="execreqmgr.cpp:3653">
    <![LOG[Could not find the policy in WMI for package LIA002A0 program InstallEN]LOG]!><time="09:47:19.242+300" date="01-28-2015" component="execmgr" context="" type="2" thread="3684" file="softdistpolicy.cpp:2851">
    <![LOG[CreateMandatoryRequestRecursively failed at FindUserOrSystemPolicy InstallEN]LOG]!><time="09:47:19.243+300" date="01-28-2015" component="execmgr" context="" type="2" thread="3684"
    file="execreqmgr.cpp:3670">

    Did you check this
    post?
    It turned out the root cause of the problem was one of the packages that the TS called.  Even though SCCM had been set to use the selected distribution points and said the package was installed on those DPs, it hadn't actually copied the files over.
     Updating to a new source version and ensuring the files copied correctly resolved the issue.  Hopefully SCCM 2012 will do a better job of communicating a dependency problem, but I haven't had a chance to test it yet.
    You can also check this
    post.
    it appears the majority of these messages occur when you have a system that has an expired advertisement still being applied to it. 
    Nick Pilon | Blog : System Center Dudes

  • Windows 7 64-bit Installation Error "Could not find appropriate listener"

    *11.2.0.1* Installation fails on Win7 Professional 64-bit
    1) Installed software (did not create database initially)
    2) Create Listener via Net Config (no apparent problems here)
    3) Added DB to Listener via Net Mgr
    4) dbca fails in final portion of DB creation. Error states: *"Could not find appropriate listener for this database. Configuring DB control requires database to be registered with at least one listener.*
    My Listener services is started.
    All current updates have been applied to Win 7.
    I have searched around and found similar issues that seem to center around adminstrator rights, but I have not been able to make any progress.
    C:\Users\scott_hp>lsnrctl status
    LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 20-FEB-2012 10:16
    :11
    Copyright (c) 1991, 2010, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.195)(PORT=1522
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
    ction
    Start Date 20-FEB-2012 09:47:07
    Uptime 0 days 0 hr. 29 min. 7 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File C:\oracle\app\scott_hp\product\11.2.0\dbhome_1
    etwork
    \admin\listener.ora
    Listener Log File c:\oracle\app\scott_hp\diag     nslsnr\SCOTT-HP\listener\
    alert\log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.0.195)(PORT=1522)))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
    Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "mmodb.192.168.0.195" has 1 instance(s).
    Instance "mmmodb", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully <gphmh>
    Edited by: svk1965 on Feb 20, 2012 7:17 AM
    Edited by: svk1965 on Feb 20, 2012 7:22 AM

    svk1965 wrote:
    FIXED!! *Thank you very much.* I followed your instructions, renaming listener.ora, before the lsnrctl start. I then waited and ran dbca and walked through the configuration screens and this time it processed through to 100%. But I am not sure I understand what caused the issue??
    C:\Windows\system32>lsnrctl stop
    LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 20-FEB-2012 11:34
    :24
    Copyright (c) 1991, 2010, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.195)(PORT=1521
    The command completed successfully
    C:\Windows\system32>lsnrctl start
    LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 20-FEB-2012 11:36
    :51
    Copyright (c) 1991, 2010, Oracle. All rights reserved.
    Starting tnslsnr: please wait...
    TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Production
    Log messages written to c:\oracle\app\scott_hp\diag     nslsnr\SCOTT-HP\listener\al
    ert\log.xml
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=SCOTT-HP)(PORT=1521)))
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
    ction
    Start Date 20-FEB-2012 11:36:56
    Uptime 0 days 0 hr. 0 min. 5 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Log File c:\oracle\app\scott_hp\diag     nslsnr\SCOTT-HP\listener\
    alert\log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=SCOTT-HP)(PORT=1521)))
    The listener supports no services
    The command completed successfully
    C:\Windows\system32>lsnrctl status
    LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 20-FEB-2012 11:39
    :30
    Copyright (c) 1991, 2010, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
    ction
    Start Date 20-FEB-2012 11:36:56
    Uptime 0 days 0 hr. 2 min. 37 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Log File c:\oracle\app\scott_hp\diag     nslsnr\SCOTT-HP\listener\
    alert\log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=SCOTT-HP)(PORT=1521)))
    Services Summary...
    Service "mmmodb.192.168.0.195" has 1 instance(s).
    Instance "mmmodb", status READY, has 1 handler(s) for this service...
    Service "mmmodbXDB.192.168.0.195" has 1 instance(s).
    Instance "mmmodb", status READY, has 1 handler(s) for this service...
    The command completed successfullyThe db instance will register itself with the listener every minute or so. When you first start the listener, it will have to wait until the next cycle of the instance self-registration before it (the listener) knows about the db instance.

Maybe you are looking for