Erro - Verificação de Status do Serviço

Bom Dia a Todos,
Está ocorrendo o seguinte erro ao solicitar a verificação do status do serviço no ambiente de homologação da SEFAZ-MG:
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Unexpected Error java.lang.NoClassDefFoundError at br.inf.portalfiscal.nfe.controller.ValidaDadosStatusServico.validaDadosStatusServico(ValidaDadosStatusServico.java:19) at br.inf.portalfiscal.nfe.controller.ValidacaoXMLHelper.validaDadosStatusServico(ValidacaoXMLHelper.java:324) at br.inf.portalfiscal.nfe.controller.UtilSession.processaNfeStatusServico(UtilSession.java:1558) at sun.reflect.GeneratedMethodAccessor134.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.invocation.Invocation.performCall(Invocation.java:359) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648) at org.jboss.ejb.Container.invoke(Container.java:954) at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430) at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103) at $Proxy73.processaNfeStatusServico(Unknown Source) at br.inf.portalfiscal.nfe.wsdl.nfestatusservico.NfeStatusServicoImpl.nfeStatusServicoNF(NfeStatusServicoImpl.java:73) at sun.reflect.GeneratedMethodAccessor122.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.xfire.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:59) at org.codehaus.xfire.service.invoker.ObjectInvoker.invoke(ObjectInvoker.java:45) at org.codehaus.xfire.service.binding.ServiceInvocationHandler.sendMessage(ServiceInvocationHandler.java:320) at org.codehaus.xfire.service.binding.ServiceInvocationHandler$1.run(ServiceInvocationHandler.java:86) at org.codehaus.xfire.service.binding.ServiceInvocationHandler.execute(ServiceInvocationHandler.java:134) at org.codehaus.xfire.service.binding.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:109) at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) at org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64) at org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38) at org.codehaus.xfire.transport.http.XFireServletController.invoke(XFireServletController.java:304) at org.codehaus.xfire.transport.http.XFireServletController.doService(XFireServletController.java:129) at org.codehaus.xfire.transport.http.XFireServlet.doPost(XFireServlet.java:116) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at br.inf.portalfiscal.nfe.util.manipulaXml.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:106) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)</SAP:AdditionalText>
Alguém já passo por essa situação e pode por favor esclarecer qual o motivo deste erro?
Agradeço antecipadamente!

Bom dia Guilherme,
Este erro foi gerado pela Sefaz MG, repare que as classes não são do PI (jboss, apache, tomcat, catalina). Contacte a Sefaz para maiores detalhes, deve ser algum erro temporário.
De sua parte é importante você se certificar que estava funcionando.... e parou de funcionar, ou melhor, que você está fazendo o pedido corretamente. Veja no SXI_MONITOR sua mensagem saindo pra Sefaz se está tudo ok.
Atenciosamente,
Fernando Da Ró

Similar Messages

Erro NO_RECEIVER_CASE_BE cenário status serviço(ambiente funcionava no )

Pessoal,
Estou tendo o erro na verificação de status serviço desde a manhã de hoje, no qual está afetando os dois SEFAZ (SP e RS) em Produção que estão configurados no cliente que funcionavam há bastante tempo, na SXI_MONITOR aparece o erro NO_RECEIVER_CASE_BE na interface SRVSC_nfeStatusServicoNF_SYNC_OB para ambos os SEFAZ , ja tentei restart o PI, Full Cache refresh, CPa Cache, não há filas paradas e tbm já fiz o teste do certificado digital no Java. etc...
Poderiam me ajudar?
abs,
Daniel Feitoza

