Unable to connect to remote JMS service

Hi I am running J2EE server on a remote machine and trying to access it from a client. But I am getting this exception. Can anybody help me in fixing this problem.
Aug 10, 2003 5:45:45 PM com.sun.jms.ConnectionFactoryImpl establishRemoteReferences
SEVERE: ConnectionFactoryImpl: Failed to lookup or connect to JMS service because: javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
Aug 10, 2003 5:45:45 PM com.sun.jms.ConnectionFactoryImpl establishRemoteReferences
SEVERE: ConnectionFactoryImpl: Failed to lookup or connect to JMS service because: javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
Exception in thread "main" java.lang.NullPointerException
at com.sun.jms.client.ConnectionImpl.invokeRemoteCreateConnection(ConnectionImpl.java:161)
at com.sun.jms.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:314)
at com.sun.jms.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:74)
at com.sun.jms.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:52)
at com.sun.jms.connector.ra.JMSConnectionFactoryAdapter.createQueueConnection(JMSConnectionFactoryAdapter.java:97)
at EventSender.initProcess(EventSender.java:189)
at EventSender.start(EventSender.java:77)
at EventSender.main(EventSender.java:21)
The command I used is "java -Dorg.omg.CORBA.ORBInitialHost=www.salvias.net EventSender 0 2 q1 q2 q3". I am running server on salvias.net.
tia,
Srinivas

I forgot to mention that lookuos are succeeding. When I print the results of lookup operation, null is not getting printed. The application is failing at this statment
conn = qcFactory.createQueueConnection();
I am using J2EE server provided by SUN. And also where can I find the source code of J2EE.
tia
Srinivas

Similar Messages

SSRS 2008 - Unable to connect to remote server

Win2k3 R2 SP2/SQL Server 2008 instance with SSRS/Visual Studio 2008
I installed SQL 2008 and SSRS with native mode default configuration.
All SQL 2008 services are running under "NT Authority\Network Service" account.
When i try to deploy a new report, I get the "Unable to connect to remote server" error.
The deploy operation creates empty folders on the web server (hosted by the SQL Server 2008 service)
for e.g.
my instance name is <machinename>$sql2008. i configured the WebService URL and the Reports Manager URL to port 85
the deploy from VS creates ssrs2008Test folder and a Shared Data Sources folder in the following virtual directory
- Report Manager URL: http://<machinename>:85/Reports_SQL2008/
- Web Service URL: http://<machinename>:85/ReportServer_SQL2008
however these folders are empty w/ no .rdl or .rds file. and i get the "Unable to connect to remote server" error in Visual Studio 2008 when i deploy it.
is there something else i have to tweak in either the SQL Server/SSRS Configuration Manager or the Windows Server Settings(like port settings or group policy) to get the reports to work?
thanks
-vt

