No ideas what they're for, but if it's continuing to happen and you need to find out, my suggestion would be to review the time stamps on the files, find the IP addresses in the Management Points IIS logs, then connect to those IP addresses and see what's going on with the clients. The time stamps may not line up exactly as it's file time creation, not necessarily when the client sent the file, but you'll get close enough to get an idea what they're being created for, if it's client data which it seems like it is.
From: [email protected] [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Monday, October 26, 2015 8:20 AM To: [email protected] Subject: RE: [mssms] SMF files accumulating in Statesys inbox But seriously Jason, any ideas? That inbox has crept up to 7,900 items now. The smf files are all empty. From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, October 23, 2015 3:35 PM To: [email protected] Subject: RE: [mssms] SMF files accumulating in Statesys inbox Do you like watching paint dry also? How about grass growing? ;-0 From: [email protected] [mailto:[email protected]] On Behalf Of Nick Sent: Friday, October 23, 2015 9:51 AM To: [email protected] Subject: RE: [mssms] SMF files accumulating in Statesys inbox I stared at our inbox for a while and did not see any SMF files coming in our inbox at the time I was staring. From: [email protected] [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Friday, October 23, 2015 9:15 AM To: [email protected] Subject: RE: [mssms] SMF files accumulating in Statesys inbox Hey Nick, thanks for looking. We already had our summarization turned down to every 8hrs and our CPU utilization is sitting pretty good. Right now the inbox is still sitting steady at around 5400 items, with other things processing in and out. I'm thinking that most of these are now just bad or corrupted messages from when the server was overloaded the other day. My google-fu is failing me in finding a good description of what these smf files are for and if it matters if we delete them. From: [email protected] [mailto:[email protected]] On Behalf Of Nick Sent: Thursday, October 22, 2015 5:53 PM To: [email protected] Subject: RE: [mssms] SMF files accumulating in Statesys inbox Hey Jeff, We had issues with Software update summarization schedules which caused lots of processing on the site server and created a backlog in the statesys directory. The solution was to change the software update summarization schedules to once per day instead of once per hour. Here's a link I had in my notes. https://social.technet.microsoft.com/Forums/ar-SA/5a8adf02-7e9f-40e2-b849-f7 c6135d7312/sum-update-status-summarizer-consumes-100-cpu-every-hour-for-15-m inutes?forum=configmanagergeneral From: [email protected] [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Thursday, October 22, 2015 9:51 AM To: [email protected] Subject: [mssms] SMF files accumulating in Statesys inbox Having an issue with a large amount of smf files accumulating in the statesys inbox. I can see that it is processing smx files without issue, but the SMS_STATE_SYSTEM component is in a critical status due to this back log. From the statesys.log file I have the following errors: >From the statesys.log: SQL MESSAGE: spProcessStateReport - Error: Message processing encountered an error parsing the report XML: Root element is missing. SMS_STATE_SYSTEM 10/22/2015 6:51:15 AM 41816 (0xA358) CMessageProcessor - Non-fatal error while processing N_891d7faf-ddf4-4973-985c-fde1b62b57cc_{84EBFABF-8901-42F0-A170-84E2574EA4A3 }_800_HFH.SMF SMS_STATE_SYSTEM 10/22/2015 6:51:15 AM 41816 (0xA358) >From the status message viewer: The State System message file processing could not process file 'N_891d7faf-ddf4-4973-985c-fde1b62b57cc_{84EBFABF-8901-42F0-A170-84E2574EA4A 3}_800_HFH.SMF' and moved it to the corrupt directory. Review the statesys.log file for further details. The backlog of files is around 5400 in the statesys>incoming box. We did experience a major issue with our primary server the other day, a process was taking up all the CPU cycles and caused the server to become unresponsive and was very behind on processing inbox items. Once we resolved the issue with the CPU utilization it took 6-8hrs to get caught back up and become responsive to clients requests again. Everything is running find now, but except for the component status and back log of smf files. I also have not been able to find a good description of what the smf files are for, it it's safe to delete them? Etc. Jeff Krueger [email protected] 248.853.4466 IT - Solutions Design Team Henry Ford Health System _____ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
