Let me know if I can get you any other info.
dwl2 "temp" files that are created for crash recovery while a drawing is open? My only working theory right now is that somehow Everything's indexing "interrupted" the saving of a file due to indexing being in progress at the time of the save? Perhaps it interfered with the. I plan to deploy in a test environment first though. I'm really hoping that Everything wasn't cause for the corruption because it's a fantastic program! I am going to reconfigure indexing using an ETP server instead to see if that fixes the issue. It's largely Greek to me, but may be of use to you. You may find this article that details organization of the. Once the user finds the file(s) they are looking for, they were instructed to use the "Open Path" function in Everything, and subsequently open the file from Windows Explorer. The idea behind using Everything was originally to provide a simple way to search their "P:\" (production) files and also "A:\" (archive) files from a single window. dwg files by either double clicking from Windows Explorer, or open via 'Recent" files directly within Civil 3D 2019 Workstations all have "P:\" drives mapped back to the fileserver.
Maybe explain the methodology used in your opening of the files, & how Everything plays into that methodology? Thanks for the help, I am mainly just trying to rule things out at this point. Is the way I configured Everything causing the corruption? Is this even a possibility? I am just learning about using an ETP server to provide a central index for multiple users. I did a brief search on this forum for similar events, but didn't find anything matching Autodesk software issues. No Windows updates have been installed recently, and Everything was the most recent change on each machine. The machines are all running Windows OS Build 17134.706. This same scenario occurred for 3 other users throughout the day. The strange thing is we recovered the file in question from the last save that occurred 10 minutes prior to the corruption, and it worked fine. This is a Civil Engineer office, so in the morning I got reports from several users that their drawing files were corrupted upon opening.
I configured Everything to index these drives every 6 hours. I then configured each user workstation to index "A:\" and "P:\" drives which are mapped back to the file server. Last night, I deployed Everything on a domain network from the domain controller for about 15 users. I have been using Everything on a basic level for a few years now.
0 kommentar(er)