SecureConnectionLevel = 2
From logFile:
appdomainmanager!DefaultDomain!740!08/29/2008-08:00:30:: i INFO: Appdomain:6 ReportServer_SQL2008_0-3-128644956308203194 started.
appdomainmanager!ReportServer_0-3!740!08/29/2008-08:00:31:: i INFO: RS authentication mode is 5; effective ASP.NET authentication mode is Windows. vdir=/ReportServer_SQL2008.
httpruntime!ReportServer_0-3!740!08/29/2008-08:00:31:: i INFO: Report Builder manifest file C:\Program Files\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\ReportServer\ReportBuilder\ReportBuilder_2_0_0_0\MSReportBuilder.exe.manifest not found.
appdomainmanager!DefaultDomain!740!08/29/2008-08:00:31:: i INFO: Appdomain:6 ReportServer_SQL2008_0-3-128644956308203194 initialized (#2).
webserver!ReportServer_0-3!740!08/29/2008-08:00:37:: i INFO: Reporting Web Server started
resourceutilities!ReportServer_0-3!740!08/29/2008-08:00:37:: i INFO: Reporting Services starting SKU: Developer
resourceutilities!ReportServer_0-3!740!08/29/2008-08:00:37:: i INFO: Evaluation copy: 0 days left
resourceutilities!ReportServer_0-3!740!08/29/2008-08:00:37:: i INFO: Running on 1 physical processors, 4 logical processors
runningjobs!ReportServer_0-3!740!08/29/2008-08:00:37:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
runningjobs!ReportServer_0-3!740!08/29/2008-08:00:37:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
runningjobs!ReportServer_0-3!740!08/29/2008-08:00:37:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
library!ReportServer_0-3!1588!08/29/2008-08:00:38:: Call to GetItemTypeAction(/ssrs2008Test).
library!ReportServer_0-3!1588!08/29/2008-08:00:39:: i INFO: Catalog SQL Server Edition = Developer
crypto!ReportServer_0-3!1588!08/29/2008-08:00:39:: i INFO: Initializing crypto as user: NT AUTHORITY\NETWORK SERVICE
crypto!ReportServer_0-3!1588!08/29/2008-08:00:39:: i INFO: Exporting public key
crypto!ReportServer_0-3!1588!08/29/2008-08:00:39:: i INFO: Performing sku validation
crypto!ReportServer_0-3!1588!08/29/2008-08:00:39:: i INFO: Importing existing encryption key
library!ReportServer_0-3!740!08/29/2008-08:00:39:: Call to GetItemTypeAction(/Data Sources).
library!ReportServer_0-3!1588!08/29/2008-08:00:39:: Call to GetItemTypeAction(/Data Sources/masterDB).
library!ReportServer_0-3!740!08/29/2008-08:00:40:: Call to GetItemTypeAction(/ssrs2008Test/sp_who2).

HTTP Response :500 unable to connect to remote system.

Hi,
I am doing proxy-xi-file scenario, where i am getting this error in sxmb_moni in R/3.
The error reads with red flag:
HTTP Response :500 unable to connect to remote system.
Please tell me what can be the reason.

Snehal,
Error: The error message 503 Service unavailable Application stopped! is displayed.
Description: The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
Refer SAP Note 803145,807000,791655
You can have a look on this blog for the same.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Sarvesh

JMS Exception - unable to connect to the JMS destination

Hi,
I've configured WebLogic10R3 Cluster with one Admin Server and 2 Managed Servers.
I deployed the application to the Cluster. (Ie. both Managed 1 and Managed Server 2.)
I am geeting the following JMS destination not found exception while starting the Second Managed Server.
There are no errors occurred in the First Managed Server.
{color:#ff0000}<Warning> <EJB> <BEA-010061>
<The Message-Driven EJB: SysAuditLogger is unable to connect to the JMS destination: topic/efpAuditTopic.
The Error was: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server efpserver_man2
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:efpserver_man2.
Resolved 'weblogic .messaging.dispatcher'; remaining name 'S:efpserver_man2>{color}
Configuration Details:
##config.xml:
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/wls [http://www.bea.com/ns/weblogic/90/security/wls.xsd] [http://www.bea.com/ns/weblogic/920/domain] [http://www.bea.com/ns/weblogic/920/domain.xsd] [http://www.bea.com/ns/weblogic/90/security/xacml] [http://www.bea.com/ns/weblogic/90/security/xacml.xsd] [http://www.bea.com/ns/weblogic/90/security] [http://www.bea.com/ns/weblogic/90/security.xsd]">
<name>efpdomain</name>
<domain-version>10.3.0.0</domain-version>
<security-configuration>
<name>efpdomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{3DES}hcdd+yZGXk5DHgRKqCM7E86l4+VxPcZ9Ut7rB6WaXqMyvbtDjDUKNCKbMQdCN/BEYCv5E0N4Hms9kntfqhaduDO1WGMtbmJL</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{3DES}Q2xO0EiChbay/HkRiorTjg==</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address>192.168.12.240</listen-address>
</server>
<server>
<name>efpserver_man1</name>
<listen-port>8011</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>efpserver_man2</name>
<listen-port>8012</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<cluster>
<name>efpcluster</name>
<cluster-address>192.168.12.240:8011,192.168.12.240:8012</cluster-address>
<multicast-address>239.192.0.0</multicast-address>
</cluster>
<embedded-ldap>
<name>efpdomain</name>
<credential-encrypted>{3DES}q/XQGirHcAcgi4iwPiXIkRHP8xte4xVBgJwjM+qMwbk=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.0.0</configuration-version>
<app-deployment>
<name>efp</name>
<target>efpcluster</target>
<module-type>ear</module-type>
<source-path>applications\efp.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<xml-registry>
<name>XMLEFP</name>
<document-builder-factory>weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl</document-builder-factory>
<sax-parser-factory>weblogic.apache.xerces.jaxp.SAXParserFactoryImpl</sax-parser-factory>
<transformer-factory>weblogic.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
</xml-registry>
<jms-server>
<name>eFpJMSServer</name>
<target>efpserver_man1 (migratable)</target>
<persistent-store>eFpJMSJDBCStore</persistent-store>
</jms-server>
<jms-server>
<name>eFpJMSServer2</name>
<target>efpserver_man2 (migratable)</target>
<persistent-store>eFpJMSJDBCStore2</persistent-store>
</jms-server>
<migratable-target>
<name>efpserver_man1 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<migratable-target>
<name>efpserver_man2 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<jdbc-store>
<name>eFpJMSJDBCStore</name>
<prefix-name>WLJMS_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man1 (migratable)</target>
</jdbc-store>
<jdbc-store>
<name>eFpJMSJDBCStore2</name>
<prefix-name>WLJMS2_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man2 (migratable)</target>
</jdbc-store>
<jms-system-resource>
<name>eFPJMS</name>
<target>efpcluster</target>
<sub-deployment>
<name>eFPServer</name>
<target>eFpJMSServer</target>
</sub-deployment>
<sub-deployment>
<name>eFPServer2</name>
<target>eFpJMSServer2</target>
</sub-deployment>
<descriptor-file-name>jms/efpjms-jms.xml\JMS Description-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>eFpDataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpDataSource-2004-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>eFpNonXADataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpNonXADataSource-6172-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
##JMS Description-jms.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms [http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd]">
<connection-factory name="ConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/ConnectionFactory</jndi-name>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<connection-factory name="XAConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/XAConnectionFactory</jndi-name>
<transaction-params>
<transaction-timeout>3600</transaction-timeout>
<xa-connection-factory-enabled>true</xa-connection-factory-enabled>
</transaction-params>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<uniform-distributed-queue name="ActiveActivityQueue">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>queue/efpActiveActivityQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
<uniform-distributed-topic name="AdminTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAdminTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="AuditTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAuditTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ErrorTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpErrorTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="FreeTextTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpFreeTextTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ReportingTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpReportingTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
</weblogic-jms>
-----

Getting the following exception while trying to connect the JMS destination I am using weblogic 10.3.3 connecting to oracle AQ. The config has been done as per the 'Interoperating with Oracle AQ JMS' document from oracle. I could see that while deploying the application the number of connections in the database increasing to 15 and getting the following error message.
<Jun 15, 2011 4:14:29 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: SampleEJBBean is unable to connect to the JMS destination: jms/propQueue. Th
e Error was:
oracle.jms.AQjmsException: Internal error: Cannot obtain XAConnection weblogic.c
ommon.resourcepool.ResourceLimitException: No resources currently available in p
ool TestDataSource to allocate to applications, please increase the size of the
pool and retry..
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal
(ResourcePoolImpl.java:555)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:322)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:438)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:317)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:93)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:
1670)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
468)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:355)
at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
at oracle.jms.AQjmsXAConnection.createXAQueueSession(AQjmsXAConnection.j
ava:214)
at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSession
s(JMSConnectionPoller.java:1545)
at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnecti
on(JMSConnectionPoller.java:2047)
at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnec
tionPoller.java:787)
at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPo
lling(MDConnectionManager.java:244)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDriv
enManager.java:584)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerSt
art(MessageDrivenBeanInfoImpl.java:1334)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessa
geDrivenBeans(MessageDrivenBeanInfoImpl.java:1314)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(
EJBDeployer.java:1669)
at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:14
93)
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:614)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
ListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
ulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
va:1269)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleM
oduleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
entStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
pContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.ac
tivate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.ac
tivateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Commit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.co
mmit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeplo
ymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.com
mit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Xcode - Unable to Connect to Remote Repository

