Persona management - extremely high logon times

Hello,
we're using a dynamic windows 7 pool with persona management activated via GPO.
Whenever a user logs on a desktop for the first time (so no local profile exists), the logon times can be up to 1 hour!
The client shows the windows status "waiting for user profile service".
Here are some lines from the persona log (the user name here is "sgsas"):
[15187289][05/19/2015 05:55:55:0985][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming
[15187079][05/19/2015 05:55:56:0000][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\Tracing, Value: 0x2
[15187316][05/19/2015 05:55:56:0000][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Apple Computer
[15187337][05/19/2015 05:55:56:0016][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Apple Computer
[15187347][05/19/2015 05:55:56:0016][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Apple Computer
[15187316][05/19/2015 05:55:56:0016][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Apple Computer, Value: 0x2
[15187355][05/19/2015 05:55:56:0016][RTOLogon!RedirectFile
] VMWGetFileInfo Failed: Process: System, File: \Device\HarddiskVolume2\Users\sgsas\AppData\desktop.ini, 0xC0000034
[15187355][05/19/2015 05:55:56:0016][RTOLogon!RTORetrieveOfflineFile] Retrieved User Identity: Path: \Device\HarddiskVolume2\Users\sgsas\AppData\desktop.ini
[15187355][05/19/2015 05:55:56:0016][RTOLogon!RTORetrieveOfflineFile] Received FALSE From Service: 0x0, ulResult: 0x80070002
[15187355][05/19/2015 05:55:56:0016][RTOLogon!RedirectFile
] RTORetrieveOfflineFile Returned: Process: System, Offline: 0, 0x80070002
[15187367][05/19/2015 05:55:56:0032][RTOLogon!RedirectFile
] VMWGetFileInfo Failed: Process: System, File: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\desktop.ini, 0xC0000034
[15187367][05/19/2015 05:55:56:0032][RTOLogon!RTORetrieveOfflineFile] Retrieved User Identity: Path: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\desktop.ini
[15187367][05/19/2015 05:55:56:0032][RTOLogon!RTORetrieveOfflineFile] Received FALSE From Service: 0x0, ulResult: 0x80070002
[15187367][05/19/2015 05:55:56:0032][RTOLogon!RedirectFile
] RTORetrieveOfflineFile Returned: Process: System, Offline: 0, 0x80070002
[15187409][05/19/2015 05:55:56:0047][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Media Center Programs
[15187422][05/19/2015 05:55:56:0047][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Media Center Programs
[15187424][05/19/2015 05:55:56:0047][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Media Center Programs
[15187409][05/19/2015 05:55:56:0047][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Media Center Programs, Value: 0x2
[15187449][05/19/2015 05:55:56:0063][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia
[15187463][05/19/2015 05:55:56:0078][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia
[15187468][05/19/2015 05:55:56:0078][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia
[15187449][05/19/2015 05:55:56:0078][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Macromedia, Value: 0x2
[15187482][05/19/2015 05:55:56:0094][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player
[15187498][05/19/2015 05:55:56:0094][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player
[15187511][05/19/2015 05:55:56:0110][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player
[15187482][05/19/2015 05:55:56:0110][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player, Value: 0x2
[15187516][05/19/2015 05:55:56:0125][RTOLogon!RedirectFile
] VMWGetFileInfo Failed: Process: System, File: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\desktop.ini, 0xC0000034
[15187516][05/19/2015 05:55:56:0125][RTOLogon!RTORetrieveOfflineFile] Retrieved User Identity: Path: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\desktop.ini
[15187516][05/19/2015 05:55:56:0125][RTOLogon!RTORetrieveOfflineFile] Received FALSE From Service: 0x0, ulResult: 0x80070002
[15187516][05/19/2015 05:55:56:0125][RTOLogon!RedirectFile
] RTORetrieveOfflineFile Returned: Process: System, Offline: 0, 0x80070002
[15187552][05/19/2015 05:55:56:0125][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com
[15187576][05/19/2015 05:55:56:0141][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com
[15187581][05/19/2015 05:55:56:0141][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com
[15187552][05/19/2015 05:55:56:0156][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com, Value: 0x2
[15187588][05/19/2015 05:55:56:0156][RTOLogon!RedirectFile
] VMWGetFileInfo Failed: Process: System, File: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\desktop.ini, 0xC0000034
[15187588][05/19/2015 05:55:56:0156][RTOLogon!RTORetrieveOfflineFile] Retrieved User Identity: Path: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\desktop.ini
[15187588][05/19/2015 05:55:56:0156][RTOLogon!RTORetrieveOfflineFile] Received FALSE From Service: 0x0, ulResult: 0x80070002
[15187588][05/19/2015 05:55:56:0156][RTOLogon!RedirectFile
] RTORetrieveOfflineFile Returned: Process: System, Offline: 0, 0x80070002
[15187632][05/19/2015 05:55:56:0172][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin
[15187655][05/19/2015 05:55:56:0188][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin
[15187660][05/19/2015 05:55:56:0188][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin
[15187632][05/19/2015 05:55:56:0188][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin, Value: 0x2
[15187665][05/19/2015 05:55:56:0188][RTOLogon!RedirectFile
] VMWGetFileInfo Failed: Process: System, File: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\desktop.ini, 0xC0000034
[15187665][05/19/2015 05:55:56:0188][RTOLogon!RTORetrieveOfflineFile] Retrieved User Identity: Path: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\desktop.ini
[15187665][05/19/2015 05:55:56:0188][RTOLogon!RTORetrieveOfflineFile] Received FALSE From Service: 0x0, ulResult: 0x80070002
[15187665][05/19/2015 05:55:56:0188][RTOLogon!RedirectFile
] RTORetrieveOfflineFile Returned: Process: System, Offline: 0, 0x80070002
[15187717][05/19/2015 05:55:56:0219][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin\airappinstaller
[15187745][05/19/2015 05:55:56:0234][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin\airappinstaller
[15187754][05/19/2015 05:55:56:0234][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin\airappinstaller
[15187717][05/19/2015 05:55:56:0234][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin\airappinstaller, Value: 0x2
[15187761][05/19/2015 05:55:56:0250][RTOLogon!RedirectFile
] VMWGetFileInfo Failed: Process: System, File: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin\desktop.ini, 0xC0000034
[15187761][05/19/2015 05:55:56:0250][RTOLogon!RTORetrieveOfflineFile] Retrieved User Identity: Path: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin\desktop.ini
[15187761][05/19/2015 05:55:56:0250][RTOLogon!RTORetrieveOfflineFile] Received FALSE From Service: 0x0, ulResult: 0x80070002
[15187761][05/19/2015 05:55:56:0250][RTOLogon!RedirectFile
] RTORetrieveOfflineFile Returned: Process: System, Offline: 0, 0x80070002
[15187861][05/19/2015 05:55:56:0328][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com
[15187881][05/19/2015 05:55:56:0344][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com
[15187887][05/19/2015 05:55:56:0344][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com
[15187861][05/19/2015 05:55:56:0344][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com, Value: 0x2
[15187900][05/19/2015 05:55:56:0359][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com\support
[15187923][05/19/2015 05:55:56:0375][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com\support
[15187928][05/19/2015 05:55:56:0375][RTOLogon!VMWQueryEA  
] No EAs Found: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com\support
[15187900][05/19/2015 05:55:56:0375][RTOLogon!VMWSetEA    
] Set EA: File: \Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com\support, Value: 0x2
[15187936][05/19/2015 05:55:56:0390][RTOLogon!RedirectFile
] VMWGetFileInfo Failed: Process: System, File: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com\desktop.ini, 0xC0000034
[15187936][05/19/2015 05:55:56:0390][RTOLogon!RTORetrieveOfflineFile] Retrieved User Identity: Path: \Device\HarddiskVolume2\Users\sgsas\AppData\Roaming\Macromedia\Flash Player\macromedia.com\desktop.ini
[15187936][05/19/2015 05:55:56:0390][RTOLogon!RTORetrieveOfflineFile] Received FALSE From Service: 0x0, ulResult: 0x80070002
I cant find anything about "No EAS Found".
Any ideas?
Thanks in advance
tim

Hello h3nkY,
thanks for your advice. I will try that.
Besides, I saw this entry in another log on the client right before the logon process freezes for long time:
[MessageFrameWork] Client/agent channel pending wssm to start
Does it mean the clients is waiting for the persona sync or could it be something else?
Thanks again.
Tim

Similar Messages

  • Hard drive passes all tests but extremely high response times causing major performance issues.

    I have a HP Compaq Presario CQ62-360TX pre-loaded with Windows 7 home premium (64-bit) that I purchased just under a year ago.
    Recently my experience has been interrupted by stuttering that ranges from annoying in general use to a major headache when playing music or videos from the hard drive.
    The problem appears to be being caused by extremely hard drive high response times (up to 10 seconds).  As far as I know I didn't install anything that might have caused the problems before this happened, and I can't find anything of note looking back through event viewer.
    In response to this I've run multiple hard drive scans for problems (chkdsk, scandsk, test through BIOS, test through HP software and others) all of which have passed with no problems. The only thing of any note is a caution on crystaldiskinfo due to the reallocated sector count but as none of the other tests have reported bad sectors I'm unsure as to whether this is causing the problem. I've also updated drivers for my Intel 5 Series 4 Port SATA AHCI Controller from the Intel website and my BIOS from HP as well as various other drivers (sound, video etc), as far as I can tell there are none available for my hard drive directly. I've also wanted to mess with the hard drive settings in the BIOS but it appears those options are not available to me even in the latest version.
    System Specs:
    Processor: Intel(R) Pentium(R) CPU P6100 @ 2.00GHz (2 CPUs), ~2.0GHz
    Memory: 2048MB RAM
    Video Card: ATI Mobility Radeon HD 5400 Series
    Sound Card: ASUS Xonar U3 Audio Device or Realtek High Definition Audio (both have problem)
    Hard Drive: Toshiba MK5065GSK
    Any ideas?
     Edit: The drive is nowhere near full, it's not badly fragmented and as far as I can tell there's no virus or malware.

    Sounds like failing sectors are being replaced with good spares sucessfully so far, this is done on the fly and will not show in any test, you have a failing drive, I would back up your data and replace the hard drive.
    Sector replacement on the fly explains the poor performance also, replacing sectors with spares is normal if it is just a few over many years, but crystal is warning you there are too many, a sign of drive failure is around the corner.

  • Extremely High Ping time. Unusable internet for VOIP.

    I am having extremely bad ping times due to which my VOIP phone service is literally unusable. My net meetings at home is having lost conversations and I am having real tough time working from home. Comcast service rep has visited my house twice and checked everything from my modem to comcast network end and everything seems to be fine.I have attached the ping times screenshot for my closest servers and both of which show unacceptable ping times.

    Start by reviewing the troubleshooting tips at this sticky and post the requested information.
    http://forums.xfinity.com/t5/Basic-Internet-Connectivity-And/Connection-Troubleshooting-Tips/m-p/1253575#U1253575

  • Extremely high ping times only fixed via restart

    I have 2 BR350 in bridge to a remote tower that has an AP350 providing access to customers. The customers will call in with complaints of very slow access. I have been onsite to see that a user can login to the AP350(web) fine but the BR350 at the tower is slow and the BR350 at the far tower is for most purposes dead. The link still shows up around 65% to 75% signal strength. By restarting either BR350 the link will come back fine. I have been using Ping Plotter to keep track of the ping times and see that the response times sometime slow grow or instantly grow to around 2000ms to 4000ms. Ping times from the customer to the AP350 on the tower remain below 10ms during all of this.
    I have had a similar problem with an AP350 in another city thats ping time do the same thing and require a reboot. It's ping time from the client side can range form 4ms to 800ms on regular usage as well. This customer has an average of 80% signal strength from the Workgroup Bridge.
    How can I find out what is causing that strange high ping time on these situations.
    All units running firmware 12.00
    Thanks for the help.
    MV

    Normally ,the first thing to do is to check the software version used. Here,in your case you are using the latest software release(12.00T). So now the problem can be isolated to other issues. Bridge software provides tools to show you the types of problems and where the bridge is encountering the problems. Two of the most helpful tools are the Throughput statistics and the Error statistics screen.You can get the procedure for collecting the error statistics using the following URLs:
    http://www.cisco.com/warp/public/102/wlan/br-ts-22950.shtml#conn
    http://www.cisco.com/warp/public/102/wlan/errors.html

  • Extremely high ping times ( 3000ms) and unusable ...

    Hi all,
    I am currently at my girlfriends house, trying to do some work but am experiencing absolutely dreadful internet connectivity.
    I have just setup a small *nix box plugged directly into the HH4's gigabit ethernet port purely to monitor this abysmal connectivity. Due to the super high latency and low bandwidth for upload / downloads our internet is virtually unusable.
    Here are a couple of excerpts from this mornings logged data.
    Firstly latency of 4129.204 ms!!!
    23/06/15 : 09:09
    ./speedtest-cli
    Retrieving speedtest.net configuration...
    Retrieving speedtest.net server list...
    Testing from BT (86.165.237.95)...
    Selecting best server based on latency...
    Hosted by Spectrum Internet (Cardiff) [90.75 km]: 4129.204 ms
    Testing download speed........................................
    Download: 0.10 Mbit/s
    Testing upload speed..................................................
    Upload: 0.10 Mbit/s
    Secondly ping test to bbc.co.uk again showing very high and varied latency. Avg 1629.844ms  high 2361.604ms
    PING bbc.co.uk (212.58.244.18) 56(84) bytes of data.
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=1 ttl=50 time=653 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=2 ttl=50 time=730 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=3 ttl=50 time=1188 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=4 ttl=50 time=1529 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=5 ttl=50 time=1464 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=6 ttl=50 time=600 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=7 ttl=50 time=153 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=8 ttl=50 time=491 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=9 ttl=50 time=148 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=10 ttl=50 time=870 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=11 ttl=50 time=1163 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=12 ttl=50 time=1202 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=13 ttl=50 time=1192 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=14 ttl=50 time=1209 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=15 ttl=50 time=1193 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=16 ttl=50 time=644 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=17 ttl=50 time=139 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=18 ttl=50 time=96.6 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=19 ttl=50 time=158 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=20 ttl=50 time=510 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=21 ttl=50 time=653 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=22 ttl=50 time=613 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=23 ttl=50 time=827 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=24 ttl=50 time=829 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=25 ttl=50 time=922 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=26 ttl=50 time=124 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=27 ttl=50 time=94.0 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=28 ttl=50 time=90.9 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=29 ttl=50 time=419 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=30 ttl=50 time=364 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=31 ttl=50 time=358 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=32 ttl=50 time=361 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=33 ttl=50 time=402 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=34 ttl=50 time=382 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=35 ttl=50 time=427 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=36 ttl=50 time=409 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=37 ttl=50 time=443 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=38 ttl=50 time=566 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=39 ttl=50 time=651 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=40 ttl=50 time=580 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=41 ttl=50 time=205 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=42 ttl=50 time=361 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=43 ttl=50 time=372 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=44 ttl=50 time=386 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=45 ttl=50 time=360 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=46 ttl=50 time=381 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=47 ttl=50 time=419 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=48 ttl=50 time=430 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=49 ttl=50 time=408 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=50 ttl=50 time=409 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=51 ttl=50 time=492 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=52 ttl=50 time=709 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=53 ttl=50 time=817 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=54 ttl=50 time=1073 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=55 ttl=50 time=1373 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=56 ttl=50 time=1197 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=57 ttl=50 time=1406 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=58 ttl=50 time=1565 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=59 ttl=50 time=1714 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=60 ttl=50 time=1835 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=61 ttl=50 time=2018 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=62 ttl=50 time=2151 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=63 ttl=50 time=2237 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=64 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=65 ttl=50 time=2295 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=66 ttl=50 time=2300 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=67 ttl=50 time=2311 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=68 ttl=50 time=2329 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=69 ttl=50 time=2352 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=70 ttl=50 time=2323 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=71 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=72 ttl=50 time=2236 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=73 ttl=50 time=2257 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=74 ttl=50 time=2224 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=75 ttl=50 time=2250 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=76 ttl=50 time=2242 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=77 ttl=50 time=2247 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=78 ttl=50 time=2258 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=79 ttl=50 time=2237 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=80 ttl=50 time=2251 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=81 ttl=50 time=2341 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=82 ttl=50 time=2330 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=83 ttl=50 time=2257 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=84 ttl=50 time=2319 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=85 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=86 ttl=50 time=2278 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=87 ttl=50 time=2361 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=88 ttl=50 time=2341 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=89 ttl=50 time=2306 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=90 ttl=50 time=2358 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=91 ttl=50 time=2328 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=92 ttl=50 time=2252 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=93 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=94 ttl=50 time=2248 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=95 ttl=50 time=2302 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=96 ttl=50 time=2322 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=97 ttl=50 time=2281 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=98 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=99 ttl=50 time=2295 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=100 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=101 ttl=50 time=2244 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=102 ttl=50 time=2256 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=103 ttl=50 time=2253 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=104 ttl=50 time=2244 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=105 ttl=50 time=2252 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=106 ttl=50 time=2291 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=107 ttl=50 time=2245 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=108 ttl=50 time=2309 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=109 ttl=50 time=2299 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=110 ttl=50 time=2313 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=111 ttl=50 time=2300 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=112 ttl=50 time=2286 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=113 ttl=50 time=2254 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=114 ttl=50 time=2242 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=115 ttl=50 time=2242 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=116 ttl=50 time=2246 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=117 ttl=50 time=2261 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=118 ttl=50 time=2251 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=119 ttl=50 time=2253 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=120 ttl=50 time=2219 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=121 ttl=50 time=2210 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=122 ttl=50 time=2261 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=123 ttl=50 time=2261 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=124 ttl=50 time=2228 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=125 ttl=50 time=2274 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=126 ttl=50 time=2265 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=127 ttl=50 time=2255 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=128 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=129 ttl=50 time=2248 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=130 ttl=50 time=2274 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=131 ttl=50 time=2282 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=132 ttl=50 time=2283 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=133 ttl=50 time=2250 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=134 ttl=50 time=2270 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=135 ttl=50 time=2273 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=136 ttl=50 time=2192 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=137 ttl=50 time=2304 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=138 ttl=50 time=2296 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=139 ttl=50 time=2284 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=140 ttl=50 time=2270 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=141 ttl=50 time=2272 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=142 ttl=50 time=2263 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=143 ttl=50 time=2305 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=144 ttl=50 time=2283 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=145 ttl=50 time=2250 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=146 ttl=50 time=2266 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=147 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=148 ttl=50 time=2247 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=149 ttl=50 time=2267 ms
    ^C
    --- bbc.co.uk ping statistics ---
    151 packets transmitted, 149 received, 1% packet loss, time 150279ms
    rtt min/avg/max/mdev = 90.912/1629.844/2361.604/830.792 ms, pipe 3

    Anyone able to advise what to do about this problem?

  • Extremely high latency from 4am - 12pm in Baltimore, MD

    Lately for the past month I have been getting extremely high latency 1500ms+.  I am directly wired to the Actiontec router using a new cable on a confirmed working lan card.  I believe the problem maybe at the POD card.  How would I go about proving to Verizon without going through numerous transfers of people that don't have a clue?

    I had the same problem since Mid-June. Seems like it's anywhere in North Eastern United States. I myself is located about 20 Minutes from Washington DC. I get the latency right around 12~50 ms on first hop to Google or verizon.net on a good day with trace route test. The people in Verizon tells me that's normal but I don't buy that because my neighbor gets around less than 20 ms, never higher. It gets progressively bad around prime time and onward. Around 12 AM it can reach from 100~400 ms on latency to Google or verizon.net server.
    I am a late night gamer and need that low latency badly. Seems like most of the people I have talk to from FSC (Fios solution Center) had no idea what is the difference between Bandwidth to Latency. They just call it "Speed". I have spoken with these people for almost every night for a month and a half, when I get a hint that they have no idea what they're talking about, I just hang up and call another one up or just request a supervisor to speak with.
    Here is my trace route result, I have highlight the part that are unacceptable.
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
      1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
      2    61 ms    54 ms    23 ms  L100.WASHDC-VFTTP-62.verizon-gni.net [96.231.212.1]
      3    25 ms    15 ms    19 ms  G11-3-662.WASHDC-LCR-06.verizon-gni.net [130.81.104.182]
      4    36 ms    17 ms    33 ms  so-4-2-0-0.RES-BB-RTR2.verizon-gni.net [130.81.28.146]
      5    57 ms    65 ms    58 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
      6    56 ms    67 ms    54 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
      7    60 ms    71 ms    68 ms  206.46.228.130
      8    76 ms   102 ms   141 ms  206.46.232.39
    Trace complete
    I'm going to list the things I have done so that perhaps if you are having the same issue, maybe you can anticipate or maybe save you time with this issue.
    Replaced Router
    This will be my 3rd Router in my possession. The odds of having 3 bad routers are astronomical but yet FSC will try to keep sending you more.
    Replaced coax cable (twice), ONT, and splitter.
    Once again, the problem still persist. To get these fix, I had total of 4 dispatchers. From the word of their mouth, they stated it's beyond their level and when it comes to latency the tech at verizon server will be the best people to help you.
    Reset ONT by unplugging it for 5 minutes or more to pull up a new Gateway IP.
    Appearently, someone were able to fix their latency issue this way but the results are mixed. Either it's a permanent fix or temporary fix or it made the problem even worse.
    Optimizing connection/wired connections
    I have a gaming PC, when they ask to clear the cache to solve my problem, it's an insult. Not only it's irralavent, in order for the computer to bog down because of cache overload, I must possess a computer that is less than of Pentium 2 back from 1995.
    Anti-virus and FireWall
    If these were actually the source of my problem then the high latency should be constantly bad.
    Potentially hacked or other connection to your router.
    While this problem can be an issue, I can see who uses the internet and even turned off the wireless. There's no way an uninvited person can slow down my connections.
    The server that I am connecting to such as website and gaming server is not guaranteed by the verizon.
    Yes, that is true but what are the odds of having google, verizon.net, altavista, gaming server from Steam, etc are having the latency issue all at the same time? It is as if they are blaming traffic problem on I-95 for having bad congestion on I-66. It's not relevant at all!
    Verizon in-home Agent
    Must I continue?
    I will now list the solutions that others have found. Please keep in mind that these problems may not be relevant to you.
    1) Bad PON card
    Good luck convincing the verizon that this is the issue. For this to be the issue, people from your neighborhood must experience the same problem. Sadly, the problem is the latency and most people will be completely unaware of the problem as long as they are "online". There were cases where group of people resolved the problem but unfortunately the problem came back again the next day because the network tech at Verizon decided to switch them back to the old one.
    2) Faulty hardware on rack
    As far as I have been told, couple claimed that this has been the issue and was permitted to move their line into another rack.
    3) Switching Gateway IP
    One have claimed that certain Gateway IP they have been assigned are bad. For example, the house you're trying to drive away from has a huge pothole so you have to go around it by taking a detour.
    4) Resetting the ONT by unplugging the battery
    There has been claim that doing this for 5 mintues clears it up. What this actually does is it allows you to get a new Gateway IP and re-establish connections.
    5) They blocked my IP
    Yes, this can happen. I have been blocked once or more perhaps because sometimes I like to purchase and download games from Steam. When I do download, it does so for about an hour to 3 hours depending on the size of the game. Whilst this is going on, my room mate watches movie on Netflex and perhaps download music on the side. Also I watch On-Demand (requires internet). Also not to mention sometimes torrent and other P2P downloads. Check to see if you are blocked.
    6) Last but not least, Verizon is purposely gimping our latency to squeeze budget.
    There has been talks and speculations that since many primary account holders are not advance users. In otherwords, many would settle for just being "online". This supports the claims for having such a low standard for latency management in verizon. If so, Verizon must stop advertising their "fast" gaming gimmick that they display on their commercial.

  • Slow Logon Times to Business One

    One thing to look at when logon times get slower and slower in SAP Business One is your Business One inbox.   Especially if the logon takes longer before the add-ons are loaded.
    If you are using Alerts in Business One then it is possible that the OAIB and OALR tables are growing larger and larger if your users are not deleting these Alert messages from their Inbox.   The OAIB table stores the messages in the inbox and are keyed by alert and user-id. The OALR table has a record for each time a alert is fired in Business One and are keyed by Alert ID.
    If you have an Alert that is triggered (conditions are met) and that Alert goes to 5 users, then there will be 5 new records in the OAIB table. If that Alert is set up to run every 5 mins and the 'Save History" check box is marked on the Alert, then you get 5 records each and every min to the OAIB table.  5x60x24 or 7,200 records a day. A reason why it is better not to check the Save History option on your alerts. 
    If your users are checking their inbox and deleting these messages then the users OAIB, and possibly the OALR record are being deleted. If they don't check their inbox or don't delete them both tables continue to grow.   (the OALR record will not be deleted until each user message referencing that Alert ID is deleted).  So 1 user not deleting their Inbox alert messages then B1 will be keeping the OALR records.
    So how does this impact the logon time....  
    Well when you logon Business One one of the things it does after validating your user id and password is check the OAIB and OALR tables. With SQL Profiler I saw many SQL Select statements against the OALR table.  One statement for each record in the OALR table.....   In one client database I saw over 12,000 OAIB alert records for 1 user that had never been viewed or deleted. This 12,000 OAIB records meant 12,000 + OALR records which meant 12,000 individual SELECT statements against OALR at each and every sign on to Business One.   Since the user had never been taught to check their inbox and the General Setting>Services option "Display inbox when new message arrives" was turned off they never new they were getting Alerts.   This was compounded by 3 other user with similar counts in OAIB and cumulative in OALR.   Also many of the Alerts were to "OLD USER IDs" (ones that users never logged on to anymore because they had left the company) but were still generating OAIB and keeping OALR records. Many Partners allways include Manager on a Alert list and this id may no longer be used on a regular basis or even have licenses assigned anymore.
    So the remedy is to run this quick query to see if you have the problem.
    SELECT count(T0.usersign), T1.u_name from OAIB T0 INNER JOIN OUSR T1 ON T0.usersign = T1.Internal_K  Group BY T0.usersign, T1.u_name
    This should list a row fore each userid and how many records they have in the OAIB table.  If the counts are high then you should sign on to these users and delete their old Alert Messages from the inbox.   if you do this for all users then they OALR records should also be deleted. This should cut down the logon time if you have counts like this one user.
    The other thing to consider going forward is to review who is getting these alerts (remove old users and those that don't need to be informed) Also make sure that you don't have the Save History option turned on if not really required.  Also deactivate the alerts if they are no longer valid or being used.
    Hope this helps
    Dan Love  SAP

    Hi,
    In addition to my previous opinion,  I think what you suggest here is correct only if we use the query alert frequency but the system alert seems have no frequency setting.
    So, I think SAP makes it different because they want that the query alert must be restricted its frequency except system alert. This is quite confusing and can make us wondering why.
    you could see if we want to create new alert management, there is directly available frequency field and save history check box meanwhile the system alert is not.
    As a smart consultant, I think it will become a full concern why they are different.
    Rgds,

  • Extremely high memory usage on ideapad u310

    Hi all,
    I've got a problem with my ideapad u310 touch running windows 8.1. When doing completely nothing (just staring at the desktop with no programs running) my laptop uses ~55% of ram. I find this extremely high, when i open a few chrome tabs and listen to some music, maybe open a powerpoint it even rises to 80+%. My Medion erazer laptop(also running 8.1) with 4GB ram uses ~65% with the same usage and ~35% while doing nothing. I deleted almost every lenovo programm except energy management and OneKey recovery and i disabled as much programs as possible on startup but there's almost no difference.
    Now, I don't really care about the high percentages but what I do care about is that it gets extremely slow when 80% of the ram is in use. Does anybody know what i can do about this? I already tried the refresh windows option but that didn't help. Or am I just stuck with a device that has very very very poor multitasking performance.

    hi spromper,
    Welcome to Lenovo Community Forums!
    Opening Task Manager will show you which application utilizes the RAM.
    Also Doing a clean boot will help on freeing up RAM
    http://support.microsoft.com/kb/929135
    Hope this helps
    Cheers!
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Extremely high memory usage after upgrading to Firefox 12

    After I upgraded to Firefox 12, I began frequently experiencing Firefox memory usage ballooning extremely high (2-3GB after a few minutes of light browsing). Sometimes it will drop back down to a more reasonable level (a few hundred MB), sometimes it hangs (presumably while trying to garbage collect everything), and sometimes it crashes. Usually the crashing thread cannot be determined, but when it can be, it is in the garbage collection code ( [https://crash-stats.mozilla.com/report/list?signature=js%3A%3Agc%3A%3AMarkChildren%28JSTracer*%2C+js%3A%3Atypes%3A%3ATypeObject*%29] ).
    I was able to capture an about:memory report when Firefox had gotten to about 1.5 GB and have attached an image.
    A couple of things I've tried. I have lots of tabs open (though the Don't load tabs until selected option is enabled), so I copied my profile, kept all my extensions enabled, but closed all my tabs. I then left a page open to http://news.google.com/ and it ran fine for several days, whereas my original profile crashes multiple times a day.
    I also tried disabling most of my extensions, leaving the following extensions that I refuse to browse without:
    Adblock Plus
    BetterPrivacy
    NoScript
    PasswordMaker
    Perspectives
    Priv3
    However, the problem still happened in that case.
    Don't know if any of this helps or not. I'm looking forward to trying Firefox 13 when it comes out.

    hello, thanks for reporting back with detailed information.
    from a brief look at your extensions i don't recognize any known (to me at least) memory leaking ones. in the last weeks there were also reports about the java plugin causing high memory consumption in combination with firefox 12 - in case you have it installed in firefox > addons > plugins try disabling it for a few days & test how firefox is behaving with many tabs.
    & although probably not related to the memory problems you could update your graphics driver to get better results with hardware acceleration in firefox - this is the latest driver by intel for your model & os:
    [http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21135&lang=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=Drivers]

  • EXTREMELY HIGH URGENT!!!

    Hi! SAP GURUS!
    We've got the following trouble:
    Event Type: Error
    Event Source: SAPDB:T11
    Event Category: Fast
    Event ID: 18606
    Date:  24.03.2008
    Time:  17:18:47
    User:  NT AUTHORITY\SYSTEM
    Computer: SAP-1
    Description:
    The description for Event ID ( 18606 ) in Source ( SAPDB:T11 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SAPDB - T11; :
    - ERROR   TID: 0xE0  PID: 0xEC8  MsgID: 18606
      ; Could not find account name, Location: 1, rc = 1789.
    What is the problem and what the solution can be?

    Hi Anton,
    as forums cannot guarantee quick answers please don't shout words like "extremely high urgent" and abuse the exclamation marks...
    Instead (if you're are SAP customer): open a support message. If it is really an emergency, set the priority to very High - the message will be answered.
    About your technical problem: well the returncode (rc = 1789) points to some network authentication issues.
    Perhabs you should check MS technet [here|http://support.microsoft.com/?scid=kb%3Ben-us%3B823659&x=11&y=9] (scroll down or search for 'error 1789').
    KR Lars

  • File size extremely high for .avi after render PE 9

    I'm very new to PE and have tried to learn quick to redact info (faces etc) in .avi files for a government agency. I was able to open the file (in the trial version) and make the track matte by dragging the original file to the timeline then dragging it again to the video 2 timeline for the top layer, Question 1) is this the same as copy and paste or am I doubling the size already? Anyway, I was able to get the matte and everything done. Now, to Render and save... I choose computer/avi again (I need to keep it the same) and it took 1 hr 45 min to render it, that seemed long to me but maybe not... but mainly the file size was then 100,883 kb! Starting with a 29.7 kb file. This is what my question is about....could this be right? I can't use it if this is what I get. So, here are the particulars as I got G-spot and looked it up, as per serveral suggestions I saw here. I'm trying to understand the CODEC info but I fear I have a ways to go before I can figure out what I did wrong. (This is my test computer, the future work would be done on a newer, better computer).  The videos I would be working with come from various sources and will vary in length but will probably all be a kind of avi.
    Intel Pentium processor 1600 mhz
    221 mhz, 2.00 gb ram
    Microsoft windows xp sp3
    video:
    length: 0:27.261
    frms:  817
    Kbps: 28770
    pic:  720x480
    codec: dvsd dvc/dy
    I appreciate any help you can give

    Thanks for you response and the information was very helpful. I was able to choose and output that gave me a good file size and I do want DV-AVI (I don't remember what I chose but it worked) but, I don't see an option for DV-AVI - is that a general DV output selection, because there seem to be numerous (AVCHD, NTSC, DV STANDARD) acronyms (I have tried to understand what each is) which do I want?
    From: Bill Hunt <[email protected]>
    To: Mid Century Modern <[email protected]>
    Sent: Wednesday, September 28, 2011 6:07 PM
    Subject: File size extremely high for .avi after render PE 9
    Re: File size extremely high for .avi after render PE 9 created by Bill Hunt in Premiere Elements - View the full discussion
    For the use of Track Matte Keying, with say a Gaussian Blur, or maybe Moasic Effect, if you have not altered the In & Out Points, then just dragging the Asset to both Video 1 and Video 2 will work fine. If you HAVE adjusted the In & Out Points, you can just click-drag from the Source Monitor, where you set those In & Out Points, and all is good. The Copy/Paste is just another way to do it.
    As you are doing an "overlay," the output File Size will not be affected in any way. You are also limiting the Blur, or Effect on Video 2 to just the area "exposed" by the Track Matte, so the pixel count will not be altered.
    As Steve points out, the output CODEC in the AVI will determine the output File Size. File Size is basically determined by the Timeline's Duration and by the Bit-Rate of the output file. With DV-AVI, that Bit-Rate is pretty well set, and your Timeline determines the Duration. At ~ 13GB/hour, a DV-AVI will be pretty large, but that is the nature of the beast. Also, and as Steve points out, if you are going to do additional editing, and will be Importing that file into a New Project, DV-AVI is about as good, as it gets.
    Good luck,
    Hunt
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/3943683#3943683
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/3943683#3943683. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Premiere Elements by email or at Adobe Forums
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Update work process has too high respose time.

    Our functional team is facing issue while saving data in va03 transaction. IT prompts Sales order saved successfully and when we go to va02 and try to open getting error Document "SD document not in database or has been archived"
    So when I checked sm66 update WP is on hold due to RFC response. and in st03 it has high response time
    Task          steps  response time                                             wait time
    UPDATE2    2       1.130,0               335,0    65,0    724,0    0,0    0,0                0,0    0,0    70,5
    UPDATE    29        1.188.035,2       19,6    8,6    35,9    0,0         1.187.979,4    0,0    0,0    0,3
    Also in SM13 all updates are at Initial status. Nothing get updated in database.
    Please help as functional team is no more able to work and as basis person We need to resolve the same.

    Hi Spr,
    Please check the following
    1) Update has status active in SM13
    2) You have enough space in the oraarch directory
    3) You have enough space in tablespaces
    4) Check for any error message on in alert_<SID>.log file
    5) Update oracle dictionary, missing and all statistics in the database.
    Hope this helps.
    Regards,
    Deepak Kori

  • Extremely high 3g traffic since updating my iPhone 4 to iOS 5

    Hi!
    Since I updated my iPhone 4 to iOS 5.0 I recogniced that my device is generating extreme high amounts of traffic on 3G.
    Sometimes 60MB each day (= 1,8 GB traffic per month, but only 1GB data option, could get expensive)!!! Before updating I had this traffic in about a week or so.
    I have already shut down ALL sync services, I am not logged in to GameCenter or other services.
    Before updating to iOS 5.0 I also used Twitter & FANCY and so on, these apps generates a lot of traffic when using them several times each day.
    Now I have already deleted Twitter and FANCY and some other apps and anyway the traffic generated by the OS itself is really huge!!!
    Anyone has the same problem or anyone can help me finding the reason for this high traffic in iOS 5.0??
    Also some location services are permanently running and are killing the battery within a day... Why are they always turned on?
    Now I turned off all location services and the battery life is still bad - only 1,5 days with low usage (former 3 or 4 days)...
    Please help!!
    Thanks in advance,
    Wolfgang

    Hi Urs
    I searched a lot and maybe found a part of the reason for this high data traffic.
    I'm synchronizing my contacts, calendar & reminder with iCloud & my mail with Hotmail.
    When push is activated for Hotmail, that doesn't matter, but when push is activated for iCloud, the amount of data nearly explodes. So I turned iCloud to manual and let Hotmail on push.
    Contacts, calendar & reminder are synchronizing when opened (I think this is enough).
    Also I do a backup on iCloud and than I deactivate the function (I do not delete the last backup, I only deactivate the option for automatic backup).
    It seems, that the backup functionality also generates traffic when not on WiFi - especially at night!!
    The battery life has been getting better, when I deactivated the support for automatic time zone changes (location services were always on).
    The battery finaly got MUCH BETTER since the update on iOS 5.0.1.
    My traffic is actually higher than on iOS 4 but not so high as before I deactivated some services...
    I hope this info is a little help for you!!
    Let me know if this works for you, ok?
    Best regards,
    Wolfgang

  • High GUI time in ST03

    I found high GUI time in ST03.
    Example: In last minute's load --> workload overview -->
    Start of interval  27.10.2008  07:43:00
    End of interval    27.10.2008  07:58:00
    Time period        0   Day(s)  00:15:01
    I found 1280ms Roll wait time and 1280 GUI time. It seems too high. How can I find what cause it? how can I locate the root case?
    Please advise. Thanks so much.
    James

    Hi,
    Here are the few things to check when the GUI time is high.
    1. Check in ST03--> Transaction Profile the Tx SESSION_MANAGER may be on top id yes, the load caused by the transaction SESSION_MANAGER, combined with the high roll in + wait time could indicate that the SAP Easy Access menu might not be configured correctly and should be tuned to improve overall response times. It is also possible that your users have been assigned disproportionately large user menus. We advise you to ensure there are a reasonable number of entries (nodes) in the User Menu.
    Generally, its recommended that users should have no more than 1000 and as an absolute maximum 2000 menu nodes configured, (for comparison, the complete SAP menu contains 70,000 entries).  A high number of entries may lead to high memory consumption on the server and to long response times for the menu. Refer to SAP Notes 203617 and 203994 for details
    2. ST06 --> Detail Analysis Menu --> Lan check by Ping with more than 10 Presentation
    servers.
    See the Average and Loss coloumn and check wether is there any problem exits.
    However, review the following recommendations to identify any network issues. Given below are the response times which are thresholds for a good network performance.
    Recommendation: Characteristic response times are:
    -  In a local area network (LAN) : <20 milliseconds
    -  In a "fast" Wide Area Network (WAN) (for example, 256 or 384 KBit/sec):   < 50 milliseconds
    -  In a "slow" wide area network (WAN) (For example, 128 KBit/sec or less): < 250 milliseconds
    -  Losses of data packets ("Loss") should not occur at all.
    Review SAP Notes 203924 (under subheading 'General Performance Analysisu2019), 8963 and 578118 for further information on SAP GUI and response time components.
    In case of long response times due to performance problems in the network (in particular when using SAPGUI in WAN), you should use configuration "Low Speed Connection" in SAPLOGON. As a result, menus are only transferred on request, and the quantity of the transferred data is reduced correspondingly. This measure reduces the network load significantly. You can find this setting option under: SAPLOGON -> PROPERTIES -> ADVANCED.
    Option for a low speed connection:
    On a low speed connection (LSC) to the network, the benefits of the improved interaction design may be outweighed by increased response times due to the heavier network traffic. To counterbalance this effect, SAP has introduced the option for a low speed connection to the network in Release 4.6. A flag can be set in the options of an SAP logon connection item or on the SAP GUI command line. This action has the following effects:
    -  Menus are loaded only on demand as before
    -  Background Bitmaps are not transferred (depending on the application)
    -  The list control transfers only the lines that are visible on the screen
    -  The application can query the flag to react to the network condition individually.
    Examine the following SAP Notes and verify that the SAP recommendations contained are fully implemented:
    -  SAP Note Number 161053   Low Speed Connection is in use
    -  SAP Note Number 164102   Network load between application servers +camera front end
    -  SAP Note Number   62418   Network Load of SAPGUI Frontend Communication (Required Bandwidth).
    Please let me know if the performance improves.
    Thank you,
    Tilak

  • Very long (10min+) logon time on clients

    Hi!
    Around 2 weeks ago our employees started to report that some macbooks/imac's (with maverick ob board) have very long logon time - 10min+ "spinning wheel" after home sync.
    Issue is related only to couple of client machines. Upgrade from Maverick To Yosemite fix the issue, but only for couple of days! Then issue re-occuring on the machines again. It's not related to the mobile profile, sync is very fast, "spinning wheel" appear after the sync and spiining for another 10+ minutes.
    Our infrastructure:
    - OS X Maverick (10.9.4) + Server 3.1.2
    - clients machines - 30+ machines, maverick and couple of yosemites.
    - Open Directory/File Sharing/Profile Manager on Server
    - Mobile Profiles on clients with enabled syncing during logon/logoff only.
    I noticed those errors during the "spinning wheel" (log gathere on server, not client):
    Nov 13 11:10:28 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:56766 for host/[email protected] [canonicalize, forwardable]
    Nov 13 11:10:28 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:10:28 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:54978 for krbtgt/[email protected] [forwardable]
    Nov 13 11:10:28 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:10:29 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:63166 for host/[email protected] [canonicalize, forwardable]
    Nov 13 11:10:29 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:10:29 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:51181 for krbtgt/[email protected] [forwardable]
    Nov 13 11:10:29 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:16:32 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:54374 for host/[email protected] [canonicalize, forwardable]
    Nov 13 11:16:32 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:16:32 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:50691 for krbtgt/[email protected] [forwardable]
    Nov 13 11:16:32 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:16:33 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:58251 for host/[email protected] [canonicalize, forwardable]
    Nov 13 11:16:33 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:16:33 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:53871 for krbtgt/[email protected] [forwardable]
    Nov 13 11:16:33 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:16:32 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:16:32 odmaster.OURDOMAIN.com kdc[54]: TGS-REQ [email protected] from 192.168.1.232:50691 for krbtgt/[email protected] [forwardable]
    Nov 13 11:16:32 odmaster.OURDOMAIN.com kdc[54]: Server not found in database: krbtgt/[email protected]: no such entry found in hdb
    Nov 13 11:16:33 odmaster.OURDOMAIN.com kdc[54]: AS-REQ [email protected] from 192.168.1.232:64393 for krbtgt/[email protected]
    Nov 13 11:16:33 --- last message repeated 1 time ---
    Nov 13 11:16:33 odmaster.OURDOMAIN.com kdc[54]: AS-REQ [email protected] from 192.168.1.232:65181 for krbtgt/[email protected]
    Nov 13 11:16:33 --- last message repeated 1 time ---
    Please advise. We would like to not upgrade/migrate to Yosemite for now.

    Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
    1. The OD master must have a static IP address on the local network, not a dynamic address.
    2. You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
    3. The primary DNS server used by the server must be itself, unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
    4. Follow these instructions to rebuild the Kerberos configuration on the master.
    5. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases. Otherwise delete all certificates and create new ones.
    6. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
    7. Reboot the master and the clients.
    8. Don't log in to the server with a network user's account.
    9. Disable any internal firewalls in use, including third-party "security" software.
    10. If you've created any replica servers, delete them.
    11. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.
    If you get this far without solving the problem, then you'll need to examine the logs in the Open Directory section of the log list in the Server app, and also the system log on the clients.

Maybe you are looking for