DLL not registering -- Win7

[Chris]

Done exactly what you suggested (while you were typing the suggestion :-)

Have checked: HKLM\System\CurrentControlSet...
HKLM\System\ControlSet001 and 002
HKLM\Software\Microsoft\CurrentVersion\RunOnce
and RunOnceEx
HKLM\Software\WOW6432Node\......\RunOnce

Although install ended with message System must be restarted....
None of the locations had any files pending. NO FILES PENDING.
The \PendingFileRenameOperations node is not there.

So.... ????

[Chris]

Forgot to say.... I have done this using the latest Development Build of SB8 that you suggested.

Happy to send you the DLL. errr. which one? :-)

[linder]

See attached screenshot. I have simulated a locked-file scenario for you on Windows 7 Ultimate x64. The file is in-use during the installation and so Windows needs a reboot. The Windows API writes the required information to the registry (elevated running setup).

Friedrich

[linder]

The one that does not register <g>. And you only need the Development Build if your self-registration DLL needs the additional OleInitialize() call.

If a locked file causes a reboot request then it is definitely logged in the registry (PendingFileRenameOperations value).

Friedrich

[linder]

NO FILES PENDING.
The \PendingFileRenameOperations node is not there.

So.... ????

There is no PendingFileRenameOperations "node". It's a value name under the "Session Manager" key name. And don't get confused with the empty "FileRenameOperations" key name

Friedrich

[Chris]

I mean there is no PendingFileRenameOperation value name under the SessionManager Key.

[Chris]

Oops, I may need you to delete my last message to avoid me being thought of as stupid. I need to go and repeat the process.

[linder]

If there is no PendingFileRenameOperations value then the installer did not request a reboot to replace a locked file. The only other action that causes a reboot message is a "Reboot Operating System" script function in your project.

Friedrich

[linder]

Please do not delete it All this Windows UAC / x86 / x64 is very complex. It took us years to understand how it all works.

Friedrich

[Chris]

Thanks Friedrich,

I hereby declare that I did not properly read the helpful reply which did in fact point me at the right place. :-|

Anyway. The file that is pending is expsrv.dll (part of VBA DAO system).
In the SB8 Installation script it is set as Check Version/Date, and therefore should not need to be installed.

BUT... (maybe this is the problem).
Source file (to be installed): date: 02/14/2008 vers: 6.0.72.9590
Target file (already installed): 07/14/2009 vers: 6.0.72.9589
ie. Date newer but version older

Target file is already installed in both Win\System32\ and \sysWOW64\

Despite me having run the install a dozen times (and restarted), this file has NOT been replaced in either target location. But is shown as pending.

Maybe you can guess at what is getting confused.
(I probably do not need to install this file anyway -- historic reasons why it's there -- and also I will try changing source file Date to after 7/14/2009 to see if that fixes everything).