I have a mac mini running OS X Server 4 on Yosemite 10.10.1 and I am trying to set up the Xcode server to host my repositories.
On my development machine, when I try to create a project on the remote server, or when I try to push to the server I get the error..
"Unable to Connect to Remote Repository
Could not connect to the remote repository because the server was unreachable. Verify the server is running and try again."
My machine knows that the remote server is there and alive. I am able to add the server in Xcode preferences without any problem.
I can even pull projects that were already on the server. But anything new I cannot push or create.
All the other services I use on the server are working. Hosting a website, Screen sharing and I can SSH into it without any problem.
The strangest part is that when I get the error about being unable to connect, the project I am trying to push actually does show up on the server.
The project shows up on the server in the Repositories. Just my development machine doesn't know it.
Its driving me nuts, can anyone offer any ideas?

     You said you had SSH access working so this may be a different issue. I was able to ssh into my server only with my admin account which made me think that ssh was working, but it turns out it wasn't for all user accounts.   I had the same error message and it turned out I could not ssh into the server with my developer accounts. If I tried to clone a local repository to the server I got the same error, however the repository was actually create, but it was empty.   For reasons that don't matter to this discussion I originally setup all my users as "local network users" with no "Home Folder". And that was the problem. Basically ssh won't allow you to login without a home directory.
     I had to go back and add a "Home Folder" of "Local Only" for those users who were going to have xCode access. Once the "home" directory was created I could login via ssh on those accounts AND creating and cloning repositories through xCode worked fine. The admin account that I was able to login with already had a home directory and wasn't a network user.
