"Failed to load VSUtil dll" during silent install of VSE7 1

[mib147]

We have been working with VSE7 since the day it came out. We have found some issues that NAI is having a hard time addressing (Surprise surprise). We are planning on deploying this package to 5,000 clients so we build a customized package, with there tool, so it will run silently in the background. We started seeing error failed to load VSUtil dll twice whenever it ran. This did not seem to affect the installation or the functionality but it was an error we could do without. We found that if outlook was open during the install, it would generate this error. So I wrote a script that check to see if outlook is open and if so, it tells the user it is going to close outlook in 2 minutes so it can update the virus software. That eliminates the error message. Here is my script:


Dim booloutlook, appoutlook, boolmapi, WshShell, fs
Set WshShell = CreateObject("wscript.shell&quot
Set fs = CreateObject("Scripting.FileSystemObject&quot

booloutlook = ProcessIsRunning("outlook.exe&quot
If booloutlook = "True" Then 'Check to see if outlook is open. If so, close it.
WshShell.Popup "We are about to upgrade your virus software and outlook must be closed during this process. You have two minutes to save all work and close or outlook will close automatically. Thank You.", 20, "McAfee 7.0 Install"
wscript.Sleep 120000 'Sleep for one minute
set appOutlook = Wscript.CreateObject("Outlook.Application&quot
appOutlook.Quit
Set appOutlook = Nothing
wscript.Sleep 10000
boolmapi = ProcessIsRunning("Mapisp32.exe&quot
If boolmapi = "True" Then
ProcessTerminate("Mapisp32.exe&quot
End If
End If
wscript.Sleep 20000 'Sleep for 20 seconds


'wshshell.Run "setup.exe /qb+" 'Install McAfee




Private Function ProcessIsRunning( strProcess )
Dim colProcessList
Set colProcessList = Getobject("Winmgmts:&quot.Execquery _
("Select * from Win32_Process Where Name ='" & strProcess & "'&quot
If colProcessList.Count > 0 Then
ProcessIsRunning = True
Else
ProcessIsRunning = False
End If
Set colProcessList = Nothing
End Function


Private Function ProcessTerminate( strProcess )
Dim colProcessList, objProcess
Set colProcessList = GetObject("Winmgmts:&quot.ExecQuery _
("Select * from Win32_Process Where Name ='" & strProcess & "'&quot
For Each objProcess in colProcessList
objProcess.Terminate()
Next
Set colProcessList = Nothing
End Function

 

[AVChap]

I figure you haven't heard of the McAfee Installation Designer, have you? No need to go through all of this. Use the MID 7 to pre-configure VSE 7 with all of the prompts answered and running silently. We've used that for deploying on our network.

AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation

 

[mib147]

As a matter of fact, I have heard of the Installation Designer. If you read my first post again, I even state "so we build a customized package, with their tool(MID), so it will run silently in the background." The problem is when you run the MID created package on a machine that has outlook open. It's actually not the install of VSE7.0 that generates the error its the 4.5.1 or earlier uninstall that does it.

When you run VSE7.0 silently, if it detects an older version installed, it will automatically uninstall it. If outlook is open during this uninstall, VirusScan cannot completely uninstall smoothly because outlook is still hanging onto a component which then generates the error "failed to load VSUtil dll". Try it out. NAI has been able to reproduce the issue and is currently looking for a fix or solution.

 

[topkat]

I am running into the exact same problem that MIB147 is running into. Using the Installation Designer does not offer anything to handle this issue. The problem is that if you have VSCAN 4.5.x on the machine, VSE7 will try to uninstall it. This causes a problem if MS Outlook 2K or XP is open. It would help if the program had a shutdown clock to close Outlook prior to the 4.5.x uninstallation, but that is not so. McAfee's answer to this was to make sure that Outlook was closed prior to running the installation. That is impossible in a large corporate environment. Your script looks pretty good. I am going to try it out and see what happens. THanks,

 

[VictorySabre]

In regards to getting Outlook closed, why not schedule the upgrades after hours when users are not usually at work and before sending out the upgrade, send out an e-mail to let users know that they must log out of their PCs to ensure upgrades are successful.

I usually do this when I roll out these upgrades at work and most users do close and log out. Those who don't...we just deal with them manually in the morning when programs no longer respond.

 

[mib147]

That's good advice VictorySabre but unfortunately we have a lot of remote users. So when they leave, so does their machine.