Error 70  - Código do status 225: Rejeição: Falha no Schema XML da Nfe.

Bom dia grupo!
Nós estamos atualmente recebendo a seguinte mensagem de erro da SEFAZ relacionado aos batches que nós enviamos: Error status 70 "Error from the authorities" and Código do status (Status Code) 225: Rejeição: Falha no Schema XML da Nfe.
Nossa configuração é 46C com muitos OSS notes aplicados (veja abaixo)
Nós estamos realmente parados neste momento e não temos nem ideia de onde começar.
Atenciosamente,
Marc de Ruijter
OSS notes for NF-e phase 2
989115      Nota Fiscal Electronica (NF-e) - Overview Note
852302      Implementation Overview ISS 2004 - Legal Change MP135/LC116
759965      New Condition Formulas for MP-135 and ISS 2004
747607      Basic Customizing for MP135 and ISS legal change Brazil
980214      DDIC changes: PIS / Cofins Tax Law and Tax Situation
981123      PIS / Cofins Tax Law and Tax Situation
981687      NFe: For Services in Muncipio Sao Paulo
934846      Syntax error: TYPE-POOL 'SXRT' is unknown
979881      Message S 000 in NF writer when mandatory fields not filled
980213      Nota Fiscal Electronica (NF-e) of SEFAZ - Phase 2
1037070      NF-e of SEFAZ - Phase 2, Enhancement 01
1014600      No output found for the Nota Fiscal
1052575      NF-e of SEFAZ - Phase 2 / DDIC changes after shipment
1043688      NF-e of SEFAZ - Phase 2, Enhancement 02
1062468      NF-e: Multiple volume structure for XML file
1062251      NF-e: Extension of BADI Interface FILL_HAEDER
1070261      NF-e of SEFAZ - Phase 2, Enhancement 03
1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
1000130      Public System for Digital Bookkeeping (SPED) - Overview Note
1008306      SD: Manual changes of CFOP for services when ISS tax applies
998194      Missing ISS Tax Situation in the Nota Fiscal
1047606      SD/Brazil: Using of error log during Nota Fiscal creation
120449      SD-Brazil Exchange variance error in Nota Fiscal
92383      LSA:BR:SD: Tax laws in return nota fiscal
689157      Nota Fiscal Split and number of Packages
987882      ISS Tax Law (field J_1BTAXLW3) not copied from sales order
989965      CFOP redermination in the delivery document not working
909835      Message 8B 679 raised during the delivery process
337554      SD: No. of packages in Nota Fiscal
533046      Repair order inconsistent to object list
920330      Error when changing the tax codes in a sales order
998195      PIS/COFINS/ISS Tax Law and Tax Situation in SD
104606      EDI/IDoc: Mapping IDoc types to ANSI X12
1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
1105588      J_1BLFZF: Runtime error OBJECTS_OBJREF_NOT_ASSIGNED
     OSS notes for XML ver 1.1 and NF-e phase 3
1065334      NF-e: Extension of BADI Interface FILL_ITEM with tax table
1068615      NF-e: Extension of BADI Interface with SD document flow
1079826      NF-e: BAdI Interface Enhancement for NF Messages
1069919      NF-e: Partner in Block E should always be main partner
1090279      NF-e monitor: automatic refresh upon user actions
1093252      NF-e: ICMS tax situation in XML File and DANFE
1113127      NFe: New XML Layout - Version 1.10
1114348      NF-e - xNFe integration - backend
1122294      Send/resend NF-e: fill VBFA for BAdI item method
1124075      NF-e: Serie not taken from Contingency NF-Type
1144194      NF-e: Cancellation/Skipping Reason
     Bug Fix notes for NF-e BAPI.
1049946      NF-e: Adaption of Nota Fiscal Bapis
1147934      NFe: Random number should not be generated for incoming NFes
1150733      NFe: Randon number and check digit not cleared
1154995      NF-e: NF BAPI - enhancement for NF-e processing
1158622      NF-e: NF BAPI - no input of random number possible
     Bug Fix notes for Contingency process
1158612      NF-e: Wrong partner in Block-E for Entrada
1240212      NF-e: One time Vendor data not transferred to XML file
1255450      NF-e: Jurisdiction code for one time vendor / customer
1257030      NF-e: Country Name for one time vendor / customer
1069018      Cancellation of incoming NFe shows error J1B_NFE 003
1070077      NF-e: Protocol number and document status for Denied NF-e
1145148      NFe: Cancellation for Contingency NFes
1152263      NF-e monitor: wrong action status '7' for C-NF-e
1146914      NFe: Synchronous call to messaging system from backend
1149356      NFe: Dump when NFe is cancelled with MIGO
1152081      NFe: Dump when NFe is cancelled with VL09
1153533      NFe: Dump when NFe in contingency is cancelled with VL09
1156116      NF-e: Contingency by stock transfers
1160107      NF-e: Cancellation of contingency NF-e with DOCSTA = 1 or 2
1161347      NF-e: Cancellation of Contingency NF-e - correction
1238648      NF-e monitor: req. action '3' (send) wrong for swtch. NF-e
1165953      NF-e: Numbering Gaps
1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP
1245425      NF-e monitor: required process step - contingency
1252567      NF-e: Resend of NF-e - rejected or with validation error
1266344      NF-e: Action Indicator for NF-e with validation error
1254565      NF-e: Synchronization of RFC call between ERP and xNFe
1053626      MIRO: wrong document reference in nota fiscal
1073259      NF-e: Transfers - Outgoing NF-e No. not taken by Incoming
1153874      NF-e: GR for future delivery takes wrong NF-e number
1174946      NF-e: Serie not considered for duplicate NF-e number in MIRO
     Miscellaneous bug fix notes