Your issue slightly different even though I got the same error message, so not sure if this will solve your issue or not. But on the off chance that it is the same issue,   I figured I would post my solution to my problem. ymmv
P.S. I did turn off websites on my server and haven't turned it back on yet, so not sure if that will be a problem if I turn it back on.

AQJMSMDBEJB is unable to connect to the JMS destination

I am trying to integrate WebLogic 8.1 MDB and Oracle 9i AQ using a start-up class that creates XAConnection and Queue. However, I'm currently getting this error and I'm not sure what I need to do.
<The Message-Driven EJB: AQJMSMDBEJB is unable to connect to
the JMS destination: AQJMSQueue. The Error was:
oracle.jms.AQjmsException: JMS-137: Payload factory must be specified for destinations with ADT payloads
oracle.jms.AQjmsException: JMS-137: Payload factory must be specified for destinations with ADT payloads
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:266)
at oracle.jms.AQjmsConsumer.<init>(AQjmsConsumer.java:326)
at oracle.jms.AQjmsConsumer.<init>(AQjmsConsumer.java:196)
at oracle.jms.AQjmsSession.createReceiver(AQjmsSession.java:1415)
at oracle.jms.AQjmsSession.createReceiver(AQjmsSession.java:1386)
at weblogic.deployment.jms.WrappedTransactionalSession_oracle_jms_AQjmsXAQueueSession.createReceiver(Unknown Sou
rce)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1609)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1844)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

1. Security:
Perhaps you need to check the security configuration for the queue (Q) to ensure it matches the MDB (M) security parameters.
Q:
Weblogic Security Realms: User/Group
JMSModule Security: Role/Group , Policy: Role
M:
MDB: MDBRole/Principal (User) in weblogic-ejb-jar.xml
2. Double check that the queue created in weblogic
3. Test your queue (manually create a new message using weblogic console) or observe unconsumed messages (if producer has run and placed messages)
Carlos

The search request was unable to connect to the Search Service

