Folders being closed upon connection loss?

The issue is that previously it would bring up an error saying that connection was lost and would still show the folders but without any contents, and it would've been possible to do a refresh when you'd have a connection, now it instantly brings to Network folder.
Update:
Previously before the OS reinstall, I've tested what's causing the CPU usage to go up so high using ProcessExplorer, and found out that explorer.exe is using too much services/libraries, mainly ntdll.dll, which is being looped constantly, i.o. ntdll.dll would be copied and copied and copied until you'd restart the process (explorer.exe) 

Hello,I'm currently having an issue with a user that is often on the road and obviously it's often that connection is being lost. That person often opens a lot of folders that we have on our local file server, and as soon as his connection is lost it brings him to the "Network" folder. Any idea what could be the issue? Also CPU would rise up to a %100 in total (File explorer .exe consuming approx. 40-60% because explorer.exe has a looping ntdll.dll library being looped in its process).He uses a Dell XPS 13 ultrabook with a four core i7 processor.Before connection loss:After connection loss:
OS: 8.1 Pro (Latest updates)File server, DC&AD: Win Server 2012 R2, Folder share.
What has been tried:sfc /scannowOS reinstall
This topic first appeared in the Spiceworks Community

Similar Messages

  • How to prevent a TCP connection being closed when the VI that opened it finishes.

    Hello everyone.
    I am developing an application based around servers and clients communicating over TCP in LabVIEW 2012.
    When the server/client opens a TCP connection ,it launches an asynchronosly running "connection handler", to which it passes the connection reference which then takes over all the communcation. This all works fine.
    However - I have a situation where a client's connection handler can be informed of another "new" server. I would like it to open the connection (to see if it is still valid) and then pass this connection reference back to the client's main code to spawn a new connection handler. This prevents me locking up the Client's main code with a long-ish timeout if the "new" server is not actually accepting connections.
    The issue is that if the connection handler that opened up the connection to the "new" server is stopped, then it appears to destroy the reference that it opened. This means that the other connection handler that was merrily communcating with the "new" server has its TCP communciations closed (I get an Error code 1 on a write).
    I have created an example to demonstrate the issue which should be used as follows:
    1. Run server.vi - it will listen for a connection on the port specifed on its BD.
    2. Run CH Launcher.vi - it will open a connection to the server and pass the TCP reference to an instance of Connection Handler.vi which it launches.
    3. The Connection Handler should send data to the Server
    4. Stop the CH Launcher.vi
    5. The Connection Handler.vi will error.
    Any suggestions would be much appreciated.
    Cheers
    John
    Solved!
    Go to Solution.
    Attachments:
    TCP Test.zip ‏35 KB

    John_Neutron escreveu:
    In my case I have changes the part of the code that opens the TCP connection to a VI that has the same lifetime as the main VI so that any connections that have been opened will only be closed automatically when the main VI stops.
    And what are the effects? You are still facing the same problem or closing the connection only when the whole applicaton stops solved your problem?
    Regards
    Mondoni

  • LDAP connections not being closed

    Hi,
    I am trying to authenticate against a Netscape LDAP server and it works fine for 2 out of the 3 cases I am testing against.
    The first case is authenticating with the correct username and correct password. In this case the user is authenticated and the connection is closed.
    In the second case, I try to authenticate with the correct username and a wrong password. The authentication fails and an AuthenticationException is thrown. The connection is closed.
    In the third case, where I have the PROBLEM is if I provide a wrong username, AuthenticationException is thrown indicating that such an username does not exist. But the CONNECTION IS NOT CLOSED.
    Following is the code :
         private boolean authenticate(String userName, String password) throws Exception {
              Hashtable env = new Hashtable(11);
              env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
              env.put("com.sun.jndi.ldap.connect.pool", "false");
              env.put(Context.SECURITY_AUTHENTICATION, "simple");
              env.put(Context.SECURITY_PROTOCOL, "ssl");
              env.put(Context.SECURITY_PRINCIPAL, getSecurityPrincipal(userName));
              env.put(Context.SECURITY_CREDENTIALS, password);
              env.put(Context.PROVIDER_URL,"ldap://ldap05.nike.com:11003");
              DirContext ctx = null;
              try {
                   // Create initial context
                   ctx = new InitialDirContext(env);
                   return true;
              } catch (AuthenticationException e) {
                   log.error(e.getMessage());
              } catch (NamingException e) {
                   log.error("The user could not be validated on LDAP server due to :" + e.getMessage());
              } finally {
                   if (ctx != null) {
                        ctx.close();
              return false;
         }Any help is appreciated.
    Thanks in Advance.

    I did run the NETSTAT command and found some interesting things.
    I ran it for the three cases. The first case is running netstat immediately after authenticating the user with VALID credentials. The status of the connection is TIME_WAIT which is the desired behaviour.
    In the second case, when trying to authenticate with CORRECT username but a wrong password, an AuthenticationException is thrown. When I run the netstat command, the connection is in TIME_WAIT state which is the desired one.
    In the third case, when I provide a wrong username, an AuthenticationException is thrown. When I run the netstat command, the connection is in ESTABLISHED state, which it should not be in.
    An authenticationException is thrown for wrong username and also for wrong password. But the connection is closed for wrong password, but not for wrong username.This is what seems to me as a weird behaviour.
    I was under the impression that in the CODE I mentioned at the begining of this topic, the INITIALDIRCONTEXT had the responsibility of closing the connection when authentication fails as we don't have a handle to close it. It is doing so in the case of ERROR 49 which is wrong password, but not in the case of ERROR 32 which is wrong username. Correct me if I am wrong, but doesn't it seem to be a bug with the INITIALDIRCONTEXT class.
    Thanks.

  • Connection loss SUM GUI to SL Controller

    Hi experts,
    I am experiencing an issue that I need to resolve. It is that I lose the connection from SUM GUI (locally) to the SL Controller running on the remote server.
    Currently I am doing an upgrade and after some time, e.g. when I have an error and don't notice it immediately, I get a warning message.
    "The connection to the SL Controller is down.
    The SDT GUI will reestablish the connection, when possible."
    On the server I get the following error message:
    May 26, 2014 7:49:47 AM [Error]: com.sap.sdt.engine.core.communication.FactoryAlreadyRegisteredException: Factory for key 'com.sap.sdt.engine.core.com
    munication.FactoryKey@13c2c5f4' is already registered.
    May 26, 2014 7:49:47 AM [Error]: com.sap.sdt.engine.core.communication.FactoryAlreadyRegisteredException: Factory for key 'com.sap.sdt.engine.core.com
    munication.FactoryKey@13c2c5f4' is already registered.
    May 26, 2014 7:49:47 AM [Error]: com.sap.sdt.server.core.ServerException
    May 26, 2014 7:49:51 AM [Warning]: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    May 26, 2014 7:49:51 AM [Warning]: Error while closing connection.
    May 26, 2014 7:49:51 AM [Error]: com.sap.sdt.engine.core.communication.SendException: Error while sending data.
    Network input/output exception has occurred: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    java.net.SocketException: Broken pipe
    May 26, 2014 7:49:51 AM [Error]: com.sap.sdt.engine.core.communication.SendException: Error while sending data.
    Network input/output exception has occurred: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
    java.net.SocketException: Broken pipe
    My current assumption is that the firewall drops the connection due to inactivity.
    The main issue then is:
    although I restart my local SUM GUI and reconnect to the server I can't continue the upgrade because the Buttons are "unclickable" (grey).
    Currently I always had to restart SUM including the services on ther server (SL controller).
    My question is:
    what can I do to avoid this connection loss?
    Is there a option to set a "keep alive" to the network connection?
    so that the firewall does not validate the connection as idle and drops?
    Unfortunately we can't do much about the firewall settings due to security restrictions.
    I would be glad to hear from you.
    Kind regards,
    Niklas

    Hi Mathias,
    I got an answer from SAP. There is no option that can be executed with STARTUP to solve this.
    I already proposed to forward this request to the dev team at SAP
    What I am currently doing is:
    Start the GUI and keep it open only if I know if there is are Actions coming next, otherwise I close it (only the GUI) and when some time has passed by I logon again to check.
    This is a really bad solution, but currently the only one.
    Regards,
    Niklas

  • Trying to detect connection loss

    I have built a little telnet program which is specialized for a specific telnet supporting server... Everything works just fine except for detecting connection loss...
    I am connected to the server using java.net.Socket, data is sent using java.io.PrintStream and data is received using java.io.InputStream...
    I have tried having a thread running and looking if the Socket was still connected, but even after closing the server, the Socket keeps returning true when I call Socket.isConnected()... How could I detect the moment when a connection is broken, would it be because the user has a modem connection and gets disconnected or because the server shuts down or any other such reason?

    You can detect a dead socket when a write to it fails.
    So, you could periodically send "keep alive" messages
    to know approximately when it drops.Okay, I had noticed that the PrintStream would set it's error state to true when I try to send a message and the socket is dead, but I hoped I didn't have to wait until that moment... Thanks though! You confirmed me I'll have to do it that way :P

  • Closing data connection

    My program connects to a SQL database that I connect to on port 23 because outgoing connections to port 3306 are blocked from work.
    In my Database class I have this:
    public static Connection sqlConnection ()
            Connection connection = null;
            String serverName = null;
            String mydatabase = null;
            String url = null;
            String dbuser = null;
            String dbpass = null;
            String port = "23";
            try
                System.out.println ("Trying port " + port + "...");
                String driverName = "com.mysql.jdbc.Driver";
                Class.forName (driverName);
                serverName = "server_address";
                mydatabase = "database";
                url = "jdbc:mysql://" + serverName + ":" + port +  "/" + mydatabase;
                //url = "jdbc:mysql://" + serverName + "/" + mydatabase; // a JDBC url
                dbuser = "user";
                dbpass = "pass";
                connection = DriverManager.getConnection (url, dbuser, dbpass);
            catch (SQLException e)
                // Could not connect to the database
                JOptionPane.showMessageDialog (null,"<b>Unable to connect to the database.</b>\n\nPlease check your network connection."
                        + "Contact the administrator if the problem persists.", "Connection Error",
                        JOptionPane.ERROR_MESSAGE);
                System.out.println ("Error: " + e.getMessage ());
            catch (ClassNotFoundException e)
                // Could not find the database driver
                System.out.println ("Error: " + e.getMessage ());
                JOptionPane.showMessageDialog (null,"Could not find the database driver.", "Connection Error",
                        JOptionPane.ERROR_MESSAGE);
            return connection;
        }From my other classes I call the connection by using:
    Connection connection = Database.sqlConnection ();and close my connection with:
    connection.close (); System.out.println ("Connection closed.");This way in my console I can see when the connection is opening and closing.
    run:
    java.awt.Dimension[width=0,height=0]
    Trying port 23...
    6
    Tristan Lee
    [email protected]
    1
    2
    0
    2
    0
    Connection closed.
    Trying port 23...
    Connection closed.
    Trying port 23...
    Connection closed.
    Trying port 23...
    Connection closed.
    Trying port 23...
    Connection closed.When I use netstat to view my current connections, they still show a connection that, to me, looks like a connection that's staying open until it simply times out.
    [tristan@tristan ~]$ netstat
    Active Internet connections (w/o servers)
    Proto Recv-Q Send-Q Local Address               Foreign Address             State
    tcp        0    115 192.168.1.110:59820         205.188.9.53:aol            ESTABLISHED
    tcp        0      0 192.168.1.110:39436         64.12.31.96:aol             ESTABLISHED
    tcp        0    280 192.168.1.110:60949         cs8.msg.dcn.yahoo.com:mmcc  ESTABLISHED
    tcp        0     70 192.168.1.110:40097         by1msg5276706.phx.gbl:msnp  ESTABLISHED
    tcp        0      0 192.168.1.110:49336         oam-m07b.blue.aol.com:aol   ESTABLISHED
    tcp        0      0 ::ffff:192.168.1.110:43641  cpe-24-95-42-77.colu:telnet TIME_WAIT
    tcp        0      0 ::ffff:192.168.1.110:60616  cpe-24-95-42-77.colu:telnet TIME_WAIT
    tcp        0      0 ::1:36998                   ::1:38330                   TIME_WAIT
    tcp        0      0 ::ffff:192.168.1.110:51197  cpe-24-95-42-77.colu:telnet TIME_WAIT
    tcp        0      0 ::ffff:192.168.1.110:53461  cpe-24-95-42-77.colu:telnet TIME_WAIT
    tcp        0      0 ::ffff:192.168.1.110:37406  cpe-24-95-42-77.colu:telnet TIME_WAITWhy aren't my connections being closed?

    I know port 23 is for Telnet. The program runs at work and accesses a MySQL database from my house. Because I can't connect to port 3306 from work, Telnet connections are allowed so my program uses port 23 which my router forwards to port 3306 of my server, which works.
    I changed my code a bit because I noticed that I'm not closing my ResultSets, Statements, and PreparedStatements. Now I have the following in my Database class:
    public static void closeConnection (Connection connection)
            try
                connection.close ();
            catch(Exception e)
                System.out.println("Error closing connection:\n\n" + e);
        public static void closeStatement (Statement stmt)
            try
                stmt.close ();
            catch(Exception e)
                System.out.println("Error closing statement:\n\n" + e);
        public static void closePreparedStatement (PreparedStatement pstmt)
            try
                pstmt.close ();
            catch(Exception e)
                System.out.println("Error closing PreparedStatement:\n\n" + e);
        public static void closeResultSet (ResultSet rs)
            try
                rs.close ();
            catch(Exception e)
                System.out.println("Error closing ResultSet:\n\n" + e);
        }And then in my blocks where I'm connecting to the database I am using the following to close the connections:
                    Database.closeResultSet (rs);
                    Database.closePreparedStatement (pstmt);
                    Database.closeStatement (stmt);
                    Database.closeConnection (connection);
                    System.out.println ("Connection closed.");Does this look better?

  • The underlying connection was closed: A connection that was expected to be kept alive was closed by the server

    Dear forum 
    Please help
    I'm running an application that receive some messages (mail)
    I'm running under server 2012.
    For some reason the messages are stop to being received due to the session that is being closed.
    i can read the log saying:
    HTTPS ReceiveProcess(): Null segement received
    Closing session, dispatch Timer: 60000 ms.
    The underlying connection was closed: A connection that was expected to be kept alive was closed by the
    server
    Changing session Thread Time from 60 000ms to 2000ms.
    BatapWebService socket closed.
    Can anyone tell me how to fix that it's very annoyin that is closing the connexion and my messages are not
    being received.
    I need to restart the server each time to be able to receive all messages.
    is that a parameter i have to change?
    please help

    What exactly is the application?
    What is giving you the error? Is there a specific Event ID number and Source name?
    I haven't seen a segmentation error in quite some time. The last time I saw one it was due to an app trying to do something on the OS side that the OS didn't like. I believe DEP protected it, but it was long ago and I don't fully remember the details. It
    was a custom written app and the programmers corrected it.
    I'm not a dev, so I can't help with the app itself.
    Here's more on segmentation errors:
    http://en.wikipedia.org/wiki/Segmentation_fault
    If you need assistance with the app itself, I would suggest to post it to MSDN:
    http://social.msdn.microsoft.com/forums/en-US/categories/
    If it's an app written by another language, you can try this:
    Test your web browser for WebSocket support
    http://jimbergman.net/websocket-web-browser-test/
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

  • SP L20 hanging whilst user closing network connections on LAN

    I have 2 new laptops on out network Satellite Pro L20. They work ok until the user logs off from he network and the machine hangs on 'closing network connections'. It powers up and down no problem when not connected to the network. I have Win XP SP 2 all the win updates installed, all of the bios upgrades and drivers from the website.
    I need HELP.
    What should I check and do?? it is still the same hanging on closing network connections and I have to hard boot the laptop to restart, although it does restart eventually if I leave it for 10 minutes.

    Hello Sio
    Believe me it is not easy to say why this happen exactly because the LAN configuration of your unit is not known to us. First of all you should discuss it with your network administrator. He is the person who knows how it works in your company.
    I dont know if you have some folders for sharing. It is possible that someone use the data saved on your notebook and in this situation the notebook can not cut off the connectivity. What is with your IP Address (defined one or you get it automatically)?

  • Getting Error:closing a connection for you. Please help

    Hello All,
    I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
    I'm getting below errors occasionally
    'No managed connection exception
    java.lang.OutOfMemoryError: Java heap space
    [CachedConnectionManager] Closing a connection for you. Plea
    se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
    5
    I've given below my dao connection code here,
    package com.drtrack.util;
    import java.sql.Connection;
    import java.sql.SQLException;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import javax.sql.DataSource;
    public class DAOUtil {
    private static DataSource _ds;
    public Connection con;
    public DAOUtil() throws SQLException {
    try {
    if (_ds == null)
    assemble();
    if(_ds != null && con == null) {
    con = _ds.getConnection();
    }catch(SQLException ex) {
    ex.printStackTrace();
    private void assemble() {
    Context ic = null;
    try {
    ic = new InitialContext();
    DrTrackUtil drutil = new DrTrackUtil();
    _ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
    drutil = null;
    }catch (Exception e) {
    e.printStackTrace();
    }finally {
    try {
    ic.close();
    }catch(NamingException ne) {}
    public void closeConnection() throws SQLException {
    if(con != null)
    con.close();
    con = null;
    }below is the code with get connection and doing transaction in it.
    public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
    AccountMasterValueBean bean = null;
    DAOUtil dao = null;
    CallableStatement cst = null;
    ResultSet rs = null;
    try {
    dao = new DAOUtil();
    cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
    cst.setObject(1, acctId);
    rs = cst.executeQuery();
    if(rs != null && rs.next()) {
    bean = new AccountMasterValueBean(
    Integer.valueOf(rs.getString("accountkeyid")),
    rs.getString("latitude"),
    rs.getString("longitude"));
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    if(rs != null){
    try {
    rs.close();
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    rs = null;
    if(cst != null) {
    try{
    cst.close();
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    cst = null;
    if(dao != null) {
    try {
    dao.closeConnection();
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    dao = null;
    return bean;
    }I closed connections, resultsets and statements properly.
    Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
    Thanks.

    Hello All,
    I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
    I'm getting below errors occasionally
    'No managed connection exception
    java.lang.OutOfMemoryError: Java heap space
    [CachedConnectionManager] Closing a connection for you. Plea
    se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
    5
    I've given below my dao connection code here,
    package com.drtrack.util;
    import java.sql.Connection;
    import java.sql.SQLException;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import javax.sql.DataSource;
    public class DAOUtil {
    private static DataSource _ds;
    public Connection con;
    public DAOUtil() throws SQLException {
    try {
    if (_ds == null)
    assemble();
    if(_ds != null && con == null) {
    con = _ds.getConnection();
    }catch(SQLException ex) {
    ex.printStackTrace();
    private void assemble() {
    Context ic = null;
    try {
    ic = new InitialContext();
    DrTrackUtil drutil = new DrTrackUtil();
    _ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
    drutil = null;
    }catch (Exception e) {
    e.printStackTrace();
    }finally {
    try {
    ic.close();
    }catch(NamingException ne) {}
    public void closeConnection() throws SQLException {
    if(con != null)
    con.close();
    con = null;
    }below is the code with get connection and doing transaction in it.
    public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
    AccountMasterValueBean bean = null;
    DAOUtil dao = null;
    CallableStatement cst = null;
    ResultSet rs = null;
    try {
    dao = new DAOUtil();
    cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
    cst.setObject(1, acctId);
    rs = cst.executeQuery();
    if(rs != null && rs.next()) {
    bean = new AccountMasterValueBean(
    Integer.valueOf(rs.getString("accountkeyid")),
    rs.getString("latitude"),
    rs.getString("longitude"));
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    if(rs != null){
    try {
    rs.close();
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    rs = null;
    if(cst != null) {
    try{
    cst.close();
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    cst = null;
    if(dao != null) {
    try {
    dao.closeConnection();
    }catch(SQLException se) {
    logger.info("SQL Error: " + se);
    finally {
    dao = null;
    return bean;
    }I closed connections, resultsets and statements properly.
    Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
    Thanks.

  • Difference between closing the connection before and after committing user transaction?

              I was wondering what's the difference between closing the connection before committing
              the transaction versus closing the connection after committing the transaction?...
              for e.g....
              Scenario 1.........
              UserTransaction useretran;
              usertran.begin();
              Connection con = datasource.getCOnnection();
              // do bunch of stuff...
              conn.close();
              usertran.commit()
              Scenario 2...
              UserTransaction useretran;
              usertran.begin();
              Connection con = datasource.getCOnnection();
              // do bunch of stuff...
              usertran.commit()
              conn.close();
              thanks....
              Srini
              

    Hi. As long as you're sure there's a transaction going on, and the connection
    is a transaction-aware object (from a TxDataSource), either will be fine.
    In the first scenario the actual semantics of the close() call are less than
    normal, because we really don't close the connection or return it to the
    pool until the actual transaction commits, and in the second case, we have
    already taken the connection out of your service as of the commit().
    The second scenario is the usual coding style. If there's ever a chance your
    code will get non-transaction-aware connections, it is crucial to close
    connections, and I always recommend putting the close() in a finally block
    so it's guaranteed to happen.
    Joe
    srinivas wrote:
    I was wondering what's the difference between closing the connection before committing
    the transaction versus closing the connection after committing the transaction?...
    for e.g....
    Scenario 1......... UserTransaction useretran; usertran.begin(); Connection con =
    datasource.getCOnnection(); // do bunch of stuff... conn.close(); usertran.commit()
    Scenario 2... UserTransaction useretran; usertran.begin(); Connection con = datasource.getCOnnection();
    // do bunch of stuff... usertran.commit() conn.close();
    thanks....
    Srini

  • Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)

    Fresh installation of Exchange Server 2013 on Windows Server 2012.
    Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize
    your folders with your Outlook data file (.ost)" is displayed.
    If I turn off cached Exchange mode, setting the email account to not
    cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first
    time.
    I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.
    Microsoft Exchange RPC Client Access service is running.
    No warning, error or critical messages in the eventlog, it's like the healthiest server alive.
    Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

    So it looks like a lot of people are having this issue and seeing how Exchange 2013 is still new (relatively to the world) there isn't much data around to answer this. I've spend ALOT of time trying to figure this out.
    Here is the answer. :) - No I don't know all but I'm going to try to give you the most reasonable answer to this issue, in a most logical way.
    First thing I did when I was troubleshooting this issue is that I ignored Martina Miskovic's suggestion for Step4 http://technet.microsoft.com/library/jj218640(EXCHG.150)because it didn't make sense to me because I was trying to connect
    Outlook not outside the LAN but actually inside. However, Martina's suggestion does fix the issue if it's applied in the correct context.
    This is where the plot thickens (it's stew). She failed to mention that things like SSL (which I configure practically useless - anyone who ever worked in a business environment where the owner pretty much trusts anyone in the company, otherwise they don't
    work there - very good business practice in my eyes btw, can confirm that...) are some sort of fetish with Microsoft lately. Exchange 2013 was no exception.
    In exchange 2003, exchange 2007 and exchange 2010 - you could install it and then go to outlook and set it up. And when outlook manual Microsoft Exchange profile would ask you for server name, you would give it and give the name of the person who you setting
    up - as long as machine is on the domain, not much more is needed. IT JUST WORKS! :) What a concept, if the person already on premises of the business - GIVE HIM ACCESS. I guess that was too logical for Microsoft. Now if you're off premises you can use things
    like OutlookAnywhere - which I might add had their place under that scenario.
    In Exchange 2013, the world changed. Ofcourse Microsoft doesn't feel like telling it in a plain english to people - I'm sure there is an article somewhere but I didn't find it. Exchange 2013 does not support direct configuration of Outlook like all of it's
    previous versions. Did you jaw drop? Mine did when I realized it. So now when you are asked for your server name in manual outlook set up and you give it Exchange2013.yourdomain.local - it says cannot connect to it. This happens because ALL - INTERNAL AND
    EXTERNAL connection are now handled via OutlookAnywhere. You can't even disable that feature and have it function the reasonable way.
    So now the question still remains - how do you configure outlook. Well under server properties there is this nice section called Outlook anywhere. You have a chance to configure it's External and Internal address. This is another thing that should be logical
    but it didn't work that way for me. When I configured the external address different from the internal - it didn't work. So I strongly suggest you get it working with the same internal address first and then ponder how you want to make it work for the outside
    users.
    Now that you have this set up you have to go to virtual directories and configure the external and internal address there - this is actually what the Step 4 that Martina was refering to has you do.
    Both external and internal address are now the same and you think you can configure your outlook manually - think again. One of the most lovely features of Outlook Anywhere, and the reason why I had never used it in the past is that it requires a TRUSTED
    certificate.
    See so it's not that exchange 2013 requires a trusted certificate - it's that exchange 2013 lacks the feature that was there since Windows 2000 and Exchange 5.5.
    So it's time for you to install an Active Direction Certificate Authority. Refer to this wonderful article for exact steps - http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
    Now even after you do that - it won't work because you have to add the base private key certificate, which you can download now from your internal certsrv site, to Default Domain Policy (AND yes some people claim NEVER mess with the Default Domain Policy,
    always make an addition one... it's up to you - I don't see direct harm if you know what you want to accomplish) see this: http://technet.microsoft.com/en-us/library/cc738131%28v=ws.10%29.aspx if you want to know exact steps.
    This is the moment of ZEN! :) Do you feel the excitement? After all it is your first time. Before we get too excited lets first request and then install the certificate to actual Exchange via the gui and assign it to all the services you can (IIS, SMTP and
    there is a 3rd - I forgot, but you get the idea).
    Now go to your client machine where you have the outlook open, browse to your exchange server via https://exchang2013/ in IE and if you don't get any certificate errors - it's good. If you do run on hte client and the server: gpupdate /force This will refresh
    the policy. Don't try to manually install the certificate from Exchange's website on the client. If you wanna do something manually to it to the base certificate from the private key but if you added it to the domain policy you shouldn't have to do it.
    Basically the idea is to make sure you have CA and that CA allows you to browse to exchange and you get no cert error and you can look at the cert and see that's from a domain CA.
    NOW, you can configure your outlook. EASY grasshoppa - not the manual way. WHY? Cause the automatic way will now work. :) Let it discover that exachange and populate it all - and tell you I'm happy! :)
    Open Outlook - BOOM! It works... Was it as good for you as it was for me?
    You may ask, why can't I just configure it by manual - you CAN. It's just a nightmare. Go ahead and open the settings of the account that got auto configed... How do you like that server name? It should read something like [email protected]
    and if you go to advanced and then connection tab - you'll see Outlook Anywhere is checked as well. Look at the settings - there is the name of the server, FQDN I might add. It's there in 2 places and one has that Mtdd-something:Exchange2013.yourdomain.local.
    So what is that GUID in the server name and where does it come from. It's the identity of the user's mailbox so for every user that setting will be different but you can figure it out via the console on the Exchange server itself - if you wish.
    Also a note, if your SSL certs have any trouble - it will just act like outlook can't connect to the exchange server even though it just declines the connection cause the cert/cert authority is not trusted.
    So in short Outlook Anywhere is EVERYWHERE! And it has barely any gui or config and you just supposed to magically know that kind of generic error messages mean what... Server names are now GUIDs of the [email protected] - THAT MAKES PERFECT
    SENSE MICROSOFT! ...and you have to manage certs... and the only place where you gonna find the name of the server is inside the d*** Outlook Anywhere settings in the config tab, un it's own config button - CAN WE PUT THE CONFIG ANY FURTHER!
    Frustrating beyond reason - that should be Exchange's new slogan...
    Hope this will help people in the future and won't get delete because it's bad PR for Microsoft.
    PS
    ALSO if you want to pick a fight with me about how SSL is more secure... I don't wanna hear it - go somewhere else...

  • Windows server 2012 and windows xp remote desktop connection loss

    I am having this problem for a month now, and i am stumped with trying to find an answer . I have talked with several network admins in my area and with no luck i have not found a solution. I have a windows server 2012 placed with 5 pcs that are connected
    on a local network , those 5 pc's connect to the server via remote desktop. List of pc's:
    1x Windows 7
    4x Windows XP SP3
    All have the latests network drivers, all have the latest version of remote desktop installed. All have been scanned for viruses. All have antivirus software.
    Problem is the 4 XP machines lose connection on when connected via remote desktop. If one starts losing connection the other 3 start to lose the connection aswell. The windows 7 machine is not affected by this it works fine.
    What have I tried:
    Scanning for viruses.
    Disabling Firewall and antivirus software.
    Updating all drivers.
    Did many changes to group policy like keepalives etc.
    Turning off SMBv2 SMBv3.
    Turning off network adapter Offload settings.
    Changed some registry settings like keepalive, smb etc.
    Updating every pc and server with all windows updates.
    Changed the router and switch.
    Port forwarded needed ports like 3389.
    Updating remote desktop to 7.0.
    I might be forgetting some stuff i will add as i remember anything.
    So the thing is this. I use a Windows XP machine from my office I remotely connect to the server via the Internet and I DO NOT experience any connection loss. BUT the XP machines on the local network constantly experience connection loss via remote desktop.
    I pinged every Machine from the server via CMD command PING. So when they lose connection the Packets get time outs . Packets get dropped between 1-10 packets when a connection is lost. This packet drop does not occur when using the internet or anything else.
    ONLY when connected to the server via remote desktop. The packets get dropped at random intervals.
    Problem is I use an XP machine and I am not experiencing any loss of connection , while the XP machines on the local network experience it , but not the windows 7 machine.
    Router is ASUS RT-N53 , and switch is Dlink DES-1008D. Server is a Dell PowerEdge T110 II.
    Can someone please tell me what can i do to solve this problem?

    So today got some word from their office. They were using RDP from 8AM until 12PM all was working fine. Then got back after lunch about 1PM and got a few connection lost errors when they tried using RDP again. Its weird since they didn't have disconnects
    in the morning, and started having them after lunch.
    Also noticed, that two pc were not using RDP and were disconnected as shown in task manager. And they still got request timeouts.
    Maybe this is not a remote desktop issue?
    TASK MANAGER
    The 2 disconnected pc's ping screens:

  • No event in Udev upon connecting a DVI-HDMI display

    Hi all!
    Im pretty new to Archlinux and sarted "linuxing" generally not so long ago.
    Arch is my latest stop and love-for-first-sight, learned a lot from its wiki and forum.
    I tried to cook (honestly more like copy) a script today to let KDE (xrandr) automatically configure my TV, which is connected with a DVI-HDMI cabel through a HDMI switch.
    As per instructions i tried to check out its proper name with
    udevadm monitor
    but there r absolutely no events in it.
    Im guessing thats why my script isnt invoked upon connecting/disconnecting.
    Also, even if i connect/disconnect TV, KDE generally does not get it untill i let Display Settings run or
    xrandr
    from terminal.
    That means if i disconnect, then reconnect, my settings r still the same. If i run any of them in the while, or boot up Linux so that my TV is turned off, i loose my settings.
    Is that normal?
    What can i do that i can get udev events?
    Thanks a lot for your help guys in advance!
    EDIT:
    Two more things
    Disconnecting my primary monitor shos nothing as well at udevadm monitor.
    Interestingly DVI-0 is my TV with DVI-HDMI connection
    HDMI-0 is my primary monitor with DVI-DVI connection.
    Kinda weird.....
    Last edited by dragonreborn (2014-08-11 21:50:18)

    dragonreborn wrote:What can i do that i can get udev events?
    Fix the driver in the kernel to broadcast uevents on HPD handling.
    Last edited by falconindy (2014-08-11 22:00:31)

  • Is there anyway to solve Wifi problem on Macbook while using it closed and connected to external display?

    Hello,
    I'm using my Macbook connected to external LCD while the screen of the Macbook is closed. So I can use the full screen resoluiton of my LCD. When not closed but connected the mirroring reduces the resolution and not useful.
    But recently I recognized that when the Macbook screen is closed my fiber internet speed is down almost %50. When I test my fiber speed, when the macbook screen is open it's around 20mb/s, when the screen is closed and connected to LCD it's around 10 mb/s. I guess the wifi antenna is located at the screen I don't know. Is there any way to solve this probem? I want to use the lid closed without any sacrifice from my internet speed.
    Thanks for any answers in advance

    I have this same issue but what's strange is that it's only recently occurred since upgrading to FiOS's 50MB/s service.  I was seeing 20MB/s WiFi speeds with my previous 25MB/s service.  Frustrating!!

  • Why do I have Intermittent Wifi Connection Loss during music streaming ?

    Hello,
    I have an ipad3 and an iPhone 4S and I am getting with both devices interruption of the sound when I send music to the Apple TV. It generally happens after a few minutes. The signal for the wifi is still good and I have still access to the Internet  I have tried all the recommendations of the article "iOS: Troubleshooting Wi-Fi networks and connections" but this did not help. I have used several applications for sending music to the Apple TV (music application from Apple and DSAudio from Synology) but I'm getting the same issue. I have also the same issue with the media center application from Bouygues Telecom connecting directly to my internet router. My router is a bbox sensation. I had also the same kind of issue with my old router when sensing photo albums to the internet: I had the error message "your system is running low on ressources". How can I solve these intermittent wifi connection losses ?

    Try #5.
    Some things to try first:
    1. Turn Off your iPad. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
    2. Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
    3. Change the channel on your wireless router (Auto or Channel 6 is best). Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
    4. Go into your router security settings and change from WEP to WPA with AES.
    5.  Renew IP Address: (especially if you are droping internet connection)
        •    Launch Settings app
        •    Tap on Wi-Fi
        •    Tap on the blue arrow of the Wi-Fi network that you connect to from the list
        •    In the window that opens, tap on the Renew Lease button
    6. Potential Quick Fixes When Your iPad Won’t Connect to Your Wifi Network
    http://ipadinsight.com/ipad-tips-tricks/potential-quick-fixes-when-your-ipad-won t-connect-to-your-wifi-network/
    ~~~~~~~~~~~~~~~~~~~~~~~~~
    Wi-Fi Fix for iOS 6
    https://discussions.apple.com/thread/4823738?tstart=240
    iOS 6 Wifi Problems/Fixes
    How To: Workaround iPad Wi-Fi Issues
    http://www.theipadfan.com/workaround-ipad-wifi-issues/
    Another Fix For iOS 6 WiFi Problems
    http://tabletcrunch.com/2012/10/27/fix-ios-6-wifi-problems-ssid/
    Wifi Doesn't Connect After Waking From Sleep - Sometimes increasing screen brightness prevents the failure to reconnect after waking from sleep. According to Apple, “If brightness is at lowest level, increase it by moving the slider to the right and set auto brightness to off.”
    Fix For iOS 6 WiFi Problems?
    http://tabletcrunch.com/2012/09/27/fix-ios-6-wifi-problems/
    Did iOS 6 Screw Your Wi-Fi? Here’s How to Fix It
    http://gizmodo.com/5944761/does-ios-6-have-a-wi+fi-bug
    How To Fix Wi-Fi Connectivity Issue After Upgrading To iOS 6
    http://www.iphonehacks.com/2012/09/fix-wi-fi-connectivity-issue-after-upgrading- to-ios-6.html
    iOS 6 iPad 3 wi-fi "connection fix" for netgear router
    http://www.youtube.com/watch?v=XsWS4ha-dn0
    Apple's iOS 6 Wi-Fi problems
    http://www.zdnet.com/apples-ios-6-wi-fi-problems-linger-on-7000004799/
    ~~~~~~~~~~~~~~~~~~~~~~~
    How to Boost Your Wi-Fi Signal
    http://ipad.about.com/od/iPad_Troubleshooting/a/How-To-Boost-Your-Wi-Fi-Signal.h tm
    Troubleshooting a Weak Wi-Fi Signal
    http://ipad.about.com/od/iPad_Troubleshooting/a/Troubleshooting-A-Weak-Wi-Fi-Sig nal.htm
    How to Fix a Poor Wi-Fi Signal on Your iPad
    http://ipad.about.com/od/iPad_Troubleshooting/a/How-To-Fix-A-Poor-Wi-Fi-Signal-O n-Your-iPad.htm
    iOS Troubleshooting Wi-Fi networks and connections  http://support.apple.com/kb/TS1398
    iPad: Issues connecting to Wi-Fi networks  http://support.apple.com/kb/ts3304
    WiFi Connecting/Troubleshooting http://www.apple.com/support/ipad/wifi/
    How to Fix: My iPad Won't Connect to WiFi
    http://ipad.about.com/od/iPad_Troubleshooting/ss/How-To-Fix-My-Ipad-Wont-Connect -To-Wi-Fi.htm
    iOS: Connecting to the Internet http://support.apple.com/kb/HT1695
    iOS: Recommended settings for Wi-Fi routers and access points  http://support.apple.com/kb/HT4199
    How to Quickly Fix iPad 3 Wi-Fi Reception Problems
    http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
    iPad Wi-Fi Problems: Comprehensive List of Fixes
    http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
    Connect iPad to Wi-Fi (with troubleshooting info)
    http://thehowto.wikidot.com/wifi-connect-ipad
    Fix iPad Wifi Connection and Signal Issues  http://www.youtube.com/watch?v=uwWtIG5jUxE
    Fix Slow WiFi Issue https://discussions.apple.com/thread/2398063?start=60&tstart=0
    How To Fix iPhone, iPad, iPod Touch Wi-Fi Connectivity Issue http://tinyurl.com/7nvxbmz
    Unable to Connect After iOS Update - saw this solution on another post.
    https://discussions.apple.com/thread/4010130
    Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
    Wi-Fi or Bluetooth settings grayed out or dim
    http://support.apple.com/kb/TS1559
    ~~~~~~~~~~~~~~~
    If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
     Cheers, Tom

Maybe you are looking for