Autodesk identified an issue when in a specific scenario, the Sheet Set Manager is using DWG files stored in a Windows 2008 R2 server with SMB V2 active.
As soon we open a Sheet Set from the server, Process Explorer shows that the process AdcomFolderWatch.dll uses until 50% CPU utilization, and the Network traffic goes up and stays at ~5 Mbps, even after closing all drawings in AutoCAD).
This issue only affects the systems having SMB Ver.2 active, like Windows 2008 Server R2.
The Autodesk development team has been informed. For the time being, the only way to avoid it is to enable SMB 1. See How to Disable SMB 2.0 on Windows Vista/2008
I will update this post as soon a fix will be available for this problem.
A fix has been released for this issue. AutoCAD and AutoCAD LT 2012 SP1 SMB V2 Hotfix
Thanks for posting about this. I submitted a trouble ticket to Autodesk back in February but those guys couldn't even begin to get a grasp on troubleshooting the problem.
Posted by: Madmarv | 06/28/2011 at 10:02 AM
Hi Madmarv,
I’m sad to know that you have reported a similar issue and you did not receive any answer from us.
I was trying to check the status of your case, but unfortunately I've not been able to identify any report from you about a similar problem.
Can you provide to me the case ID?
Antonio
Posted by: Antonio Barroca | 06/28/2011 at 10:24 AM
This issue was also reported by me, back in December 2010. The issue exists in AutoCAD 2010, 2011 and also 2012. And it is really simpel to reproduce.
Autodesk's answer to just downgrade to SMB v1 is of course not possible for some companies (like us), because we benefit greatly from this new protocol version.
SMB v2 was already around in Windows Server 2008, which is on market for a long period.
They also stated that no other company reported this issue (which seems kind of strange as we have a pretty standard setup).
The main response from Autodesk support (Antonio) was that they didn't know when a fix would be available, if a fix would be available and if that would be in a new product release (AutoCAD 2013) or with a Service Pack.
After trying to escalate this issue via our reseller 3 times, they finnaly got someone on the phone who (hopefully) takes customer satisfaction and bugs in their software more serieusly.
Posted by: Wouter de Mna | 06/28/2011 at 07:39 PM
We've been dealing with this issue since mid 2010. We really started noticing high network usage with our new Win 7 clients. We searched and searched for a possible explanation, and spent quite a bit of time on this. It would have been nice for Autodesk to acknowledge the issue sooner.
When can we expect a fix for this?
Posted by: Nic | 07/20/2011 at 09:47 PM