I have upgraded from WSS 3.0 to SharePoint Foundation 2010. So far everything appears to be OK apart from my search.
When I attempt a search I get the following:
The search request was unable to connect to the Search Service.
I checked the Manage Database Update Status in Central Admin and noticed the following(an upgrade is required):
Also, I checked Manage Services on Server and noticed that the only search related service is 'SharePoint Foundation Help Search'.
If I go into Manage Service Applications and click new there is no option to add a search service.
Finally I tried PSConfig:
PS C:\Users\administrator.ACHESON> PSConfig.exe -cmd upgrade -inplace b2b -force
-cmd applicationcontent -install -cmd installfeatures
SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) M
icrosoft Corporation 2010. All rights reserved.
Performing configuration task 1 of 6
Initializing SharePoint Products upgrade...
Waiting to get a lock to upgrade the farm.
Successfully initialized SharePoint Products upgrade.
Performing configuration task 2 of 6
Initiating the upgrade sequence...
Successfully initiated the upgrade sequence.
Performing configuration task 3 of 6
Registering SharePoint features...
Feature installation has determined that there are no new features that require
installation.
Successfully registered SharePoint features.
Performing configuration task 4 of 6
Installing the application content files...
Installing the SharePoint Central Administration Web Application content files..
Installing the SharePoint Web Application content files...
Successfully installed the application content files.
Performing configuration task 5 of 6
Upgrading SharePoint Products...
10.00%Failed to upgrade SharePoint Products.
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
urationTaskException was thrown. Additional exception information: The upgrade
command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products.
Total number of configuration settings run: 5
Total number of successful configuration settings: 4
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed. Configuration must be performed be
fore you use SharePoint Products. For further details, see the diagnostic log l
ocated at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\1
4\LOGS\PSCDiagnostics_10_9_2013_12_47_54_528_1859316720.log and the application
event log.
This is the warnings and errors that the log contained:
10/09/2013 12:48:16 10 WRN Found registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS\ComponentsToRegister, but the SubKeyCount is zero
10/09/2013 12:48:24 10 WRN Failed to add the service connection point for this farm
10/09/2013 12:48:24 10 WRN Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=acheson-glover,DC=com doesn't exist in the directory.
at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
10/09/2013 12:48:40 10 ERR The exclusive inplace upgrader timer job failed.
10/09/2013 12:48:40 10 ERR Task upgrade has failed with a PostSetupConfigurationTaskException An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: The upgrade command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products.
10/09/2013 12:48:40 10 ERR An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: The upgrade command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
10/09/2013 12:48:40 10 ERR Task upgrade has failed
10/09/2013 12:48:40 1 ERR Task upgrade SharePoint Products failed, so stopping execution of the engine
10/09/2013 12:48:40 1 ERR Failed to upgrade SharePoint Products.
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: The upgrade command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
10/09/2013 12:48:41 1 ERR One or more configuration tasks has failed or some tasks were not run
10/09/2013 12:48:41 1 ERR One or more configuration tasks has failed to execute
10/09/2013 12:48:41 1 ERR Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\PSCDiagnostics_10_9_2013_12_47_54_528_1859316720.log, fix the problem, and run this configuration wizard again.
10/09/2013 12:48:41 1 ERR Post setup configuration was not run successfully when using the command line task driver module
How do I resolve this?
Cheers
Paul

Hi,
SharePoint Foundation the search service should be installed by default. It's not the same as with 2010 Standard or Enterprise where you can create a "Service Application" for it.
Follow this article to configure SharePoint Foundation Search:
http://plexhosted.blogspot.com/2011/11/how-to-configure-sharepoint-foundation.html
Meanwhile, here is a thread which discusses the similar question:
Configuration of SharePoint Foundation 2010 Search
http://social.technet.microsoft.com/Forums/sharepoint/en-US/af57728f-ae20-477b-8c67-2b594a1a72de/configuration-of-sharepoint-foundation-2010-search?forum=sharepointadminprevious
Thanks.
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.

SharePoint Online - "Unable to connect to remote server"

Hi,
I have a Provider Hosted App which gets the data from a different site collection. Now, when i try to connect to a different site collection, the TokenHelper
class gives me an error - "Unable to connect to remote server".
The error is thrown in the below line:
acsMetadata = webClient.DownloadData(acsMetadataEndpointUrlWithRealm);
The above error is not thrown always. It throws occasionally. I am not getting the reason for this. Could anybody explain what is the problem, please?

Hi,
According to your description, my understanding is that the error "Unable to connect to remote server" occurs in the WebClient.DownloadData Function.
As this error throws occasionally, it should be related to the network issue, for a better troubleshooting, I suggest you can check the detailed error message using Fiddler.
Fiddler
Thanks
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Debugger unable to connect to remote process

