UCCX 8.0.2. HA unable to manualy sinchronize directory Services

Good morning,
     We have an agent that exists as a Call Manager user with an IPCC extension, the same user shows up in RMCM under de UCCX 8.0.2, but he is unable to log in to CAD with error "ID introuvable" (ID NOT FOUND). When we look in the Desktop administrator, we notice the user is missing. When we try to initiate a manual directory services synck, we instantly get the error "CDAUI2082 At least one error has occured during the manual synchronization of directory services. Contact Technical Support"
We found BUG ID CSCtd94036 , no luck after increasing the timeout value to even 120s.We restarted both UCCX with no change in behavior. IF you remove the IPCC extension in the end users of CUCM, the user becomes a unactive agent instantly and if you go give the IPCC extension he is back in RMCM, but never shows up in Desktop administrator.
Anybody knows of a fix, or necessary debugs to gather before we go to TAC on this ?
Thanks.

here are some few interesting debug I gathered. means anything to anyone?
2011-07-14 15:50:42:958 DEBUG [0x29b4ba0] ManualSync.cpp[76] DASynchronize: BEGIN.
2011-07-14 15:50:42:959 DEBUG [0x29b4ba0] LCLDAP.cpp[454] Get: First entry is NULL.
2011-07-14 15:50:42:959 DEBUG [0x29b4ba0] LCServerType.cpp[310] Get: End false.
2011-07-14 15:50:42:959 DEBUG [0x29b4ba0] ManualSync.cpp[167] GetServerIOR: Error getting Server Type Profile from LDAP.
2011-07-14 15:50:42:959 ERROR [0x29b4ba0] WAL2237 DASynchronize: Error getting GetServerIOR for Sync Server.
2011-07-14 15:50:42:959 DEBUG [0x29b4ba0] ManualSync.cpp[80] DASynchronize: Could not connect to Directory Services Synchronize Server.
2011-07-14 15:50:42:959 ERROR [0x29b4ba0] WAL2223 write: Error synchronizing directory services.
2010-12-01 12:50:26:376 ERROR SPLKTSSP2038 Network communication error (TRANSIENT).
2010-12-01 12:51:23:406 ERROR SPLKTSSP2038 Network communication error (TRANSIENT).
2010-12-01 12:52:13:550 ERROR SPLKTSSP2038 Network communication error (TRANSIENT).
2010-12-02 16:25:52:194 INFO STD0005 Client disconnected from service at <192.168.8.16>.
2010-12-02 16:25:52:209 INFO LC0012 Failed to bind to Calabrio LDAP service on <192.168.8.16>: <-1>
2010-12-02 16:25:53:017 WARN SOCKET3000 Received an invalid event from SocketLRMClient socket service. Recovery initiated. Error nested com.spanlink.util.socket.SplkClosedChannelException: Attempting to read when the connection has been closed.>.
ontact LDAP server>

