Airport is not able to connect to Dlink G604T wireless

I'm experiencing this bug:
Airport is able to recognize an open wireless connection provided by G604T dlink router. So Airport try to connect (no pwd are required, the wireless isn't encrypted). The error is due to timeout connection (as showed by SL pop up).
I've tried many solution (as to delete library/preferencies/systemconfiguration files, or to update the firmware at ftp://ftp.dlink.co.uk/dslroutersmodems/dsl-g604t/ , or to change wi-fi channel, or to create a new user, or to create a new connection profile, and so on). Nothing solved the bug.
Other suggestions are pretty apprecciated.
Thanks a lot.
Luca.

D-Link routers have always made me nuts ...
http://store.apple.com/us/product/FC340LL/A?mco=MTc4MzI5NzM

Similar Messages

AirPort Express Not Able to Connect Wirelessly

Hardware is iMac 2.4 GHz Intel Core 2 Duo with 4 GB 667 MHz DDR2 SDRAM. Mac OS 10.6.8
Connected to Internet via Motorola Surfboard SBG6580 Modem / Router, so I connect by wireless through the modem.
I followed the installation instructions to install AirPort Express to play music on my home stereo. I connected the Airport Express to the receiver by the tape port. I was not able to install AirpPort Express via wireless mode, so I connected the iMac to the AirPort Express by CAT-5 hard wire cord. The installation was successful and the AirpPort Express obtained an AP address. I was then able to play music from iTunes pm the iMac through the stereo speakers...as long as the AirPort Express was connected by hard wire to the iMac.
When I remove the CAT-5 cord from the AirPort Express, the AirPort Express retains the green light, but it is not able to receive data from the iMac. To the contrary, the AirPort Utility is not able to find any AirPort wireless devices unless the AirPort Express is connected via the hard wire CAT-5 cord.
As an experiment, I then connected the AirPort Express to the cable modem / router via the hard wire CAT-5 cord. The AirPort utility on the iMac was still not able to find any AirPort wireless devices. Further, the model then assigned a different AP address to the iMac so that it was not able to connect to the Internet..
Meanwhile, the AirPort Express still retains the green light, indicating the installation was a success and that it is ready to transmit.
Any advice to resolve this issue would be very much appreciated. Thanks in advance for your thoughts.

I suggest that you start by performing a "factory default" reset on the 802.11n AirPort Express Base Station (AXn) to get it back to its "out-of-the-box" configuration. By default, the AXn will broadcast an unsecured wireless network with a Network Name of something like: Apple Network NNNNNN
After the reset has completed, plug the AXn into power, and then, verify from the iMac that this network shows up in the list of networks under the AirPort icon in the OS X menu bar. Does it?
If so, then from the AirPort icon, switch your iMac to connect to the AXn's wireless network. Note: You will temporarily lose the Internet connection from your Motorola router. Then, run the AirPort Utility. The Utility should now find the AXn. If not, use the Utility's "Configure Other" option under the File menu option in the Utility's menu bar. Enter 10.0.1.1 for the Address and "public" for the Password.
AirPort Utility > Select the AXn > Manual Setup > AirPort > Wireless
Wireless Mode: Join a wireless network
Network Name: <existing Motorola's wireless network>
Wireless Security: <select the encryption type of the existing wireless network>
Wireless Password: <enter the existing wireless network password>
Verify Password: <re-enter the existing wireless network password>
AirPort Utility > Select the AXn > Manual Setup >Music
Enable AirPlay (checked)
iTunes Speaker Name: <enter desired speaker name>
iTunes Speaker Password: (optional)
Verify Password: (optional)
Click Update to write the new settings to the AX

Not able to connect on my secured wireless network

I am having WRT54G2 router and i configure my router for my home. I configured it as secured network. I have a laptop (IBM Thinkpad R52). But i am not able to connect my home wireless secured network. When i try to connect any other unsecured (open to all) network from my laptop it allows me. For any secured network it says Acquiring Network address. What should I do?

What encryption are you using?
What operating system are you using?
For WEP, you must enter WEP "key 1" (found in the router) into your computer, not the WEP password or passphrase.
For WPA or WPA2, you must enter the key (sometimes called password or passphrase) into your computer.
Note that WPA2 (= WPA with AES) requires that you upgrade Windows XP to SP3. If you have not done this yet, do this now. Note that Windows Vista already works with WPA2.
If you still have trouble connecting, in the computer, temporarily disable your software firewall, including Windows Firewall, and see if that helps.
If you still have trouble, download and install the latest driver for the wireless adapter in your computer.
Message Edited by toomanydonuts on 05-30-2008 01:22 AM

HT4259 I have the old airport express but my iPad 3 is not able to connect to it even with the app downloaded. What can I do?

I have the old airport express but my iPad 3 is not able to connect to it even with the app downloaded. What can I do?

Use a windows computer.. or ask a friend to bring a windows laptop and use the 5.6 version windows utility.

AE only shows 5Ghz even though it says dual band. so i am not able to connect devices which only works with 2.4 ghzs

Hi Can you please help me to resolve the issue of my Airport Extreme only showing 5Ghzs and not dual band. i am not able to connect any of my 2.4 ghzs devices.

Hi Can you please help me to resolve the issue of my Airport Extreme only showing 5Ghzs and not dual band. i am not able to connect any of my 2.4 ghzs devices.

My time capsule sometimes is not able to connect or appear like is out or range , and need wait a few min. to connect again

sometimes , the time capsule is not able to connect and it take a few min. to connect again , even using the airport utilities cannot connect , it shows like is out of the range , when is connect to the line , also cannot use using the new ipad, iphone 4s or airport .

janeyq wrote:
If we replace our Time Capsule, what is the best way to handle the data stored on the old TC?
Archive the material via airport utility (old v5 not v6).. to a USB drive of suitable size for all the data.
Do this before the TC dies. Once dead you will have no choice but to repair it.. or to open and remove the HD and put it in a holder.

Airport does not want to connect to a weaker signal

my airport has decided that it does not want to connect to a weaker signal. at home if i am next to the wireless source my computer connects just fine, but if i go downstairs to my room the signal strength starts dropping and then will disconnect all together and i am unable to connect again. the signal strength is strong enough to connect because my computer connected just fine before and i tried it with my brothers computer (he has a 15in macbook pro) and it connects just fine. any suggestions? thanks
=)-SamIam-(=

yes everything connects to the same wireless internet. i did notice i had a harder time connecting around the time i upgraded to 10.5.6. (i cant remember for sure)
i don't think it matters but i am not connecting to a AP base station at home. We use our iMac for our wireless internet. but even if i am not at home i cant connect to any wireless signal while others around me are connecting to a free service in town. (i used to be able to connect to the same service in town to which i can not anymore)
i did notice that when i open my MBP and wake it form sleep i am able to connect for a couple of min, then the signal gets weaker and weaker until it disconnects and i am not able to connect again.
thanks
=)-SamIam-(=

10g Enterprise Manager is not able to connect to the database instance

I am running a Oracle 10g database in Solaris 10 server. When i am trying to connect to the enterprise manager it says Enterprise Manager is not able to connect to the database instance.
The database instance is open,the listener is up and the agent connection also says that it succeeded.
The server houses two 10g databases and the EM was working properly till yesterday. Kindly Help.
Thanks in advance.
Ram

Hi,
The EM is started and if i give emctl status dbconsole
-bash-3.00$ emctl status dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.3.0
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
http://gladiator:1158/em/console/aboutApplication
Oracle Enterprise Manager 10g is running
Logs are generated in directory /db8/ora10gr2/product/10.2.0/Db_4/gladiator_TROY/sysman/log
it says that the EM is running. But when i am trying to access the URL it is in IE it says Page cannot be displayed what could be the problem for this???
Thanks in advance.
Ram

Reporting Services not able to connect with sharepoint

HI
We have a Sql server instance where we are not able to install reporting services, so what we have done is we have created one more sql server instance on the same server with reporting services.
When we configured reporting services in sharepoint integrated mode and try to connect that web service url in sharepoint we are getting an error in sharepoint central administartion that not able to connect to the reporting services.
Request you to throw some light on the same.
Thanks
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

Hi Geeth,
Based on the limited information, I am not very clearly about you issue. In order to solve the problem more efficiently, I need to clarify some information. Could you post more detail information about “try to connect that web service url in sharepoint we
are getting an error in sharepoint central administartion”? For example, the detail steps about the action, the screenshot of the action, and what error message you received. I’m not sure which step are you trying to do. And could you tell me the edition of
your SQL Server and SharePoint? It is benefit for us to do further analysis.
References:
2008 R2:
http://technet.microsoft.com/en-us/library/bb283190(v=sql.105).aspx
http://sharepointtaskmaster.blogspot.in/2010/11/intergration-reporting-service-with.html
http://technet.microsoft.com/en-us/library/bb326213(v=sql.105).aspx
2012:
http://technet.microsoft.com/en-us/library/47efa72e-1735-4387-8485-f8994fb08c8c
http://denglishbi.wordpress.com/2011/07/22/configuring-sql-server-denali-reporting-services-sharepoint-2010-integration/
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Not able to connect CRM Online to PowerBI

Not able to connect CRM Online to PowerBI, Please let me know if you have an idea to resolve this issue.
oops, something went wrong
Failed to update model parameters
Activity Id59a2a854-8e34-6636-0679-3d2e245d2241
Request Id9b7fa606-324e-4ec8-495f-13f91d03bc54
Error Code400
TimeWed Mar 18 2015 21:24:18 GMT-0400 (Eastern Daylight Time)
Version11.0.9165.945
Cluster URIhttps://wabi-south-east-asia-redirect.analysis.windows.net

Hi Kiran
Please chcek the Note 1359600-MDM stopped communicating after upgrading to 7.1.03 from SAP NOTES.
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1359600
SAP Note Description:
Summary
Symptom
MDM components stopped communicating after upgrading to 7.1.03
Other terms
TCP ports, Firewall, connection, network, SP03, SP3, 7.1
Reason and Prerequisites
Starting from version 7.1.03 the MDM suite is using different TCP ports for its operations. The change was in order to be compliant with the Internet Authority for Numbering Assignment. Port numbers changed as follows:
Application Old Port # New Port #
MDS 20005 59950
MDLS 20008 59650
MDIS 20009 59750
MDSS 20010 59850
If firewalls were configured to allow MDM's communication throughout the landscape, they actually might prevent (depending on their rules table) the communication after an upgrade to MDM suite starting at version 7.1.03 and higher.
Solution
Revise the firewall rules such that they will allow the communication according to the changes described above.
In order to check that the ports are allowed to pass trough the firewall a telnet test could be done like so:
1) Open a terminal window (on UNIX) or a command window (on Windows) on the same machine which hosts the application which tries to connect, and issue the following command:
telnet <MDM server host name or IP address> <TCP port to test>
2) If no error response is received than it means that the TCP port is allowed to go trough.
3) Repeat steps 1,2 for all the other ports need by the application.
Thanks
Sowseel
Edited by: sowseel pasumarthi on Jan 18, 2011 6:36 AM