Hi There,
I am running Jdev on pc and OAS 10g on an unix environment. I followed the step in the doc to set up the remote debugging. However, when I start the remote debugger from jdev, i got the following error message.
Debugger attempting to connect to remote process at ax-portal-www6.dev.ipass.com 4000..
Debugger unable to connect to remote process.
Your help wuld be greatly appreciated.

A couple things to try:
1) Verify your jdk version and build bug 4411232
2) Increase your Debugger preferences Connection retries to double the default (especially if multiple apps running, low memory or a slow machine)
Without more specifics on versions, type of debugging or details not much more I can suggest.

ORA-29701: unable to connect to Cluster Synchronization Service

Hi, I'm working on an Oracle 11.2 EE on a RedHat 5.4.
I installed the Grid Infrastructure to work with ASM.
While starting ASM instance I got this error:
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
I tried to start the resource wiht:
$ crsctl start resource -all
CRS-4639: Could not contact Oracle High Availability Services
CRS-4000: Command Start failed, or completed with errors.
Then i tried this:
$ crsctl start has
CRS-4124: Oracle High Availability Services startup failed.
CRS-4000: Command Start failed, or completed with errors.
Do you have any suggestion on how start the CSS?
Thanks in advance.
Samuel

Hi,
it was just a metter of the run level.
As soon as I set it to 5 everything started to work.
Samuel

IP address changed and unable to connect to the java services?

Hi Guys,
we had installed PI 7.1 and everything is working perfectly fine. we have moved the system to the data center from our network. The server has been assigned a new IP address. All instances (ABAP+JAVA) have come up and i was able to login the ABAP stack.
But when i try to open http://hostname:50000/dir is not working and when i check in SMICM trace i am getting the error as conect to host:50000 failed check the host configuration .
I have also mapped the IP address to the host name in the host file but it did not help.
any help would be appreciated
Thanks,
Srini
Edited by: srinivas kapu on Dec 5, 2008 5:34 PM

Hi Bhargav,
Thanks for the quick reply. I am unable to connect to any java services like IR, ID, NWA etc with neither IP or FQDN. We did not had any issues previously with the FQDN and only change is now the IP address is changed.
Thanks,
Srini