Olá Henrique,
Segue as conditions dos Receivers Determination:
RS = (/p1:nfeStatusServicoNF2/p1:cUF = 43 AND /p1:nfeStatusServicoNF2/p1:tpEmis u2260 3 AND /p1:nfeStatusServicoNF2/p1:tpAmb = 1)
SP = (/p1:nfeStatusServicoNF2/p1:cUF = 35 AND /p1:nfeStatusServicoNF2/p1:tpEmis u2260 3 AND /p1:nfeStatusServicoNF2/p1:tpAmb = 1)
e segue payload do XML:
do RS:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:nfeStatusServicoNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:P1P:/1SAI/TAS4DFEC4071863FF72A429:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
<n0:cUF>43</n0:cUF>
<n0:tpEmis>3</n0:tpEmis>
<n0:tpAmb>1</n0:tpAmb>
- <n0:nfeDadosMsg>
- <n1:consStatServ versao="2.00">
<n1:tpAmb>1</n1:tpAmb>
<n1:cUF>43</n1:cUF>
<n1:xServ>STATUS</n1:xServ>
</n1:consStatServ>
</n0:nfeDadosMsg>
</n0:nfeStatusServicoNF2>
de SP:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:nfeStatusServicoNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:P1P:/1SAI/TAS4DFEC4071863FF72A429:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
<n0:cUF>35</n0:cUF>
<n0:tpEmis>3</n0:tpEmis>
<n0:tpAmb>1</n0:tpAmb>
- <n0:nfeDadosMsg>
- <n1:consStatServ versao="2.00">
<n1:tpAmb>1</n1:tpAmb>
<n1:cUF>35</n1:cUF>
<n1:xServ>STATUS</n1:xServ>
</n1:consStatServ>
</n0:nfeDadosMsg>
</n0:nfeStatusServicoNF2>
Obrigado pela ajuda,
Daniel Feitoza

SCAN não retorna status do serviço

Bom dia,
Desde 14/08/2011 às 08:05:56 o nosso tipo de emissão SCAN não está retornando STATUS de ativo, e também não é realizada a consulta do status do mesmo.
Dei uma olhada no GRC/PI/Java/ECC... e aparentemente está tudo ok
Quando o SCAN parou pela primeira vez, deu o seguinte erro:
PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_MATCH_ELEMENT in /1SAI/TXS2731B33DE5F5A8813C20 Line 268 Elem.'nfeStatusServicoNFResponse2' esperado
Pesquisando sobre o erro, achamos 2 trheads:
http://forums.sdn.sap.com/click.jspa?searchID=73768752&messageID=10193658
http://forums.sdn.sap.com/click.jspa?searchID=73768752&messageID=10151927
Elas sugerem a aplicação das notas abaixo:
1501345 - Xi runtime: Manifest
1522630 - Xi runtime: Payload ignored due to parsing error
1162160 - CX_ST_MATCH_ELEMENT in XML Inbound processeing
Inclusive um dos usuários comenta que após aplicada a 1522630 o problema foi resolvido... (Mas não sei se isso irá funcionar)
Outro check que realizei foi do erro retornado no status do serviço do SCAN agora, e o GRC retorna o seguinte erro:
MAPPING.JCO_COMMUNICATION_FAILURE "COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection
Pesquisando sobre o erro, encontrei algumas sugestões:
1) Alguns sugerem a exclusão da conexão RFC AI_RUNTIME_JCOSERVER para TCP/IP (SM59) no GRC e criar novamente... mas não sei se isso iria funcionar...
2) Em outras pesquisas, alguns falam que a Conexão entre ABAP e JAVA foi quebrada... isso é a razão para o erro JCO_COMMUNICATION... e a sugestão é reiniciar o Java...
3) Em outra pesquisa: Quando há muitas mensagens a serem processadas simultaneamente. O número padrão de processos paralelos em VisualAdmin -> JCO Provider RFC -> AI_RUNTIME_) e ver se isso ajuda.
Obs.: À alguns dias, tivemos um problema que ocorreu com a SEFAZ-GO, a mesma colocou nossa faixa de IP's em uma Blacklist (ainda não sabemos porque) e daí ela nos retornava que estava "fora do ar". Será que poderia ser isso? Como posso checar isso?
O nosso S.P. é o:
SLL-NFE 100 0018 SAPK-10018INSLLNFE xNFE 1.0
Alguém poderia nos auxiliar? Pois isso não gera impacto em nossos processos desde que a SEFAZ (GO/PR/SP/MT) não fique inativa, pois caso isso ocorra o nosso processo de emissão de NF-e em SCAN não irá funcionar e a emissão de NF-e irá parar.
Qualquer dúvida estou à disposição.
Edited by: MATEUS PARREIRA GUIMARÃES on Sep 1, 2011 7:12 PM
Edited by: Fernando Ros on Sep 2, 2011 10:24 PM - trocado code por quote para melhor visualizaçã

