Dúvida -  NF-e: Maintain Connected Authority Systems - layout 3.10

Boa noite!
Estou realizando o customize da SPRO, porém notei que só posso inserir a seguinte entrada para um mesmo CNPJ:
Ou seja, quando tento colocar os demais estados o erro de chave duplicada é retornado devido aos campos logical system e Company's Own CNPJ. Dessa maneira, quando executo o novo programa de status de serviço (/XNFE/NFE_CHECK_SRV_STATUS) relalizando o debug noto que existe uma verificação durante a execução da função (/XNFE/SRVSTA_READ_CUST) na qual, por mais que eu tenha cadastro todos os cUF na spro que ficam registrados na tabela (/xnfe/tcuf) o status de serviço acaba sendo executado apenas para o que existe na tabela (/xnfe/govpar) alimentada pela configuração da NF-e: Maintain Connected Authority Systems da imagem que enviei posteriormente. Sendo assim só é executado o status de serviço para SP e não para todas as cUF que estão na atividade NF-e: Define Service Status Request for Authority (SEFAZ). Abaixo segue trecho do código que verifiquei que realiza esse controle no debug:
SELECT * FROM /xnfe/govpar INTO TABLE lt_govpar
                              WHERE doctype = iv_doctype.
*--- 2. Version determination
  IF lt_govpar IS NOT INITIAL.
    SELECT * FROM /xnfe/xmlversdet INTO TABLE lt_xmlversdet
                       FOR ALL ENTRIES IN lt_govpar
                             WHERE doctype  = iv_doctype
                               AND logsys   = lt_govpar-logsys
                               AND ( cnpj     = lt_govpar-cnpj
                                OR   cnpj     = ' ' )
                               AND messtype = iv_messtype.
*--- 3. Service status check parameter
    SELECT * FROM /xnfe/tcuf INTO TABLE lt_tcuf.
    LOOP AT lt_govpar ASSIGNING <ls_govpar>.
*--- Get corresponding entry from version determination
      READ TABLE lt_xmlversdet WITH KEY doctype = <ls_govpar>-doctype
                                        logsys  = <ls_govpar>-logsys
                                        cnpj    = <ls_govpar>-cnpj
                              ASSIGNING <ls_xmlversdet>.
      IF sy-subrc <> 0.
*--- If nothing is found try with blank CNPJ
        READ TABLE lt_xmlversdet WITH KEY doctype = <ls_govpar>-doctype
                                          logsys  = <ls_govpar>-logsys
                                          cnpj    = ' '
                                ASSIGNING <ls_xmlversdet>.
      ENDIF.
      IF sy-subrc IS INITIAL.
*--- Get corresponding entry for service status check parameter
        READ TABLE lt_tcuf WITH KEY doctype = <ls_govpar>-doctype
                                    cuf     = <ls_govpar>-cuf
                                  ASSIGNING <ls_tcuf>.
        IF sy-subrc IS INITIAL.
          ls_stacheck-cuf       = <ls_govpar>-cuf.
          ls_stacheck-tpamb     = <ls_govpar>-tpamb.
          ls_stacheck-xmlvers   = <ls_xmlversdet>-xmlvers.
          ls_stacheck-sscperiod = <ls_tcuf>-sscperiod.
          ls_stacheck-tzone     = <ls_tcuf>-tzone.
          ls_stacheck-respcont  = <ls_tcuf>-respcont.
          ls_stacheck-checkcont = <ls_tcuf>-checkcont.
          APPEND ls_stacheck TO et_stacheck.
        ENDIF.
      ENDIF.
      CLEAR: ls_stacheck.
    ENDLOOP.
  ENDIF.
Sendo assim, como faço para que na atividade NF-e: Maintain Connected Authority Systems eu possa inserir todos os cUF com para os quais executarei o status de serviço e posteriormente enviarei notas?
Obrigado.,