Not able to connect N70 to pc(xp) using ca-53 cabl...

Not able to connect N70 to pc(xp) using ca-53 cable
hi i am having this trouble from a year... i am unable to connect my phone n70 using cable to my pc,.,. even after installing all drivers n pc suite n havin it reinstalled also n again doin d same process.. its not getting detected at all.. please help me out... pleaseeee..been tryin 4m a year..nevr checkd des forumss.. hopin som bdy ll help ,me out.. !!!. !!!!

The DKU-2 cable is no longer supported and so cannot be guaranteed to be compatible with current PC Suites, you should be using either your current CA-53 or the CA-70.
Have you had the chance to connect any other phone with the PC using this cable? This would test if thr cable itself might be faulty.
Otherwise remove PC Suite, PC Connectivitiy Solution and Connectivity Cable Drivers from control panel, run the PC Suite Cleaner program that you can get from the PC Suite support pages on the web site, then reinstall everything.

Not able to connect to wifi wpa2 networks in lenovo vibe x2

Not able to connect to wifi wpa2 networks in lenovo vibe x2. It displayed saved.but not connecting. It connects to open and WEP wifi networks. Please help

Are you trying to connect to a 2.4GHz or a 5GHz network?
What encryption is your router set to use : AES,TKIP/AES,..?
Have you tried to unplug the router from the power source for 2-3 minutes->Plug it back in-> Wait until it establishes an Internet connection-> Try to recreate the phone connection.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as ''ACCEPT AS SOLUTION"!
Unsolicited PM's will not be answered! ....Please post your question/s in the appropriate forum board.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Not able to connect to a queue under a foreign server.