Boa tarde a todos!
Pessoal incluindo mais informações as já enviadas pelo Mateus; quando fazemos um check pela SXI_monitor esta
retornando sempre o mesmo retorno:
Qualquer dica ou nota agradecemos,
Pamplona
CENTRAL
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>8AB8CC05-D44B-11E0-8D74-000000729692</SAP:MessageId>
<SAP:RefToMessageId>E0D44B74-1BE5-7BF1-975B-0024E8437829</SAP:RefToMessageId>
<SAP:TimeSent>2011-09-01T03:36:13Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">SEFAZ_2_SCAN</SAP:Party>
<SAP:Service>Producao</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNFSoapIn_SYNC_IB</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<SAP:Service>GRPCLNT200</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNF_SYNC_OB</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNFSoapIn_SYNC_IB</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemErrorAckRequested="true" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTPEXCEPTION - HTTP 403 Forbidden----

Mensagem de status do serviço - versão 2.0

No SAP PI, estamos enfrentando problemas com o mapeamento da mensagem que verifica o status do serviço.
No SP07
Quando a mensagem de transformação está completa, estamos obtendo uma mensagem em xml com nome da
operação. Então, no PI, a mensagem em xml vem "envelopada" em uma mensagem SOAP. Então, não há nenhum problema no sistema datapower que usamos para precessar o arquivo.
No SP15
Quando a mensage de transformação está completa, estamos obtendo uma mensagem SOAP em xml sem o nome da
operação. Então, no PI, a mensagem em xml ~é "envelopada" em outra mensagem SOAP. Este não é uma processo standard de mensages. Então, oo sistema datapower não consegue processar a mensage.
O que vocês acham?
Grata,
Fabiana

Bom dia Fabiana,
Não apenas novos campos no manual do contribuinte, mas também a forma do envelope e SOAP, parametros foram modificados no 2.0, isso mudou além do próprio layout, ou seja, no datapower será também necessário adaptar para que ele consiga receber do GRC corretamente e fazer a ponte para Sefaz e o retorno.
Atenciosamente, Fernando Da Ró

Error sending DAV request. HTTP code 500, status 'Internal Server Error'

Hi All,
I am getting the error On SCCM R2 Environment .. on the client machine we are getting the below issue and software center
is not showing any information..
While checking on the client's DatatransferService.log.. i am getting the below issues..
Successfully sent location services HTTP failure message.
Error sending DAV request. HTTP code 500, status 'Internal Server Error'
GetDirectoryList_HTTP('http://MachineName:80/SMS_DP_SMSPKG$/7ea0b105-5592-48cd-8b8e-81777537c34f') failed with code 0x87d0027e.
i realize it because of Isapi filter issues.. can any one guide me to resolve the issues..
KJSUBBU

Hi,
In addition, I recommend you check whether you have additional Authentication methods (like ASP.NET Impersonation) enabled.
Disable the authentication method and try again.
Also, please review the link below, here is a article about troubleshoot ISAPI filter issue.
Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.0 – Internal Server Error"
http://support.microsoft.com/kb/942031
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.

GRC NF-e 2.0 - Status de Serviço com Erro

Boa noite Srs,
Estamos recebendo um erro no cenário SRVSC_WebAS_Outbound_ServiceStatusCheck.
No NF-e Monitor o Status de Erro é 70 (Error from the authorities). Verifiquei a MONI e encontrei a seguinte mensagem:
/CPACache/refres...
CPA cache refresh (mode=full) successfully executed in 1607 milliseconds.*
Estamos no SLLNFE 16 do XI Content e SAP_APPL 604/07 do ERP; Nossa versão do PI é a 7.0.
Alguém teria alguma dica que pudesse nos ajudar a resolver este erro.
Grato,
Ricardo