Bom dia Luís,
Exatamente! De fato o que ocorreu foi uma confusão, pois na versão anterior era possível enviar o status de serviço mesmo se você não possuísse uma filial para o estado em questão. Quando fui fazer a migração do cliente todos os estados estavam configurados para emitir status de serviço, porém não há necessidade de enviar o status de serviço para um estado visto que você não possui uma filial para emissão de Nota no mesmo.
Abs.,

Similar Messages

  • NF-e: Maintain Connected Authority Systems - Já existe uma entrada com a mesma chave

    Bom dia!
    Estou tendo um problema para adicionar novas entradas na SPRO - OUTBOUND -NF-e: Maintain Connected Authority Systems para configuração do layout 3.10:
    Sendo assim, como devo configurar todos os estados para a SEFAZ se o sistema lógico e CNPJ são chaves da tabela /xnfe/govpar?
    Com isso, não consigo executar todos os status de serviço no layout novo através do report (/XNFE/NFE_CHECK_SRV_STATUS) depois de cadastrálos na atividade NF-e: Define Service Status Request for Authority (SEFAZ,) pois durante a execução do report  (/XNFE/NFE_CHECK_SRV_STATUS) além da tabela  /xnfe/tcuf a tabela /xnfe/govpar também é verificada.
    Grato.,

    Bom dia Luís,
    Exatamente! De fato o que ocorreu foi uma confusão, pois na versão anterior era possível enviar o status de serviço mesmo se você não possuísse uma filial para o estado em questão. Quando fui fazer a migração do cliente todos os estados estavam configurados para emitir status de serviço, porém não há necessidade de enviar o status de serviço para um estado visto que você não possui uma filial para emissão de Nota no mesmo.
    Abs.,

  • Power Bi for o365 - Odata connection test worked but "The server encountered an error processing the request. See server logs for more details". Port 8051? Authority\System

    We set up the Data Management Gateway and created a new data source (odata to SQL via sqL user)
    Did a connection test and it was successful!
    Tried the URL (maybe it needs more):
    https://ourdomain.hybridproxy.powerbi.com/ODataService/v1.0/odatatest
    That resolves to some :8051 port address and then spits out this message:
    The server encountered an error processing the request. See server logs for more details.
    I checked and the data management gateway is running.
    Does that 8051 port need to be opened on our firewall for this server? How can I confirm that is the issue.. I see no event on the server indicating this is the issue?
    I am seeing this event:
    Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'PowerBiTest'. [CLIENT: IP of the Server]

    O365,
    Is this still an issue?
    Thanks!
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • Maintaining connections to/ from XI system.

    Hi,
    plz tell me,how to Maintaining connections to/ from XI system.
    with warm regards.
    vikash

    Connection from R/3 to XI  
    You have to two create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.
    Program ID will be
    LCRSAPRFC_<PID>or<XID> depends on your XI Box for RFC destination LCRSAPRFC
    and same for the next connection (SAPSLDAPI_<PID> or <XID>
    Note: make sure you give the gateway host and gateway service of the XI sytem but not the R/3 sytem. The details you can find with TX-SMGW on the xi system.
    Before testing these connections login to the VA tool on the XI system and create these destination under JCO RFC Provider and under repository make sure that you give the host name of the R/3 system as you have created the RFC connection on the R/3 server.
    once these connections are successful, go with the TX-SLDAPICUST on the R/3 system and there the R/3 system should point to the XI SLD.
    Go to RZ70 and run the data suppliers and register the R/3 system in the SLD
    USE TCode SLDAPICUST and maintain the necessary information like Host, Port.
    for RFC LCRSAPRFC and SAPSLDAPI...you hve to create this as TCPIP with PID...to find the appropriate PID for these...try to find out from the basis what they have maintained in the visual admin
    login to Visual admin...click on servers....JCO connections there what is the name of the LCRSAPRFC and SAPSLDAPI use the same name...if you are not sure of this ask the basis to give exact name
    once you do this run the TCODE SLDCHECK it shouls login to SLD...check SPROXY then
    If you are doing the IDOC communication from R/3 to XI means
    Ale Settings
    Steps
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
    IDOCXIFile Scenario
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    Note: reward points if solution found helpfull
    Regards
    Chandrakanth.k

  • Sql Server 2012 Login Failed for user "NT Authority\System"

    I have installed SQL Server on a new server. I have been getting the following error on each of the database in it.
    Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ABC'. [CLIENT: xxx.xxx.xxx.xxx]
    Here is some information on the instance:
    1) Default instance
    2) SQL Server, Sql Server Agent, Sql Server Reporting services are running / log on using a domain service account.
    3) Sql Server Browser is disabled.
    4) SQL Server VSS Writer is running / log on as Local Service.
    5) NT AUTHORITY\SYSTEM does exists in Login with just public server roles.
    I ran a trace on login failed and I get:
    ApplicationName: Microsoft Windows Script Host
    and it runs every 15 minutes.
    Help please?

    Hi,
    The error was thrown when the SCOM components connected to the backend SCOM databases.
     You can specify a domain account, grant it the sysadmin role and the error should be gone.
    Also, see the replies in your previous thread:
    http://social.technet.microsoft.com/Forums/en-US/23f6b6cb-ec41-4117-8613-26d24c948827/login-failed-for-user-username-reason-failed-to-open-the-explicitly-specified-database
    Thanks.
    Tracy Cai
    TechNet Community Support

  • XI 2.0: HowTo connect Bus.-Systems with different Releases to XI (RFC-Ad.)

    Hi,
    can anybody help me solving this problem:
    I have Business-Systems connected to XI by RFC-Adapter. Everything works fine. Now I want to upgrade some of these Business-Systems to a newer Release --> RFCs are changing! (For both Releases I have separate Developing-Systems)
    Does the following work?
    - Creating a new Product-Version
    - Creating new Software-Component-Versions for the new Product-Version
    - Creating Namespaces with the same names (as in the older Software-Component-Versions)
    - Tools/Release-Takeover for every Software-Component
    - Connecting Develop-System of the new Release to the new Software-Components (Interface-Import of RFCs)--> in the new Software-Components only new RFCs can be uploaded.
    - Business-Systems with old Release keep connected with old Product-Version. Business-Systems with new Release are connected with new Product-Version.
    Does it work? Is this the best approach or are there other possibilities?
    Thanks in advance,
    Max.

    Hey
    are u suppose to do an IDOC(R/3 system A)-Xi-IDOC(R/3 system B) scenario,of u have to collect IDOC's from both the R/3 systems and send it to a single file?
    in any case u have to maintain separate Business system and logical system name for both R/3 systems
    thanx
    ahmad
    Message was edited by:
            Ahmad

  • Critical SMS_Executive SQL Login failed for user 'NT AUTHORITY\SYSTEM'.

    I am getting sql login errors on my sms executive log that i believe is stopping me from pxe booting. I have tried finding where to enter the credentials but i cannot find it.
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    Starting SMS_EXECUTIVE... SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Microsoft System Center 2012 Configuration Manager v5.00 (Build 7958)
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    Copyright (C) 2011 Microsoft Corp. SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Running as a Win32 service. SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Process ID: 2368 SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Worker thread ID: 2412 SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Certificate (0x610450) is Exportable SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Initialize COM Security. SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    InitializeCOMSecurity: RegOpenKeyEx for appid key Succeeded.
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    InitializeCOMSecurity: RegQueryInfoKey for appid key Succeeded.
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    InitializeCOMSecurity: RegQueryValueEx for AccessPermission Succeeded.
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    InitializeCOMSecurity: IsValidSecurityDescriptor() Succeeded.
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    InitializeCOMSecurity: MakeAbsoluteSD() Succeeded.
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    InitializeCOMSecurity: CoInitializeEx() Succeeded.
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    InitializeCOMSecurity() Succeeded. SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Installation directory: E:\Program Files\Microsoft Configuration Manager
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    This server: E076SCCM SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Site server: sccmserver.org SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Site code: 076 SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    Site type: 1 SMS_EXECUTIVE
    4/10/2014 3:13:12 PM 2412 (0x096C)
    CSMSExecService::RegisterDBConnection: Register a DB connection...
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
    Initializing the status message reporting system...
    SMS_EXECUTIVE 4/10/2014 3:13:12 PM
    2412 (0x096C)
        The path to the "Status Manager" inbox is "E:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs".
    SMS_EXECUTIVE 4/10/2014 3:13:13 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:14 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:14 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:14 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:14 PM
    2412 (0x096C)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    SMS_EXECUTIVE 4/10/2014 3:13:14 PM
    2412 (0x096C)
    CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
    SMS_EXECUTIVE 4/10/2014 3:13:14 PM
    2412 (0x096C)
    CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
    SMS_EXECUTIVE 4/10/2014 3:13:14 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:19 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:19 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:19 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:19 PM
    2412 (0x096C)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    SMS_EXECUTIVE 4/10/2014 3:13:19 PM
    2412 (0x096C)
    CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
    SMS_EXECUTIVE 4/10/2014 3:13:19 PM
    2412 (0x096C)
    CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
    SMS_EXECUTIVE 4/10/2014 3:13:19 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:24 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:24 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:24 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:24 PM
    2412 (0x096C)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    SMS_EXECUTIVE 4/10/2014 3:13:24 PM
    2412 (0x096C)
    CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
    SMS_EXECUTIVE 4/10/2014 3:13:24 PM
    2412 (0x096C)
    CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
    SMS_EXECUTIVE 4/10/2014 3:13:24 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:31 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:31 PM
    2412 (0x096C)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
    SMS_EXECUTIVE 4/10/2014 3:13:31 PM
    2412 (0x096C)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
    SMS_EXECUTIVE 4/10/2014 3:13:31 PM
    2412 (0x096C)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    SMS_EXECUTIVE 4/10/2014 3:13:31 PM
    2412 (0x096C)
    CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
    SMS_EXECUTIVE 4/10/2014 3:13:31 PM
    2412 (0x096C)
    CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
    SMS_EXECUTIVE 4/10/2014 3:13:31 PM
    2412 (0x096C)
        SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used.
    SMS_EXECUTIVE 4/10/2014 3:13:47 PM
    2412 (0x096C)
    Registered this process as a source of "SMS Server" events.
    SMS_EXECUTIVE 4/10/2014 3:13:47 PM
    2412 (0x096C)
    Registered this process as a source of "SMS Client" events.
    SMS_EXECUTIVE 4/10/2014 3:13:47 PM
    2412 (0x096C)
    Registered this process as a source of "SMS Provider" events.
    SMS_EXECUTIVE 4/10/2014 3:13:47 PM
    2412 (0x096C)
    Status message reporting system initialized successfully.
    SMS_EXECUTIVE 4/10/2014 3:13:47 PM
    2412 (0x096C)
    STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_EXECUTIVE" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:47.950 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_EXECUTIVE 4/10/2014 3:13:47 PM
    2412 (0x096C)
    Certificate maintenance interval is every 1800 seconds
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_AD_FOREST_DISCOVERY_MANAGER initialized, DLL = "\bin\x64\ADForestDisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Sun Apr 13 00:00:00 2014 Eastern
    Daylight Time". SMS_EXECUTIVE
    4/10/2014 3:13:48 PM 2412 (0x096C)
    STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_FOREST_DISCOVERY_MANAGER" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.119 2014 ISTR0="2014 04 0 13 04 00 00 000" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsgdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern
    Daylight Time". SMS_EXECUTIVE
    4/10/2014 3:13:48 PM 2412 (0x096C)
    STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.120 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1=""
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_AD_SYSTEM_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsysdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
    Time". SMS_EXECUTIVE
    4/10/2014 3:13:48 PM 2412 (0x096C)
    STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SYSTEM_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.157 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_AD_USER_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adusrdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
    Time". SMS_EXECUTIVE
    4/10/2014 3:13:48 PM 2412 (0x096C)
    STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_USER_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.158 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_AI_KB_MANAGER initialized, DLL = "\bin\x64\aikbmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_ALERT_NOTIFICATION initialized, DLL = "\bin\x64\NotiCtrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_AMT_PROXY_COMPONENT initialized, DLL = "\bin\x64\amtproxymgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_CERTIFICATE_MANAGER initialized, DLL = "\bin\x64\CertMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_CLIENT_CONFIG_MANAGER initialized, DLL = "\bin\x64\ccm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_CLIENT_HEALTH initialized, DLL = "\bin\x64\chmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_CLOUD_SERVICES_MANAGER initialized, DLL = "\bin\x64\CloudMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_COLLECTION_EVALUATOR initialized, DLL = "\bin\x64\colleval.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_COMPONENT_MONITOR initialized, DLL = "\bin\x64\compmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_COMPONENT_STATUS_SUMMARIZER initialized, DLL = "\bin\x64\compsumm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_DATABASE_NOTIFICATION_MONITOR initialized, DLL = "\bin\x64\smsdbmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_DESPOOLER initialized, DLL = "\bin\x64\despool.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_DISCOVERY_DATA_MANAGER initialized, DLL = "\bin\x64\ddm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_DISTRIBUTION_MANAGER initialized, DLL = "\bin\x64\distmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_ENDPOINT_PROTECTION_CONTROL_MANAGER initialized, DLL = "\bin\x64\EPCtrlMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_ENDPOINT_PROTECTION_MANAGER initialized, DLL = "\bin\x64\EPMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_EN_ADSERVICE_MONITOR initialized, DLL = "\bin\x64\adctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_FALLBACK_STATUS_POINT initialized, DLL = "\bin\x64\fspmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_HIERARCHY_MANAGER initialized, DLL = "\bin\x64\hman.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_INBOX_MANAGER initialized, DLL = "\bin\x64\inboxmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_INBOX_MONITOR initialized, DLL = "\bin\x64\inboxmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_INVENTORY_DATA_LOADER initialized, DLL = "\bin\x64\dataldr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_INVENTORY_PROCESSOR initialized, DLL = "\bin\x64\invproc.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_LAN_SENDER initialized, DLL = "\bin\x64\sender.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_LICENSE_MANAGER initialized, DLL = "\bin\x64\licensemgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_MIGRATION_MANAGER initialized, DLL = "\bin\x64\migmctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_MP_CONTROL_MANAGER initialized, DLL = "\bin\x64\mpcontrol.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_MP_FILE_DISPATCH_MANAGER initialized, DLL = "\bin\x64\mpfdm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    SMS_NETWORK_DISCOVERY initialized, DLL = "\bin\x64\netdisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", not scheduled to start again.
    SMS_EXECUTIVE 4/10/2014 3:13:48 PM
    2412 (0x096C)
    STATMSG: ID=1106 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_NETWORK_DISCOVERY" SYS=sccmserver.org SITE=076 P

    First, if your site server is having problems logging into the DB, which it clearly is, you've got bigger issues than just PXE.
    Have you verified the permissions in your SQL Server instance for the local System account (I'm assuming at this point that it is local to the site server)?
    Jason | http://blog.configmgrftw.com

  • System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM

    Dear ALL 
    After successfully shifting the CRM from 2011 to 2013 i found a problem in Reporting section none of the report is working after some finding i conclude that MSCRM_FetchDataSource is not able to connect successfully 
    Through my report manager i tried to test the connection of MSCRM_FetchDataSource but i got the following error 
    System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed. Login failed for
    user 'NT AUTHORITY\SYSTEM'. 
    I already add the NT Authority \ System as a db_owner under my database user of MSCRM_CONFIG
    But still no success any one have any idea why it's happaning 
    Regards 
    RB

    I found a solution I hope my post will help other
    I gave the  db_owner to 'NT AUTHORITY\SYSTEM' and 'NT AUTHORITY\NETWORK' and assigned with both CRM and Config database
    It resolved my issue
    RB

  • URGENT: connection to system landscape Directory (SLD) could not be openend

    Hi ,
    information: when login as adminstrator yesterday, it asked for a new password & i given a new password to the administrator
    Error in portal: Failed to resolve JCO destination name 'WD_GPMS_RFC_METADATA_DEST' in the SLD
    My Findings
    1) http://...../sld , given j2ee_admin, pwd .
    then clicked on Administration --> showing --> status running.
    2) Logged into portal with j2ee admin , CA --> web dynpro ,
    Create Jco Destination , Maintain JCo destinatations , start assigned SLD are in the disabled mode.
    Check SLD Connection is in enable mode.When clicked on test connection ,
    it is giving the following message :
    connection to system landscape Directory (SLD) could not be openend successfully.
    3) Also CIMClient test giving failed .
    With Regards,
    NSM

    Hi Nikil,
    i had seen your reply after i had resolve the issue by my own. As my administrator password got changed, i had changed SLDDSUSER password. Both adminstrator password & SLDUSUSER password should be same.
    (any how iam rewarding you with points as mostly it is correct answer)
    Thanks
    Hussain.

  • Remove NT AUTHORITY\SYSTEM from sysadmin role - sql 2008 r2

    This topic was somewhat covered for SQL server 2005, I couldn't find any on 2008 R2, so asking again.
    I have NT AUTHORITY\SYSTEM, NT SERVICE\MSSQLSERVER and NT SERVICE\MSSQLSERVER$AGENT accounts in sql server sysadmin role on all my servers. SQL Server service and sql server agent service are running under different Active directory service accounts
    accounts, not the last two mentioned above.
    How do I remove these accounts from sysadmin role without breaking anything? Can anyone provide documentations addressing this problem specific for SQL server 2008 R2? If you know any reasons for I should not attempt to remove them,
    please point me to the 2008 r2 specific documentation. These came up in security audit and I have to provide specific docs.
    Thanks In advance.
    Mars

    Hi,
    I recommend you not to remove NT AUTHORITY\SYSTEM, NT SERVICE\MSSQLSERVER and NT SERVICE\MSSQLSERVER$AGENT accounts from sysadmin role in SQL Server 2008 R2.
    NT AUTHORITY\SYSTEM is a very high-privileged built-in account. It has extensive privileges on the local system and acts as the computer on the network.
    The Database Engine runs in Windows as a Windows service named MSSQLSERVER. The NT SERVICE\MSSQLSERVER login is used by the service to connect to the Database Engine. The SQL Server Agent runs as a Windows service named NT SERVICE\SQLSERVERAGENT. The NT SERVICE\SQLSERVERAGENT
    login is used by the SQL Server Agent service to connect to the Database Engine. The two logins act as a Security Identifier (SID) for the two services respectively in Windows, and they are members of the sysadmin fixed server role in SQL Server, so they can
    do anything in the Database Engine.
    For more details, please review the following links:
    Setting Up Windows Service Accounts:http://msdn.microsoft.com/en-us/library/ms143504(v=sql.105).aspx
    How to Create Secure SQL Server Service Accounts:http://www.mssqltips.com/sqlservertip/2503/how-to-create-secure-sql-server-service-accounts/
    Thanks
    Lydia Zhang

  • HT4972 my (4s) just updated and now it connect maintain connection to my wifi, and all apps that I downloaded are not on my screen. If i search them in the App Store I can open them, but not keep them on my screen.

    i just updated my iPhone to the new operating system.  It will not maintain connection to MY wifi.  In addition, the applications that I had installed are no longer on the screens. I can only access them via the app store... and there I can "open" them,

    Tried that as well. The problem isn't that the apps aren't downloading, it's that the app icon is stuck on Waiting. I can actually open and use the apps from the App Store, but not from the home screen.
    I'm adding photos to try help explain, though I'm not they'll show up well on since I'm on mobile.
    THats the the home screen with useless icons
    BUt if I search the App Store for one (like Buzzfeed)
    IT it shows it being installed, and I can even open the app an use it. I would try to reinstall but I cant remove the apps.

  • Steps for connecting ext. system (nonSAP) via tRFC

    Hi i need detailed description on how to connect ext. system (nonSAP) or program to XI.
    I need a RFC-Destination - what type?! TCP/IP?!
    Scenario will be that we send a receive IDoc from this nonSAP-System.
    Can someone provide me with detailed informations?! Which user-type etc., do i need a user....?
    br

    Hi,
    Assuming target system is your R3.
    You need to follow the below configuration:
    Pre-requisites for Inbound IDoc to R/3 from PI:
    Configuration required at Xi side:
    Go to IDX1: configure the port.
    Go to IDX2: load the DOC metadata.
    Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
    Configiration required at R3 side:
    Maintain Logical System for XI (transaction SALE)
    Maintain Port (WE21)
    Maintain partner profile for XI. (WE20):
    This is just example you can see the configuration part:
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Thnx
    Chirag

  • Iphone 5 wifi does not maintain connection or automatically connect

    I phone 5 does not always maintain connection and does not automatically connect. I have selected the wifi system and entered password for such but each time I have to reenter password.

    "Ask to join networks" is off. I also tried turning off the phone and restarting it. My wife's iPhone 5 is doing the same thing. Could it have something to do with my router?

  • DB connect source system creation in BI

    Hi,
    I would like to create a DB connect source system to an external MSSQL 2005 database in RSA1.
    The external MSSQL 2005 database is setup using Windows Authentication mode.
    Question: Which user actually should I specify when creating the source system in RSA1? or which user should I assign the db_ddladmin role in the external MSSQL database?
    Many thanks,
    YJ.

    Hi,
    Please note the following with regard to the user:
    To avoid problems loading data, proceed as follows:                   
    1. Create a special login for the extraction. You should add this login to the db_ddladmin database role in the 
    corresponding database. This generates a similar DB user at database level. The user you use must have the 'CREATE VIEW'
    authorization at least.  This is contained in the role mentioned above.
    2. For the extraction, you should only use DB views that were  created under this DB user. (refer also to type conversion, naming       
    convention and so on)                                                    
    3. Assign the necessary authorizations (SELECT at least) to the  selected user in the source tables, or the columns of these tables.      
    4. Use the specially created login in the logon information when you set up the DB source system in BW.   
    You will find much more detailed information on how to setup the connection and known problems and issues in the
    attached note 512739.
    Best Regards,
    Des.

  • Error when connecting to system

    Hi,
    I have been off topic for quite a while and when I wanted to pick up today, I couldn't connect to the HANA server anymore. I haven't changed any settings since last setup, all I get is the "Error when connecting to system" in the Quick Lauch of the infornation modeler.
    Any suggestions?
    THX
    Markus

    Hello,
    did you connect since upgrade to SP03?
    You might be looking for this thread.
    SAP In-Memory Developer Center - planned downtime 2011-11-15, 10-11am PST
    Tomas

