Land Desktop Companion 2008, both SA and NW
This morning up arriving to work I found that several SA workstations could
not start AutoCAD and displayed a missing file message for ADLMDLL.DLL.
Upon checking my own SA workstation I discovered a message stating that the
installation was an invalidly licensed product (I'd left AutoCAD running
overnight...no one else received this message). Restarting my AutoCAD I
then received the missing file message the other workstations produced and
never received the license message again after restarting several times.
I tried running a Repair and Reinstall (installations are from server
Adminimages), both unsuccessfully. However, I kept getting the message that
ADLMDLL.DLL could not be found in my SA Adminimage. Luckily, I have backups
and was able to restore 4 files that had been removed from my SA Adminimage.
After that, running Repair actually worked and my SA workstations are back
in business.
As of this afternoon my NW workstations began exhibiting the same behavior
including removal of the same 4 files from the workstations and my NW
Adminimage.
I have spoken with someone at Autodesk (the Business something-or-other
dept...not the Tech dept) who tells me that there are no issues/flags/etc
with any of my licenses/serial #s. He said he wasn't technically trained to
tell me whether Autodesk has some crazy disabling scheme to remove files
from an adminimage, much less a workstation.
What disturbs me is that my Adminimages are read-only for all in my office
except myself and one other individual whose workstation did not exhibit any
of these issues. Granted, there may be *something bad* on my workstation
that caused this...I'm in the process of scanning now. But this is highly
specific and just plain freakin' weird.
The files erased are:
\PROGRAM FILES\ROOT\ADLMDLL.DLL
\PROGRAM FILES\ROOT\LACADS.DLL
\PROGRAM FILES\ROOT\lciv3ds.dll
\PROGRAM FILES\ROOT\llddts.dll
Things are working again but I fully anticipate it's gonna happen again.
Does anyone have any clue as to what's going on?
Thanks,
Josh