Marlo, obrigado por sua resposta!
Refiz novamente todo o cenário de StatusServico, e todos os conditions estão perfeitamente setados, conforme exemplo de São Paulo abaixo:
Condition Homologation: (/p1:nfeStatusServicoNF2/p1:cUF = 35 AND /p1:nfeStatusServicoNF2/p1:tpAmb = 2)
Condition Production: (/p1:nfeStatusServicoNF2/p1:cUF = 35 AND /p1:nfeStatusServicoNF2/p1:tpAmb = 1)
Para todos os outros estados utilizei a mesma regra citada, com exceção ao cenário BATCH, que segui conforme o PDF da nota 1465726 que utiliza o tpEmis (diferente de 3).
Estou fazendo um refresh no sld e reiniciando o server para ver o que acontece...rs
Mais alguma outra dica?
Grato,
Ricardo

Erro no status de serviço NF-e 2.0

Olá pessoal,
Estamos com um erro de PI aqui no cliente, álguém consegue nos ajudar ?
Eles tem 3 ambientes de PI, DEV, QAS e PRD. todos no SPK 16 do GRC, a versão do PI é a 7.1.
o erro ocorre apenas no ambiente QAS e esta impactando diretamente nos testes.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">RESOURCE_NOT_FOUND</SAP:Code>
<SAP:P1>fc277224-4c15-11dc-8dc6-d7af0a115642</SAP:P1>
<SAP:P2>http://sap.com/xi/NFE/006</SAP:P2>
<SAP:P3>SRVSC_ServiceStatusCheckToSOAP12InConverter.xsl</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to find resource fc277224-4c15-11dc-8dc6-d7af0a115642 in the following software component versions: http://sap.com/xi/NFE/006SRVSC_ServiceStatusCheckToSOAP12InConverter.xsl-1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Alguém tem alguma idéia do que seja este erro ?
Desde ja, obrigado.
Julio.

Henrique,
Obrigado, limpar o cache resolveu meu problema.
mais uma vez, obrigado a todas as respostas.
Julio

Erro Retorno ERP Nota status 10

Bom dia Srs,
Estou com um problema para voltar o status de uma nota para o ERP, a nota tem status 10 erro de validação.
Já tentei algumas coisas:
Verifiquei os jobs esta rodando normalmente, smq2, e monitor enfim tudo em ordem.
Rodei o programa /XNFE/UPDATE_ERP_STATUS_DIAL sem sucesso, pois também não esta na tabela /xnfe/backstatus.
Alterei o status da nota na tabela /XNFE/NFeHist para 24, para rodar novamente na aba de erro de assinatura, mas mesmo assim sem sucesso o status não volta para o ERP, porem essa nota antes estava com status 25 erro de assinatura também.
Meu GRC esta no SP16 SP do PI 23 e SAP_BASIS 24, e vamos subir para o 17, mas creio que isso não vai resolver o problema.
Será que alguém tem mais alguma idéia?
Obrigado
Abs

Fernando, eu já tinha 3 notas neste situação nos testes, agora eu fiz uma simulação desse erro que esta ocorrendo, vou explicar o procedimento:
Eu alterei a senha do J2ee_admin no CC SIG_SOAP_RCV, enviamos uma nota essa nota vai dar erro assinatura , então a mesma fica parada no monitor do GRC com erro de assinatura status u201C25u201D, corrigi o problema da senha do j2ee_admin no CC, após isso reenvie a nota pela aba erro de assinatura , o que acontece a nota cai na mesma situação relatada aqui:
Monitor GRC status u201C10u201D
Monitor SAP ERP
Status da Açao: engrenagem
Log NF-e : Bandeira Vermelha ( com o mesmo log de erro do monitor do GRC)
Status Sist.msgs: status u201CAu201D
Seu tiver 1 mil notas que cair nessa situação de dar erro na assinatura e fazer o reenvio, todas elas vão ficar com esse status nos monitores.
Alguma coisa não esta funcionando como deveria não?
GRC SP17
Será que esta faltando aplicar alguma nota no ECC, acho que não, mas se vê tiver alguma idéia.
Agradeço
Abs

"unable to get printer status" and "server-error-not-accepting-jobs"