Similar Messages

  • INSTALLED ITUNES AND THE ERROR-MAPI WAS UNABLE TO LOAD THE INFORMATION SERVICE APLZOD-OCCURS. WHAT DO I DO.

    INSTALLED ITUNES AND THE ERROR-MAPI WAS UNABLE TO LOAD THE INFORMATION SERVICE APLZOD-OCCURS. WHAT DO I DO.

    Is this on a Windows XP, Vista or 7 system?

  • Many years ago synced iCal with Microsoft program. Since installing Lion whenever I try to create an event in iCal it flashes up message "Unable to open Microsoft sync services Power PC applications no longer supported." How do I get rid of message?

    Many years ago synced iCal with Microsoft program. Since installing Lion whenever I try to create an event in iCal it flashes up message "Unable to open Microsoft sync services Power PC applications no longer supported." How do I get rid of message?

    Lion no longer supports PowerPC apps. If this is Microsoft Office 2008 (Entourage 2008) then you should disable the syncing services.  (I don't have Office 2008 installed anymore so I don't know exactly what it's called anymore.)  If you have Microsoft Office 2004 or earlier, then it can't be run on Lion at all since Lion removed Rosetta, which is what allowed a PPC app to run on an Intel based Mac.
    Also, I believe Microsoft removed sync services from the current Outlook 2011 (which replaces Entourage) so even upgrading to a newer version of Microsoft Office will not get you back that calendar sync feature.  Supposedly Microsoft is working on a new syncing system, but I wouldn't hold my breath.

  • BIA 7.9.6.1 Unable to connect to Informatica services from DAC

    Hi All,
    As a learning exercise, I have installed the following on a single Windows XP machine (Am aware that Windows XP is not supported for Informatica Service install - but currently have access to only this machine)
    - OBIA 7.9.6.1
    - Informatica 8.6.1 client & services with hotfix 6
    - DAC client & server
    I have created the Repository and Integration services in Informatica PowerCenter and are running in normal mode
    I have configured the DAC as per installation document. I am now trying to configure the DAC Integration Settings for informatica.
    I am unable to register an Integration service or a repository service and get the following errors,
    On testing the Integration Service registration
    Failure connecting to "INFORMATICA_DW_SERVER"!
    And in the log file I find
    SEVERE Thu Nov 12 11:43:54 WST 2009
    ANOMALY INFO::: Error while pinging informatica server using command pmcmd pingservice -sv int_service -d Domain_ASG596138
    MESSAGE:::log\ping.log (The system cannot find the file specified)
    EXCEPTION CLASS::: java.io.FileNotFoundException
    java.io.FileInputStream.open(Native Method)
    java.io.FileInputStream.<init>(FileInputStream.java:106)
    java.io.FileInputStream.<init>(FileInputStream.java:66)
    com.siebel.etl.functional.ReadFileToBuffer.readFileToBuffer(ReadFileToBuffer.java:39)
    com.siebel.etl.gui.data.StaticDatabaseCalls.testServer(StaticDatabaseCalls.java:917)
    com.siebel.etl.gui.data.StaticDatabaseCalls.testInformaticaServer(StaticDatabaseCalls.java:887)
    com.siebel.etl.net.ExecutionPlan.getInformaticaStatus(ExecutionPlan.java:275)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.mBeanRequestInformaticaStatus(ClientMessageDispatcher.java:433)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.consoleMessage(ClientMessageDispatcher.java:224)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.run(ClientMessageDispatcher.java:144)
    On testing the Repository Service registration
    Failure connecting to "INFORMATICA_REP_SERVER"!
    ANOMALY INFO::: Error while pinging informatica repository server
    MESSAGE:::C:\orahome\10gR3_2\bifoundation\dac\log\pmrepConnect.log (The system cannot find the file specified)
    EXCEPTION CLASS::: java.io.FileNotFoundException
    java.io.FileInputStream.open(Native Method)
    java.io.FileInputStream.<init>(FileInputStream.java:106)
    java.io.FileInputStream.<init>(FileInputStream.java:66)
    com.siebel.etl.functional.ReadFileToBuffer.readFileToBuffer(ReadFileToBuffer.java:39)
    com.siebel.analytics.etl.infa.interaction.PmrepInvoker.pmrep(PmrepInvoker.java:100)
    com.siebel.etl.gui.data.StaticDatabaseCalls.testRepositoryServer(StaticDatabaseCalls.java:959)
    com.siebel.etl.gui.data.StaticDatabaseCalls.testInformaticaServer(StaticDatabaseCalls.java:890)
    com.siebel.etl.net.ExecutionPlan.getInformaticaStatus(ExecutionPlan.java:275)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.mBeanRequestInformaticaStatus(ClientMessageDispatcher.java:433)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.consoleMessage(ClientMessageDispatcher.java:224)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.run(ClientMessageDispatcher.java:144)
    Could anyone please suggest what could be the cause of these errors. Any pointers to how to debug this will also be great. Please note I am totally new to Informatica and OBIA.
    Many Thanks,
    Kiran

    HI All,
    I fixed the first part of the issue. Now I am able to connect top the Integration Service. I created system environment variable INFA_DOMAINS_FILE and included the BIN path in PATH variable.
    However unable to connect to the Informatica Repository service. I am getting the follwoing error
    Failure connecting to "INFORMATICA_REP_SERVER"!
    ANOMALY INFO::: Error while connecting to informatica repository server
    MESSAGE:::
    pmrep Connect Error
    =====================================
    STD OUTPUT
    =====================================
    Informatica(r) PMREP, version [8.6.1], build [183.1218], Windows 32-bit
    Copyright (c) Informatica Corporation 1994 - 2008
    All Rights Reserved.
    This Software may be protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775; 6,850,947; 6,895,471; 7,254,590 and other U.S. Patents Pending.
    Invoked at Thu Nov 12 12:59:16 2009
    [11/12/2009 12:59:25-[REP_12164] Domain-related error: [[PCSF_46008] Cannot connect to gateway to look up service [repo_service]. [FAULT_PCSFTIMEOUTEXCEPTION]].]
    [11/12/2009 13:00:26-[REP_55115] Still trying to connect to the Repository Service [repo_service]. The remaining resilience time is 110 seconds.]
    [11/12/2009 13:00:35-[REP_12164] Domain-related error: [[PCSF_46008] Cannot connect to gateway to look up service [repo_service]. [FAULT_PCSFTIMEOUTEXCEPTION]].]
    [11/12/2009 13:01:37-[REP_55115] Still trying to connect to the Repository Service [repo_service]. The remaining resilience time is 39 seconds.]
    [11/12/2009 13:01:46-[REP_12164] Domain-related error: [[PCSF_46008] Cannot connect to gateway to look up service [repo_service]. [FAULT_PCSFTIMEOUTEXCEPTION]].]
    [11/12/2009 13:02:21-[REP_55112] Unable to connect to the Repository Service [repo_service] since the resilience time is up.]
    [Failed to connect to repository service [repo_service].]
    An error occurred while accessing the repository[Failed to connect to repository service [repo_service].]
    [11/12/2009 13:02:21-[REP_55102] Failed to connect to repository service [repo_service].]
    Repository connection failed.
    Failed to execute connect.
    Completed at Thu Nov 12 13:02:21 2009
    =====================================
    ERROR OUTPUT
    =====================================
    EXCEPTION CLASS::: com.siebel.analytics.etl.infa.interaction.PmrepConnectException
    com.siebel.analytics.etl.infa.interaction.PmrepInvoker.pmrep(PmrepInvoker.java:102)
    com.siebel.etl.gui.data.StaticDatabaseCalls.testRepositoryServer(StaticDatabaseCalls.java:959)
    com.siebel.etl.gui.data.StaticDatabaseCalls.testInformaticaServer(StaticDatabaseCalls.java:890)
    com.siebel.etl.net.ExecutionPlan.getInformaticaStatus(ExecutionPlan.java:275)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.mBeanRequestInformaticaStatus(ClientMessageDispatcher.java:433)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.consoleMessage(ClientMessageDispatcher.java:224)
    com.siebel.etl.net.ClientMessageDispatcher$WorkerThread.run(ClientMessageDispatcher.java:144)
    Please help.
    Thanks,
    Kiran

  • The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.

    We are in the process of removing a child domain from the forest and are down to two DCs. These are both Server 2008r2 sp1 servers, one physical and virtual (PDC). When I try to remove a DC (not the PDC emulator) I get the following error:
    The operation failed because:
    Active Directory Domain Services could not transfer the remaining data in directory partition DC=DomainDnsZones,DC=mydomain,DC=local to
    Active Directory Domain Controller \\V-Svr03.mydomain.local.
    The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles."
    I have checked replication with repadmin /showrepl and all connections were successful. The dcdiag /test:kccEvent test on all servers passed.
    Most DCdiag tests are successful. The only failure is on NCSecDesc when running dcdiag /test:NCSecDesc
       Testing server: Default-First-Site\DC1-DEV-OFC
          Starting test: NCSecDesc
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=hookemup,DC=local
             ......................... DC1-DEV-OFC failed test NCSecDesc
    In researching this I find "If you do not plan to add an RODC to the forest, you can disregard this error."
    We have not successfully run ADprep /rodcPrep nor do we plan on having any Read-Only DCs, so I think we can ignor this error. We did try running ADprep /rodcPrep but got an LDAP error which I can duplicate if this is important.
    Schema and Naming FSMOs are on a DC higher in the forest. RID, PDC, and Infrastructure FSMOs for the child domain are on the Virtual server (PDC).
    Any guidance on where to go from here would be greatly appreciated as I have no more hair on my head to pull.

    Ok... I ran repadmin /showreps /v again and it shows no errors
    C:\>repadmin /showreps /v
    Default-First-Site\DC1-DEV-OFC
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: b294c59f-8b46-4133-89c5-0f30bfd49607
    DSA invocationID: 1054285d-cffe-42b4-8074-e2d44adbb151
    ==== INBOUND NEIGHBORS ======================================
    CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381490/OU, 16381490/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114817/OU, 114817/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66047/OU, 66047/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098197/OU, 8098197/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    CN=Schema,CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8097482/OU, 8097482/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 65239/OU, 65239/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114149/OU, 114149/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381373/OU, 16381373/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=ForestDnsZones,DC=mydomain,DC=local
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66295/OU, 66295/PU
            Last attempt @ 2012-10-29 13:57:48 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098367/OU, 8098367/PU
            Last attempt @ 2012-10-29 13:58:13 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 115032/OU, 115032/PU
            Last attempt @ 2012-10-29 13:58:25 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381653/OU, 16381653/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
    DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114871/OU, 114871/PU
            Last attempt @ 2012-10-29 13:54:02 was successful.
    DC=DomainDnsZones,DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=mydomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 16381614/OU, 16381614/PU
            Last attempt @ 2012-10-29 13:56:52 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 66325/OU, 66325/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 8098385/OU, 8098385/PU
            Last attempt @ 2012-10-29 13:58:38 was successful.

  • Unable to install SQL 2005 Service Pack 3 (Unable to install Windows Installer MSI file)

    I'm unable to install SQL 2005 Service Pack 3. This results in the following error message: Unable to install Windows Installer MSI file.
    Could someone please help me. Thanks in advance!
    === Verbose logging started: 3-4-2009  9:33:00  Build type: SHIP UNICODE 4.05.6001.00  Calling process: d:\5ddfa356349ddf2e676c336d95c5\hotfix.exe ===
    MSI (c) (E0:88) [09:33:00:404]: Resetting cached policy values
    MSI (c) (E0:88) [09:33:00:404]: Machine policy value 'Debug' is 0
    MSI (c) (E0:88) [09:33:00:404]: ******* RunEngine:
               ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (E0:88) [09:33:00:404]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (E0:88) [09:33:00:404]: Grabbed execution mutex.
    MSI (c) (E0:88) [09:33:00:419]: Cloaking enabled.
    MSI (c) (E0:88) [09:33:00:419]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (E0:88) [09:33:00:419]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (28:28) [09:33:01:747]: Running installation inside multi-package transaction C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
    MSI (s) (28:28) [09:33:01:747]: Grabbed execution mutex.
    MSI (s) (28:CC) [09:33:02:029]: Resetting cached policy values
    MSI (s) (28:CC) [09:33:02:029]: Machine policy value 'Debug' is 0
    MSI (s) (28:CC) [09:33:02:029]: ******* RunEngine:
               ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (28:CC) [09:33:02:685]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (28:CC) [09:33:03:450]: File will have security applied from OpCode.
    MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi' against software restriction policy
    MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi has a digital signature
    MSI (s) (28:CC) [09:33:04:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (28:CC) [09:33:04:888]: End dialog not enabled
    MSI (s) (28:CC) [09:33:04:888]: Original package ==> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
    MSI (s) (28:CC) [09:33:04:888]: Package we're running from ==> C:\WINDOWS\Installer\3d3a713.msi
    MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
    MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (28:CC) [09:33:05:685]: MSCOREE not loaded loading copy from system32
    MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\2f1994e.msi 3: -2147287038
    MSI (s) (28:CC) [09:33:05:825]: Opening existing patch 'C:\WINDOWS\Installer\e6ba0.msp'.
    MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\e6ba0.msp 3: -2147287038
    MSI (s) (28:CC) [09:33:05:825]: Couldn't find local patch 'C:\WINDOWS\Installer\e6ba0.msp'. Looking for it at its source.
    MSI (s) (28:CC) [09:33:05:825]: Resolving Patch source.
    MSI (s) (28:CC) [09:33:05:825]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (28:CC) [09:33:05:825]: User policy value 'DisableMedia' is 0
    MSI (s) (28:CC) [09:33:05:825]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Trying source \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\.
    MSI (s) (28:CC) [09:33:06:607]: Note: 1: 2203 2: \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\SqlSupport.msp 3: -2147287037
    MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
    MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing net source list.
    MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
    MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing media source list.
    MSI (s) (28:CC) [09:33:07:654]: SOURCEMGMT: Resolved source to: 'SqlSupport.msp'
    MSI (s) (28:CC) [09:33:37:732]: Note: 1: 1314 2: SqlSupport.msp
    MSI (s) (28:CC) [09:33:37:732]: Unable to create a temp copy of patch 'SqlSupport.msp'.
    MSI (s) (28:CC) [09:33:37:732]: Searching provided command line patches for patch code {EE92F683-5F5C-4970-BB0B-9AC591B60268}
    MSI (s) (28:CC) [09:33:37:763]: Note: 1: 1708
    MSI (s) (28:CC) [09:33:37:763]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.
    MSI (s) (28:CC) [09:33:37:763]: Windows Installer installed the product. Product Name: Microsoft SQL Server Setup Support Files (English). Product Version: 9.00.4035.00. Product Language: 1033. Installation success or error status: 1635.
    MSI (s) (28:CC) [09:33:37:779]: MainEngineThread is returning 1635
    MSI (s) (28:28) [09:33:37:888]: No System Restore sequence number for this installation.
    This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
    MSI (s) (28:28) [09:33:37:888]: User policy value 'DisableRollback' is 0
    MSI (s) (28:28) [09:33:37:888]: Machine policy value 'DisableRollback' is 0
    MSI (s) (28:28) [09:33:37:888]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (28:28) [09:33:37:904]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (28:28) [09:33:37:919]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (28:28) [09:33:37:919]: Restoring environment variables
    MSI (c) (E0:88) [09:33:37:935]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (E0:88) [09:33:37:935]: MainEngineThread is returning 1635
    === Verbose logging stopped: 3-4-2009  9:33:37 ===

    This post should definitely help you
    http://blogs.msdn.com/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?CommentPosted=true
    Feroz
    Mark as Answer if it helps. This posting is provided "AS IS" with no warranties and confers no rights.

  • Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services

    Getting this error from DirSync
    Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [UserPrincipalName
    [email protected];].  Correct or remove the duplicate values in your local directory.  Please refer to
    http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values.
    Quick eyeball and couldn't see the cause in the user account so used the script here:
    http://gallery.technet.microsoft.com/office/Fix-Duplicate-User-d92215ef
    And got these outputs:
    PS C:\Windows\System32\WindowsPowerShell\v1.0> Export-OSCADUserPrincipalName -UserPrincipalName "[email protected]" -Path .\outputs.csv
    WARNING: Cannot find objects with specified duplicate user principal name
    [email protected]
    Found 0 user(s) with duplicate user principal name.
    Where to from here?
    Richard P

    Hi,
    Did you talk about the Microsoft Azure Active Directory Sync tool ?
    If yes, this issue occurs if one or more of the following conditions are true:
    An object in the on-premises Active Directory has an SMTP address that's the same as the SMTP address of the object that's reporting the problem.
    An object in the on-premises Active Directory has a mail attribute that's identical to the object that's reporting the problem.
    An object already exists in your organizational account and has the same SMTP address or mail attribute as the object in the on-premises Active Directory
    More detail information, please refer to:
    http://support.microsoft.com/kb/2520976/en-us
    [Troubleshooting] Unable to update this object because the following attributes associated with this object
    http://blogs.technet.com/b/aadsyncsupport/archive/2014/05/20/troubleshooting-unable-to-update-this-object-because-the-following-attributes-associated-with-this-object.aspx
    Regards.
    Vivian Wang

  • Unable to create a business service from a jca file

    I have taken a jca file of a file adapter from Oracle JDeveloper and I am trying to create a business service though eclipse for OSB.
    But I am unable to create a business service as the jca protocol is NOT available in the "Transport Configuration" section of a business service.
    I have got OSB 11.1.1.3 and wls 10.3.3.0 installed along with the corresponding integrated eclipse(oepe_11gR1PS2).
    Pls suggest!

    Refer this for the solution
    Business service NOT getting configured from jca file in Windows 7

  • Unable to create database entry in the directory service. - TNS-04

    We run into this error when we tried to register an Oracle 10.2.0.4 database with OID server (10.1.4.3):
    Unable to create database entry in the directory service. - TNS-04409: Directory service error
    We use Oracle DBCA to register to the OID. Both Oracle database and OID server are all running under Sun Solaris environment.
    In the meantime, I found these errors in the oid logs:
    oidldapd01.log:
    2009/07/13:21:15:47 * DispatcherListener:2 * ERROR : gslsflAcceptConnAndSend : OS 2 : Unable to accept New TCP
    connection
    Any ideas?
    Thanks
    Naiying

    Hi,
    Thanks for update.
    No, didn't find DSCC agent logs get updated when I have the pop up.
    C:\dsee7\var\dcc\agent\logs
    In the glassfish server log, I didn't find new transaction when I hit the issue
    C:\glassfish3\glassfish\domains\domain1\logs

  • Unable to convert the sender service to an ALE logical system

    Hello,
    file adapter > XI 3.0 > Idoc adapter > r/3 system
    In sxmb_moni I receive "Unable to convert the sender service to an ALE logical system".
    In we05 in r/3 system no Idocs are arrving. I have no problem with idoc > XI >  idoc scenario to this same r/3 system (using same sld business system)
    I read other topics on this error but it seems they all talk about an IDOC outbound interface.
    What should I check?
    Thanks
    Boaz

    I do have the same problem as Boaz Paz
    When I try :
    file adapter > XI 3.0 > Idoc adapter > r/3 system
    > This is a B2B scenario where "AVTItalia" is the external party trying to send via its "AwayOrders" business service (a file pickup) an idoc to business system "UPG" (non party service)
    I get an error while XI tries to call its IDoc Adapter:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
    <SAP:P1>AwayOrders</SAP:P1>
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Unable to convert sender service AwayOrders to an ALE logical system</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    With the following trace logs :
    <Trace level="1" type="T">Party normalization: sender</Trace>
    <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
    <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
    <Trace level="1" type="T">Sender party external = AVTItalie</Trace>
    <Trace level="1" type="T">Sender party normalized = AVTItalie</Trace>
    I ve tried to (cf. /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc ):
    1. add a logical system name "ACYAVTFBC1" in "Adapter specifier Id" of "AwayOrders"
    In the runtime cache > services an entry appears for " ... Logical System | AVTItalia | ACYAVTFBC1...".
    2. declare "AVTItalia" as a business partner in SLD with the logical system name
    Plz help!

  • File-idoc     Unable to convert the sender service  to an ALE logical syste

    Hi experts
    iam working on file-idoc scenario ,iam getting the below error in sxmb_moni and RWB
    "Unable to convert the sender service  to an ALE logical system"
    i checked the partnetr profile, RFC(sm59) and IDX1 t codes.
    the connection is ok. but still i could figureout the problem.
    please suggest me
    Thanks
    vasavi

    Hi,
    Have u checked the logical system is added in the Sender Business service in the Integration Directory?
    Open the Buiness Service/System --> EDIT-ADAPTER SPECIFIC IDENTIFIERS
    then specify the logical system name.
    Go throgh the following link
    Troubleshooting  File-to-IDOC Scenario in XI.
    Regards
    Sridhar Goli

  • Unable to convert the sender service BS_PARTNER to an ALE logical system..!

    Hi All,
    File to IDoc scenario.
    1. Business system is correct because its working for other scenarios.
    2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
    3. Refreshed cache.
    But still... its showing the below error.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>BS_PARTNER</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Any idea what might be wrong?
    Regards
    Deepthi.

    Hi Experts,
                      Could you please help me to fix this.
    SCENARIO:  SAP - IDOC -
    > XI -
    > SOAP Adapter (Webservice)
    Workaround:
    1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
    2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
    3. Identifier Tab in comm channel    details: Its empty - no values.
    SXMB_MONI :
    Error Details:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>CAPTOR3_PRU</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks in Advance,
    Sunil.

  • Unable to convert the sender service PPG to an ALE logical system

    Hello all,
    maybe anybody can help or give me further information.
    I have set up a scenario  to send IDOC from a business system  ( ERP )  to a business service ( EXT ).
    Receiver is a linux system so I use the FTP-FILE adapter as communication channel.
    The send-process is so far ok.
    Here my tests:
    1)  exclude the specific IDOC  in  IDXNOALE table  (  means no technical acknowledgment for this IDOC ) 
         result :
         a)  message in SXMB_MONI:   status-flag: processed,   acknowledgment-flag:  not in use
         b)  message in RWB-Monitor:  Sender ERP  -->   Receiver EXT   ok 
    2) But I would like to have a system status.....   here  now the problem
        add specific IDOC into IDXNOALE table   ( for request acknowledgments )
        result: 
        a)  message in SXMB_MONI:  status-flag: processed,   acknowledgment-flag:   acknowledgment not possible
                                                   -->  error message:  unable to convert the sender service EXT to an ALE logical system
        b)  message in RWB-Monitor:  there are now two message, 
             first:        Sender ERP  -->   Receiver EXT   =   ok 
             second:   Sender EXT --->   Receiver ERP  =   system error 
                             Receiver-Interface is :  http/ww.ahlstrom.com/EXT/ MI_IN
       3)  furhter tests:
            a)  change FTP apdapter channel  ( put some wrong settings )
                  message in SXMB_MONI:   status-flag: processed,   acknowledgment-flag:   contains system errors
                  message in RWB-Monitor  3 messages  (  one ok,  and two error messages )
             b)  changed only the receiver communication channel to HTTP  ( other extisting scenario )
                  then the acknowledgment works fine wihout errors.
                  I'm  wondering, but here Receiver-Interface  is:   http://sap.com/xi/xI/Message/30/Acknowledgment
    Summary:  The process works,  but strange:
                      message in SXMB_MONI: unable to convert the sender service EXT to an ALE logical system
                      message in RWB:  system error
                      No problems with HTTP adapter
    Regards,
    Reinhard Doeker

    Hi,
    Addition to the above said by Udo...
    for routing the ack back to the sender system you need to create communication channel of type idoc with name as Ack.....
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
    Check the above link section 3.2
    HTH
    Rajesh

  • Unable to convert the sender service ABC_Service to an ALE logical system

    Hi,
    I have a JMS (Party) --> PI --> IDOC scenario.
    Party: ABC_Party
    Service: ABC_Service
    I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
    I have already done the below settings:
    1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
    2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
    The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
    Have already seen:
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
    Thank you,
    Pankaj.

    You need to create party if its a B2B scenario
    Under Identifiers
    under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
    Please refer this for more details
    http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
    Re: Party Configuration
    In case of cross company process it is required
    Regards
    Ninad
    Edited by: Ninad Sane on Nov 18, 2010 11:17 AM

  • (Basis)Unable to start some XI services in the J2EE Engine

    Hello,
    Our XI system was up & running Fine, however suddenly the
    J2EE engine  is unable to start some XI services like XI.Repository,XI directory,
    XI RWB etc .. However the Adapter Framework services are up & running fine .
    The Application startup fails to start even when we manually start through Visual
    Admin tool . (cluster ->server->services->Deploy) .
    We had many times stopped & started the J2EE Engine also . ABAP Stack works fine .
    We get the Class not found exception error .
    Start application
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/UploadService.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/MapServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/CrossTransport.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepSpecMiscServicesBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/ConnTestServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepLoginServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepObjectAccessBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepObjectAccessBeanSwcv.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepHmiBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepPvcMigrationBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepDiagBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepQueryServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepRoaBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepTransformationServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepEOAServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepTransportServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepChangeListMgmtBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepConflictResolutionBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepPrintViewServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepMiscServicesBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepVersionHistoryBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepAuthorizationBean.
    Error occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application [sap.com/com.sap.xi.repository].
         at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:118)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.prepareStart(WebContainer.java:398)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:89)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:233)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error while deploying web application [rep].
         at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:630)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.createContext(WebContainerHelper.java:540)
         at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:51)
         ... 10 more
    Caused by: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB  vmcid: 0x0  minor code: 0  completed: No
         at org.omg.CORBA.ORB.create_impl(ORB.java:297)
         at org.omg.CORBA.ORB.init(ORB.java:336)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.parse(WebApplicationConfig.java:116)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:617)
         ... 12 more
    Caused by: java.lang.ClassNotFoundException: com.sun.enterprise.iiop.POAEJBORB
    Loader Info -
    ClassLoader name: [sap.com/com.sap.xi.repository]
    Parent loader name: [Frame ClassLoader]
    References:
       common:service:http;service:servlet_jsp
       service:ejb
       common:service:iiop;service:naming;service:p4;service:ts
       service:jmsconnector
       library:jsse
       library:servlet
       common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
       library:ejb20
       library:j2eeca
       library:jms
       library:opensql
       interface:resourcecontext_api
       common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
       interface:webservices
       interface:cross
       interface:ejbserialization
       library:tc~jmx
       library:opensqlextensions
       service:applocking
       interface:keystore_api
       library:com.sap.exception
       library:com.sap.guid
       library:sapxmltoolkit
       library:com.sap.tc.Logging
       library:com.sap.mw.jco
       library:com.sap.mdi
       library:com.sap.lcr.api.cimclient
       library:com.sap.rprof.dbprofiles
       library:compilation_lib
       service:tcsecsecurestorage~service
       library:tci18ns2x
       library:com.sap.xi.jnlp.servlet
       library:com.sap.util.monitor.jarm
       sap.com/com.sap.aii.security.ws.proxy
       service:tcsecwssec~service
       library:tc.httpclient
       library:tcSLCMS~IDEClient
       library:tcSLCMS~Util
       library:com.sapportals.htmlb
       service:com.sap.aii.af.svc
       library:tcsldsldclient_sda
    Resources:
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ib_core.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_map_api.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrcsimpl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ibrep_core.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrutilbasic~impl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ib_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_xml.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\clientjars\clientaii_ibrep_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ib_server.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\applicationjars\aii_ib_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_mt_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ibrep_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_utilxi_misc.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\applicationjars\aii_ibrep_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_cimaccess.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrpvcimpl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrutilimpl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\servlet_jsp\rep\work
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_upload_sap.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ibrep_server.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_sql.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_mt_rt.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\clientjars\clientaii_ib_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_upload_core.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_xsd.jar
    Loading model: {parent,references,local}
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at org.omg.CORBA.ORB.create_impl(ORB.java:295)
         ... 15 more
    We had referered to notes 803145 & 753567 , but could find much help .
    Please Help .
    Regards
    Kumar

    Hi
    Refer to the link
    See the troble shooting guide
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    Regards,
    Kumar

Maybe you are looking for

  • Sharing some library items with another itunes library on the same computer

    My daughter had pretty much taken over my ipod, and thankfully just received her own for her birthday. I'm not interested in much of her music choice, so I think she should have her own itunes library; however many of the songs in my itunes library a

  • Problem with rfkord10_pdf print program

    Hi,      When i try to execute the standard RFKORD10_PDF program it shows the fallowing error. In comp.code XXX for program RFKORD10_PDF the default form set  is missing Can any one tell me suitable solution to solve this issue. with regards , M.Sree

  • Report which shows Transaction code for each company

    Hi Experts There is a requirement for a report which must display the following Parameters Tcode : S_ALR_87013340 User       Tcode                         Description      Profit Center         Profit Group     MEND    S_ALR_87013340      XXXXXXXXX  

  • E Recruitment(BSP, Webdynpro)

    In   E Recruitment  with  latest  version,  can  I  use  Webdynpro  and BSP  ( both ). IF  Webdynpro   implements  which  scenarios  we can  implement  and  BSP. Thanks, Asha

  • HT4759 Why is the iCloud not backing up?

    Why is the iCloud not backing up?