1175538      NF-e: Reference between NF and NF-e
1244881      NF-e: Mixed scenario in MIRO shows error 8B219
1257422      MIRO: Error 8B 219 by posting of reference invoices
1150843      NFe: Text for cancel reason not transferred to XML file
     Bug Fix Notes Group 2
1059699      NF-e: Reference between NF and NF-e
1139062      NF-e incoming: Posted via J1B1N -> Wrong Document Status
1144199      NF-e: SD Billing and Contingency
1145089      NF-e: Cancellation despite rejected cancel request
1149787      NF-e: Wrong status-code text in NF-e history
1151112      NF-e: cancellation-reason text gets lost (pre req of 1150172)
1150172      NF-e monitor: selection leads to dump
1068379      Creation of Billing document issues an error 8B 145 (pre req of 1145089)
1152842      NF-e: cancellation reason does not work
1154700      NF-e: Random number & check digit not stored in active table
1073145      PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
1082527      Missing PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
997868      VL02N: CFOP, tax laws not copied from delivery (error 8B148) u2013 (pre req of 1155231)
1155231      PIS/COFINS tax law in NF/NF-e by split valuated material
1155424      NF-e monitor: Menu -> "Check MS Connection" does not work
1159177      NF-e: FUNC J_1B_NFE_SET_STATUS_IN_BACKEND set as Rem.Enabl
1161951      NF-e monitor: "Resend" functionality.
1162232      NF-e: switch to contingency not possible after MSS Update
1162512      NF-e: cancellation reason not initial at first-time call.
1162629      NF-e: creation date gets deleted from NF-e data-base table
1164283      NF-e: SCS '5' - upon authr.to cancel system does not cancel
1165155      NF-e Monitor: BACK (F3) leads to cancellation
1165360      NF-e Monitor: new selection parameter - creation user
1168394      NF-e: Reference document not taken from Nota Fiscal header
1168798      NF-e: User decision for used NF-Type for Material Movements
1171383      NF Writer: Copy NF-e that was switched to contingency.
799445      Nota Fiscal creation: Consideration of local dates (pre req of 1171383)
1104003      NF-Writer: Serie not taken from Reference NF (pre req of 1171383)
1156037      NF-e: NF-Writer allow reference with different NF-types (pre req of 1171383)
1175759      NF-e: central contingency per business place - correction
1239598      NF-e: Random number and check digits are lost in NF writer.
1163888      NF-e: Random Number includes spaces (pre req of 1239598)
1245425      NF-e monitor: required process step u2013 contingency. u2013 applied in bug fix notes no need to apply.
1246700      NF-e: Wrong reference for NF entradas.
1257688      NF-e: Update termination with error J1B_NFE 021
1258021      NF-e: Dump by creation of NF header text for XML file
1258974      NF-e: Monitor report aborts with DBIF_RSQL_INVALID_RSQL
1265172      NF-e - Decouple RFC from DB Update
1285851      NF-e: Cancellation of none authorized documents
1288925      NF-e: References between NF-e and non NF-e
1272677      NF-e: Cancellation for Material Document with serial number (pre req for 1288925)
1247602      NF-e: Cancellation of material documents with serial numbers
1163104      NF-e: Cancel Material documents with initial cancel reason
1293944      NF-e: Cancellation of material documents with batch classes.
1267128      NF-e: Cancellation goods movement with MVT 844 not possible (pre req for 1293944)
1300000      NF-e: Decouple - Contingency
1314856      NF-e: Decouple - Contingency in J1BNFE and VF01 & VF04
1321837      F-e: Cancel of material documents not possible
1092028      NF-e: Protocol number in NF-header overwritten (pre req for 1265172)
1114283      NF-e: cancellation - document status cleared in J_1BNFDOC (pre req for 1265172)
1234053      Local time / local date in NF header and NF-e XML (pre req for 1265172)
1288994      NF-e: Decupling note 1265172 causes error for incoming NF-e (pre req for 1300000)
1297042      NF-e: NF-e number missed in access key after decoupling (pre req for 1300000)
1087535      RFFOBR_A,U:Doc.no should be filled with 9 digits in DME file Applied OSS note 1087535 to the object Z_RFFORIY1 which was copied from RFFORIY1
1097455      NFE: Bank files should accommodate Doc. Numbers with 9 digits
304961      Wrong boleto check digit with carteira data (pre req of 1097455) - Not relevant
336117      Include due date factor in Boleto barcode for A/R (pre req of 1097455) - Not relevant
705726       ITAU: Boleto has negative interest value (pre req of 1097455) - Not relevant
846297      Func Mod - BOLETO_DATA not printing correct nosso numero (pre req of 1097455) - Not relevant
852782       BOLETO_DATA - Corrections of note 846297 for Bredesco only (pre req of 1097455) - Not relevant
1227478      Dump in payment run (F110) when XBLNR is empty
1138278      NFe: Field PREDBC not filled in XML interface structure (pre req of 1149585)
1149585       NFe: CST field required in XML file for taxes not in NFe
1053855      VL02N raises error 8B 053 "Branch not foundu201D
1165696      RFEBBU00: Error in batch input due to changes in Nota Fiscal
1180402      NF-e: BADI methods FILL_HEADER and FILL_ITEM
1180672      NF-e: Gap numbering check doesnu2019t consider the series
1225338      RFEBBU00: Additional changes to the note 1165696
1241922      NF-e: Report J_1BNFECHECKNUMBERRANGES xNFe adaption
1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP (Applied using other Kintana)
1270813      NF-e: Year not included in the XML file
1247264      NF-e: Error in RFC to /XNFE/NFE_CREATE after note 1241922 (pre req for 1274200)
1274200      NF-e: Numbering gaps report sends SERIE with spaces
1276185      NF-e: Numbering gaps report sends SERIE with spaces
1294917      NF-e: Gap numbering check - several corrections
1324538      Missing address for OT Customer in J_1B_NFE_CREATE_TXT_FILE
1331432      NF-e: Numbering gaps report detects gaps for initial series
1332167      NF-e: Rep. J_1BNFECHECKNUMBERRANGES aborts with error DC 006
1092341      RFFOBR_A,RFFOBR_D: Performance problem while rebate calcula
1237089      RFEBBU10:While uploading ITAU Bank returnfile- Error(F5 170)
1051314      Check Digit missing from Boleto number (pre req for 1306966)
1306966      J_1BBR30:XREF3 is not updated correctly with Boletofrom bank
1005924      RFFOBR_A-The DME file does not include Rebate for ITAU (pre req for 1287633)
1287633      RFFOBR_A: Discount amount not calculated correctly
1234054      NF-e: function J_1B_NFE_MS_REQUESTS_DATA is not RFC enabled
1297534      NFe cancellation problems in GRC
1243964      NF-e: Adaption of xNFe interface of function NFE/NFE_SKIP
1165746      NF-e: Cancel - Error log not updated
1327465      The program /xnfe/update_erp_status is not updating R/3
1326691      BAdI for controlling the RFC call of external systems
1333136      Prevent simultaneous click on buttons in NF-e monitor
1333742      NF-e got the status 218
1354192      Validation rules: correction for fields TPLACA and T_UF1
1373175      Lock object for /XNFE/NFE_CREATE to prevent double transm
1376500      BAPIRET2 to provide the detailed information to ERP
1267455      Not possible to create different DOCREF per item using BAPI (pre req for 1373321)
1373321      BAPI_J_1B_NF_CREATEFROMDATA: DOCREF from Header go to item
1328583      NF-Writer posting of NF/NFe when mandatory fields not filled
1338166      NF-e: Random number and check digit lost after note 1328583
1259918      NF-e: RFC calls for request for cancellation or skip
1152140      NF-e: backend allows inconsistent new SCS (pre-req for 1298283)
1162852      NF-e: Inbound errors missed in error log of Monitor Report (pre-req for 1298283)
1163056      NF-e: Problems with printing via BADI method CALL_RSNAST00 (pre-req for 1298283)
1276438      NF-e: Parallel Phase not identified in messaging system (pre-req for 1298283)
1296515      NF-e: J1BNFE reset rejected NF-e after skipping request (pre-req for 1298283)
1297823      NF-e: Cancelled NF-e shows wrong action indicator (pre-req for 1298283)
1298283      NF-e: Skip for NF-e with validation error
1362969      NF-e: check cancellation for billing documents
1368159      NF-e: cancellation of invoices via original application only
1370933      NF-e: Accept Rejection to Cancel - wrong status in monitor
1376324      NF-e: Skip for NF-e with validation error
1140579      NFe: Field length conflicts from backend interface to XML
1357713      NF-e: Cancel of incoming NF-es does not update active table.
1173018      NF-e: Field control for Random Number and Check Digit (pre-req for 1366320)
1321517      NF-e: MIRO Credit Memos for NF-e shows error 8B 020 (pre-req for 1366320)
1366320      NF-e MIRO:Save is allowed without mandatory fields filled for NFe
1375066      NF-e: J_1BNFECHECKNUMBERRANGES ends too early, wrong subrc
1375894      NF-e: J1BNFE authority check for company code
1377879      NF-e: Report J_BNFECALLRFC aborts with message A098
1379062      NF-e: posting GR after cancellation leads to wrong NF-e
1357777      Cancel billing document without Nota Fiscal cancellation
1380861      NF-e Resend(proc.stat.07) with Signature error impossible
1362025      Error while sending Bacen Code EX with 0 on begining
1249819      NF-e: Field MODFRETE filled incorrectly