I've got an Intel Mac Pro with Tiger. When I accepted the latest update from Apple, I lost all my defined printers! I've re-added a local USB printer and a networked Laserjet - fine. But I also added a Phaser 850 color printer (networked) which used to work fine. It connects ok, and opens the printer queue window, but when it tries to print, it says "Unable to get printer status (server-error-not-accepting-jobs". The queue stays active (not stopped) but the jobs don't move. I've tried deleting the printer and re-making it - same deal. What's going on?
Mike

Hi Mike,
One think I really dislike about OSX is the Rocket Science needed to just Print!
Might try these two...
Mac OS X: About the Reset Printing System feature ...
http://support.apple.com/kb/HT1341?viewlocale=en_US
Might try Printer Setup Repair 5.1...
http://www.fixamac.net/software/index.html

BO4, CMC: status of server, yellow icon

Hi,
on a fresh installed BO4 server (Windows) all servers are up and running but I see a yellow "Server status" icon in the CMC at the InputFileRepository and OutputFileRepository server. All other server have a green status.
I didn't find further information regarding this in the admin guide. What does that status exactly mean, how can I find the reason for this issue?
Thanks!

Hi Steve,
yellow status means...either its in STARTING or STOPPING as you can see in the Server Node. Stop the Input and Ouput FRS and start again.
Regards,
Arjun

Showing status of server

Hi,
I have an application developed using form.
I have a web site that users can click and the form will be opened.
But I would like to display a small status in my website to show whether the form is available for use or not.
any suggestions?
Thanks

I assume the admin interface is running on the same machine as the server instance.
By default the Web Server instances use a directory in /tmp as a scratch/temp dir (something like /tmp/instance_name.hash/, e.g. /tmp/www.qweqwe.com-7f54fa82). One of the files stored there is the pid file. The pid file contains the pid of the running instance and is used by the admin interface (and the stop script, and the Admin agent I think) to keep track of which webservd "owns" which instance, etc. Unfortunately the /tmp directory is kept clean by the OS, and sometimes the OS daemon will remove the Web Server's directory and its associated files. When this happens the Web Server will (usually) continue working as though nothing were wrong, but the admin interface (and stop script, etc) will show that the instances are "Not Running."
For this reason one of the first things I do with a new Web Server instance is move its directory into the Web Server install location (something like /export/WS7/instance_name.hash/) and update the server.xml temp-path element to reflect the new location. Note that Web Server is very specific about how it wants the permissions set on this directory. It will report in its errors log if you get the permissions wrong.

Direct Access: DNS error on Operations Status (DNS server not responding)

Hi!
I am testing Direct Access on Windows 2012 R2 Standard. So far I have deployed the Remote Access role to our server "ABC-DA1". I have completed the configuration wizard for a Single NIC deployment and defined a FQDN as the "public name"
(da.domain.com).
After completing the wizard I go to the the Operations Status page and find the an error telling me one of the DNS servers is unavailable. The mentioned server is no longer operational as it was running on an old Win2k8R2 DC server that was demoted.
Is there a way to remove the reference to the old server? I have 3 new DNS servers running on the new Domain Controllers but it seems like the old DC did not completely remove itself.
Below is a screenshot of the operations status.
Thank you for your help :)

Hi,
Please go to the Name Resolution Policy and check if you can change the DNS server there.
Computer Configuration -> Policies -> Windows Settings -> Name Resolution Policy
Hope this helps.
Jeremy Wu
TechNet Community Support

How to get status of server side

