Author Archive for eli

ClamAV Update Breaks Mail Delivery

Postfix + ClamAV + SpamAssassin + Amavisd-New

As we all know, ClamAV versions older than 0.95 stopped working yesterday. This was announced some time ago by ClamAV, but caught most people (Myself and Devin) by surprise when mail flow stopped cold on our email servers. ClamAV pushed down an update that broke older versions, forcing sysadmins to either disable Antivirus, or update ClamAV to a more recent version.

We were running a very old version of ClamAV, 0.91.2-1~volatile1, from 2007. An upgrade was long overdue anyway. Here are 2 ways to fix it.

Continue reading ‘ClamAV Update Breaks Mail Delivery’

Unable to run Live Update in Backup Exec 2010

This error happens frequently in Backup Exec 12.5 and Backup Exec 2010. Live Update cannot find any installed products to update. Here is the text of the error message:

LU1805: LiveUpdate was unable to find any products to Update

There are no products on this computer than can be updated by LiveUpdate

Continue reading ‘Unable to run Live Update in Backup Exec 2010’

Upgrading to Symantec Backup Exec 2010 Part 2

In my previous post I upgraded from Symantec Backup Exec 12.5 to Symantec Backup Exec 2010. I ran into a few problems during the upgrade process, including one that caused the nightly backups to fail. Here is the error in the backup job log:

Completed status: Failed Final error: 0xe0001201 – For this operation, the Backup Exec Virtual File Filter (VFF) driver must be installed on the media server. The VFF driver is installed when you install any of the following Backup Exec agents or options: Exchange Agent Active Directory Recover Option VMware Virtual Infrastructure Agent Microsoft Virtual Server Agent Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-4609

The error I encountered when installing the licenses indicated that the installation was not successful. I chose to ignore this error after the upgrade completed, but it appears to be critical and has to be fixed. Continue reading ‘Upgrading to Symantec Backup Exec 2010 Part 2’

Upgrading to Symantec Backup Exec 2010 Part 1

A client I was working with was having an issue with their Virtual Machine (VM) running on Hyper-V. It was an odd one that I have never seen before. The VM was running Server 2008 R2 and had a single synthetic Virtual NIC attached with a static IP. The problem was that when the VM was restored from a saved state, occasionally, the network would not work. This obviously caused issues for users that needed to connect to the VM via RDP. Luckily, this VM did not completely rely on the Internet, so minor downtime when the VM was restored from a saved state wasn’t a major issue. Disconnecting and reconnecting the NIC in Hyper-V did not fix the issue, and ipconfig /renew wouldn’t fix anything since the IP address was static. The only thing the admin was able to do to temporarily fix the issue (until the next saved state restore) was to log into the VM via Hyper-V console and disable and then enable the NIC that was having issues. Unfortunately, time was a factor in finding a solution, and I was unable to physically see the hardware or VM in action. This made it very difficult to figure out what was causing the issue in the first place. A workaround seemed to be a much better use of time than spending hours trying to deduce the problem via E-mail.

The restore action for the saved state was done by via script. So it would be very easy to tie in another script to essentially disable and enable the NIC after the VM was restored. From what I can tell, this can’t be done using the Hyper-V Powershell APIs from the host. Also, since the network was the problem, I couldn’t run a remote script from the host to fix the NIC. Anything that could be done would have to be done within the VM. Granted this is not a solution to the original problem, but a workaround, and given more time we would have looked into what the actual cause was. So, here is the workaround to the problem.

Continue reading ‘Upgrading to Symantec Backup Exec 2010 Part 1’

TODO: Remove “TODO:” code comments before RTM

I was tweaking the editmessage.aspx page for OWA 2007 in Exchange 2007 and I noticed some leftover code comments from the developers at Microsoft.

Do code comments like this make it past the QA process often?

<td id="tdSubjLbl"> </td>
 <!--LocalizedStrings.GetHtmlEncoded(Strings.IDs.SubjectColon)-->
 
			<!-- TODO: OWA: 775: make sure this comment (and any others) are removed in retail -->
			<!-- For some reason, if this input field is not wrapped in a div, when the user types some text it resizes itself by a few pixels. Go figure.-->
<td> </td>
<div class="h100"><input id="txtSubj" class="edtSubj" maxlength="255" type="text" value="&lt;% RenderSubject(false); %&gt;" /></div>