From: PatrickC on 21 Dec 2006 09:09 SBS2003 Exchange Newbie here, I've inherited an server here and noticed this month that the temp folder is filling up with MONxxxx.tmp files. Once a day at 4:30am, a half GB file gets dumped there. I know how to fix it by moving the temp enviroment variable, but can't at the moment since there's only one drive and one partition. The question is are those MON temp files safe to delete so I can keep it going until I get another drive installed? Thanks, Patrick
From: "Inn Jin [MSFT]" on 22 Dec 2006 00:55 Hi Patrick. Thank you for posing. From your description, I understand you want to delete MONxxx.tmp files in Windows\Temp folder, since they occupied a lot of disk space, and want to know whether it is safe to delete them. If I am off base, please don't hesitate to let me know. Base on my knowledge, all file under %systemroot%\windows\temp folder can be deleted without causing any problem, these MONxxx.tmp files may be created by some third-party applications, as it exist under temp folder, please feel free to delete them. Related information: 253597 Automating Disk Cleanup Tool in Windows http://support.microsoft.com/kb/253597/en-us I appreciate your time. I am happy to be of assistance to you and look forward to your reply. Have a nice day! Best regards, Inn Jin (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ===================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
From: PatrickC on 22 Dec 2006 09:11 Hello Inn, Thanks for your input. I've deleted some of the older MON temp files with no ill effects so far. The server runs SBS2003 with exchange, Symantec CE, and SQL and that's about it. Strange how this left those files every couple of months for the past 2 years, then every morning this month. Thanks again, Patrick
From: "Inn Jin [MSFT]" on 25 Dec 2006 03:04 Hi, Patrik. Thank you for updating. I appreciate you followed our suggestion. You said you want to know what the MONxxx.tmp files are and why did they generate periodically? Base on my knowledge, Microsoft's products do not generate these files, it should be generated by the third-party applications, I am sorry for that we are not familiar with third party applications. It is better way to contact the software vendor for support. Your understanding is appreciated. If you want to know how these files generates, I suggest you use Filemon tool to monitor the temp files creation process to find the root cause. Filemon and Regmon are free monitoring utilities from http://www.microsoft.com/technet/sysinternals/default.mspx available for download. They allow you to monitor file and registry access on a machine. When you start either one of these utilities (Filemon.exe,Regmon.exe), you will notice that they start monitoring activity on your machine right away. Are goal in running these utilities is to capture file and registry activity during the sequence of events that causes the problem you are experiencing. Please use the following steps to capture data with these utilities. You will need to follow the steps below for both utilities. Download page: http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx I suggest you view the above filemon tool introduction information and run the Filemon application for 24 hour to monitor the process. NOTE: In order to see minimal traffic from the utilities close all other applications that are not involved in the test and use filter dialog to filter .tmp data; And also you can check those Monxx.tmp file created time period and run the Filemon tool during that time period in order to minimize traffic. You can create a task schedule to do that. From the data, I believe you can find the cause. I appreciate your understanding and cooperating, if you have further concern on this issue, please feel free to let me know. Have a nice day and Merry Christmas! Best regards, Inn Jin (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ===================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
From: PatrickC on 15 Jan 2007 12:11 Hi Inn, Thanks for the FileMon util. It did show me that mssbsssr.exe is responsible for the MONxxx.tmp file creation. Now I have to find out why it's intermittantly creating these 488MB temp files. I'll try the RegMon next. Thanks again, Patrick ""Inn Jin [MSFT]"" wrote: > Hi, Patrik. > > Thank you for updating. > > I appreciate you followed our suggestion. You said you want to know what > the MONxxx.tmp files are and why did they generate periodically? Base on my > knowledge, Microsoft's products do not generate these files, it should be > generated by the third-party applications, I am sorry for that we are not > familiar with third party applications. It is better way to contact the > software vendor for support. Your understanding is appreciated. > > If you want to know how these files generates, I suggest you use Filemon > tool to monitor the temp files creation process to find the root cause. > Filemon and Regmon are free monitoring utilities from > http://www.microsoft.com/technet/sysinternals/default.mspx available for > download. > > They allow you to monitor file and registry access on a machine. When you > start either one of these utilities (Filemon.exe,Regmon.exe), you will > notice that they start monitoring activity on your machine right away. Are > goal in running these utilities is to capture file and registry activity > during the sequence of events that causes the problem you are experiencing. > Please use the following steps to capture data with these utilities. You > will need to follow the steps below for both utilities. > > Download page: > > http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx > > I suggest you view the above filemon tool introduction information and run > the Filemon application for 24 hour to monitor the process. > > NOTE: In order to see minimal traffic from the utilities close all other > applications that are not involved in the test and use filter dialog to > filter .tmp data; > And also you can check those Monxx.tmp file created time period and run the > Filemon tool during that time period in order to minimize traffic. You can > create a task schedule to do that. > > From the data, I believe you can find the cause. > > I appreciate your understanding and cooperating, if you have further > concern on this issue, please feel free to let me know. > > Have a nice day and Merry Christmas! > > Best regards, > > Inn Jin (MSFT) > > Microsoft CSS Online Newsgroup Support > > Get Secure! - www.microsoft.com/security > ===================================================== > This newsgroup only focuses on SBS technical issues. If you have issues > regarding other Microsoft products, you'd better post in the corresponding > newsgroups so that they can be resolved in an efficient and timely manner. > You can locate the newsgroup here: > > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx > > When opening a new thread via the web interface, we recommend you check the > "Notify me of replies" box to receive e-mail notifications when there are > any updates in your thread. When responding to posts via your newsreader, > please "Reply to Group" so that others may learn and benefit from your > issue. > > Microsoft engineers can only focus on one issue per thread. Although we > provide other information for your reference, we recommend you post > different incidents in different threads to keep the thread clean. In doing > so, it will ensure your issues are resolved in a timely manner. > > For urgent issues, you may want to contact Microsoft CSS directly. Please > check http://support.microsoft.com for regional support phone numbers. > Any input or comments in this thread are highly appreciated. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. > >
|
Next
|
Last
Pages: 1 2 Prev: Slightly OT - Event ID 12302 - WSS error Next: Backup fails suspect VSS problem |