Not able to connect to a queue under a foreign server.
I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
OS used is AIX 6.0 on both servers.
Tried restarting the local server but nothing helps. Same error continues.
HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?
It throws following errors:
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
     at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
     at javax.naming.InitialContext.internalInit(InitialContext.java:286)
     at javax.naming.InitialContext.<init>(InitialContext.java:211)
     at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
     at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:436)
     at weblogic.jms.common.CDS$2.run(CDS.java:503)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
     at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
     at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
     at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
     at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
     ... 46 more
>
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
<Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
Edited by: 942523 on Jun 24, 2012 11:38 PM

Thanks René van Wijk for the reply.
I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.
Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:
This page displays details about this bound object.
Failed to create InitialContext using factory specified in hashtable
Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
     java.io.EOFException]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
     at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:436)
     at weblogic.jms.common.CDS$2.run(CDS.java:503)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
     java.io.EOFException
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
     at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
     ... 36 more
Caused by: java.io.EOFException
     at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
     at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
     at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
     at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
     at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
     at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
Let me know if any other thing i'm missing or it can be something else like network or some other issue.

IPad 2 - I am not able to connect my iPad 2 to my tv anymore using AV adapter.

What is wrong with my iPad 2? I'm not able to conect my iPad to my proyector or tv anymore using AV adaptor. Is there something wrong with my iPad?
I tried it with my wife's iPad 2 and it was the same result. I was not able to connect her iPad to my TV. Niether TV or a proyector couldn't find the device.
Would you please help me? Your help will be well appreciated.

