Connection to data store on host MYSQL failed

We have observed multiple occurrence of below errors on the 6 App-V servers (default server group).
<ServerName> 3796 9044 SW_ServerAuthenticationTask::Authorize - "Default Provider" <UserID> - 2 41472 "Module execution failed."
<ServerName>nPool::Reconnect - "Default Provider" <UserID> - 2 41543 "Connection to  data store on host MYSQL failed.
APPV Server details:
APPV Server 4.5.3.19480
The issue is been there for some time and we seen these error on the SFT-SERVER log now and then.Though the error is reported in the APP-V log but we have not seen any issue accessing any APPV application during the duration.
Could someone suggest solution to resolve the issue.

Do all your servers face this issue? They are load balanced I suppose?
Check those servers if the App-V management Server service is running and that the firewall doesn't block anything. If that's not the case, try to give the machine account of those servers full control for Share/NTFS on the content-share.
If that does not work, open a ticket with MS.

Similar Messages

  • 703: Subdaemon connect to data store failed with error TT9999

    All,
    I'm getting the following error whilst trying to connect to a TimesTen DB:
    connect "DSN=my_cachedb";
    703: Subdaemon connect to data store failed with error TT9999
    In the tterrors.log:
    16:39:24.71 Warn: : 2568: 3596 ------------------: subdaemon process exited
    16:39:24.71 Warn: : 2568: 3596 exited while connected to data store '/u01/ttdata/datastores/my_cachedb' shm 33554529 count=1
    16:39:24.71 Warn: : 2568: daRecovery: subdaemon 3596, managing data store, failed: invalidate (failcode=202)
    16:39:24.71 Warn: : 2568: Invalidating the data store (failcode 202, recovery for 3596)
    16:39:24.72 Err : : 2568: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc -2 err1 703 err2 9999
    16:39:24.72 Warn: : 2568: 3619 Subdaemon reports creation failure
    16:39:24.72 Err : : 2568: TT14000: TimesTen daemon internal error: Deleting 3619/0x1558650/'/u01/ttdata/datastores/my_cachedb' - from association table - not found
    16:39:24.72 Err : : 2568: TT14004: TimesTen daemon creation failed: Could not del from dbByPid internal table
    16:39:24.81 Warn: : 2568: child process 3596 terminated with signal 11
    16:39:25.09 Err : : 2568: TT14000: TimesTen daemon internal error: daRecovery for 3619: No such data store '/u01/ttdata/datastores/my_cachedb'
    I've checked and the datastore does exist and is owned by the timesten UNIX user.
    ttversion:
    TimesTen Release 11.2.2.2.0 (64 bit Linux/x86_64) (tt1122:53396) 2011-12-23T09:26:28Z
    Instance admin: timesten
    Instance home directory: /home/timesten/TimesTen/tt1122
    Group owner: timesten
    Daemon home directory: /home/timesten/TimesTen/tt1122/info
    PL/SQL enabled.
    Datastore definition from sys.odbc.ini:
    [my_cachedb]
    Driver=/home/timesten/TimesTen/tt1122/lib/libtten.so
    DataStore=/u01/ttdata/datastores/my_cachedb
    LogDir=/u01/ttdata/logs
    PermSize=40
    TempSize=32
    DatabaseCharacterSet=AL32UTF8
    OracleNetServiceName=testdb
    Kernel parameters from sysctl -a:
    kernel.shmmax = 68719476736
    kernel.shmall = 4294967296
    Memory / SWAP:
    MemTotal: 2050784 kB
    SWAP: /dev/mapper/VolGroup00-LogVol01 partition 4095992
    I'm new to TimesTen and I'm planning on evaluationg it to see if it could solve an issue we're having. Any suggestions would be much appreciated.
    Thanks,
    Ian.

    Hi Ian,
    Can you please answer the following / provide the following information:
    1. What are your kernel parameters relating to semaphores set to? Is anything else on the mahcine using significant numbers of semaphores?
    2. Please provide the output of the following shell commands:
    ls -ld /u01
    ls -ld /u01/ttdata
    ls -ld /u01/ttdata/datastores
    ls -ld /u01/ttdata/logs
    3. Please provide an excerpt of the detailed message log (ttmesg.log) between around 16:38 and 16:40 (i.e. from a little while before the problem until after the problem).
    Thanks,
    Chris

  • TtRestoring a Data Store w/ a Large PermSize to a Smaller PermSize

    If have a backup of a data store created by ttBackup. I'd like to restore that data store into a data store with a smaller PermSize. The original data should fit in the new data store. However, I'm encountering errors doing this.
    I've done the following:
    - Ran ttBackup on the source data store.
    - The source data store has a PermSize of 16 Gb, but it's backup file is about 4.5 Gbytes.
    - On the target machine, I created an entry in the odbc.ini for the new data store, but with a PermSize=6144
    - On the target machine, I then run ttIsql target_dsn_name
    - This works okay and ipcs shows a shared memory segment with a size that correlates to the PermSize=6144.
    - Then that data store is ttDestroy'ed to get it out of the way.
    - Next I ran: ttRestore -fname source_dsn_name -connstr "DSN=target_dsn_name;Preallocate=1;PermSize=6144;TempSize=120" -dir . -noconn
    - This succeeds, but only because "-noconn" was specified.
    - When I 1st try to connect to the datastore by running: ttIsql "DSN=target_dsn_name;PermSize=6144;TempSize=120"
    - It fails with the following error:
    836: Cannot create data store shared-memory segment, error 22
    703: Subdaemon connect to data store failed with error TT836
    - The tterror.log contains:
    19:59:05.54 Err : : 3810: TT14000: TimesTen daemon internal error: Error 22 creating shared segment, KEY 0x0401a8b2
    19:59:05.54 Err : : 3810: -- OS reports invalid shared segment size
    19:59:05.54 Err : : 3810: -- Confirm that SHMMAX kernel parameter is set > datastore size
    19:59:05.54 Err : : 3820: subd: Error identified in [sub.c: line 3188]
    19:59:05.54 Err : : 3820: subd: (Error 836): TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9342, procedure "sbDbConnect"
    19:59:05.54 Err : : 3820: file "db.c", lineno 9342, procedure "sbDbConnect"
    19:59:05.54 Warn: : 3820: subd: connect trouble, rc 1, reason 836
    19:59:05.54 Err : : 3820: Err 836: TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9342, procedure "sbDbConnect"
    19:59:05.54 Err : : 3810: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc 400 err1 703 err2 836
    19:59:06.45 Warn: : 3810: 3820 ------------------: subdaemon process exited
    Note that on the target machine total shared memory is configured for only 10 Gb, which is smaller than the size of the original data store.

    Hi Brian,
    ttRestore cannot be used for this purpose. The restored datastroe will always have the PermSize that was in effect when it was backed up. You cannot shrink an existing datastore. If you need to move the tables and data to a store with a smaller PermSize (assuming they will fit of course) then you need to use ttMigrate instead.
    Chris

  • 925: Cannot create data store semaphores (Invalid argument)

    I'm trying to connect to Timesten, but I'm getting this error.
    I have looked at other similar discussions, but yet I could not solve the problem.
    [timesten@atd info]$ ttisql "dsn=tpch"
    Copyright (c) 1996, 2013, Oracle and/or its affiliates. All rights reserved.
    Type ? or "help" for help, type "exit" to quit ttIsql.
    connect "dsn=tpch";
      925: Cannot create data store semaphores (Invalid argument)
      703: Subdaemon connect to data store failed with error TT925
    The command failed.
    Done.
    Here is my information.
    [tpch]
    Driver=/home_sata/timesten/TimesTen/tt1122/lib/libtten.so
    DataStore=/home_sata/timesten/TimesTen/tt1122/tpch/tpch
    LogDir=/home_sata/timesten/TimesTen/tt1122/tpch/logs
    PermSize=1024
    TempSize=512
    PLSQL=1
    DatabaseCharacterSet=US7ASCII
    kernel.sem = 400 32000 512 5029
    kernel.shmmax=68719476736
    kernel.shmall=16777216
    [timesten@atd info]$ cat /proc/meminfo
    MemTotal:       297699764 kB
    MemFree:        96726036 kB
    Buffers:          582996 kB
    Cached:         155831636 kB
    SwapCached:            0 kB
    Active:         115729396 kB
    Inactive:       78767560 kB
    Active(anon):   44040440 kB
    Inactive(anon):  8531544 kB
    Active(file):   71688956 kB
    Inactive(file): 70236016 kB
    Unevictable:           0 kB
    Mlocked:               0 kB
    SwapTotal:      112639992 kB
    SwapFree:       112639992 kB
    Dirty:               160 kB
    Writeback:             0 kB
    AnonPages:      38082348 kB
    Mapped:         15352480 kB
    Shmem:          14489676 kB
    Slab:            3993152 kB
    SReclaimable:    3826768 kB
    SUnreclaim:       166384 kB
    KernelStack:       18344 kB
    PageTables:       245352 kB
    NFS_Unstable:          0 kB
    Bounce:                0 kB
    WritebackTmp:          0 kB
    CommitLimit:    261457104 kB
    Committed_AS:   74033552 kB
    VmallocTotal:   34359738367 kB
    VmallocUsed:      903384 kB
    VmallocChunk:   34205870424 kB
    HardwareCorrupted:     0 kB
    AnonHugePages:  35538944 kB
    HugePages_Total:      32
    HugePages_Free:       32
    HugePages_Rsvd:        0
    HugePages_Surp:        0
    Hugepagesize:       2048 kB
    DirectMap4k:        6384 kB
    DirectMap2M:     2080768 kB
    DirectMap1G:    299892736 kB
    ------ Shared Memory Limits --------
    max number of segments = 4096
    max seg size (kbytes) = 67108864
    max total shared memory (kbytes) = 67108864
    min seg size (bytes) = 1

    The error message suggests that the system is running out of semaphores although plenty seem to be configured:
    kernel.sem = 400 32000 512 5029
    Could it be that there are other programs on this machine as this user using semaphores?
    Have you made changes to the kernel parameters and haven't made them permanent with
    # /sbin/sysctl -p
    or a re-boot?
    If you've done a # /sbin/sysctl -p have you recycled the TT daemon
    $ ttDaemonAdmin -restart
    So TT takes up the new settings?
    Tim

  • Cannot create data store shared-memory segment error

    Hi,
    Here is some background information:
    [ttadmin@timesten-la-p1 ~]$ ttversion
    TimesTen Release 11.2.1.3.0 (64 bit Linux/x86_64) (cmttp1:53388) 2009-08-21T05:34:23Z
    Instance admin: ttadmin
    Instance home directory: /u01/app/ttadmin/TimesTen/cmttp1
    Group owner: ttadmin
    Daemon home directory: /u01/app/ttadmin/TimesTen/cmttp1/info
    PL/SQL enabled.
    [ttadmin@timesten-la-p1 ~]$ uname -a
    Linux timesten-la-p1 2.6.18-164.6.1.el5 #1 SMP Tue Oct 27 11:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
    [root@timesten-la-p1 ~]# cat /proc/sys/kernel/shmmax
    68719476736
    [ttadmin@timesten-la-p1 ~]$ cat /proc/meminfo
    MemTotal: 148426936 kB
    MemFree: 116542072 kB
    Buffers: 465800 kB
    Cached: 30228196 kB
    SwapCached: 0 kB
    Active: 5739276 kB
    Inactive: 25119448 kB
    HighTotal: 0 kB
    HighFree: 0 kB
    LowTotal: 148426936 kB
    LowFree: 116542072 kB
    SwapTotal: 16777208 kB
    SwapFree: 16777208 kB
    Dirty: 60 kB
    Writeback: 0 kB
    AnonPages: 164740 kB
    Mapped: 39188 kB
    Slab: 970548 kB
    PageTables: 10428 kB
    NFS_Unstable: 0 kB
    Bounce: 0 kB
    CommitLimit: 90990676 kB
    Committed_AS: 615028 kB
    VmallocTotal: 34359738367 kB
    VmallocUsed: 274804 kB
    VmallocChunk: 34359462519 kB
    HugePages_Total: 0
    HugePages_Free: 0
    HugePages_Rsvd: 0
    Hugepagesize: 2048 kB
    extract from sys.odbc.ini
    [cachealone2]
    Driver=/u01/app/ttadmin/TimesTen/cmttp1/lib/libtten.so
    DataStore=/u02/timesten/datastore/cachealone2/cachealone2
    PermSize=14336
    OracleNetServiceName=ttdev
    DatabaseCharacterset=WE8ISO8859P1
    ConnectionCharacterSet=WE8ISO8859P1
    [ttadmin@timesten-la-p1 ~]$ grep SwapTotal /proc/meminfo
    SwapTotal: 16777208 kB
    Though we have around 140GB memory available and 65GB on the shmmax, we are unable to increase the PermSize to any thing more than 14GB. When I changed it to PermSize=15359, I am getting following error.
    [ttadmin@timesten-la-p1 ~]$ ttIsql "DSN=cachealone2"
    Copyright (c) 1996-2009, Oracle. All rights reserved.
    Type ? or "help" for help, type "exit" to quit ttIsql.
    connect "DSN=cachealone2";
    836: Cannot create data store shared-memory segment, error 28
    703: Subdaemon connect to data store failed with error TT836
    The command failed.
    Done.
    I am not sure why this is not working, considering we have got 144GB RAM and 64GB shmmax allocated! Any help is much appreciated.
    Regards,
    Raj

    Those parameters look ok for a 100GB shared memory segment. Also check the following:
    ulimit - a mechanism to restrict the amount of system resources a process can consume. Your instance administrator user, the user who installed Oracle TimesTen needs to be allocated enough lockable memory resource to load and lock your Oracle TimesTen shared memory segment.
    This is configured with the memlock entry in the OS file /etc/security/limits.conf for the instance administrator.
    To view the current setting run the OS command
    $ ulimit -l
    and to set it to a value dynamically use
    $ ulimit -l <value>.
    Once changed you need to restart the TimesTen master daemon for the change to be picked up.
    $ ttDaemonAdmin -restart
    Beware sometimes ulimit is set in the instance administrators "~/.bashrc" or "~/.bash_profile" file which can override what's set in /etc/security/limits.conf
    If this is ok then it might be related to Hugepages. If TT is configured to use Hugepages then you need enough Hugepages to accommodate the 100GB shared memory segment. TT is configured for Hugepages if the following entry is in the /u01/app/oracle/EXALYTICS_MWHOME/TimesTen/tt1122/info/ttendaemon.options file:
    -linuxLargePageAlignment 2
    So if configured for Hugepages please see this example of how to set an appropriate Hugepages setting:
    Total the amount of memory required to accommodate your TimesTen database from /u01/app/oracle/EXALYTICS_MWHOME/TimesTen/tt1122/info/sys.odbc.ini
    PermSize+TempSize+LogBufMB+64MB Overhead
    For example consider a TimesTen database of size:
    PermSize=250000 (unit is MB)
    TempSize=100000
    LogBufMB=1024
    Total Memory = 250000+100000+1024+64 = 351088MB
    The Hugepages pagesize on the Exalytics machine is 2048KB or 2MB. Therefore divide the total amount of memory required above in MB by the pagesize of 2MB. This is now the number of Hugepages you need to configure.
    351088/2 = 175544
    As user root edit the /etc/sysctl.conf file
    Add/modify vm.nr_hugepages= to be the number of Hugepages calculated.
    vm.nr_hugepages=175544
    Add/modify vm.hugetlb_shm_group = 600
    This parameter is the group id of the TimesTen instance administrator. In the Exalytics system this is oracle. Determine the group id while logged in as oracle with the following command. In this example it’s 600.
    $ id
    $ uid=700(oracle) gid=600(oinstall) groups=600(oinstall),601(dba),700(oracle)
    As user root edit the /etc/security/limits.conf file
    Add/modify the oracle memlock entries so that the fourth field equals the total amount of memory for your TimesTen database. The unit for this value is KB. For example this would be 351088*1024=359514112KB
    oracle hard memlock 359514112
    oracle soft memlock 359514112
    THIS IS VERY IMPORTANT in order for the above changes to take effect you to either shutdown the BI software environment including TimesTen and reboot or issue the following OS command to make the changes permanent.
    $ sysctl -p
    Please note that dynamic setting (including using 'sysctl -p') of vm.nr_hugepages while the system is up may not give you the full number of Hugepages that you have specified. The only guaranteed way to get the full complement of Hugepages is to reboot.
    Check Hugepages has been setup correctly, look for Hugepages_Total
    $ cat /proc/meminfo | grep Huge
    Based on the example values above you would see the following:
    HugePages_Total: 175544
    HugePages_Free: 175544

  • 836: Cannot create data store shared-memory segment, error 22

    Hi,
    I am hoping that there is an active TimesTen user community out there who could help with this, or the TimesTen support team who hopefully monitor this forum.
    I am currently evaluating TimesTen for a global investment organisation. We currently have a large Datawarehouse, where we utilise summary views and query rewrite, but have isolated some data that we would like to store in memory, and then be able to
    report on it through a J2EE website.
    We are evaluating TimesTen versus developing our own custom cache. Obviously, we would like to go with a packaged solution but we need to ensure that there are no limits in relation to maximum size. Looking through the documentation, it appears that the
    only limit on a 64bit system is the actual physical memory on the box. Sounds good, but we want to prove it since we would like to see how the application scales when we store about 30gb (the limit on our UAT environment is 32gb). The ultimate goal is to
    see if we can store about 50-60gb in memory.
    Is this correct? Or are there any caveats in relation to this?
    We have been able to get our Data Store store 8gb of data, but want to increase this. I am assuming that the following error message is due to us not changing the /etc/system on the box:
         836: Cannot create data store shared-memory segment, error 22
         703: Subdaemon connect to data store failed with error TT836
    Can somebody from the User community, or an Oracle Times Ten support person recommend what should be changed above to fully utilise the 32gb of memory, and the 12 processors on the box.
    Its quite a big deal for us to bounce the UAT unix box, so l want to be sure that l have factored in all changes that would ensure the following:
    * Existing Oracle Database instances are not adversely impacted
    * We are able to create a Data Store which is able fully utilise the physical memory on the box
    * We don't need to change these settings for quite some time, and still be able to complete our evaluation
    We are currently in discussion with our in-house Oracle team, but need to complete this process before contacting Oracle directly, but help with the above request would help speed this process up.
    The current /etc/system settings are below, and l have put in the current machines settings as comments at the end of each line.
    Can you please provide the recommended settings to fully utilise the existing 32gb on the box?
    Machine
    ## I have contrasted the minimum prerequisites for TimesTen and then contrasted it with the machine's current settings:
    SunOS uatmachinename 5.9 Generic_118558-11 sun4us sparc FJSV,GPUZC-M
    FJSV,SPARC64-V
    System Configuration: Sun Microsystems sun4us
    Memory size: 32768 Megabytes
    12 processors
    /etc/system
    set rlim_fd_max = 1080                # Not set on the machine
    set rlim_fd_cur=4096               # Not set on the machine
    set rlim_fd_max=4096                # Not set on the machine
    set semsys:seminfo_semmni = 20           # machine has 0x42, Decimal = 66
    set semsys:seminfo_semmsl = 512      # machine has 0x81, Decimal = 129
    set semsys:seminfo_semmns = 10240      # machine has 0x2101, Decimal = 8449
    set semsys:seminfo_semmnu = 10240      # machine has 0x2101, Decimal = 8449
    set shmsys:shminfo_shmseg=12           # machine has 1024
    set shmsys:shminfo_shmmax = 0x20000000     # machine has 8,589,934,590. The hexidecimal translates into 536,870,912
    $ /usr/sbin/sysdef | grep -i sem
    sys/sparcv9/semsys
    sys/semsys
    * IPC Semaphores
    66 semaphore identifiers (SEMMNI)
    8449 semaphores in system (SEMMNS)
    8449 undo structures in system (SEMMNU)
    129 max semaphores per id (SEMMSL)
    100 max operations per semop call (SEMOPM)
    1024 max undo entries per process (SEMUME)
    32767 semaphore maximum value (SEMVMX)
    16384 adjust on exit max value (SEMAEM)

    Hi,
    I work for Oracle in the UK and I manage the TimesTen pre-sales support team for EMEA.
    Your main problem here is that the value for shmsys:shminfo_shmmax in /etc/system is currently set to 8 Gb therby limiting the maximum size of a single shared memory segment (and hence Timesten datastore) to 8 Gb. You need to increase this to a suitable value (maybe 32 Gb in your case). While you are doing that it would be advisable to increase ny of the other kernel parameters that are currently lower than recommended up to the recommended values. There is no harm in increasing them other possibly than a tiny increase in kernel resources, but with 32 GB of RAM I don't think you need be concerned about that...
    You should also be sure that the system has enough swap space configured to supprt a shared memory segment of this size. I would recommend that you have at least 48 GB of swap configured.
    TimesTen should detect that you have a multi-CPU machine and adjust its behaviour accordingly but if you want to be absolutely sure you can set SMPOptLevel=1 in the ODBC settings for the datastore.
    If you want more direct assistance with your evaluation going forward then please let me know and I will contact you directly. Of course, you are free to continue using this forum if you would prefer.
    Regards, Chris

  • ISE Alarm : Warning : Session directory write failed : [TimesTen][TimesTen 11.2.2.2.0 ODBC Driver][TimesTen]TT0846: Data store connection invalid or not current -- file "dbAPI.c"; lineno 7475; procedure "sb_connLatchAcquire"

    I got this message about 20 times:
    Log Collection Error
    Details :
    Session directory write failed : [TimesTen][TimesTen 11.2.2.2.0 ODBC Driver][TimesTen]TT0846: Data store connection invalid or not current -- file "dbAPI.c"; lineno 7475; procedure "sb_connLatchAcquire"
    Description :
    The ISE M&T collector process is unable to persist the audit logs generated from the Policy Service nodes
    Suggested Actions :
    This will not impact the actual functionality of the Policy Service nodes, Please contact TAC"
    It started after I've added a third DNS Server and did not reboot the whole appliance, but just all services....
    Does anyone know what really might triggered this? After rebooting ISE everything was ok again. But I couldn't find anything in ISE's logs
    KR

    I did a reboot and the problem was solved. I got the message when I tried to stop ISE while all services were just about to get up.
    ISE Version: 1.2.0.899

  • I have a MacBook and cannot connect to App Store. I have no problem with the internet connection. I want to be able to buy the apps that are available for my computer. The date, time and location are all correct - all the suggestions have failed

    I have a MacBook - I am unable to connect to App Store - I have no problems using the internet to connect to anything else. I have checked out all the suggestions - Apple Preference and time, date, location etc. they are all correct. I cannot think what else I should do. Any suggestions please Cynthiafromgrayshott.

    If you don't see any messages, not have anti-malware running or the Firewall on, try installing the Mac OS X 10.6.8 Update Combo
    It's ok to do this even though you are already running v10.6.8 (according to your profile).
    Restart your Mac after the combo in installed, try the App Store.
    Also... if you have an app called Little Snitch installed, that can prevent a connection to the App Store.

  • Can not connect  to host  where the data base is hosted

    sql.free.fr is where the data base is hosted
    String host = "jdbc:mysql://sql.free.fr/
    her's the code
    public f()
    String pilote = "org.gjt.mm.mysql.Driver";
    String host = "jdbc:mysql://sql.free.fr/";
    String login = "login";
    String pw = "password";
    setTitle("Programmation avanc�e Java II (NicoWatt)");
    setSize(x,y);
    setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
    show();
    TM = new TMFromMysql(pilote,host,login,pw,"select * from TCar");
    JTable T = new JTable(TM);
    JScrollPane JSP = new JScrollPane(T);
    JSP.setPreferredSize(new Dimension(x,y));
    getContentPane().add(JSP,BorderLayout.CENTER);
    pack();
    }

    Basic network debugging:
    1. Try to ping the server; at the command line, type "ping sql.free.fr" and see what happens.
    If that fails then you have a network connectivity problem. Talk to the person who controls your network (the point where you connect to the Internet) and discuss it.
    2. Try to connect to the server at the same port that MySQL is using (normally 3306 but confirm that with the people running it); at the command line, type "telnet sql.free.fr 3306" and see if you get a connection.
    If that fails, then again you have a problem. Again discuss this with your network person. There are several reasons why these may fail (proxy servers, firewalls, and so on) and you will get better answers from people who know about the network then from random strangers on the Internet.

  • Java.sql.SQLException: The TCP/IP connection to the host  has failed.

    Hello. I hope you had a happy new year! Now its back to work.
    I am having a problem connecting to a remote SQL Server DB. I am using NetBeans 5.5 and the latest J2EE. I am able to see the tables in the IDE and bind objects to data. But when I run it it gets this:
    java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: no further information
    at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:100)
    at com.sun.sql.rowset.internal.CachedRowSetXReader.connect(CachedRowSetXReader.java:344)
    at com.sun.sql.rowset.internal.CachedRowSetXReader.readData(CachedRowSetXReader.java:126)
    at com.sun.sql.rowset.CachedRowSetXImpl.execute(CachedRowSetXImpl.java:968)
    at com.sun.sql.rowset.CachedRowSetXImpl.execute(CachedRowSetXImpl.java:1428)
    I checked the SQL Server Configuration manager on that machine and TCP/IP connections are allowed. What else could be wrong?
    Thank You.

    "Connection refused" means that the client sends a packet saying "I would like to connect to port number NNNN please" to the server computer, and the server computer's OS sends the reply "there is no process listening to that port on the network interface you are using".
    The database server is not running, or running but not listening to TCP/IP connections, or at a different port from what you think, or listening to only selected network interfaces (it is possible for a process to listen to a specific interface or a wildcard for all interfaces). A less likely scenario is that a firewall is sending the "connection refused" message.
    First aid check list for "connection refused":
    - Check host name in connect string.
    - Check port number in connect string.
    - Try numeric IP address of server host in connect string, in case name server is hosed.
    - Are there any firewalls between client and server blocking the port.
    - Check that the db server is running.
    - Check that the db server is listening to the port. On the server, try: "telnet localhost the-port-number". Or "netstat -an", there should be a listening entry for the port. You need to configure the database to accept TCP connections; the server documentation or google should explain how.
    - Try "telnet server-host-name the-port-number" from the client, to see if firewalls are blocking it.
    - If "telnet" fails: try telnet with the numeric ip address.
    - If "telnet" fails: does it fail immediately or after an obvious timeout? How long is the timeout?
    - Does the server respond to "ping serverhost" or "telnet serverhost" or "ssh serverhost"?

  • PowerView: Failed to Close connection for data source 'EntityDataSource'

    Hi All,
    I am using SharePoint 2013 and SQL Server 2012 SP1 PowerView. PowerView reports are created from PowerPivot workbooks hosted on the SharePoint 2013 BI Site. The PowerView report runs fine most of the times but when I interact heavily (click different slicers,
    filters, charts)with the report, all of the charts or one of the charts will grey out showing no data at all while it should actually show data. The error message which pops out is in the screenshot below:
    To solve the issue. we either click on any slicer, filter on the PowerView report or refresh the IE webpage. This restores the connection and it will be active again.  Can someone please let us know the fix to this?
    Thanks, Ashish Singh

    Hi Ashish,
    The error message "Failed to close connection for data sourcee 'EntityDataSource'" doesn't give much useful information. To get more detail error message, I suggest that you turn on the Reporting Services events for the SharePoint trace log (ULS) and
    post the complete error message in the verbose ULS Log. To do this, please see the document:
    http://technet.microsoft.com/en-us/library/ff487871.aspx.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click here
    Mike Yin
    TechNet Community Support

  • Connecting to AOP data store with multiple NIC's

    I have a situation where I need to have the computer running Diadem to be connected to two different networks.  I have two NIC's installed in the machine, NIC A and NIC B, we will call them.  The reason for this, is that I am using Diadem to access an AOP server on an AVL PUMA machine.  If I connect PUMA to the LAN, PUMA occasionally crashes, probably something to do with the IP address.  So, PUMA needs to be on a network that does not have a router.  My diadem computer needs to communicate with PUMA, and with the local shared drives on our company network.
    Anyway, I have the company LAN hooked up on NIC A, and the PUMA network hooked up on NIC B.  Diadem fails to connect when both networks are connected, but connects to the data store no problem when only the PUMA network is hooked up. Any ideas how to fix this?  It seems diadem is looking at NIC A instead of NIC B, like it should be. 
    For reference, when both NIC's are hooked up, I can access share drives, and ping computers on both separate networks, without a problem, so it's not a connection issue.
    Any help would be appreciated.
    -Russ
    Solved!
    Go to Solution.

    I assume poth NIC have different IP range.
    - Did you use IP instead of server name.
    - Do you use RPC or CORBA to access the PUMA server?
    - Which DIAdem version.
    Can you create a logfile when the connection fails?
    Greetings
    Andreas

  • Connect "Generic Data Source" target to a MySQL instance

    I'm trying to connect our TEO (2.2) instance to a MySQL instance, but unable to do so successfully.
    On the TEO server, I've loaded the MySQL provider as well as the ODBC driver.
    I then try to define the connection details in the new target:
    Hostname: <hostname of the server hosting MySQL>
    Default user: <runtime user for the read-only account to the database>
    Connection String: Provider=MySQLProv;Data Source=<database name>
    Clicking "OK" throws the following error: "The 'MySQLProv' provider is not registered on the local machine."
    Based on the error, it feels to me like the TEO server doesn't recognize that provider, but I'd like some help on getting it to the point where it does.
    Could you please provide me with the steps needed to get our TEO instance to connect to the DB?
    Thanks,
    Mark
    Solution:
    1) Install the provider from Cherry City Software : http://cherrycitysoftware.com/CCS/Providers/ProvMySQL.aspx
    2) Configure the connection string as follows: Provider=OleMySql.MySqlSource.1;Data Source=<FQDN of DB host>;Initial Catalog=<DB name>
    Thank you very much C Roberts!

    The connection string shows "MySQLProv", is that what you actually used?
    Looking at the sample C# code(and VB.net) I see this as the provider:
    OleMySql.MySqlSource.1
    Did you try that?
    Also it looks like
    Data Source=
    Initial Catalog=
    If you cannot get by this, would probably be best to open a TAC case for review.

  • TT0846: Data store connection invalid or not current

    In one of our environments we started getting TT0846 error randomly.
    Everytime we get this error we have to restart our application to reconnect to datasore.
    When we checked the error logs, we found the following:
    08:32:00.56 Err : : 20084: 20089/0x198ede80: XXX: fstat returned with info uid=670 gid=673 mode=drwxr-xr-x size=12288
    08:32:00.56 Err : : 20084: 20089/0x198ede80: XXX: fstat returned with info uid=670 gid=673 mode=-rw------- size=0
    08:32:00.56 Err : : 20084: 20089/0x198ede80: Log flusher encountered error 906: TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2031, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate". fslsn = 2031.0, disklsn = 2030.534409216, ckptInfo.existLFN = 2028, newestlfn = 2030.
    08:32:01.56 Err : : 20084: 20089/0x198ede80: Log flusher reports success: previously-reported error 906 (TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2031, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate") no longer pending.
    08:40:01.67 Err : : 20084: 20089/0x198ede80: XXX: Dbhdr group: dba Logpath:/mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2032
    08:40:01.67 Err : : 20084: 20089/0x198ede80: XXX: fstat returned with info uid=670 gid=673 mode=drwxr-xr-x size=12288
    08:40:01.67 Err : : 20084: 20089/0x198ede80: XXX: fstat returned with info uid=670 gid=673 mode=-rw------- size=0
    08:40:01.67 Err : : 20084: 20089/0x198ede80: Log flusher encountered error 906: TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2032, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate". fslsn = 2032.0, disklsn = 2031.536557568, ckptInfo.existLFN = 2030, newestlfn = 2031.
    08:40:01.67 Err : REP: 26549: UAT_DSN_DS:misc.c(247): TT16046: Failed to force log
    08:40:01.67 Err : REP: 26549: UAT_DSN_DS:misc.c(247): TT722: TT0722: Log flusher reports error 906 (TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2032, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate") -- file "logflusher.c", lineno 6136, procedure "sbLogBufOSErrorPush"
    08:40:01.67 Err : REP: 26549: UAT_DSN_DS:receiver.c(1241): TT16160: Failed to flush log records. Replication Agent exiting; but will be restarted by TimesTen daemon
    08:40:01.75 Warn: REP: 26549: UAT_DSN_DS:receiver.c(2870): TT16060: Failed to read data from the network. TimesTen replication agent is stopping
    08:40:02.68 Err : : 20084: 20089/0x198ede80: Log flusher reports success: previously-reported error 906 (TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2032, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate") no longer pending.
    08:40:02.91 Err : : 20084: repagent says it has failed to start: Failed to flush log records. Replication Agent exiting; but will be restarted by TimesTen daemon
    08:48:02.62 Err : : 20084: 20089/0x198ede80: XXX: Dbhdr group: dba Logpath:/mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2033
    08:48:02.62 Err : : 20084: 20089/0x198ede80: XXX: fstat returned with info uid=670 gid=673 mode=drwxr-xr-x size=12288
    08:48:02.62 Err : : 20084: 20089/0x198ede80: XXX: fstat returned with info uid=670 gid=673 mode=-rw------- size=0
    08:48:02.62 Err : : 20084: 20089/0x198ede80: Log flusher encountered error 906: TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2033, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate". fslsn = 2033.0, disklsn = 2032.534587392, ckptInfo.existLFN = 2031, newestlfn = 2032.
    08:48:02.62 Err : : 20084: 20428/0x2aac1c17e850: sbXactCommit: Unable to sync log to disk. Errors/warnings follow.
    08:48:02.62 Err : : 20084: 20428/0x2aac1c17e850: TT0722: Log flusher reports error 906 (TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2033, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate") -- file "logflusher.c", lineno 6136, procedure "sbLogBufOSErrorPush"
    08:48:02.62 Err : : 20084: 20428/0x2aac1c17e850: *** 20428: (Error 722): TT0722: Log flusher reports error 906 (TT0906: Cannot change mode on log file /mtsuatlog/timesten/UAT_DSN_logdir/UAT_DSN_ds.log2033, error Operation not permitted -- file "logfile.c", lineno 813, procedure "sbLogFileCreate") -- file "logflusher.c", lineno 6136, procedure "sbLogBufOSErrorPush"
    08:48:02.62 Err : : 20084: 20428/0x2aac1c17e850: *** 20428: -- file "logflusher.c", lineno 6136, procedure "sbLogBufOSErrorPush"
    08:48:02.63 Err : : 20084: 20428/0x2aac1c17e850: Data store marked invalid [xact.c:/st_timesten_11.2.1/3:sbXactCommit:6597] PID 20428 (timestenorad) CONN 13 (Refresher(S,60000)) Context 0x2aac1c17e850
    08:48:03.57 Warn: : 20084: 2649/0x40b2590: Forced Disconnect /timesten/UAT_DSN_datastore/UAT_DSN_ds
    08:48:03.57 Warn: : 20089: Stopping subdaemon HistGC thread for /timesten/UAT_DSN_datastore/UAT_DSN_ds because db is invalid.
    08:48:03.57 Warn: : 20089: subd not sending crs notification, no valid socket
    08:48:03.57 Warn: : 20089: Stopping subdaemon Log Marker thread for /timesten/UAT_DSN_datastore/UAT_DSN_ds because db is invalid.
    08:48:03.57 Warn: : 20089: subd not sending crs notification, no valid socket
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:transmitter.c(9660): TT16127: Failed to read transaction logs
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:transmitter.c(9660): TT994: TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 9656, procedure "sb_dbLogReadQ"
    08:48:03.57 Warn: : 20084: 2649/0x3f58850: Forced Disconnect /timesten/UAT_DSN_datastore/UAT_DSN_ds
    08:48:03.57 Warn: : 20084: 2649 ----------: Disconnecting from an old instance
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:meta.c(604): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by TimesTen daemon (depending on restart policy)
    08:48:03.57 Warn: REP: 2649: UAT_DSN_DS:receiver.c(2870): TT16060: Failed to read data from the network. TimesTen replication agent is stopping
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:repagent.c(1237): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by TimesTen daemon (depending on restart policy)
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:misc.c(247): TT16046: Failed to force log
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:repagent.c(3364): TT16005: Failed to disconnect from datastore '/timesten/UAT_DSN_datastore/UAT_DSN_ds' for 'TRANSMITTER' thread
    08:48:03.57 Warn: : 20084: 20089/0x19901490: Forced Disconnect /timesten/UAT_DSN_datastore/UAT_DSN_ds
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:misc.c(247): TT994: TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 5166, procedure "sb_dbLogFlush"
    08:48:03.57 Warn: : 20084: 20089 ----------: Disconnecting from an old instance
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:repagent.c(3364): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3178, procedure "sb_dbDisconnect()"
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:repagent.c(1237): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by TimesTen daemon (depending on restart policy)
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:repagent.c(3364): TT16005: Failed to disconnect from datastore '/timesten/UAT_DSN_datastore/UAT_DSN_ds' for 'LOGFORCE' thread
    08:48:03.57 Err : REP: 2649: UAT_DSN_DS:repagent.c(3364): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3178, procedure "sb_dbDisconnect()"
    08:48:03.57 Warn: : 20084: 20089/0x19914aa0: Forced Disconnect /timesten/UAT_DSN_datastore/UAT_DSN_ds
    08:48:03.57 Warn: : 20084: 20089 ----------: Disconnecting from an old instance
    What I could gather from this is that Replication agent tried to change permissions of transaction logs and was unable to and the datastore was marked invalid and disconnected.
    But I have not been able to find a reason for this error occurring, the environment has not been touched, there have been changes made to database objects but can they lead to this error.
    If not, what is causing the error and how can we resolve it.
    Thanks, your help is much appreciated.

    You have a permission problem. For some reason your logfiles have the owner/group 'timesten:timesten' but based on the information from ttVersion and from the permissions on the checkpoint file they should be 'timesten:db'a. Also, the permissions shoiuld be rw-rw---- but they are set to rw-------. There could be several reasons for this, the most likely are:
    1. Incorrect permissions set on the directory that holds the transaction log files.
    2. TimesTen daemon processes running with incorrect userid/group.
    3. Instance administrator user (timesten) no longer has group membership of the protection group (dba).
    For (1), this would be 'user error'. For (2) and (3), this could only happen if permissions on TimesTen install files have been manually changed (something that should not be done without a very clear understanding of how the permissiosn need to be set) or the uid/gid for the instance administrator user has been changed at the O/S level after installing TimesTen or the 'timesten' user has been removed from the 'dba' group.
    I would suggest that you check all these and see what may have been done at the O/S level.
    Chris

  • ERROR: Unable to connect to any of the specified MySQL hosts.

    Hi all, 
    I have run into an issue and not able to resolve it. 
    There was a requirement to connecting to a MySQL data source. For that I unknowingly added an entry in the "ODBC Data Source Administrator" ->
    User DSN & System DSN 
    I was totally unaware that I am breaking my SP setup (Development). Now Central Admin site and all other sites have stopped working. 
    I tried repairing by re-running the config wizard but no use. Error I get is "An unexpected error has occurred." OR "Unable to connect to any of the specified MySQL hosts." 
    But when I try accessing other site, its showing an error from the "machine.config" file: >
    Line 284: <siteMap>
    Line 285: <providers>
    Line 286: <add name="MySqlSiteMapProvider" type="MySql.Web.SiteMap.MySqlSiteMapProvider, MySql.Web, Version=6.9.6.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" connectionStringName="LocalMySqlServer" applicationName="/" />
    Line 287: </providers>
    Line 288: </siteMap>
    Source File: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config 
    For record, I have already removed those entries from that User DSN & System DSN.
    Still error persists. 
    If some has ANY IDEA how to resolve it... please help! 
    Regards, Nayan

    Can you give us a description of what is happening? Errors form the Application and System Event Log, and/or ULS logs?
    Trevor Seward
    Follow or contact me at...
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Maybe you are looking for