Post in A sporadic but re-occurring problem with our Thermo QExactive plus unit: ABRF Discussion Forum: ABRF Discussion Forums

Hi, a few years ago we suffered from a similar chronic problem - our runs would abort sporadically and we never knew when it would happen. We have a Dionex Ultimate 3000 LC connected to a Q Exactive and the problem seemed to be coming from the autosampler. Replacing the cable connecting the LC to the computer did not help. In the end we replaced the whole autosampler (it cost around $18,000). Since then the system has been behaving very well - 4 years now..... Bill Breuer Proteomics/Mass spectrometry Unit, Institute of Life Sciences, Edmond J. Safra Campus - Givat Ram, Hebrew University of Jerusalem, Jerusalem, 9190401 Israel

On Thu, Nov 18, 2021 at 4:28 AM Susie <email obscured>> wrote: > Do you have an automatic update function turning on for your mass spec PC? > Can you turn it off? If you Google the cited language，people are taking > about proxy settings. You may want to adjust that, but take careful notes > for what you change d, so you can always change back. > > Not sure this helps or not. Unless the lab policy has requirements for LIMS > and online data transfer, my approach for mass spectrometers is do not go > to internet unless it is very necessary. Our IT folks don't like it, but I > am able to bypass the IT folks that my mass spec does not need internet. > When I need internet, we use wireless jump drives. > I am not an individual who believes "ware" updates for mass spec. Many > years ago, I lost my confidence after our GCMS service engineer convinced > me to update my firmware when he was doing our PM. I ended up with losing > all my methods and had to rebuild all of them. > Susie > > > > On Wed, Nov 17, 2021, 5:42 PM Kym Faull <email obscured>> wrote: > > > > Dear Colleagues: We have a problem with our LC/MS QE instrument. > Long > > ago we had a problem with it in which every Thursday morning at the same > > time the instrument would quit because of some glitch with the internet > > connection. We concluded that a strange signal from the internet was > > causing the instrument to quit. We implemented a work-around in which > the > > internet connection was disabled for the time around when this was > > happening, and the connection was re-established after the elapsed time. > > This work-around worked for a long time with occasional instances at > other > > times when the problem would sporadically pop-up. The situation has > > recently changed. The hiccup is now occurring frequently. It has > recently > > occurred 10 times in 4 days. The error messages that are reported are > > copied below. Of course we have been run touch with Thermo people, but > so > > far the problem has not been solved. Any and all advice about this will > be > > greatly appreciated. > > > > Kym > > > > > > Kym Francis Faull, Ph.D. > > Director, Pasarow Mass Spectrometry Laboratory > > Jane and Terry Semel Institute for Neuroscience and Human Behavior at > UCLA > > Professor Emeritus on Recall, Department of Psychiatry and Biobehavioral > > Sciences > > David Geffen School of Medicine at UCLA > > Telephone: (310) 206 7881 (office) > > Telephone: (310) 206 7886 (laboratory) > > Facsimile: (310) 206 2161 > > Electronic mail: <email obscured> <email obscured>> > > > > > > > > > > > > > > > > > > > Begin forwarded message: > > > > > > From: Julian Whitelegge <email obscured>> > > > Subject: Re: we need help > > > Date: November 16, 2021 at 1:28:57 PM PST > > > To: Kym Faull <email obscured>> > > > > > > Kym, Have you tried posting the error message on the ABRF site ? I > can’t > > believe we are the only ones with this problem... Julian > > > > > >> On Nov 16, 2021, at 1:26 PM, Kym Faull <email obscured> <mailto: > > <email obscured>>> wrote: > > >> > > >> Kent: We have done everything you suggest and the problem still > > occurs. Sometimes it occurs shortly after setting a worklist running, > and > > last weekend it ran uninterrupted from Friday until sometime on Sunday > when > > it quit. Attached below is the error message that appears when the > > problems occurs. We don’t know what t o do next, Can you help us? > Before > > we request a visit from a service engineer I thought a ZOOM or WEbEX > > “meeting” might be the next thing to try. > > >> > > >> > > >> Kym > > >> > > >> > > >> > > >>> Begin forwarded message: > > >>> > > >>> From: whitaker cohn <email obscured> <email obscured>>> > > >>> Subject: Fw: QE Error Message > > >>> Date: November 11, 2021 at 9:03:33 AM PST > > >>> To: Kym Faull <email obscured> <email obscured>>> > > >>> > > >>> The QE turned off again last night. These were the error messages at > > the time of the event: > > >>> > > >>> -Info Service 18:40:20.142-07:00 on 2021-11-04 Starting > > acquisition > > >>> > > >>> -Warning Service 19:49:55.603-07:00 on 2021-11-04 reading > > data: A connection attempt failed because the connected party did not > > properly respond after a period of time, or established connection failed > > because connected host has failed to respond > > >>> > > >>> -Warning Service 19:49:57.069-07:00 on 2021-11-04 reading > > data: A connection attempt failed because the connected party did not > > properly respond after a period of time, or established connection failed > > because connected host has failed to respond > > >>> > > >>> -Warning Service 19:49:57.132-07:00 on 2021-11-04 reading > > data: A connection attempt failed because the connected party did not > > properly respond after a period of time, or established connection failed > > because connected host has failed to respond > > >>> > > >>> -Error Instrument 19:50:04.601-07:00 on 2021-11-04 > > [Inspect/Networking/Control handler] No network connection to data system > > (s) > > >>> > > >>> I think we need to focus on remedying "A connection attempt failed > > because the connected party did not properly respond after a period of > > time, or established connection failed because connected host has failed > to > > respond". Not sure how to do this. Maybe Boston has some ideas. > > >>> > > >>> This also occurs when the instrument is not connected to the > internet. > > It would be great if these error messages could be shared among the > Thermo > > instrument technicians. Somebody has to have encountered this before... > > >>> > > >>> Sincerely, > > >>> Whitaker > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> Whitaker Cohn, B.S. > > >>> Ph.D. Candidate > > >>> Drug Discovery Lab > > >>> Pasarow Mass Spectrometry Lab > > >>> UCLA | Molecular, Cellular & Integrative Physiology Program > > >>> (818) 268-5795 > > >>> > > >>> > > >> > > > > > > > > > ―― > > View topic http://list.abrf.org/r/topic/60topbHh4FJLQCk1kNc0nI > > Leave group <email obscured>?Subject=Unsubscribe > > > > > > ―― > View topic http://list.abrf.org/r/topic/7v6CfBG8ylP1UORGjfrhTe > Leave group <email obscured>?Subject=Unsubscribe > >