Auto FE Updater

Error Messages

The publisher could not be verified.  Are you sure you want to run this software?

The shortcut file '\\ServerName\FolderName\ Tracking System.lnk' was not found.

(Thanks to DR.) Shortcut files usually do not have the .lnk visible even though you've unselected "Hide extensions for known file types." from within Windows Explorer.   So when you look at directory using Windows Explorer do you see the .lnk extension? With the default settings in Windows you shouldn't actually see the .lnk extension although it is present. Thus what might be happening is the file actually ends in .lnk.lnk with the second .lnk hidden from view.   You can also verify this by going to the command prompt in that directory and doing a "dir *.lnk".

The application failed to initialize properly 0xc0000022

The permissions aren't setup properly on MSVBVM60.DLL in your Windows System32 folder.  Thanks to Ray Zorz for locating this problem.

1021 - DAO was not found on this system. You probably need to register the DAO DLL. For more information see my website.
(Note that the DAO version does not necessarily match the Jet version. DAO versions 3.6 through to version 2.0 were checked.)
   - or -
DAO version 2.0 was not found on this system.
Note that DAO version does not necessarily match the Jet version.
   - or -
1023 - The following problem occurred in routine 'MDBVersionFromFile'
Method '~' of object '~' failed

Very likely you need to register the DAO DLL specific to your version of Access. If Access 2000, 2002 or 2003 it is DAO360.DLL. If Access 97 it is DAO350.DLL.   

For example, at a command prompt or the Run ... menu item on the Windows Start button , key in
      regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"
with the double quotes.

Note that Don Barton reported that this problem was specific to one particular user.  He could log on to the system and all was well but the particular user was having this problem.  Once he logged on as administrator he ran the above regsvr32 and the user was now working just fine. 

Q. Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

Run Internet Explorer >> Tools >> Options >> Security tab. Under Trusted Sites add the name of the server (or your domain) to the list of trusted sites.   Note that this happened on a Terminal Server system.  The interesting thing is that the user could run a .cmd file which executed StartMDB.exe just fine.  But they couldn't run the shortcut which executed StartMDB.exe.  

This is a security risk as anyone could then load any executable onto the server.

Q: Why can't I create a shortcut on Common Programs or Common desktop in Windows Vista ?  I get either of the following messages.
1046 - CreateShortCutOnCommonPrograms = Yes is not allowed on Windows Vista (or newer)
1045 - CreateShortCutOnCommonDesktop = Yes is not allowed on Windows Vista (or newer)

Windows Vista has locked down the Common Programs and Common desktop so that only administrators can add or update new shortcuts.   While I could allow this to be done by the administrator in the future you might want a user to update the shortcut.   Now you would have to log on to their system to do so.  I chose to not allow this at all.   If this is a problem send me an email and we'll come up with a solution.