Sounds like the one common thing is the adapter. The cheaper, non apple branded ones tend to fail.
Try another adaptor before worrying about your ipad.

Enterprise Manager is not able to connect to the database instance. The sta

Enterprise Manager is not able to connect to the database instance. The state of the components are listed below.
Listener is shown as unavailable.
lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 27-NOV-2012 11:52:40
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=freds-server.i-surname.co.uk)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 27-NOV-2012 11:50:02
Uptime 0 days 0 hr. 2 min. 37 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/11g/network/admin/listener.ora
Listener Log File /opt/oracle/diag/tnslsnr/freds-server/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=freds-server)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=freds-server)(PORT=8080))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "GWORCL.i-surname.co.uk" has 2 instance(s).
Instance "GWORCL", status UNKNOWN, has 1 handler(s) for this service...
Instance "GWORCL", status READY, has 1 handler(s) for this service...
Service "GWORCLXDB.i-status.co.uk" has 1 instance(s).
Instance "GWORCL", status READY, has 1 handler(s) for this service...
The command completed successfully
I suspect that this is not just an OEM issue.
see
Listener working but not working for Enterprise manager oracle 11gr2 Linux.
for configuration files
Edited by: Neill_R on Nov 27, 2012 11:51 AM

This was solved by : Osama_mustafa
in the general questions forum
emca -deconfig dbcontrol db -repos drop
emca -config dbcontrol db -repos create

Airport is not able to connect to Dlink G604T wireless

Similar Messages

Maybe you are looking for