Networks
ind out what else you are starting, e.g. with msconfig or msinfo32
and see if stopping one of those items stops the symptom?
Otherwise run ProcMon (using its boot logging option if necessary)
to figure out what task is trying to load that module.
I suppose if the error is being logged in an event log you could try using
the Event Viewer too and probably get the same clue from it.
The DLL Help Database is giving an indication that it could have come
with Microsoft Office. Perhaps you should try repairing that product?
(E.g. to make Office--in particular any startup options it is using
aware of the change in the SQL configuration.)
http://support.microsoft.com/dllhelp/default.aspx?l=55&fid=114938
BTW this doesn't see to have anyting to do with Windows Update.
You would probably get more informed help from either an SQL
or an Office newsgroup.
This discussion is closed to new replies.
Sort by Trending