|
|
| |
By Shawn Bass on
Wednesday, November 26, 2008 1:17:14 PM
A client of mine recently rolled out their upgrade from McAfee 8.0 Enterprise to 8.7 Enterprise. On the Citrix server environment we had two major application failures that were the result of the McAfee upgrade uninstalling the MS XML 4.0 Parser on the servers. There were two applications on the production Citrix environment that required the MS XML 4.0 Parser and they both stopped working following the upgrade. Unfortunately, the issue was not caught in Lab/UAT testing and was only found after McAfee went out to production. To make matters worse, something went wrong with the deployment mechanism and the McAfee upgrade went to all servers in one blast whereas the server team usually pushes in 2-3 separate sets of server groups. All of that combined = FAIL
So McAfee is responsible for the outage, right? WRONG!
What the Mcafee installer was doing was proper behavior. It had incremented the shared component registry entry for MSXML4.dll when it was installed on the servers. The shared DLL component...
Read More »
|
By Shawn Bass on
Wednesday, November 26, 2008 12:12:43 PM
I was recently running some Windows Update patches on one of my client's Server 2003 boxes (they aren't using a patch management solution) when I ran into a strange error that stated the Windows Update site could not be accessed and the error message listed was 0x80070020. This message did not appear while trying to install the updates, it appeared right after the selection for Express vs Custom. I chose Custom and it's supposed to query the available patches for the server, but instead I was greeted with error 0x80070020. In doing some reason on this error I found that it's related to a file locking issue. Some people on various forums reported issues with BitDefender AntiVirus on Windows XP and Vista as the source of the issue. While they're not running BitDefender on their server (they run eTrust), it was worth looking into. I also found KB883825 which also lists Anti-Virus as a potential source of issues for Windows Update. So I temporarily...
Read More »
|
By Shawn Bass on
Wednesday, November 26, 2008 11:06:12 AM
I was recently installing VMWare Server 2.0 (the freely available VMware virtualization platform) and I found that after the installation initialized it threw this error message:
In doing a quick bit of research, I discovered that this is some type of an issue with Windows Installer engine with large MSIs. Essentially Windows Installer is unable to allocate the necessary virtual memory to verify the integrity of the MSI. The strange part about this issue for me is that this server has 6 GB of RAM and there's absolutely nothing else running on it....Strange eh?
Anyway, MS has a hotfix for this issue. Download and install KB925336 and you'll be good to go.
Read More »
|
|
|
|
|
|