Bom dia Marc de Ruijter,
Não dá para ler sua thread, mas imagino que seu validador esteja desligado.
No GRC vá em SPRO --> SAP GRC Nota Fiscal Electronica --> Configure System Response for Each Tax Number (CNPJ)
Para ligar/desligar o Validador basta clicar no check box na coluna Validation.
Observação: Para correto funcionamento do GRC deve-se sempre utilizar o validador ligado.
Após isto refaça seu teste, é provável que você receba um erro de validação para a NF-e. Veja em GRC Web monitor -> NFe Detailed View -> Validation History.
Atenciosamente,
Fernando Da Ró

Similar Messages

  • NFe 3.10 - Erro 225: Rejeição: Falha no shcema XML da NFe

    Boa tarde.
    Estamos com problema no Schema do XML, já verificamos as informações do post abaixo:
    http://scn.sap.com/thread/3714800
    Aqui também ocorre o mesmo problema e quando reenviamos a nota o xml é processado. Porém, precisamos encontrar uma solução
    onde não seja necessário o reenvio manual do documento.
    Baixamos o XML com problema e depois da validação no SEFAZ (após o reenvio) e a unica diferença é a tag abaixo:
    Ela é criada após a validação do XML?
    *** XML Erro Schema
      <?xml version="1.0" encoding="utf-8" ?>
    - <NFe xmlns="http://www.portalfiscal.inf.br/nfe">
    *** XML OK, após o reenvio da NF
      <?xml version="1.0" encoding="utf-8" ?>
    - <nfeProc xmlns="http://www.portalfiscal.inf.br/nfe" versao="3.10">
    - <NFe xmlns="http://www.portalfiscal.inf.br/nfe">
    Gostaria de saber se alguém já passou por este problema e qual foi a solução aplicada.
    obrigado
    Juliano Diniz

    Oi Michael,
    Essa declaração que o José comentou é diferente mesmo, não vi em nenhum outro cliente e ela que deu erro no validador da SEFAZ no seu teste. Se você remove essa TAG e faz o teste no validador da SEFAZ RS o XML aponta outros erros.
    Teoricamente o XML começaria assim:
    <?xml version="1.0" encoding="UTF-8"?>
         <NFe xmlns="http://www.portalfiscal.inf.br/nfe">
    Além disso o XML do TXT tem umas quebras de linha que separaram o conteúdo das TAG's e causaram erro no validador da SEFAZ tb.
    O validador do GRC é basicamente uma função que aponta erros técnicos no preenchimento dos dados que vieram do ERP ( campos obrigatórios em branco, campos numéricos com valor alfanumérico, etc...) porém ele não validaria a estrutura final do XML ( encoding, montagem das TAG's e namespaces adicionados ).
    OBS: No arquivo adicionado tem o XML completo e por uma questão de "data protection" eu não recomendaria disponibilizar esse tipo de arquivo na internet, pois ele contém dados teoricamente sigilosos de negócio ( Clientes, transportadores, produtos/preços, Certificado digital da empresa emissora, etc...).
    att,
    Renan Correa

  • Erro 225 -  Falha no Schema XML do lote de NFe com mensagem formato invalid

    Pessoal, boa noite.
    Estou me deparando com um problema de validação de NFe no Sefaz GO, onde está retornando o erro 225, mas quando verifico o retorno tenho a mensagem de que o formato não é valido (abaixo print) . Verificando o dado, não tem nenhuma divergencia entre os demais valores.  Alguém ja se deparou com este erro?
    <?xml version="1.0" encoding="utf-8" ?>
    - <ns1:nfeRetRecepcaoResponse2 xmlns:ns1="http://sap.com/xi/NFE/006">
    - <ns1:nfeRetRecepcao2Result>
    - <ns2:retConsReciNFe xmlns:ns2="http://www.portalfiscal.inf.br/nfe" versao="2.00">
      <ns2:tpAmb>2</ns2:tpAmb>
      <ns2:verAplic>GO2.0</ns2:verAplic>
      <ns2:nRec>521000004377506</ns2:nRec>
      <ns2:cStat>225</ns2:cStat>
      <ns2:xMotivo>Rejeição: Falha no Schema XML do lote de NFe</ns2:xMotivo>
      <ns2:cUF>52</ns2:cUF>
      <ns2:cMsg>225</ns2:cMsg>
      <ns2:xMsg>cvc-pattern-valid: Value '5499.00' is not facet-valid with respect to
    pattern '0|0.[0-9]{2}|[1-9]{1}[0-9]{0,12}(.[0-9]{2})?' for
    type 'TDec_1302'.</ns2:xMsg>
      </ns2:retConsReciNFe>
      </ns1:nfeRetRecepcao2Result>
      </ns1:nfeRetRecepcaoResponse2>
    Edited by: Fernando Ros on Apr 22, 2011 8:03 AM adicionando tag code para visualizar todos os caracteres

    Bom dia Carlos,
    Em sendo a Sefaz GO a inconstância não me surpreende, mas a de se estar atualizado, principalmente com o removedor de caracteres e validador ativo para evitar a chance do programa da Sefaz se confundir que é o que parece estar acontecendo... Está apontando o problema num lugar onde a mensagem apresentada está ok.
    Sugiro atualizar o sistema ao SP18 que é o necessário para trabalhar de forma saudável com layout 2.0
    Atenciosamente, Fernando Da Rö

  • NFE Produção - Código Status 204 Rejeição

    Olá, Boa tarde!
    Estamos com uma NFE da Produção parada, pois não estamos conseguindo atualizar o status dela.
    No monitor de GRC a NFE aparece da seguinte forma:
    Status NFE (bolinha vermelha): 05 resultado recebido
    Status de Erro: 90 erro de sistema PI
    Código Status: 204 Rejeição: Duplicidade NFE
    A opção "Consulta do Status" está disponível, porém já tentamos várias vezes, aparece a mensagem: O processo de consulta status NFE foi inicializado. Atualizar a exibição NFE.
    Atualizamos a página, porém não muda nenhum status.
    No monitor J1BNFE a NFE está aguardando o retorno do GRC.
    Não sei se tem algo a ver, mas recentemente fizemos a atualização da Versão para 2.0.
    Antes o procedimento funcionava normal... agora as NFES estão paradas...
    Aguardo comentários.
    Obrigada.
    Adriana

    Bom dia,
    Estou com esse mesmo erro, e não sei como resolver...
    Ao clicar em consultar status(Monitor GRC) da NFE em questão, o status não é atualizado(consultamos no SEFAZ e a NFe Está aprovada)..
    Verifiquei as msg na MONI e temos uma com o ACK NEG, porém desconheço o erro...segue os xml que consegui verificar na mensagem:
    XML INBOUND:
      <?xml version="1.0" encoding="utf-8" ?>
    - <n0:nfeConsultaNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PIP:/1SAI/TASB4840BC26BF382F75BE8:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
      <n0:cUF>41</n0:cUF>
      <n0:tpEmis>1</n0:tpEmis>
      <n0:tpAmb>1</n0:tpAmb>
      <n0:type>1</n0:type>
      <n0:versNum>001</n0:versNum>
      <n0:mode>I</n0:mode>
    - <n0:nfeDadosMsg>
    - <n1:consSitNFe versao="2.00">
      <n1:tpAmb>1</n1:tpAmb>
      <n1:xServ>CONSULTAR</n1:xServ>
      <n1:chNFe>41110300606549000124550000000231711903353574</n1:chNFe>
      </n1:consSitNFe>
      </n0:nfeDadosMsg>
      </n0:nfeConsultaNF2>
    XML RESPONSE:
      <?xml version="1.0" encoding="utf-8" ?>
    - <n0:nfeConsultaNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PIP:/1SAI/TASB4840BC26BF382F75BE8:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
      <n0:cUF>41</n0:cUF>
      <n0:tpEmis>1</n0:tpEmis>
      <n0:tpAmb>1</n0:tpAmb>
      <n0:type>1</n0:type>
      <n0:versNum>001</n0:versNum>
      <n0:mode>I</n0:mode>
    - <n0:nfeDadosMsg>
    - <n1:consSitNFe versao="2.00">
      <n1:tpAmb>1</n1:tpAmb>
      <n1:xServ>CONSULTAR</n1:xServ>
      <n1:chNFe>41110300606549000124550000000231711903353574</n1:chNFe>
      </n1:consSitNFe>
      </n0:nfeDadosMsg>
      </n0:nfeConsultaNF2>
    XML ACK ERROR:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <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="BPE_ADAPTER">NEGATIVE_ACKNOWLEDGEMENT</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Negative acknowledgment triggered by a process</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Alguém teria alguma dica?
    Edited by: João Luis da Silva Dovigo on Mar 16, 2011 6:20 PM

  • CTE CT-e não autorizado. Código de status 239, motivo: Rejeição: Cabeçalho - Versão do arquivo XML não suportado

    Boa tarde a todos,
    Já configuramos os cenários do CT-e para a versão 2.00, mas temos algumas notas com o seguinte erro:
    CT-e não autorizado. Código de status 239, motivo: Rejeição: Cabeçalho - Versão do arquivo XML não su
    mesmo reiniciando o processo, o status se mantem com o 239,
    alguém teria alguma solução para processar estes CT-e novamente?
    desde ja agradeço.
    Alexandre.

    Alexandre,
    Estou com o mesmo problema, o erro corre na validação do CTe de entrada quando ele foi emitido na versão 1.04.
    Realizei um teste passando a chave do CTe alterando o parametro versão para 2.0 e a consulta retornou com sucesso. Estou pensando em fazer um mapping forçando a versão para 2.0.

  • Código de Status 109

    Boa Tarde,
    Estamos com a situação de um rejeição de 9 Nfe que estão retornando o código de status 109 - Serviço Paralisado sem Previsão da SEFAZ-MT.
    Como podemos alterar esse código de status, para que o nota fiscal possa ser reenviado para a Sefaz?
    Já validei o XML no site da SEFAZ e ele está OK, assim como não existem caracteres estranhos na mensagem.
    Desde já agradeço a ajuda.
    Edgar Oliveira.
    Edited by: Suporte SAP Rexam Procwork on Jul 20, 2009 7:33 PM

    Peguei uma nota para exemplo e segue o histórico do que aconteceu:
    No dia 18/07/2009 as 10:28 foi enviada pela J1BNFE para o GRC. GRC enviou para SEFAZ e retornou o Status 109.
    Fizemos o procedimento de resetar e enviar novamente várias vezes inclusive hoje mesmo. Volta sempre com o mesmo Status.
    No GRC, consultando o histórico das notas só tenho como envio e recebimento no dia 18/07/2009. Os lotes das notas foram enviados somente no dia 18/07/2009.
    O que eu acredito que está acontecendo é que o PI não está reenviando estas notas para a SEFAZ. Esta pegando o status que se encontra no GRC e atualiza no R3.
    Abaixo o link com o histórico de uma das notas:
    Histórico J1BNFE: http://img149.imageshack.us/img149/6527/nfstatus109.jpg
    Status GRC:
    http://img79.imageshack.us/img79/8497/nfstatus109grc.jpg
    http://img174.imageshack.us/img174/2851/nfstatus109grc1.jpg
    Att,
    Edgar Oliveira.

  • Error Invoking Web Service Action: Status (500): null

    Hi forum
    I am getting an "Invoking Web Service Action: Status (500): null" error  when invoking a web service action block .  The BLS transaction used as a web service outputs a text string which I tested using an xacute query . while executing the transaction as a web service the tracer tells me that there is no output .
    Best regards,
    Antonio
    I am using an xMII 11.5 installation  .
    [INFO ]: Execution Started At: 04:17:46
    [DEBUG]: 00000.01600 Begin Transaction 'TMP45B360D9-0E02-2CF7-C4B4-F3C0B41C29E0'
    [DEBUG]: 00000.01600 Begin Sequence Sequence : ()
    [DEBUG]: 00000.01600 Begin Action WebService_0 : ()
    [ERROR]: Error Invoking Web Service Action: Status (500): null
    [ERROR]: ACTION FAILED: End Action WebService_0 : ()
    [DEBUG]: 00000.11000 Begin Sequence Sequence_0 : ()
    [DEBUG]: 00000.11000 Begin Action Tracer_0 : ()
    [INFO ]:
    [DEBUG]: 00000.11000 End Action Tracer_0 : ()
    [DEBUG]: 00000.11000 End Sequence Sequence_0 : ()
    [DEBUG]: 00000.11000 End Sequence Sequence : ()
    [DEBUG]: 00000.11000 End Transaction 'TMP45B360D9-0E02-2CF7-C4B4-F3C0B41C29E0'
    [INFO ]: Execution Completed At: 04:17:46 Elapsed Time was 94 mS

    Jamie,
    Yes Indeed, I was calling inside a web service action another BLS transaction .  Now ,  I am using a call to the transaction using the runner . It worked fine .
    Thanks,

  • CUA: One or more errors occurred while checking the status of Windows Firewall on the cluster nodes

    Cluster with 2 hosts 2012 R2
    Scheduled CAU fails with:
    CAU run {4EFE116C-AB49-456D-8EED-F7EDC764DA49} on cluster Cluster1 failed. Error Message:One or more errors occurred while checking the status of Windows Firewall on the cluster nodes. Review the errors for more information on how to resolve the problems.
    Error Code:-2146233088 Stack:   at MS.Internal.ClusterAwareUpdating.Util.<CheckFirewallsAsync>d__3a.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand.<_ProcessCluster>d__78.MoveNext()
    If I run CAU "Analyze Readiness" ALL comes as PASS
    If I run CUA by hand on same hosts with NO change to the system (not even reboot) it finishes OK
    Anybody any ideas?
    Thanks
    Seb

    Hi,
    In some case if you disabled the connection in Windows firewall inbound of
     "Cluster aware updating" service it will can’t use the CAU.
    More information:
    Starting with Cluster-Aware Updating: Self-Updating
    http://blogs.technet.com/b/filecab/archive/2012/05/17/starting-with-cluster-aware-updating-self-updating.aspx
    What is Cluster Aware Updating in Windows Server 2012? (Part 1)
    http://blogs.technet.com/b/mspfe/archive/2013/02/06/what-is-cluster-aware-updating-in-windows-server-2012.aspx
    Cluster-Aware Updating Overview
    http://technet.microsoft.com/en-us/library/hh831694.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • There was an error trying to get the status of the job. 1: The server returned an error processing CloseJob: Stack empty.

    Hi
    While trying to perform the operation 'Annul All Below' in DRM 11.1.2.1, I received the following error: There was an error trying to get the status of the job. 1: The server returned an error processing CloseJob: Stack empty.
    Has anyone seen this error before, and does anyone know what the fix is?
    Thanks,

    Just giving my view on this.
    When you try to restore a Version backup file, you get this error.
    This is a known defect.  The problem is caused by missing values in properties like AddedOn, AddedBy, which may occur when a version is copied with 'Clear Changed Properties' selected.
    this is a known bug
    but to workaround - Blend the affected version into a new, empty version, which will populate the 'ChangedOn' properties. You can then back up this version and it will restore.
    Thanks,
    ~KKT~

  • Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 500

    I get the following error when trying to connect to my BlazeDS Java server from Flex application. Flex application is on localhost:80, blazeDS on tomcat localhost:8080. Please help!
    createUser();faultHandler():(mx.messaging.messages::ErrorMessage)#0
      body = (Object)#1
      clientId = (null)
      correlationId = "9FFDEBE8-EAD0-F3D9-8E9B-E3D7D7F5AE79"
      destination = ""
      extendedData = (null)
      faultCode = "Client.Error.MessageSend"
      faultDetail = "Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 500: url: 'http://77.93.202.150:8080/QuizDS/messagebroker/amf'"
      faultString = "Send failed"
      headers = (Object)#2
      messageId = "98F54E19-7B0D-DCB9-4B86-E3D7D84E484F"
      rootCause = (mx.messaging.events::ChannelFaultEvent)#3
        bubbles = false
        cancelable = false
        channel = (mx.messaging.channels::AMFChannel)#4
          authenticated = false
          channelSets = (Array)#5
          connected = false
          connectTimeout = -1
          enableSmallMessages = true
          endpoint = "http://77.93.202.150:8080/QuizDS/messagebroker/amf"
          failoverURIs = (Array)#6
          id = (null)
          mpiEnabled = false
          netConnection = (flash.net::NetConnection)#7
            client = (mx.messaging.channels::AMFChannel)#4
            connected = false
            maxPeerConnections = 8
            objectEncoding = 3
            proxyType = "none"
            uri = "http://77.93.202.150:8080/QuizDS/messagebroker/amf"
          piggybackingEnabled = false
          polling = false
          pollingEnabled = true
          pollingInterval = 3000
          protocol = "http"
          reconnecting = false
          recordMessageSizes = false
          recordMessageTimes = false
          requestTimeout = -1
          uri = "http://77.93.202.150:8080/QuizDS/messagebroker/amf"
          url = "http://77.93.202.150:8080/QuizDS/messagebroker/amf"
          useSmallMessages = false
        channelId = (null)
        connected = false
        currentTarget = (mx.messaging.channels::AMFChannel)#4
        eventPhase = 2
        faultCode = "Channel.Connect.Failed"
        faultDetail = "NetConnection.Call.Failed: HTTP: Status 500: url: 'http://77.93.202.150:8080/QuizDS/messagebroker/amf'"
        faultString = "error"
        reconnecting = false
        rejected = false
        rootCause = (Object)#8
          code = "NetConnection.Call.Failed"
          description = "HTTP: Status 500"
          details = "http://77.93.202.150:8080/QuizDS/messagebroker/amf"
          level = "error"
        target = (mx.messaging.channels::AMFChannel)#4
        type = "channelFault"
      timestamp = 0
      timeToLive = 0

    halodev:
    I made a CF/Flex site based on the Flexstore sample app,
    using a database instead of XML as the data source; in case you
    want to see it:
    http://www.timos.com/dg/flex/DilemmaGames.html
    At first I had troubles similar to what you describe;
    initially, part of the problem was that my hosting company had not
    yet upgraded to CF 7.02. One other thing I had to correct: when you
    upload to your server, upload the entire ‘bin’ (or
    whatever your output folder is) minus the debug SWF.
    If it would help with other issues, contact me and I will be
    glad to make my project code available to you. Good luck.
    Carlos
    [email protected]

  • When launching a transaction, I am getting error that client XYZ has status

    I am in SAP APO , when I try to launch the transaction /SAPAPO/48000009
    SAP Menu -> SCM Basis -> Planning Service Manager -> Current Setting -> Define Planning Profile. I get a error saying Client XYZ has status 'not modifiable'.
    What setting could be missing?
    Please help with your inputs.
    Harsha Gatt

    You are on the wrong forum. This forum is about SAP Business One SDK.

  • InfoPackage error message "Subsequent update (requests) : Status unknown "

    After running an InfoPackage the status is set to green, but when you look at the Details tab you see an error message "Subsequent update (requests) : Status unknown "  and "With DTP in InfoProvider ZHRPYO00 : Further processed " under it. We did not used to get this error message and don't quite understand why are we getting it now. Could someone explain, please?
    Thanks!
    Luda

    Hi,
    Usually this error could be while loading the DSO or loading DSO first and then to other infoprovider.
    Error message tab at the monitor should give you clear error message where it went wrong. check this tab.
    some time while activating the data this may fail for the DSO object. or some time due to authorization problem to load the data automatically from the DSO to infocubes.
    If possible let me know what is error message.
    Regards,
    Vishwa.

  • Error in commitment update. Status is being set.

    HI Experts,
    I have this error during sales order creation
    "Error in commitment update. Status is being set. The order cannot be delivered/billed."
    The system here FMderive to get commitment item.
    Is there any missing FI in the SO?
    THanks.
    Regards,
    Clarice

    Check and maintain the following settings:
    All accounts the system finds in the SD sales order must be supplied with an existing commitment item.
    The funds center and the funds must either be entered in the account assignment panel of the SD sales order or they must be derived.
    For detail refer SAP Note 418471 - V1331 (Item & does not exist) / Funds Management.
    Thanks & Regards
    JP

  • OGG-00665  OCI Error executing single row select (status = 4060-ORA-04060:

    Unable to start Replica. Is it Oracle user permission issue ?
    ERROR OGG-00665 OCI Error executing single row select (status = 4060-ORA-04060: insufficient privileges to execute DBMS_STREAMS.SET_TAG
    ORA-06512: at "SYS.DBMS_STREAMS", line 16
    ORA-06512: at line 1), SQL<BEGIN dbms_streams.set_tag(:1); END;>.
    ERROR OGG-01668 PROCESS ABENDING.

    Operating System Version:
    Linux
    Version #1 SMP Sat Feb 25 16:26:29 EST 2012, Release 2.6.18-308.0.0.0.1.el5xen
    Node:
    Machine: x86_64
    soft limit hard limit
    Address Space Size : unlimited unlimited
    Heap Size : unlimited unlimited
    File Size : unlimited unlimited
    CPU Time : unlimited unlimited
    23,0-1 Top
    Process id: 7662
    Description:
    ** Running with the following parameters **
    2013-05-01 10:06:13 INFO OGG-03059 Operating system character set identified as UTF-8.
    2013-05-01 10:06:13 INFO OGG-02695 ANSI SQL parameter syntax is used for parameter parsing.
    replicat robey
    userid test12, password ********
    Source Context :
    SourceModule : [ggdb.ora.sess]
    SourceID : [*/aime1/adestore/views/aime1_*/oggcore/OpenSys/src/gglib/ggdbora/ocisess.c]
    SourceFunction : [oci_try]
    SourceLine : [790]
    ThreadBacktrace : [18] elements
    : [*/*/OGGCOREMAINBACKTEST/libgglog.so(CMessageContext::AddThreadContext()+0x26) [0x2af5c09b67f6]]
    : [*/*/OGGCOREMAINBACKTEST/libgglog.so(CMessageFactory::CreateMessage(CSourceContext*, unsigned int, ...)+0x28f) [0x2af5c09ae90f]]
    : [/*/*/OGGCOREMAINBACKTEST/libgglog.so(_MSG_ERR_ORACLE_OCI_ERROR_WITH_DESC_SQL(CSourceContext*, int, char const*, char const*, char const*,
    CMessageFactory::MessageDisposition)+0x64) [0x2af5c09787d4]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(OCISESS_context_def::oci_try(int, char const*, ...)+0x3ee) [0x788aae]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(query_handle::exec_stmt(bool, int)+0x19a) [0x79664a]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(OCISESS_context_def::setTag(ggs::gglib::ggunicode::UString const&, bool)+0x25a) [0x787d5a]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(OCISESS_context_def::init_context(int, int)+0x410) [0x78f230]]
    : [/*/*/OGGCOREMAINBACKTEST/replicat(DBOCI_init_connection_logon(ggs::gglib::ggapp::CLoginName const&, ggs::gglib::ggapp::CDBObjName<(DBObjType)12>
    const&, char const*, int, int, int, char*)+0x136) [0x76c566]]
    : [*/*/OGGCOREMAINBACKTEST/replicat [0x740479]]
    : [*/*/OGGCOREMAINBACKTEST/replicat [0x746f91]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(odbc_param(char*, char*)+0x364) [0x74a5f4]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(get_infile_params(time_elt_def*, time_elt_def*, char**)+0x959f) [0x57af1f]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(replicat_main(int, char**)+0x152) [0x5de8c2]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(ggs::gglib::MultiThreading::MainThread::ExecMain()+0x6f) [0x7249af]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(ggs::gglib::MultiThreading::MainThread::Run(int, char**)+0x127) [0x724d57]]
    : [*/*/OGGCOREMAINBACKTEST/replicat(main+0x4a) [0x5dafba]]
    : [lib64/libc.so.6(__libc_start_main+0xf4) [0x3f4da1d994]]
    : [*/*/OGGCOREMAINBACKTEST/replicat [0x4c70a9]]
    2013-05-01 10:06:13 ERROR OGG-00665 OCI Error executing single row select (status = 439-ORA-00439: feature not enabled: Streams Capture
    ORA-06512: at "SYS.DBMS_STREAMS", line 7
    ORA-06512: at line 1), SQL<BEGIN dbms_streams.set_tag(:1); END;>.
    2013-05-01 10:06:13 ERROR OGG-01668 PROCESS ABENDING.

  • Error executing RDS command. Status Code : 503 , Reason : Service Unavailable

    Hi,
    I am being trying to connect a Flex desktop application with a Java application running in Tomcat (6.0.29), and I get this error message when trying to use the Data wizard to connect with Blaze DS.
    I have read all the tutorials and everything looks good from the server side. This is what appears in the server log:
    2011-01-27 16:02:33,030 [ INFO] - RemotingDestinationExporter - Created remoting destination with id 'accounts'
    2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Remoting destination 'accounts' has been started started successfully.
    2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Created remoting destination with id 'customers'
    2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Remoting destination 'customers' has been started started successfully.
    2011-01-27 16:02:33,061 [ INFO] - FrameworkServlet - FrameworkServlet 'flex': initialization completed in 3887 ms
    2011-01-27 16:02:50,813 [ INFO] - MessageBrokerHandlerAdapter - Channel endpoint my-amf received request.
    2011-01-27 16:43:42,897 [ INFO] - MessageBrokerHandlerAdapter - Channel endpoint my-amf received request.
    (The last two lines appears when I put the AMF channel's URI in a browser).
    Below is what appears in the Event log from Eclipse.
    java.lang.RuntimeException: java.lang.RuntimeException: RDS server message:
    Error executing RDS command. Status Code : 503 , Reason : Service Unavailable
    at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.setVisible(J2EEServicePage.jav a:149)
    at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1171)
    at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149)
    at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1136)
    at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:830)
    at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizardDialog.nextPressed(ServiceWizardD ialog.java:93)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
    at org.eclipse.jface.window.Window.open(Window.java:801)
    at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizard.show(ServiceWizard.java:190)
    at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizard.createService(ServiceWizard.java :152)
    at com.adobe.flexbuilder.dcrad.views.ServiceExplorerView$1.handleEvent(ServiceExplorerView.j ava:528)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
    at org.eclipse.swt.widgets.Link.wmNotifyChild(Link.java:1004)
    at org.eclipse.swt.widgets.Control.wmNotify(Control.java:4877)
    at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1757)
    at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:4507)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4000)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
    at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2314)
    at org.eclipse.swt.widgets.Link.callWindowProc(Link.java:172)
    at org.eclipse.swt.widgets.Widget.wmLButtonUp(Widget.java:1917)
    at org.eclipse.swt.widgets.Control.WM_LBUTTONUP(Control.java:4301)
    at org.eclipse.swt.widgets.Link.WM_LBUTTONUP(Link.java:842)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:3982)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2411)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3501)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
    Caused by: java.lang.RuntimeException: RDS server message:
    Error executing RDS command. Status Code : 503 , Reason : Service Unavailable
    at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.initialize(J2EEServicePage.jav a:187)
    at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.setVisible(J2EEServicePage.jav a:136)
    ... 61 more
    Any help wolud be appreciated.
    Thanks

    Hi There,
    I am getting the same error. can anyone tell me what could be problem?

Maybe you are looking for