Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Tuesday, January 12, 2016 4:09 AM | 4 votes
Every time a save a word document it creates a folder. I can delete the folders created but it's a nuisance to keep deleting folder after folder. Inside the folder will be Word Work File D_1.tmp but goes away but the folder will remain. I was wondering if there is a fix for this issue
Wednesday, January 13, 2016 12:36 PM
Hi,
Generally, the .tmp file is the temporary files. Generally, a temporary file is a file that is created to temporarily store information in order to free memory for other purposes, or to act as a safety net to prevent data loss when a program performs certain functions.
I am not sure why your Word for Mac 2016 create the temporary file in a new folder. I suggest we can use a "clean startup" to determine whether background programs are interfering with Office for Mac, then confirm if the issue persists.
https://support.microsoft.com/en-us/kb/2398596
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Winnie Liang
TechNet Community Support
Thursday, July 14, 2016 4:21 PM | 8 votes
I don't understand why this has been marked as an answer. It's not even a work around. At best it is a troubleshooting measure. But the OP has never come back to report if he found the culprit.
We too have the problem but very sporadic and we don't know how to repropduce the error. So this approach dosn't help us at all.
I also wonder how other software could interfere? Preventing Office from deleting the folder? Or causing Office to create the folder in the wrong place or with he wrong permissions? Clearly as employees of the company that created the program, you should be able to shed some more light on the issue and give some hints on what kind of "background process" one has to think of.
"I am not sure why your Word for Mac 2016 create the temporary file in a new folder." - The answer lies in the code! There must be the ifs and elses that test the conditions and decide to put the folder where we find them.
This said, I of course appreciate your help very much. Where would we poor supporters be if we had not the backup of knowledgeable people like you. Thank you.
Roger
Thursday, July 21, 2016 12:51 PM
I never had this problem until I turned on the autosave feature and selected to have a backup made of the original document. So I guess Microsoft uses the folder for the backup file location. Which, if you think about it, is a pretty sweet feature. I tried to add an attachment but could not, sorry. But it shows that for three files that I opened and modified there was a folder created and in that each folder is a file that begins with the word "Backup ..."
Hope that helps!
Thursday, April 6, 2017 7:11 PM | 1 vote
We have this problem, too. I am on a mac. The temp folders remain and I have to manually delete them.
Friday, April 14, 2017 9:18 PM | 1 vote
I also have this problem. I keep deleting them but they continue to pop up like gophers. Please MS fix this issue.
Sunday, July 9, 2017 3:09 PM | 2 votes
I have the same problem. Have tried a number of fixes to no avail. But there has been one change. It used to create the unnecessary folder and put the document in it. Now Word for Mac creates and unnecessary folder for every file and leaves the folderempty.
Saturday, August 26, 2017 7:12 PM | 1 vote
This is still happening. The backup copy is put in a new folder with the same name as the file. I end up with a proliferation of backup folders. I have to move the backup copy into the parent folder and then delete the backup folder.
Tuesday, September 5, 2017 9:28 PM | 2 votes
This seems to be how Word 2016 is now saving backups when you check "always create backup copy" under Preferences and Save - by creating a folder with that same file name and placing it next to the backed-up file. In my case, the extension for the backup files within the folders is .docx, not .wbk. The problem is, these folders causeconfusion and clutter. I have tried going into Preferences, File Locations and changing the location for AutoRecover files, but this has no effect - I guess that's a different feature. After a few weeks of use, there is nothing in my designated folder for AutoRecover files and word is still creating the backup folders. Microsoft needs to clarify how we can choose and set the location of our backup files. I'm also confused as to why Word tech wouldn't know about this feature and how it works. I've consulted someone by phone as well and they weren't familiar with it.
Thursday, October 5, 2017 9:20 AM
Any luck finding out why these folders appear and why they don't get deleted?
Monday, October 16, 2017 4:37 PM | 1 vote
I've just had a client show up with the same exact issue, it's just leaving the folders there, after going through all sorts of forums and troubleshooting, I thought perhaps it was server side issue with the filesystem as to why it wouldn't delete the files, but it has reoccurred on a different share with a different user at the same client.
This topic is definitely not yet answered.
The question that probably needs to be answered: Is there a way to turn off this automatic folder creation for network share files, or a way to set a manual path for these backup/temp files to the local filesystem temp folders instead of the active folder the file is opened from?
Tuesday, October 17, 2017 9:44 AM | 1 vote
Just to expand on my experiences:
There's no setting for this as this is something that ONLY happens when your Mac is saving Office documents (Excel/Word) against a mapped network folder (SMB or AFP) where the files are residing on a DIFFERENT subnet.
To prove this point: I installed the same Win2012R2 on my local on-premises network and in Azure as a virtual machine. I setup shared folders and then from a Mac client I connected (both SMB/AFP) to them, tried saving the Word/Excel file. Guess what? On my local server (same subnet) these folders didn't appear and saving is almost instant. On Azure, the folders appear, and saving takes appr. 10-20 seconds. Packet signing is turned off. And no, it's not a latency issue at all as other file types work really well (txt, photoshop, indesign, etc). When PC clients connect, there are no problems at all regardless of destination end-point.
Wednesday, October 25, 2017 11:12 PM | 1 vote
We save our files on a host running OSX. We recently updated it to 10.13 (High Sierra) and the issue presented itself. As far as I can tell at this point, it's an issue with SMB connections ONLY. When SMB sharing is turned off and we force an AFP connection, the issue goes away.
This is not a long term solution as Apple has said their getting rid of AFP.
Anyone have an idea when MS or Apple will address this?
Thursday, November 16, 2017 5:32 PM
I realize this problem is an old request for help but it recently started happening to me in Word. After looking around I found the solution.
On a Mac, when you open Word, click in the upper left corner (Word) and scroll to preferences, click to Save, uncheck "save backup copy" and it should resolve the issue.
Friday, January 12, 2018 5:30 PM | 1 vote
For us it was the setting: Word | Preferences | Save | Allow Background Saves
https://word.tips.net/T000599_Understanding_Background_Saving.html
Our issue was worse as users could not save directly to the server at all. I have a feeling it has to do with our Sync software (CA RHA). We had a similar problem with Windows Office saves as Office apps, ONLY WHEN USING SMBv2, create a .tmp file in the same directory when saving. This is in addition to the ~$xxxx file. Our sync software was causing long delays as it was interfering with these .tmp files as I don't want to 'sync/replicate' them I had them explicitly excluded. There is a CA KB article on the issue.
I also exclude ._* | ~*.* | .DS_Store files because of the garbage they generate (it starts to add up after terabytes of data) and I have a feeling the same thing is going on here, in the 'temp folder' there is a ._xxxx file attempting to be created, but unlike Windows version of Office, Mac versions time out is much faster and so the save is canceled almost immediately.
I've been using CA RHA to replicate data for some time and previously we had SMBv2 intentionally disabled as we though this was the culprit, but after doing packet captures, it seems Office apps treat saving to remote source differently if connected via SMBv1 and SMBv2... why? I have no idea.
With SMBv1 being such a security issue now, we had to figure out SMBv2 and discovered its not the protocol, but the apps using the protocol. Other programs do not seem to have this issue OR utilize a different 'temp' naming schema.
So pending your setup, likely you do NOT have CA RHA on your servers, but you may have backup software, settings in MS FSRM file screens, etc that could potentially have the same effect. Disabling SMBv2 seems to resolve the issue, but is not a good work around.
I'm now trying to identify how much of a risk it is to OSX users in disabling "Allow Background Saves" and is it better to force them to save locally, then drag to the server.
Saturday, January 13, 2018 12:40 AM
We were incorrect in that its not just the filter issue with RHA, but the sync process period, so regardless of the filter, if SMBv2 is the connection protocol and Allow Background Saves is set, it fails... i.e. Word attempts to create this hidden folder along with a .tmp file and a .smbdeleteXXXXXXX file.
Monday, January 22, 2018 3:16 PM | 1 vote
We have this issue as well, but it is only limited to 2 users out of a total of 27. There has to be some reason that this is happening. It especially doesn't make sense that only 2 users are experiencing this, and the rest of our employees are not, especially since the machines they are all working on (MacBook Pros) were all set up identically.
Thursday, February 22, 2018 6:46 AM
Even I came across the same situation.
Every time save a word document it creates a folder. Inside the folder will be Word Work File D_1.tmp
Example:
Document name : budget.docx
Newly created Directory: budget.docx.sb_____-______
temp file : budget.docx.sb_____-______\Word Work File L_2.tmp
In your case are you using any specific software in your environment like backup\replication software ?
Wednesday, February 28, 2018 11:34 PM | 2 votes
I am also not sure why this is marked as answered and the reply by Winnie Liang is not anywhere close to an answer. I am having this exact issue in our environment as well. Sometimes the temporary folders that are created (usually 2-4, sometimes up to 6) disappear roughly 1 second after they are created when saving. Other times, the folders stay and you have to manually delete them. The times when they disappear on their own, usually only 2 folders are created.
I have unchecked "Always create backup copy" in Word's preferences and "Allow background saves" was already unchecked. These users are on OS X 10.13.3 and Word 16.10, however one Mac was on 10.11.6 and still had the issue before upgrading to High Sierra. This is a big issue that I feel is being ignored. I called Microsoft and got bounced around eventually to a paid service. I am at a large university and working off a network share connected via SMB is extremely common here. This needs to be addressed and fixed.
Wednesday, March 14, 2018 2:23 PM | 1 vote
its now middle of March 2018 WTH. I am also also also not sure why this is marked as answered and the reply by Winnie Liang is not anywhere close to an answer! i have one mac out of 15 with the issue. I want to share my SMB issues with you guys. Ever since 10.3 we have had smb issues all over our network. crippled. Adobe files would stay locked when were clearly closed. random people could open the files but not the user that created it. Saving to a PC server would beach ball constantly. search was gone. so we found "acronis files connect" and this allows the macs to connect via AFP to the PC sever super fast BUT this has has NOT fixed microsoft office. I agree there is a major smb/afp issue going on. i think its apple and not Adobe or MS. BUT its their responsibility to keep up with them. Ive talked to MS who is clueless about this. they wanted to look at the mnachine and blame apple... apple said its adobe. microsoft says its a background process.... what a circle jerk.
Thursday, March 15, 2018 11:40 PM
I agree this has not been answered!!!
Experiencing the same issues. It doesn't always happen and does not happen for everyone making it difficult to diagnose. All users are on Mac's and connecting via AFP to Synology server. As some of these folders are not automatically removed the end user is left with a folder full of Temp-Folders. We have experimented with all the Save options and have not found a magic bullet. Yes, Word saves temp files however they always used to be .temp files and therefore invisible to the end user.
Winnie Liang and Melon Chen you have errors in your choice to mark as answered and therefore put this incident in jeopardy.
Monday, April 9, 2018 9:18 AM
Same problem here. The users are connected to a windows server via SMB, and these folders keep appearing.
Nothing we have tried has worked so far. This issue needs fixing.
Monday, April 16, 2018 3:17 PM
I'm having the same issue, and on top of that Word keeps prompting me to Save As in an endless loop.
Tuesday, May 1, 2018 10:38 PM
By any chance could anyone who is having an issue with this post what kind of SMB server they're using, what OS version + what software is running it (some third party SMB server software or the built in OS one and if so with what settings)?
Tuesday, May 8, 2018 12:43 AM
FreeNAS 11.1 with a pretty standard config. The shares are Guest enabled, no password needed.
Making Un/PW access doesn't change the odd behavior.
4 Macs with most recent OS updates. 10.13 from memory. I'm not on site to check and so sick of this issue I'd rather stay away.
This is only happening on SMB connections. AFP works fine BUT somehow the Macs prefer SMB and continue to reconnect SMB. I may be wrong on that point BUT whenever the "Server is broken again" they've managed to connect SMB AGAIN and not notice!
BTW - Another "feature". Excel can't "save as" a new file to the SMB. It has two complaints about permissions then three can't create/access temp files then reports the file not saved.... Save it local and copy to the share then open and save to it all day? Apologies for the vague description I'm not there to read the err's. I read that SMB file creation has different permissions than save? Seems a plausible explanation for seriously confronting behavior.
Also WinZip couldn't unarc to the SMB share.
FreeNAS forums mention all sorts of tweeks but no joy for me.
It appears to be all about permissions and SMB's handling of Macs hidden DOT and Double DOT files/folders. Too far above my head, but looking more like Apple's SMB is still in dev.
I hope this helps Diego. Many thanks for wading into the torrent.
Thursday, June 21, 2018 3:57 PM
I'm trying to find out if someone has found a solution other than disabling SMB because I have exactly the same problem with one in 10 Macs...
Thank you!
Tuesday, August 14, 2018 7:46 AM
I don't have a solution, but I can confirm this isn't specifically a Microsoft Office on Mac saving to network share issue. It also happens to me when I save files from Mac to remote destinations from Omni programs (OmniGraffle, OmniOutliner, OmniPlan.)
With Omni Files, I'd presumed this was related to macOS' mechanism for storing versions of files, since the normal mechanism (of storing blobs and indexing to a local sqlite db) is not available over SMB. But I doubt Microsoft would subscribe to that mechanism. Plus, the folders seem to be empty. So, now I think it must be related to how Apple attempts atomic saves on remote filesystems. Save to a randomized temp directory, once successful, remove the original file, and then move the newly saved file to the proper location. It seems like the cleanup of the temp directory is not being handled properly by macOS.
I clean up the extraneous empty folders with a command like this, run from a macOS terminal:
find /path/to/share -name "*.sb-*-*" -type d -exec rmdir "{}" \
which basically is a unix command that looks for left over folders whose names contain the .sb- pattern, and if they're empty (as they are) removes them.
Monday, September 17, 2018 6:14 PM
Not sure why this was labeled as a solution. I too have several Macs with this problem of saving Word files to a Windows server, with a SMB connection.
Thursday, November 29, 2018 8:11 PM
Hey there. Funny topic, this is a super OLD BUG as i can see from my researches.
Well i made it here too.
So my case looks like that:
I never encountered the Issue over 1-2 Years, we had several Macbooks and Mac Minis in use. Synology had never a problem at all! Except finder searching with the files indexed ofc, cause finder suck at that (in private i use Path Finder and that searchtool is the most powerful on the whole macOS era, funny enough Apple never could do that but a third party dev could, but other story)
So recently we changed all our interns with windows PC to a Mac Mini, did well all super, except the Outlook bug which only occurs in few languages. (no header information on reply and answers, other topic to..)
then suddenly the next week i had user comin to me, when they edit a word file on the synology and save it, the synology made a empty folder looking like the description in this thread title... i thought WOW whats that new from microsoft. well i cannot tell its MS but on the windows machine, this wont happen as many times declared in here.
i will try now a few things which i read here but i'm certain i wont fix it.. i only wish these multi billion dollar companies could do better and not suck so hard.. :-/
but thanks i'm NOT alone with this crap. :-)
i will reply if i know more.
greets MOHji
Tuesday, January 22, 2019 10:38 AM
Have the same here, i have the problem since updating to mojave (from yosemite, where all was fine)
en only on server drives, not in internal SSD, the problem is very annoying > word makes like 5 folder per minute working in a document !!!!
crazy and unbelievable that this has not been fixed yet, by microsoft or apple, or both, i do not care, but they have to let people work.
Thursday, January 31, 2019 5:22 PM
I still have the same issue too on macOS Mojave Version 10.14.2. please fix it thank you.
Tuesday, February 26, 2019 8:21 PM
I still have the same issue too on macOS Mojave Version 10.14.2. please fix it thank you.
I try the paid support Microsoft. No success
Thursday, February 28, 2019 10:29 AM
I too have the same issue with Mojave and Word 2016. It is scandalous that two of the world's largest and most profitable corporations continually fail to treat their customers with respect. Perhaps a bit of enforced regulation of these companies would wake them up to their responsibilities? What is the solution - answer please Microsoft and Apple. Thanks in advance.
Monday, March 4, 2019 3:29 PM
Yes we have this problem too. Infuriating. And more so because we can't delete these errent folders unless we log off the server and then back on again. Tried turning off all auto save preferences and it made not difference. Can't someone at Microsoft look into this and let us know what the problem is?
Monday, March 18, 2019 12:05 AM
All the same issues here. anyone found a fix yet? or anyone from Microsoft working in the bug yet?
Monday, March 25, 2019 8:21 AM
Hi,
We faced the same issue with an Office 2016 Mac saving Word files on a Windows Server connected on SMB.
The difference with the reported issue was that the user cas unable to delete the nameoffolder.docx.sb-xxx folders.
After doing some tests, we found out that those folders created by Word when saving a file did not inherite properly the ACL. So Word is not able to delete the folders after saving the file.
We found out that some user accounts were inheritated properly, but not the groups, and the user with the issue was member of an ACL group and was not added as single user.
So we added the user account to the R/W ACL on the parent folder, and now Word create the nameoffolder.docx.sb-xxxx folder when saving the document, but instantly deletes it.
Not a very "clean" solution, but it works.
Thursday, April 11, 2019 6:54 PM
I am experiencing this issue with many of my users too, so frustrating that this has been ongoing for so long. Has anyone found a permanent fix? I am going to try pushing out permissions again. All my users have edit privilege for the affected shares, so not sure why permissions would be causing the issue (if it is indeed that).
Monday, April 22, 2019 4:59 PM
Same issue here on MacOS 10.13.6 with saving Excel files to a Synology NAS. I have tried many fix's and tweaks to no avail.
Wednesday, May 8, 2019 1:06 PM
I am having this same issue. When I save to my personal drive or Desktop, Word creates those temp folders but then deletes them when it's done saving (so there is only the single Word document in the original location).
However, when I'm saving a Word file on the company server, the Word document will create multiple folders while saving but I am NOT able to delete them. It gives me an alert saying I don't have permission. IT then has to go in to give those folders different permissions to allow me to delete them. I am able to create/delete/move other folders on the server, but not these temp folders that Word creates.
I don't have any of the backup options in Word Preferences enabled. Hoping this comment will alert me to a fix.
Wednesday, May 8, 2019 5:34 PM
Same issue... MBP 10.14.4, Synology NAS (latest updates), AFP.
Wednesday, May 8, 2019 9:26 PM
Same issue. 2016 Imac, Mojave 10.14.4, windows server 2012r2 with active directory.
Thursday, May 23, 2019 9:02 PM
It seem to be related to the "Always create a backup copy" option define in Word Preferences
Saturday, June 8, 2019 5:24 PM
Same issue with Excel. 2014 MacBook Pro, Mojave 10.14.5, Synology via AFP.
No Problems with Word!
Tuesday, June 25, 2019 2:50 PM
TrueNAS with about 60 total macs saving office documents to this server.
This is happened mostly with excel files. On my server, the files say they are in use an you cannot delete them. Finally, changing the name (shortening them) worked to allow me to delete the files. I am going to change the auto saving options and see if that helps.
I am also only experiencing this only with a couple of users. Connecting to a NAS device on the local LAN. No Sub-netting. Very frustrating. Users cannot clean up their own directories and creates overhead because I have to come in and delete files for them.
Really the most frustrating part is not having a clear answer on what is happening and how to prevent it. Besides tweaking some excel preferences, there is no rhyme or reason as to why this keeps happening? Help us out here!
Tuesday, July 2, 2019 4:43 AM
Does everyone have Dropbox.app installed?
The DropboxQL.qlgenerator (located in /Users/username/Library/QuickLook/DropboxQL.qlgenerator ) causes the issue for me.
The ExternalQuickLookSatelite process is keeping these temporary folders open, if you quit the process, you can then delete the folders. If you launch Activeity Monitor.app, find the ExternalQuickLookSatelite process and click on the "I" information button you can view the Open Files and Ports, the temporary folders will be listed.
Removing the DropboxQL.qlgenerator from the user folder resolves the issue. However, if you re-launch Dropbox.app it puts the qlgenerator back.
Friday, July 26, 2019 11:10 AM | 1 vote
I've just come across this issue myself, and I found the solution in my case was to actually turn off AFP on the NAS (which was a Synology). The strange thing is the clients were connecting via SMB so it's like the Mac made a second connection in the background via AFP. The folder is created still but it deletes within a minute or two. One thing I noted is when I opened terminal and used lsof | grep "/Volumes/*myVolume*", it was logging that "quicklook" had the randomly created folder open. This doesn't happen now AFP is off...
Monday, July 29, 2019 12:41 PM
The same problem here:
Files, both in word 2019 (.docx) and Preview in Mojave (pdf) has the issue.
Folders created. Error message when trying to delete.
Both auto save, auto backup and store for auto recovery disabled.
Trying to save to Mac server when it happens. Unclear at the moment if it uses afp or smb, but as both the client and server are Macs, I assume afp.
Here is the log from todays occurrence (one of many). It happened between 12:19 and 12:25 today.:
Jul 29 12:10:40 Hannes-MacBook-Pro syslogd[41]: ASL Sender Statistics
Jul 29 12:11:00 Hannes-MacBook-Pro kcm[6314]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:11:20 Hannes-MacBook-Pro kcm[6317]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:11:24 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.501): Service "com.apple.xpc.launchd.unmanaged.loginwindow.94" tried to register for endpoint "com.apple.tsm.uiserver" already registered by owner: com.apple.SystemUIServer.agent
Jul 29 12:11:40 last message repeated 1 time
Jul 29 12:11:40 Hannes-MacBook-Pro kcm[6320]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:12:06 Hannes-MacBook-Pro kcm[6327]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:14:12 Hannes-MacBook-Pro timed[80]: settimeofday({0x5d3ec6f4,0x70ae4}) == 0
Jul 29 12:14:38 Hannes-MacBook-Pro kcm[6350]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:14:58 Hannes-MacBook-Pro kcm[6353]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:15:18 Hannes-MacBook-Pro kcm[6356]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:15:38 Hannes-MacBook-Pro kcm[6360]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:15:45 Hannes-MacBook-Pro SecurityAgent[6363]: objc[6363]: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fffaf76a078) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10a979ce8). One of the two will be used. Which one is undefined.
Jul 29 12:15:45 Hannes-MacBook-Pro SecurityAgent[6363]: objc[6363]: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fffaf76a0a0) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10a979d10). One of the two will be used. Which one is undefined.
Jul 29 12:15:58 Hannes-MacBook-Pro kcm[6367]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:16:18 Hannes-MacBook-Pro kcm[6370]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:16:38 Hannes-MacBook-Pro kcm[6373]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:16:58 Hannes-MacBook-Pro kcm[6376]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:17:18 Hannes-MacBook-Pro kcm[6385]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:17:38 Hannes-MacBook-Pro kcm[6388]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:17:58 Hannes-MacBook-Pro kcm[6391]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:18:18 Hannes-MacBook-Pro kcm[6394]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:18:38 Hannes-MacBook-Pro kcm[6397]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:18:58 Hannes-MacBook-Pro kcm[6402]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:19:18 Hannes-MacBook-Pro kcm[6406]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:19:38 Hannes-MacBook-Pro kcm[6409]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:19:53 Hannes-MacBook-Pro AGMService[690]: ProcessPath : /Applications/Microsoft Word.app/Contents/SharedSupport/Microsoft Error Reporting.app/Contents/MacOS/Microsoft Error Reporting
Jul 29 12:19:58 Hannes-MacBook-Pro kcm[6416]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:20:03 Hannes-MacBook-Pro Dock[637]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:20:05 Hannes-MacBook-Pro AGMService[690]: ProcessPath : /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word
Jul 29 12:20:18 Hannes-MacBook-Pro kcm[6427]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:20:25 Hannes-MacBook-Pro com.apple.appkit.xpc.openAndSavePanelService[6429]: objc[6429]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fffb17c33d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10c53bf50). One of the two will be used. Which one is undefined.
Jul 29 12:20:25 Hannes-MacBook-Pro com.apple.appkit.xpc.openAndSavePanelService[6429]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jul 29 12:20:25 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.adobe.accmac.ACCFinderSync.17EBD626-EBAA-47B9-A01C-6FCE7CFCBDA2[6434]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:20:25 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.D853470B-B41A-44B7-B0AF-5585885FB94A[6435]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:20:25 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.microsoft.OneDrive.FinderSync.3D7E2ACA-D6D7-4E03-9735-3CA18506678C[6433]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:20:25 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.4B8B4ABC-452E-4206-A301-68108236BF87[6439]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:20:38 Hannes-MacBook-Pro kcm[6444]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:20:56 Hannes-MacBook-Pro syslogd[41]: ASL Sender Statistics
Jul 29 12:20:58 Hannes-MacBook-Pro AGMService[690]: ProcessPath : /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word
Jul 29 12:20:58 Hannes-MacBook-Pro kcm[6453]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:20:59 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.appkit.xpc.openAndSavePanelService[6429]): Service did not exit 5 seconds after SIGTERM. Sending SIGKILL.
Jul 29 12:21:00 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Jul 29 12:21:18 Hannes-MacBook-Pro kcm[6460]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:21:38 Hannes-MacBook-Pro kcm[6463]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:21:40 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.quicklook[6465]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Jul 29 12:21:58 Hannes-MacBook-Pro kcm[6468]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:22:04 Hannes-MacBook-Pro com.apple.appkit.xpc.openAndSavePanelService[6470]: objc[6470]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fffb17c33d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x106e7af50). One of the two will be used. Which one is undefined.
Jul 29 12:22:04 Hannes-MacBook-Pro com.apple.appkit.xpc.openAndSavePanelService[6470]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jul 29 12:22:04 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.5F23A76E-A2A9-4F9E-B9DD-BA1FBD08AA30[6474]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:22:04 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.microsoft.OneDrive.FinderSync.7E72FF02-E7E7-42D4-95E1-3C995AF61EEB[6472]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:22:05 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.adobe.accmac.ACCFinderSync.E76B12AE-0D7B-43DF-89E6-1994446C30C4[6473]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:22:05 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.F119FBB9-71DA-4AB3-A7A8-D0B774054C1B[6476]): Caller wanted oneshot behavior for pre-existing instance: caller = com.apple.appki
Jul 29 12:22:15 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Jul 29 12:22:16 Hannes-MacBook-Pro xpcproxy[6481]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination port
Jul 29 12:22:16 Hannes-MacBook-Pro iTunesCacheExtension[6482]: objc[6482]: Class ITNSImage is implemented in both /System/Library/Frameworks/iTunesLibrary.framework/Versions/A/iTunesLibrary (0x7fffafd482a0) and /Applications/iTunes.app/Contents/PlugIns/iTunesCacheExtension.appex/Contents/MacOS/iTunesCacheExtension (0x10a8c3370). One of the two will be used. Which one is undefined.
Jul 29 12:22:16 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Jul 29 12:23:18 Hannes-MacBook-Pro kcm[6494]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:23:38 Hannes-MacBook-Pro kcm[6502]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:23:58 Hannes-MacBook-Pro kcm[6506]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:23:58 Hannes-MacBook-Pro xpcproxy[6508]: libcoreservices: _dirhelper_userdir: 529: bootstrap_look_up returned (ipc/send) invalid destination port
Jul 29 12:23:58 Hannes-MacBook-Pro iTunesCacheExtension[6509]: objc[6509]: Class ITNSImage is implemented in both /System/Library/Frameworks/iTunesLibrary.framework/Versions/A/iTunesLibrary (0x7fffafd482a0) and /Applications/iTunes.app/Contents/PlugIns/iTunesCacheExtension.appex/Contents/MacOS/iTunesCacheExtension (0x10ed35370). One of the two will be used. Which one is undefined.
Jul 29 12:23:58 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Jul 29 12:24:05 Hannes-MacBook-Pro AGMService[690]: ProcessPath : /Applications/Utilities/Console.app/Contents/MacOS/Console
Jul 29 12:24:05 Hannes-MacBook-Pro diagnosticd[6516]: Posting empty stream filter
Jul 29 12:24:05 Hannes-MacBook-Pro diagnosticd[6516]: no EOS device present
Jul 29 12:24:05 Hannes-MacBook-Pro diagnosticd[6516]: allowing Console (6514) access to stream due to admin status
Jul 29 12:24:05 Hannes-MacBook-Pro diagnosticd[6516]: Posting stream filter: "{
global = 30064771083;
}"
Jul 29 12:24:05 Hannes-MacBook-Pro diagnosticd[6516]: System mode client started - Console (6514) - mode: 0xb, filter: "<empty>"
Jul 29 12:24:18 Hannes-MacBook-Pro kcm[6518]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:24:25 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Jul 29 12:24:38 Hannes-MacBook-Pro kcm[6521]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:24:54 Hannes-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.WebKit.Networking.B9BA5400-C181-47D5-8281-1BB836A7C69D[6498]): Service exited with abnormal code: 1
Jul 29 12:24:58 Hannes-MacBook-Pro kcm[6526]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:25:18 Hannes-MacBook-Pro Console[6514]: BUG in libdispatch client: vnode, monitored resource vanished before the source cancel handler was invoked { 0x60000300ed80[source], ident: 12 / 0xc, handler: 0x7fff659ab81b }
Jul 29 12:25:18 Hannes-MacBook-Pro kcm[6531]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:25:38 Hannes-MacBook-Pro kcm[6536]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:25:58 Hannes-MacBook-Pro kcm[6539]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:26:18 Hannes-MacBook-Pro kcm[6543]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:26:38 Hannes-MacBook-Pro kcm[6546]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Jul 29 12:26:58 Hannes-MacBook-Pro kcm[6549]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug
Tuesday, September 3, 2019 1:09 PM
Same problem here on 1 mac. All the others don't have this problem and are using the same software.
Mojave 10.14.5
AFP
Office 365 (Mostly word)
Wednesday, September 4, 2019 11:22 AM
I have the same Problem in a company with ~30 users and a synology nas.
i have observed that the folders are created when a file should get saved (or autosaved maybe?).
sometimes saving the file fails, but every second a new empty folder gets created until word or excel get terminated.(Beachball)
sometimes i then have to get older files from a backup because of that bug, its very frustrating.
my plan for a temporary solution is to delete the files with a script on the nas once a day, so users dont get bugged about this.
information: macOS 10.12.6, synology with SMB, Office 2019 Version >16.25
Wednesday, September 4, 2019 4:10 PM
Every time a save a word document it creates a folder. I can delete the folders created but it's a nuisance to keep deleting folder after folder. Inside the folder will be Word Work File D_1.tmp but goes away but the folder will remain. I was wondering if there is a fix for this issue
I too have this issue.
We have a Windows File Server running Acronis Files Connect and macOS 10.14.6 clients with the exact issue.
Here is my original post in Microsoft Community Forums which sent me here...
Is there a solution?
Saturday, September 21, 2019 4:02 PM
Wouldn't it make sense for Word to use ONE SINGLE FOLDER for backups and the ability to change that location in a location?
This is why no one uses Windows anymore. Now that Pages come free in every new Mac, there's no reason to use Word. Microsoft doesn't even update the Mac version, so you have to wait 4 years for the privilege of giving them more money for the newer version. It's simply not worth the headache just because of that one guy in the office that refuses to switch to Mac.
Wednesday, September 25, 2019 11:59 AM
Today an enduser told me that they installed a new microsoft update for word and powerpoint and the problem seems to be solved. Can't really find anything in the changelogs though.
Friday, September 27, 2019 6:38 PM
That's really strange but it worked out for us, too. Problem is, we need the AFP connection...
Saturday, October 12, 2019 7:41 AM
I also have this problem but i realized that this is not an MS problem. It also happens when i use Apple Pages. So it has something to do when working on SMB folder from a Mac. I guess an advanced setting in File Services settings of my NAS could fix this, but i don't know which one...
Saturday, November 16, 2019 12:20 AM
This may be already answered bc I didn't read all of the many responses. Try going to WORD > Preferences > Output and Sharing > Save > remove the check mark if present at "Always Create Backup Copy". That fixed the problem for me.
Monday, November 18, 2019 4:32 PM
I have this problem too. Nothing suggested has worked. Has anyone upgraded to Catalina using Office 2019 and seeing of the problems still exists?
Friday, November 22, 2019 3:19 PM
We are too. Running 10.13 clients with smb shares (afp disabled) on 10.12 server. This is critical, as Wirth most offices, Office is one of our central apps.
Tuesday, December 10, 2019 11:08 PM
Similar issue here. I MacOS Mojave with Excel 2019. Saving Excel files to a Windows file server. It created an empty folder with same name as the file under the same directory. That folder won't disappear and it just stays there. Next time when I Save the file, it created another folder again.
Looking forward to the fix.
Lawrence Fung
Wednesday, December 18, 2019 3:41 AM
My users are STILL to this day experiencing this issue. Has there ever been a resolution?
Friday, January 3, 2020 1:53 PM
Hello,
We experience the same issue, as apparently everyone else.
Could someone of Microsoft please explain what causes the issue and find a solution to it?
I think Microsoft should have all the elements to tackle this, or at least enough to follow this topic and not disappear after one post.
Cheers,
Giorgio
Thursday, January 23, 2020 2:37 PM
Users still having this issue.
Thursday, February 6, 2020 11:08 PM
I have upgraded to Catalina using Office 365 2019 and have this issue. Multiple folders all over the place.
Tuesday, February 11, 2020 1:43 PM
This doesnt seem to be limited to Microsoft Office for me.
We have a Server 2019 File Server and I tested on MacOS 10.12.6 and MacOS 10.14.6 with a text file using TextEdit and had the same issue:
Tuesday, May 5, 2020 1:10 PM | 1 vote
4 and a half years later, no answers. More upgrades from both Apple and Microsoft, and yet the problem has been totally ignored.
I have about 30 Mac users saving Word 2019 files to a Mac server, which now forces you to use SMB instead of the more reliable AFP for some reason.
We are still getting these odious folders and temp files that don't autodelete. They should not even be visible! Is ANYBODY at Microsoft working on this? It's getting stale!
Thursday, May 21, 2020 1:00 PM
If you disable the Auto-save feature the folder would disappear.
It is not a bug but a harness to save the data if a malfunction happens.
Thursday, July 16, 2020 8:08 AM
Every time a save a word document it creates a folder. I can delete the folders created but it's a nuisance to keep deleting folder after folder. Inside the folder will be Word Work File D_1.tmp but goes away but the folder will remain. I was wondering if there is a fix for this issue
Hi.
We’re facing the same issues. Word creates folders when saving files. We use file servers windows server 2012, 2016 and clients macOS 10.12-10.15.
The solution is as follows: check the flag Full control for the user or user group in the section ‘share permission’. This prevents from folder creation. Of course, folder privileges are granted via NTFS permissions.
Thursday, August 6, 2020 4:08 PM
Hello,
I have the same problem (in Word 2019 for Mac - OS Catalina).
What one wishes to have is a solution where one chooses to have Auto-save but where the backup files are stored in the same folder as the file that is being backed up, without generating a useless additional folder for that backup only. If one is working with many Word files that are being continually revised that creates a clutter of folders.
The previous versions of Word for Mac (e.g., 2011) did not have this problem.
(And this is different from auto-recovery information.)
Thank you for any leads towards a solution.