Unable to start connection on remote JMS server

          HI
          I have a setup in which I try to connect to a remote JMS Server (running on a
          remote WLS 8.1 SP1). It is able to get the named QueueConnectionFactory, fails
          to start the connection. The stack trace is
          weblogic.jms.common.JMSException: Connection not found
               at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
               at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:596)
               at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
               at weblogic.jms.client.JMSConnection.start(JMSConnection.java:567)
               at uk.co.concise.payments.event.EventProcessorServiceAsynchBD.(EventProcessorServiceAsynchBD.java:82)
               at uk.co.concise.payments.state.ejb.ObjectStateServiceXDBean.ejbCreate(ObjectStateServiceXDBean.java:213)
               at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_Impl.ejbCreate(ObjectStateService_1th3um_Impl.java:135)
               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:324)
               at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:172)
               at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:110)
               at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:140)
               at weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:229)
               at weblogic.ejb20.internal.StatelessEJBLocalObject.preInvoke(StatelessEJBLocalObject.java:54)
               at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_ELOImpl.createAndGetStateForObject(ObjectStateService_1th3um_ELOImpl.java:273)
               at uk.co.concise.payments.state.ObjectStateServiceBD.createAndGetStateForObject(ObjectStateServiceBD.java:123)
               at uk.co.concise.payments.submission.ejb.SubmissionServiceXDBean.createSubmission(SubmissionServiceXDBean.java:92)
               at uk.co.concise.payments.submission.ejb.SubmissionService_o0dxp8_ELOImpl.createSubmission(SubmissionService_o0dxp8_ELOImpl.java:162)
               at uk.co.concise.payments.submission.SubmissionServiceBD.createSubmission(SubmissionServiceBD.java:42)
               at uk.co.concise.payments.submission.webapp.SubmitPaymentFileAction.execute(SubmitPaymentFileAction.java:216)
               at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:446)
               at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
               at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
               at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
               at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at uk.co.concise.payments.logon.filter.LogonFilter.doFilter(LogonFilter.java:38)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Any ideas on what could be wrong
          thanks
          jaz


          Thanks Tom
          It fixed the problem.
          Jaz
          Tom Barnes <[email protected]> wrote:
          >Hi,
          >
          >I think "Connection not found" may be a symptom of a name
          >conflict. Make sure:
          > All JMS servers are named differently
          > All WL servers are named differently
          > All JMS stores are named differently
          >All three above are needed for various reasons, although I think
          >it is only first that fixes your particular problem.
          >
          >A google search of this newsgroup would likely have yielded this
          >same answer.
          >
          >Tom
          >
          >jasmeet wrote:
          >
          >> HI
          >>
          >> I have a setup in which I try to connect to a remote JMS Server (running
          >on a
          >> remote WLS 8.1 SP1). It is able to get the named QueueConnectionFactory,
          >fails
          >> to start the connection. The stack trace is
          >>
          >> weblogic.jms.common.JMSException: Connection not found
          >>      at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
          >>      at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:596)
          >>      at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
          >>      at weblogic.jms.client.JMSConnection.start(JMSConnection.java:567)
          >>      at uk.co.concise.payments.event.EventProcessorServiceAsynchBD.(EventProcessorServiceAsynchBD.java:82)
          >>      at uk.co.concise.payments.state.ejb.ObjectStateServiceXDBean.ejbCreate(ObjectStateServiceXDBean.java:213)
          >>      at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_Impl.ejbCreate(ObjectStateService_1th3um_Impl.java:135)
          >>      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:324)
          >>      at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:172)
          >>      at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:110)
          >>      at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:140)
          >>      at weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:229)
          >>      at weblogic.ejb20.internal.StatelessEJBLocalObject.preInvoke(StatelessEJBLocalObject.java:54)
          >>      at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_ELOImpl.createAndGetStateForObject(ObjectStateService_1th3um_ELOImpl.java:273)
          >>      at uk.co.concise.payments.state.ObjectStateServiceBD.createAndGetStateForObject(ObjectStateServiceBD.java:123)
          >>      at uk.co.concise.payments.submission.ejb.SubmissionServiceXDBean.createSubmission(SubmissionServiceXDBean.java:92)
          >>      at uk.co.concise.payments.submission.ejb.SubmissionService_o0dxp8_ELOImpl.createSubmission(SubmissionService_o0dxp8_ELOImpl.java:162)
          >>      at uk.co.concise.payments.submission.SubmissionServiceBD.createSubmission(SubmissionServiceBD.java:42)
          >>      at uk.co.concise.payments.submission.webapp.SubmitPaymentFileAction.execute(SubmitPaymentFileAction.java:216)
          >>      at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:446)
          >>      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
          >>      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
          >>      at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
          >>      at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          >>      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          >>      at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
          >>      at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
          >>      at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
          >>      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
          >>      at uk.co.concise.payments.logon.filter.LogonFilter.doFilter(LogonFilter.java:38)
          >>      at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
          >>      at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
          >>      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >>      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          >>      at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
          >>      at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
          >>      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          >>      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >>
          >>
          >> Any ideas on what could be wrong
          >> thanks
          >> jaz
          >

