Connection to Instance failed

Dear all,
I installed Oracle 10g Release 2 in my windows 2003 server and the installation is successful.(Not display any error message)
When I use Enterprise Manger Database Control to connect to database.The Web page tell me that Enterprise Manager is not able to connect to the database instance. And the error message is
Agent Connection to instance
status: Failed
Details : ORA-12505: TNS:listener does not currenty know of sid given in connect descriptor(DBD ERROR:OCIServerAttach)
I have checked the following service is starting: (My database name is TestDb)
(1) OracleServiceTestdb
(2) OracleOraDb10g_home1TNSListener
(3)OracleDBConsoleTestDb
I try to connect this database with SQL Plus, It display following error message:
ORA-01034 : ORACLE not available
ORA-27101: shared memeory realm does not exist
How can I do? Please give me detail.
Thanks you

HI,
Check
01. OracleServices<InstanceName>
02. in cmd prompt c:\>tnsping testdb
03. Check the SID name in the listener.ora file
04. Stop and start the listener lsnrctl
Cheers,
Kamalesh JK

Similar Messages

  • Agent Connection to Instance - Failed  ORA-12541

    Hi folks, I recently changed the SID (but not name) of my database. Everything has been working great, but I get the following error message in OEM after it's been running for about 10 minutes:
    Agent Connection to Instance
    Status Failed
    Details Failed to connect to database instance: ORA-12541: TNS:no listener (DBD ERROR: OCIServerAttach).
    Since everything else is running fine (everything else in OEM is working fine, network connections via SQL Developer, Toad, JDBC, I'm not sure where to look.
    I also have a second server running (on which I haven't changed the SID) to compare to. Outputs of lsnrctl services, the tnsnames.ora file, and everything else seems to line up.
    I'd be happy to post anything that might be useful, thanks very much!

    Hello,
    recently I was hitting the same problem:
    Listener Status: Up
    Agent Connection to Instance Status: Failed
    Details          Failed to connect to database instance: ORA-12541: TNS:no listener (DBD ERROR: OCIServerAttach).
    It turns out that the message is misleading and the problem lies in the locked dbsnmp account. I resolved that through
    Grid Control / Targets / Search List / (Select DB with problems) -> Configure
    where it showed the following error:
    "java.sql.SQLException: ORA-28000: the account is locked The Connect Descriptor was (description=(address=(host=xx)(protocol=tcp)(port=xxxx))(connect_data=(service_name=xx)(instance_name=xx)(UR=A)))
    Change dbsnmp Password - The error message shown above indicates that the agent is unable to monitor this database because the agent cannot logon. To correct this, the Monitor Password needs to match the corresponding database password for dbsnmp. To change both the dbsnmp database password and the Monitor Password, click the Change dbsnmp Pasword button. This operation will also unlock the dbsnmp user."
    It is possible to change the password from that dialog what I did. It is working fine now.
    I do not know if the problem lies in accout locked or wrong password after all, but repeating the configuration resolved the case.
    Greetings
    Remigiusz Boguszewicz

  • Agent Connection to Instance error in Oracle Database 11G EM

    Hi
    I am getting the following error message when logging into EM on Oracle 11G Database.
    Failed to connect to database instance: ORA-12541: TNS:no listener (DBD ERROR: OCIServerAttach).
    Users can connect to the database no problem and it shows the Database Instance down, Agent Connection to Instance failed. The General tab shows green and the database is up.
    I have checked the emctl status and lsnrctl commands and the listener is up and servicing the database. I checked the ORACLE_SID environment (in Windows Server 2003) and this is correct.
    I have recently changed the passwords for SYSMAN and DBNSMP which were due to expire and since then the EM console has not loaded correctly.
    As I said the database is up and can service users through their application.
    Any help would be appreciated.
    Respect.

    Hi
    The listener is up and is handling the database and users are connecting succesfully. I think it is more to do with the Enterprise Manager.
    Can anyone give me some further info to troubleshoot?
    Regards
    Spencer

  • SQL2012 SSMS fail to connect named instance

    Hi, Currently we would like to setup replication between 2 sql instances (binded to corresponding IP, listening on port 1433) on different servers (DUAT01, DUAT101). However, we found the SSMS cannot connect remote server A from server B using
    named instance.
    The sql instances can be connected by using either IP or FQDN, however, that cannot fulfill the requirement on setting up replication as it require the instance to connect as "DUAT101\SQL2K8R2" instead of "x.x.x.x" or "SQLUATCSS2K8R2.domain.com".
    We tried to change "Protocol"->"Listen All" from "No" to "Yes", then SSMS can connect the named instance successful in this format "DUAT101\SQL2K8R2", but the application using "SQLUATCSS2K8R2.domain.com"
    to connect sql instance was fail.
    Pls advise how to make it possible to connect sql instance successful in both way. thanks.

    can connect the named instance successful in this format "DUAT101\SQL2K8R2", but the application using "SQLUATCSS2K8R2.domain.com" to connect sql instance was fail.
    Hello,
    To connect to a named instance you have to use either the instance name or the instance IP port, like
    DUAT101, 1433
    The only other Option is to create a SQL Server alias using CliConfg.exe (Client configuration) tool.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]
    Hi Olaf, our server (DUAT101) have 5 sql instances. It always return the default instance with "DUAT101, 1433". When I connect using instance name, it prompt me below error that we need to solve.
    ===================================
    Cannot connect to duat101\sql2k8r2.
    ===================================
    Instance failure. (System.Data)
    Program Location:
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
    timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
    SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
       at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

  • Weblogic clustered server instance failed in less than 30 hours with no load/utilization

    system description: hpux 11, jdk 1.2.2_03, weblogic 5.1 sp1, two clustered
    instances on one box, fail over to second box on shared file system.
    problem:
    in our custom weblogic monitoring scripts, we run the weblogic ping command
    every ten seconds with the following command:
    java weblogic.Admin t3://10.7.192.103:7001 PING 10 56 system weblogic
    this weekend, both of our instances failed at one point and returned this
    error message multiple times:
    Exception in thread "main" java.lang.NullPointerException
    at
    weblogic.common.internal.BootServicesStub.findOrCreateClientContext(BootServ
    icesStub.java:112)
    at weblogic.common.T3Client.connect(T3Client.java:384)
    at weblogic.Admin.connect(Admin.java:133)
    at weblogic.Admin.main(Admin.java:216)
    our monitoring scripts successfull revived the instances, but there is a
    problem with this.
    problem: there was no load or utlization of the weblogic server instances
    at the time of the failure. both instances had only been up for about 30
    hours when they failed. is this due to weblogic instability? i hope not.
    a max uptime of 30 hours doesn't say much for the reliability of the product
    especially since there was zero utilization...
    andrew park

    This looks to be a bug (obviously). I will have someone take a look and
    let you know.
    Cheers
    Mark g
    In article <8gbj2d$m9m$[email protected]>, [email protected] says...
    system description: hpux 11, jdk 1.2.2_03, weblogic 5.1 sp1, two clustered
    instances on one box, fail over to second box on shared file system.
    problem:
    in our custom weblogic monitoring scripts, we run the weblogic ping command
    every ten seconds with the following command:
    java weblogic.Admin t3://10.7.192.103:7001 PING 10 56 system weblogic
    this weekend, both of our instances failed at one point and returned this
    error message multiple times:
    Exception in thread "main" java.lang.NullPointerException
    at
    weblogic.common.internal.BootServicesStub.findOrCreateClientContext(BootServ
    icesStub.java:112)
    at weblogic.common.T3Client.connect(T3Client.java:384)
    at weblogic.Admin.connect(Admin.java:133)
    at weblogic.Admin.main(Admin.java:216)
    our monitoring scripts successfull revived the instances, but there is a
    problem with this.
    problem: there was no load or utlization of the weblogic server instances
    at the time of the failure. both instances had only been up for about 30
    hours when they failed. is this due to weblogic instability? i hope not.
    a max uptime of 30 hours doesn't say much for the reliability of the product
    especially since there was zero utilization...
    andrew park
    ==================================================
    NewsGroup Rant
    ==================================================
    Rant 1.
    The less info you provide about your problem means
    the less we can help you. Try to look at the
    problem from an external perspective and provide
    all the data necessary to put your problem in
    perspective.

  • Dialog ABAP+Java instance fails to go to green (stays yellow)

    ECC 6.0 SPS 13 (NW 17)
    Win 2003
    SQL 2005 (latest patch)
    Using System Copy SR3
    After performing a Hom system copy (from PRD) of my QAS system, the Java "component" of the dialog instance attached to the central instance fails to start.  The central instance's java component loads just fine, but I get the following error in the jvm.bootstrap file of the DI.
    Bootstrap MODE:
    <INSTANCE GLOBALS>
    determined by parameter [ID0328058].
    Exception occurred:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
         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 com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:364)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:129)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
         at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
         at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
         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 com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.microsoft.sqlserver.jdbc.SQLServerDriver.
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:306)
         ... 14 more
    Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
         at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:141)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
         ... 17 more
    [Bootstrap module]> Problem occurred while performing synchronization.
    Any thoughts on what I can do (without having to re-install the dialog instance) to fix this?

    Hi,
    I hope this helps you, my Basis team came up with the same problem. It is because of the JDBC driver that SR3 uses seems to be wrong. This is a slightly subtle problem and it took me a while to find.
    - Open configtool
    - Go to instance --> dispatcher --> Configuration Manager --> Local Properties --> rdbms.driverLocation
    - Change it to C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\sqljdbc.jar (or similar)
    - Go to instance > server> Configuration Manager --> Local Properties --> rdbms.driverLocation
    - Change it to C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\sqljdbc.jar (or similar)
    On my system it was set to C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\base.jar;C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\util.jar;C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\sqlserver.jar;C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\spy.jar which is the old school SQL Server driver.
    Once you have changed these settings, save, exit configtool and restart the whole cluster. It will then start.
    Regards,
    John

  • TNS-04012: Unable to start Oracle Connection Manager instance.

    Hi,
    I've tried to configure Connection Manager but i fails on:
    TNS-04012: Unable to start Oracle Connection Manager instance
    This is my configuration (I've removed as much as possible to remove possible errors):
    CMAN1=(CONFIGURATION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=1522))
      (RULE_LIST=
       (RULE=(SRC=*)(DST=<IP>)(SRV=*)(ACT=accept))))
    CMCTL> administer CMAN1
    Current instance CMAN1 is not yet started
    Connections refer to (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=1522)).
    The command completed successfully.
    CMCTL:CMAN1> startup
    TNS-04012: Unable to start Oracle Connection Manager instance.I've reviewed following notes without getting any closer (298916.1 and 733421.1)
    I can't see any errors in any of the following possible issues:
    * The max_connections value must not exceed 1024. Maximum acceptable value is 1024
    * The max_gateway_processes value must not exceed 64. Maximum acceptable value is 64
    * The trace_directory and log_directory values must be valid
    * The trace_level and log_level values do not support numeric values 6,10 and 16
    * Duplicate sections
    * Misspelled parameter names or parameter values
    * Host values that are not resolvable
    * Rule list must allow the local address of the machine where cman is installed
    * A specfic address in SRC or DST for a rule in the rule list must be resolvable(Try ip address range as a workaround and see the enhancement request 6125025)
    * Windows: Ensure the ORA_DBA group is present and O/S user starting CMAN is in the group
    * Windows: Ensure any firewall is not blocking Oracle from using Network
    All help are appreciated!
    Cheers

    933746 wrote:
    Osama_mustafa wrote:
    Refer to
    Troubleshooting Guide: TNS-04012: Unable to Start Oracle Connection Manager Instance [ID 733421.1]Hi,
    As I've stated in my post I've reviewed this post without any help.I would suggest you read the provided doc [ 733421.1] more thoroughly.... the answer is there.

  • BEA-001156 - connection pool reset failed on WLS 8.1.6

    Hi,
    I run WLS 8.1.6 on Linux and JRockit 1.4.2_12. I got the following error when I tried to reset a connection pool manually from the console. This does not happen all the time, so it is hard to reproduce. There is no change to database login credential. Any suggestions are appreciated. Thanks in advance.
    BEA-141132
         Dynamic invocation while executing action reset on etg:Locat
         ion=nyclrwp_14654_2,Name=testPool,ServerRuntime=mycluster,
         Type=JDBCConnectionPoolRuntime MBean instance
         failed. The method reset with signature [] was invoked with
         parameters as [].
    weblogic.common.ResourceException: Refresh operation was partially successful, (1)
                        out of (1) resources could not be refreshed.
         at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:669)
         at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
         at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
         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.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    BEA-001156
         Stack trace associated with message 001129 follows:
    java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to
              this exception for the reason(s).
         at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:506)
         at com.sybase.jdbc2.tds.Tds.processLoginAckToken(Tds.java:3224)
         at com.sybase.jdbc2.tds.Tds.doLogin(Tds.java:483)
         at com.sybase.jdbc2.tds.Tds.login(Tds.java:405)
         at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
         at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
         at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:174)
         at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:126)
         at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:251)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:330)
         at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1694)
         at weblogic.common.resourcepool.ResourcePoolImpl.refreshAvlResources(ResourcePoolImpl.java:1982)
         at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:664)
         at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
         at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
         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.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
    BEA-001129
         Received exception while creating connection for pool "cpl1C
         onnectionPool": JZ00L: Login failed. Examine the SQLWarnings
         chained to this exception for the reason(s).
    BEA-001128 Connection for pool "testPool" closed.
    BEA-001099 Connection pool "testPool" reset by "system"

    lei wang wrote:
    Hi,
    I run WLS 8.1.6 on Linux and JRockit 1.4.2_12. I got the following error when I tried to reset a connection pool manually from the console. This does not happen all the time, so it is hard to reproduce. There is no change to database login credential. Any suggestions are appreciated. Thanks in advance.
    Please tell me why you are resetting the pool. The reason may have something
    to do with the failure messages below. The root cause of these messages is
    that the pool is trying to make a new JDBC connection to Sybase, in exactly
    the same way it does all the time, but for whatever reason, the DBMS is
    refusing the connection request. The pool should be OK anyway, ongoing,
    as long as/when the DBMS is back up and accepting connection requests.
    Joe
    >
    BEA-141132
         Dynamic invocation while executing action reset on etg:Locat
         ion=nyclrwp_14654_2,Name=testPool,ServerRuntime=mycluster,
         Type=JDBCConnectionPoolRuntime MBean instance
         failed. The method reset with signature [] was invoked with
         parameters as [].
    weblogic.common.ResourceException: Refresh operation was partially successful, (1)
                        out of (1) resources could not be refreshed.
         at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:669)
         at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
         at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
         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.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    BEA-001156
         Stack trace associated with message 001129 follows:
    java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to
              this exception for the reason(s).
         at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:506)
         at com.sybase.jdbc2.tds.Tds.processLoginAckToken(Tds.java:3224)
         at com.sybase.jdbc2.tds.Tds.doLogin(Tds.java:483)
         at com.sybase.jdbc2.tds.Tds.login(Tds.java:405)
         at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
         at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
         at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:174)
         at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:126)
         at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:251)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:330)
         at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1694)
         at weblogic.common.resourcepool.ResourcePoolImpl.refreshAvlResources(ResourcePoolImpl.java:1982)
         at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:664)
         at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
         at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
         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.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
    BEA-001129
         Received exception while creating connection for pool "cpl1C
         onnectionPool": JZ00L: Login failed. Examine the SQLWarnings
         chained to this exception for the reason(s).
    BEA-001128 Connection for pool "testPool" closed.
    BEA-001099 Connection pool "testPool" reset by "system"

  • ORA-28547: connection to server failed, probable Oracle Net admin error

    Hi Gurus
    I can't get the gateway to work? I'm running on AIX. Any suggestions are appreciated.
    listener.ora
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1522))
    # (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1522))
    SID_LIST_LISTENER=
    (SID_LIST=
    (SID_DESC=
    (SID_NAME=dg4msql)
    (ORACLE_HOME=/oracle/rcsr/base/product/11.2.0/gateway)
    (PROGRAM=dg4msql)
    tnsnames.ora
    dg4msql =
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1522))
    (CONNECT_DATA=(SID=dg4msql))
    (HS=OK)
    sqlnet.ora
    SQL_AUTHENTICATION_SERVICES = (NONE)
    NAMES.DIRECTORY_PATH= (TNSNAMES)
    ADR_BASE = /oracle/rcsr/base
    initdg4msql.ora
    HS_FDS_CONNECT_INFO=142.178.205.42:1433//komodo
    # alternate connect format is hostname/serverinstance/databasename
    HS_FDS_TRACE_LEVEL=debug
    HS_FDS_RECOVERY_ACCOUNT=RECOVER
    HS_FDS_RECOVERY_PWD=RECOVER
    $ lsnrctl status
    LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 03-MAY-2013 13:48:01
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1522)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
    Start Date 03-MAY-2013 13:38:14
    Uptime 0 days 0 hr. 9 min. 47 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP ON
    Listener Parameter File /oracle/rcsr/base/product/11.2.0/gateway/network/admin/listener.ora
    Listener Log File /oracle/rcsr/base/diag/tnslsnr/abe-rcsr-01/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1522)))
    Services Summary...
    Service "dg4msql" has 1 instance(s).
    Instance "dg4msql", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    $ tnsping dg4msql
    TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 03-MAY-2013 13:48:53
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    /oracle/rcsr/base/product/11.2.0/gateway/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1522)) (CONNECT_DATA=(SID=dg4msql)) (HS=OK))
    OK (0 msec)
    $ sqlplus aa/aa@dg4msql
    SQL*Plus: Release 11.2.0.1.0 Production on Fri May 3 13:49:52 2013
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    ERROR:
    ORA-28547: connection to server failed, probable Oracle Net admin error

    You can't directly use the gateway - you can only access a gateway using a database link.
    So this won't work:
    $ sqlplus aa/aa@dg4msql
    You need to connect to your Oracle database (for example as sysdba) and create a (public) database link:
    create [public] database link dg4msql connect to "<MS SQl Server username! identified by "<MS SQl Server password>" using 'dg4msql;
    Once you create the database link you can now access the MS SQl Server tables:
    select * from "your MS SQL Server table"@dg4msql;

  • ORA-28547: connection to server failed, probable Net8 admin error

    Hi all. I use Oracle 10G. My listener.ora is below
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.8.26)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = sened)
    (ORACLE_HOME = C:\Oracle\OraHome)
    (PROGRAM = extproc)
    I have database with name sened
    And my tnsnames is below:
    SENED =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.8.26)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sened)
    When I start Windows, I can enter as sysdba . But when I issue "shutdown immediate", after that I can't connect as sys. And get this error:
    ORA-28547: connection to server failed, probable Net8 admin error
    And I stop my listener the I start it, it gives error:
    SQL> host lsnrctl start
    Service "sened" has 1 instance(s).
    Instance "sened", status UNKNOWN, has 1 handler(s) for this service...
    Why my database's status is UNKNOWN??
    Thanks....

    I get the error
    ORA-28546: connection initialization failed, probable Net8 admin error
    ORA-06512: at line 51
    when I try to run one of my sql scripts. The script tries to make an external procedure call. I am attaching the relevant .ora files.
    1.
    $ cat tnsnames.ora
    2.
    # tnsnames.ora Network Configuration File: /home/oracle/oracle/product/10.2.0/db_2/network/admin/tnsnames.ora
    3.
    # Generated by Oracle configuration tools.
    4.
    5.
    ORCL =
    6.
    (DESCRIPTION =
    7.
    (ADDRESS = (PROTOCOL = TCP)(HOST = accord.novaglobal.com.sg)(PORT = 1521))
    8.
    (CONNECT_DATA =
    9.
    (SERVER = DEDICATED)
    10.
    (SERVICE_NAME = orcl)
    11.
    12.
    13.
    14.
    EXTPROC_CONNECTION_DATA =
    15.
    (DESCRIPTION =
    16.
    (ADDRESS_LIST =
    17.
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    18.
    19.
    (CONNECT_DATA =
    20.
    (SID = orcl)
    21.
    (PRESENTATION = RO)
    22.
    23.
    24.
    25.
    26.
    27.
    28.
    29.
    30.
    31.
    32.
    33.
    34.
    35.
    36.
    cat listener.ora
    37.
    # listener.ora Network Configuration File: /home/oracle/oracle/product/10.2.0/db_2/network/admin/listener.ora
    38.
    # Generated by Oracle configuration tools.
    39.
    40.
    41.
    42.
    SID_LIST_LISTENER =
    43.
    (SID_LIST =
    44.
    (SID_DESC =
    45.
    (SID_NAME = orcl)
    46.
    (ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_2)
    47.
    (PROGRAM = extproc)
    48.
    (ENVS = "LD_LIBRARY_PATH=/home/oracle/DSAccord/lib,
    49.
    ACCORD_SYSTEM_6=/home/oracle/DSAccord/system/,
    50.
    ACCORD_SETTINGS_6=/home/oracle/DSAccord/accord6.ini,
    51.
    EXTPROC_DLLS=libaccora10.so.6:libaccosk10.so.6")
    52.
    53.
    54.
    55.
    56.
    LISTENER =
    57.
    (DESCRIPTION_LIST =
    58.
    (DESCRIPTION =
    59.
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    60.
    (ADDRESS = (PROTOCOL = TCP)(HOST = accord.novaglobal.com.sg)(PORT = 1521))
    61.
    62.
    63.
    64.
    65.
    66.
    67.
    cat sqlnet.ora
    68.
    # sqlnet.ora Network Configuration File: /home/oracle/oracle/product/10.2.0/db_2/network/admin/sqlnet.ora
    69.
    # Generated by Oracle configuration tools.
    70.
    71.
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

  • Center instance failed

    Dear Experts:
    my sap system occured a lot of error and all user operation failed, so i have to restart it urgently, following  are some messages in trace log file, please kindly help to investigate it, thanks!
    OS: Windows Server 2003 SP1
    DB: MSS 2005(9.0.3042)
    SAP: ECC 5.0
    Kernel: 6.40 unicode 221
    in the dev_disp:
    Wed Jan 14 09:07:28 2009
    NiPWrite: ENOBUFS: buffers reduced to 4/4096 (errNo=10055; cnt=1; len=7208; hdl 28 / socket 824)
    NiPWrite: ENOBUFS: buffers reduced to 4/1024 (errNo=10055; cnt=2; len=7208; hdl 28 / socket 824)
    NiPWrite: ENOBUFS: buffers reduced to 0/4096 (errNo=10055; cnt=1; len=6184; hdl 28 / socket 824)
    in the syslog:
    09:11:51 DIA 003 300 GO01         ZFIR BY4 Database error 0 at FET access to table DDFTX
    09:11:51 DIA 003 300 GO01         ZFIR BY0 > [10054] TCP Provider: An existing connection was f
    09:11:51 DIA 003 300 GO01         ZFIR BY0 > closed by the remote host.#[10054] Communication l
    09:11:51 DIA 003 300 GO01         ZFIR BY0 > failure#[-1] Session Provider: Physical connection
    09:11:51 DIA 003 300 GO01         ZFIR BY0 > usable [xFFFFFFFF].#[-1] Communication link failur
    09:11:51 DIA 003 300 GO01         ZFIR BY0 > Session Provider: Physical connection is not usabl
    09:11:51 DIA 003 300 GO01         ZFIR BY0 > [xFFFFFFFF].#[-1] Communication link failure#[0] P
    09:11:51 DIA 003 300 GO01         ZFIR BY0 > error in TDS stream
    09:11:51 DIA 003 300 GO01         ZFIR D01 Transaction Canceled 00 951 ( 0 )
    09:11:51 DIA 003 300 GO01         ZFIR BZY Unexpected return value 8 when calling up DbSlR
    09:11:51 DIA 003 300 GO01         ZFIR BYJ Function ROLLBACK on connection R/3 failed
    09:11:51 DIA 003 300 GO01         ZFIR R39 Error in DB rollback/SyFlush, return code 016384
    09:11:51 DIA 003 300 GO01         ZFIR Q02 Stop Workproc 3, PID 23580
    09:11:51 RD                            Q0I Operating system call recv failed (error no. 10054)
    09:12:02 WRK 000                       Q0Q Start Workproc 3, Pid 25920
    In the dev_w3 dialog work process:
    C Wed Jan 14 09:11:51 2009
    C  GetNextRows: line 20630. hr: 0x80004005 Protocol error in TDS stream
    C  sloledb.cpp [GetNextRows,line 20630]: Error/Message: (err 0, sev 0), Protocol error in TDS stream
    C  Procname: [##Y3LAX05SESr3p00000059800000000020094911]
    C  sloledb.cpp [GetNextRows,line 20630]: Error/Message: (err -1, sev 0), Communication link failure
    C  Procname: [##Y3LAX05SESr3p00000059800000000020094911]
    C  sloledb.cpp [GetNextRows,line 20630]: Error/Message: (err -1, sev 0), Session Provider: Physical connection is not usable [xFFFFFFFF].
    C  Procname: [##Y3LAX05SESr3p00000059800000000020094911]
    C  sloledb.cpp [GetNextRows,line 20630]: Error/Message: (err -1, sev 0), Communication link failure
    C  Procname: [##Y3LAX05SESr3p00000059800000000020094911]
    C  sloledb.cpp [GetNextRows,line 20630]: Error/Message: (err -1, sev 0), Session Provider: Physical connection is not usable [xFFFFFFFF].
    C  Procname: [##Y3LAX05SESr3p00000059800000000020094911]
    C  sloledb.cpp [GetNextRows,line 20630]: Error/Message: (err 10054, sev 0), Communication link failure
    C  Procname: [##Y3LAX05SESr3p00000059800000000020094911]
    C  sloledb.cpp [GetNextRows,line 20630]: Error/Message: (err 10054, sev 0), TCP Provider: An existing connection was forcibly closed by the remote host.
    C  Procname: [##Y3LAX05SESr3p00000059800000000020094911]
    C  DbSlExeRead - Error 99 (dbcode 10054) on get_next_row
    C  1 times error (0,0) in sequence
    B  ***LOG BY4=> sql error 0      performing FET on table DDFTX      [dbtran#10 @ 7292] [dbtran  7292 ]
    B  ***LOG BY0=> [10054] TCP Provider: An existing connection was forcibly closed by the remote host.
    Kind Regards
    Alex Cheng

    Looking in SM21, I see the following:
    A database operation returned a return code that indicates
    that the work process is no longer connected to the database, or that
    this connection was broken for a while.
    This error can occur, for example, if the database was shut
    down, but not the SAP System. Network problems can also cause the
    connection between the application server and the database server to be
    broken.
    For initial information on the cause of the error, see the
    database error text.
    The work process with the return code has the status
    Reconnect. It attempts to reconnect itself to the database status. If it
    reconnects successfully, it can start sending database requests to the
    database instance again. An appropriate message is written in the
    syslog.
    If the work process cannot reconnect itself, it remains in
    Reconnect status and attempts to reconnect itself to the database instance until
    it is successful.
    After talking to my network guys, I get the following answer: problems reported this morning appear to be connected to an issue with one of the IBM Blade Center chassis.  They have
    found that resets have occurred on one of the I/O modules.
    Good luck!

  • Cannot get maile connection to server failed

    followed the instructions for icloud set up in apple support for ipad and iphone even deleted the account and then set the account up with the correct ID and password.  I do use a different ID  than my apple ID for my icloud account.  I use my me.com email address.  I can get into the cloud on my pc and I can send and recieve email when I log into my icloud account but this fails to work on my ipad and iphone.  Attempts to seen or get email on these devices when on a wifi network end up with the message "cannot get mail connection to server failed"
    lee

    Hi HLSdoc,
    Thanks for using Apple Support Communities.
    For more information on this, take a look at this article:
    iCloud: Troubleshooting iCloud Mail
    http://support.apple.com/kb/ts4002
    Issues sending or receiving mail on iPhone, iPad, or iPod touch
    Best of luck,
    Mario

  • "Connection to server failed" error with Gmail exchange server

    Hi,
    I upgraded my iPhone 4 to iOS 4.3 on Friday and now I can't access my Gmail account using the Microsoft Exchange settings, I just get a "Connection to server failed" error.
    I also have a Google Apps email account for my website and I am able to access it using exchange... it's just my regular Gmail account that I can't access (and that's where all my contacts are stored).
    I can access the account using the regular Gmail email settings but that doesn't sync my contacts over the air, which is the advantage of using Exchange that I love the most.
    I don't know if it is related or not, but I had a really hard time upgrading to iOS 4.3. I guess the update file was corrupt and it put my phone into restore mode. I had to use a different computer for the upgrade to finally work. Because I was using a different computer I had to restore it as a new phone rather than restoring from a backup, so maybe that has something to do with my email problem.
    Message was edited by: KJones75

    I seem to have solved the problem. I deleted my Gmail account from the phone and then changed my Gmail password from my computer, and then tried adding the account to my phone again... and surprise, surprise, it worked.
    I'm not sure why changing the password fixed the problem, but I'm glad it's working again.

  • I am unable to receive or send email from my IPAD.  The error message says "Connection to server failed".  Help!! geandreamer44

    I am unable to receive or send email from my IPAD.  The error message says "Connection to server failed".  Help!! geandreamer44

    Reset the device:
    Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears.
    If that doesn't help, tap Settings > General > Reset > Reset All Settings
    If that doesn't help, tap Settings > General > Reset > Reset Network Settings
    You will have to re enter your Wi-Fi password.
    If nothing above helped, restart your router.
    No data is lost due to a reset.

  • Toshiba EXCITE Pro - WIFI connection. Authentication failed after update

    Hello.
    Just received this Tablet.
    Everything seemed ok while updating to the latest version (did that first to solve the heat problems).
    After the last update *i lost my WIfi connection. Authentication failed* (didnt change something - was connecting - updating ok 1 minute before the last update).
    After that i started testing ,Wps connection , No security Wifi etc etc.
    *Finally at a random time (and with the initial settings) i got connected*. After i shut down the tablet the same problem occured.
    After doing the same things again i finally got connected and this time it seems to be ok, even after i shut down the tablet.
    However this is frustrating.
    Maybe you have to sort this out?
    I have seen and other people returning this tablet after having this problem.
    It is not a hardware problem since its working ok before the update.
    Of course tried factory reset twice.
    Hope i dont have this problem again, *but i am informing in hope that you fix this in a future update.*

    Toshiba sent me the fix for this. Figured I would use Facebook and they sorted a solution straight away.
    It requires a complete reset. Not the soft reset from within Android.
    I'll post it here as they will check through moderation I guess.
    Thanks for sending a private message Ben. For us to get this resolved for you we would advise to perform a reset from the Android system recovery menu, to do the reset please follow these steps:
    The reset process will delete any data, settings, and applications on your tablet. You must have a backup of any data you wish to keep before proceeding.
    1. Make sure the tablet is off and not in standby.
    2. Hold down the Volume Up and Power buttons simultaneously until the two Android icons appear.
    3. Use the volume buttons to select the white box on the right.
    4. Once selected, press the power button.
    5. Use the volume buttons to select wipe cache partition and then press the power button.
    6. Select Yes and press the power button.
    7. Use the volume buttons to select wipe data/factory reset and then press the power button.
    8. Select Yes and press the power button.
    9. The tablet will now reset.
    If you have any issues after the reset please get back to us as soon as possible!
    Its been working well ever since. I guess the cache clean part might be the main one. You'll have to select the reboot yourself as I did at the end.
    Might be best to use Facebook i'll see if I can find my post as the response was quick and efficient unlike their responses in here. I.e nowt from them so far.
    They needed my name and serial numbers probably to log problems etc.
    Message was edited by: bensimmo

Maybe you are looking for