MS Access system.mdw Problems After Domain Move
Posted on 2010-08-18
I work for a junior college with about 150 Windows XP Professional Service Pack 3 computers in a Windows Server 2003-based Active Directory environment. Each has the volume license version of Microsoft Office 2007 Enterprise on it.
Recently, we migrated users from one domain to another, Well, migrate is not the correct term. We eliminated an old domain controller and re-created user accounts, using dsadd, on the new domain controller for each user. As part of the process, we also moved the users' profile and home folders to the new domain and set proper security permissions on them for each user. Then each of our workstations had its domain membership changed from the old domain to the new. Roaming profiles, access to home directories, etc. all seem to be working fine.
However, we've suddenly started having a problem with Microsoft Access. It started out affecting only a handful of users and has now suddenly spread to all users. When a user opens Access and attempts to either create a new database or open an existing one, they get an error message stating that the file C:\Documents and Settings\xxxx\Application Data\Microsoft\Access\system#.mdw cannot be found (where xxxx is their username and # is either blank or a number from 1-7).
I have checked, and the files it is trying to access do exist. Also, each user has proper NTFS permissions to access all files, including those, in their profile folders.
If I create a new user account wiht a fresh roaming profile, one that was not duplicated from the old domain, Access works fine. And, as I said, users were having no problems the first two days after the move, but suddenly today all have this issue.
Any suggestions would be most appreciated.