[E2010] [EWS] [C#] [Windows]: Unable to connect to remote server

I have a Windows Service that uses EWS to connect to a mailbox and do some things with certain emails. The service has been running for a while now, with little to no issues. Just recently the service will stop and when viewing the event log, we receive
the following error.
Error Message: The request failed. Unable to connect to the remote server
Inner Exception: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalBind(EndPoint localEP)
   at System.Net.Sockets.Socket.BeginConnectEx(EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
   at System.Net.Sockets.Socket.UnsafeBeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
Target Site: Microsoft.Exchange.WebServices.Data.IEwsHttpWebResponse GetEwsHttpWebResponse(Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest)
Source: Microsoft.Exchange.WebServices
Stack Trace:    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
   at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
   at Microsoft.Exchange.WebServices.Data.ExchangeService.FindItems[TItem](IEnumerable`1 parentFolderIds, SearchFilter searchFilter, String queryString, ViewBase view, Grouping groupBy, ServiceErrorHandling errorHandlingMode)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.FindItems(FolderId parentFolderId, SearchFilter searchFilter, ViewBase view)
   at MyClass.CleanupDeletedItems()
   at MyClass.ReadEmail()
   at MyService.WorkerFunction()
This so far has only occured twice, but I am not sure if the issue is on the exchange servers, or the server where the service itself is running. Any ideas on what would cause this issue and how to go about fixing it?
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Don't Retire Technet

Hi Clayman
Well it makes sense to me that the registry could help, checking the lines in the error code, it appears that the for some reason the server could not stablish a connection, the error states: because the system lacked sufficient buffer space or because a queue
was full.
It seems don't make sence untill you have a look at Socket Class (MSDN article), which say: The Socket class provides a rich set of methods and properties for network communications. The Socket class allows you to perform both synchronous and asynchronous data
transfer using any of the communication protocols listed in the ProtocolType
Checking also the HttpWebRequest Class, we can see the it also relays on Socket Class, as it says by the end of your exception:
[at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)]
I also don't know if you could reboot your machine, but it would be good.
Also I really think its worthy a try, as not much information can befound on this EWS issue.
MaxUserPort
From <http://technet.microsoft.com/en-us/library/cc938196.aspx>
Socket Class
From <http://msdn.microsoft.com/en-us/library/system.net.sockets.socket(v=vs.110).aspx>
HttpWebRequest.GetResponse Method
From <http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.getresponse(v=vs.110).aspx>
HttpWebRequest Class
From <http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest(v=vs.110).aspx>
If you apply the registry change, let me know.
Think before you ask, be detalist as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

Cannot open Report Manager URL -- "Unable to Connect to Remote Server"

Hi,
I have recently installed SSRS 2012 on my remote server (Native Mode). I had the default configurations set except for the port has been changed to "8081". I created an Inbound Rule in Firewall to make sure it's enabled.
I'm unable to connect to the report manager locally at all, I got a Domain\username authentication and the credentials are never accepted locally. I tried accessing my report server using the remote server host name and I was successfully logged in,
however, I got a message "Unable to Connect to the remote server".
I checked the log folder and there was no files created for my unsuccessful login.
I've been stumbling with this issue for almost a week, Any ideas or suggestions ?

Hi SB User,
Per my understanding that after you change the IP to "8081" then you can't connect to the report server both locally and remotely, right?
Is that mean before you have changed the IP, everything works fine and did you got some pop up window ask for credential when you connect to the report server?
You issue can be caused by many factors, please try to check details information below and do some configurations:
Go to Reporting Services Configuration Manager and change the account to "Network Service" to see if it will works fine.
Change the account to domain account and re-enter the username and password to see if it works fine.
Remove the SSL if configured.
Go to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config
In rsreportserver.config Change the SecureConnectionLevel value to "0":
<Add Key="SecureConnectionLevel" Value="0"/>
Stop and restart the report services instance to see if you can connect to report server.
please also Using IP instead of computer name as the <servername> in the URL to have a test.
If your issue still exists, please try to change the IP to have a test.
If you still have any problem,please fee free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

MDBs failed to connect to remote JMS server

Hi,
          We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
          In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
          <weblogic-enterprise-bean>
               <ejb-name>MyBean</ejb-name>
               <message-driven-descriptor>
                    <destination-jndi-name>MyTopic</destination-jndi-name>
          <provider-url>t3://myhost:19009,myhost:19011</provider-url>
          <connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
          di-name>
               </message-driven-descriptor>
          </weblogic-enterprise-bean>
          When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
          (t3://myhost:19009) but got the same result.
          When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
          I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
          Any help would be greatly appreciated.
          Thanks,
          Thao

I'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?).                    I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
          >>> Could you elaborate on the known problem?
          9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
          >>> What else I can try?
          Beyond contacting customer support, I'm not sure.
          Tom

Unable to connect to remote JMS service

Similar Messages

Maybe you are looking for