Dear All,
I have developed the client program for communicating with server (Which can be developed again java or any language and on running on any platform ). So now I can connect with server and continue the communication but suppose if server down or unplugging the network wire, then how I know of that in client side programming. I try to some way but it does not work correctly.
private void monitor() throws Exception{
              isConnected = s.isConnected() &&
                           !s.isClosed() &&
                            InetAddress.getByName("192.168.1.115").isReachable(1000);
     public void run() {
          while (true){
               try {
                    Thread.sleep(2000);
                    monitor();
                    if(s !=null)
                         System.out.println(isConnected);
               } catch (Exception e) {
                    e.printStackTrace();
     } "s" is the created socket which bound at a one time to continue communication
InetAddress addr = InetAddress.getByName("192.168.1.115");
          SocketAddress sockaddr = new InetSocketAddress(addr,
                    8670);
          Socket s = new Socket();
          s.connect(sockaddr, 5000); Thing is it always print "true " even if the server is down
Can you tell me what is the way to check this ?
Regards
-Kapila

     isConnected = s.isConnected() &&Tells you whether you have called connect(), implicitly or explicitly, or got the socket from an accept().
     !s.isClosed() && Tells you whether you have closed the socket.
Neither of these tells you anything about the state of the connection.
     InetAddress.getByName("192.168.1.115").isReachable(1000);Meaningless.
The only way to tell whether a server can be connected to is to try to connect to it.
The only way to tell whether a server can be written to is to try to write to it, taking network buffering into account.
The only way to tell whether a server can be read from is to set an appropriate read timeout and try to read from it.
TCP doesn't maintain any other information about the state of a connection.

HTTP Status 500 --- server encountered an internal error

dear all,
i'm using tomcat and mysql for my system. but i'm encountered Internal Server Error. it quite strange that my other servlets running successfully, just this servlet.
*Servlet code
static final String dbURL = "jdbc:mysql://localhost/projectdb?" + "user=wongyuenmei&password=wongyuenmei";
public void doPost(HttpServletRequest request,HttpServletResponse response) throws IOException, ServletException
Connection conn = null;
String nextJSP = null;
try
Class.forName("org.gjt.mm.mysql.Driver");
catch (ClassNotFoundException e)
throw new ServletException("Unable to load JDBC driver");
try
String userid = (String)request.getParameter("userid");
String tempid=userid;
conn = DriverManager.getConnection(dbURL);
Statement stmt = conn.createStatement();
String query = "SELECT rsubcode, grade" + "FROM result" + "WHERE ridno = '" + userid + "'";
ResultSet rs = stmt.executeQuery(query);
if (rs.next())
StringBuffer stuResult = new StringBuffer ();
stuResult.append(rs.getString(3));
stuResult.append(" ");
stuResult.append(rs.getString(4));
request.setAttribute ("stuResult", stuResult.toString());
nextJSP = "/studentResult.jsp";
else
     StringBuffer temptest = new StringBuffer();
     temptest.append(userid);
     request.setAttribute("temptest", temptest.toString());
nextJSP = "/checkFailed.jsp";
conn.close();
ServletConfig config = getServletConfig();
ServletContext context = config.getServletContext();
RequestDispatcher rd = context.getRequestDispatcher(nextJSP);
rd.forward(request, response);
catch (SQLException e)
throw new ServletException("SQL call failed");
catch (Exception e)
throw new ServletException(e.getMessage());
finally
if (conn != null)
try
conn.close();
catch (SQLException e)
throw new ServletException("connection close failed");
}               //close doPost
public void doGet(HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException
doPost(request, response);
*Error
javax.servlet.ServletException: SQL call failed
     at ResultServlet.doPost(ResultServlet.java:62)
     at ResultServlet.doGet(ResultServlet.java:87)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:536)
thanx!
frm alice

sorry for the previous exception.
the actual exception:
javax.servlet.ServletException: Syntax error or access violation: You have an error in your SQL syntax near 'ridno = 'null'' at line 1
     at ResultServlet.doPost(ResultServlet.java:63)
     at ResultServlet.doGet(ResultServlet.java:88)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:536)
thanx for help!!
alice

Clients appear as offline, no status update, Server is online

Hi,
Windows Server 2012 Essentials was working for years but now I have an issue... All clients appear as offline, in the dashboard I don't see any alerts (in the top right I just see a black cross), however the clients are online, can see their alerts, backup
is working fine.
Any idea how to fix that?
Thanks,
Thomas Pagel

Hi Thomas,
Did you installed any update for Windows Server 2012 Essentials?
Based on my research, it seems that after you install Update Rollup for Windows Server 2012 Essentials, the clients have still the old Connector version running, then the client computers may appear to be offline in the dashboard until the client
side package is installed and should be rebooted after the update is applied.
I recommend you to reboot the clients to see if the issue persists.
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Erro - Verificação de Status do Serviço

Similar Messages

Maybe you are looking for