Maybe you are looking for

  • Flattened PDF Form and Barcode not displaying

    I see there are a lot of discussions that are not answered in this forum, so I am guessing this will go unanswered as well.  But I am looking for a solution for the issue in the subject. I have a simple PDF form built in LiveCycle that I am populatin

  • August 2014 Scheduled Maintenance - Are Web and Worker Roles affected?

    Are Web and Worker Roles affected by the Scheduled Maintenance that will be performed on Aug 2, 2014?  The email that I received from Microsoft Azure states that it will affect VMs and Cloud Services and goes on to say how to keep your VMs available

  • How to update Oracle Release 10.2.0.1 to 10.2.0.3

    Hi, Can anybody give me hint how can i update my oracle version 10.2.0.1 to version 10.2.0.3. I have installed oracle 10gR2 with following: SQL> select * from v$version; Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod PL/SQL Release

  • Count duplicates

    I want to select all state codes with multiple pack_size. Example is state_code 3737 with pack_size of 5 and 6. state_code pack_size 3729     12 3733     3 3734     12 3735     120 3737     5 3737     6 3756     12 3756     11

  • Page advancing problem in dotmatrix printing

    Hi Experts, We are trying to print 6 X 2 Inch sticker using dotmatrix printer in smartforms, For this I have defined a page formate assigned it to Device type and under the initialization written the following code reset \e\0x40 set line spacing 6 LP