The TMS servers at the Yale Center for British Art are running on Windows Server 2016.
Last week our Registrars experienced the same TMS crash problem when linking a file to media in the loans module (drag/drop). Also, the new file was linked after restart TMS.
First we rolled back the bad service pack that caused the TMS problems and tested. Drag/drop in the Loans module worked again without crashing TMS.
Second we installed the latest service pack that is supposed to fix the TMS crash problem and tested.
Again, we are able to link files in the Loans module without crashing TMS.
I would check with Gallery Systems to make sure the correct service pack is being applied to your server.
Good luck.
David Parsell
Systems Manager Information Technology
Yale Center for British Art
1080 Chapel Street
PO Box 208280
New Haven, CT 06520-8280
2032140986
britishart.yale.edu
Connect on
Facebook,
Twitter,
Instagram,
YouTube,
and Snapchat @yalebritishart #YCBA
ON VIEW
Eileen Hogan: Personal Geographies
May 9–August 11, 2019
Art in Focus: Blue
April 5–August 11, 2019
Tony Foster: Watercolor Diaries, Cornwall to Colorado
May 30–August 25, 2019
UP NEXT
Photographs | Contemporary Art: Recent Gifts and Acquisitions
June 20–September 8, 2019
From: The Museum System (TMS) Users <[log in to unmask]>
On Behalf Of Lindsey Richardson
Sent: Thursday, September 19, 2019 11:56 AM
To: [log in to unmask]
Subject: Re: TMS Issues Persisting after Microsoft Patch
We’re continuing to have the odd problem of crashing the entire program when trying to add a media file to a record in the Loans module or trying to right-click in the Loans module.
The stripes of death appear and the whole program closes. But when you open it again, the media file is there!
This was not fixed by the patch.
Lindsey Richardson
|
Curator of Collections
The Sixth Floor Museum at Dealey Plaza
411 Elm Street, Dallas, TX 75202-3308
Phone: 214.747.6660
|
Direct: 214.389.3061
From: The Museum System (TMS) Users <[log in to unmask]>
On Behalf Of Morgan, Rob
Sent: Thursday, September 19, 2019 7:42 AM
To: [log in to unmask]
Subject: Re: TMS Issues Persisting after Microsoft Patch
ATTENTION: The following correspondence is from an external source. Please be cautious when clicking on links or opening attachments.
Here at the Smithsonian, after the August Windows security update/upgrade -- for us, Windows 10 Education, version 1803, Build number 17134.950 -- opening the Accession Lot would cause TMS to crash. In addition,
users would see error messages if they tried to open the Events module, or enter data in the Exhibitions module.
These problems are fixed by the September Windows update (for us Windows 10 Education, version 1803, Build number 17134.1006). Also, computers that did not download the August Windows update, and were last
updated with the July update (Build number 17134.885) experienced no problems.
-
Rob
From: The Museum System (TMS) Users <[log in to unmask]>
On Behalf Of Bomgardner, Renee
Sent: Thursday, September 19, 2019 8:28 AM
To: ListServ tmsusers <[log in to unmask]>
Subject: TMS Issues Persisting after Microsoft Patch
Good Morning,
I’m reaching out to see if other TMS users are having issues after applying the Microsoft patch. We are running TMS2014 with remote desktop access. Our HelpDesk has verified
the users computers are up to date with definitions and the server is up to date as well.
These issues have mainly surfaced with the registrar’s causing them to be unable to access the Accession Lot Tool (it crashes when you try to open the window), receiving
an error message in the Exhibitions Module when trying to add a constituent, runtime errors, slowness with opening the object package window and changing between views.
Any advice would be appreciated?
Best,
Renee
Renee
Bomgardner
Collection Information Manager
Philadelphia Museum of Art
Information & Interpretive Technologies
t
215-684-7288
PO Box 7646, Philadelphia, PA 19101-7646
philamuseum.org
| @philamuseum
To unsubscribe, send an email to
[log in to unmask] with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to
[log in to unmask] with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not
the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by
Mimecast Ltd.
To unsubscribe, send an email to
[log in to unmask] with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.