Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

can't install hotfix 301030

Created: 13 Apr 2008 • Updated: 21 May 2010 | 29 comments
Hi,
 

Yesterday when I ran Live Update on my 9 different BEWS 12 installs (9 different clilents), I was told that I needed Hotfix 301030. When Live Update tried to install this hotfix, it failed to install. I downloaded the hotfix and tried to install it stand-alone. It failed with

-----------------------------------------------------------------

Error 1328.Error applying patch to file C:\CONFIG.MSI\PT4D9.tmp [NOTE: This filename changes with each succeeding attempt]. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor.
Abort      Retry      Ignore

-----------------------------------------------------------------

Clicking Retry repeats the error message. Clicking Abort initiates a roll-back. Clicking Ignore allows the hotfix to continue installing, but it doesn't successfully install because the next time I run Live Update I'm again told I need to apply the hotfix.

GaryK

Comments 29 CommentsJump to latest comment

Mike Oakley's picture
I have exactly the same symptoms, both for LiveUpdate and separately downloaded installs.  Mike
Gary Karasik's picture
I've got a case setup w/escalated tech support. I'm betting it's a bad update. I'll post back when I get a resolution.
 
GaryK
SS 2's picture
I too have a case setup w/escalated tech support. I am supposed to get a call around 0900 CST. I'll post once they have called.
Gary Karasik's picture
That's great. If there's enough squealing, they'll figure out there's a pig.
 
GaryK
SS 2's picture
I heard back from Symantec and here is what they want me to try. I can't until 1930 or later tonight, so I don't know if it works but thought I would update you.
 
- Close BE
- Open Add/Remove Programs
- Choose Symantec Backup Exec, click change
- Follow prompts, choose repair, let it finish
- Reboot.
- After reboot, try Liveupdate again
PhotoTrance's picture
SS,
I just tried this, and still the same issue. Their workaround didn't help.
Tech XL's picture

I've got this problem as well.
I also suspect it's a bad hotfix after a bit of research.

Chris.

Doug Laskosky's picture
Tried installing hotfix manually. When prompted at error, I selected ignore. The patch seems to have been installed it shows in Add/Remove programs when display updates checkbox is selected. However, after a reboot the hotfix still attempts to install via liveupdate causing an error event.
NGPIT's picture
I worked with Symantec on this issue and I might have the fix.  I had Hot Fix 300287, 300290 and 300699 installed.  We removed 300699 via add/remove programs and then ran the LiveUpdate and 301030 installed successfully.  301030 requries a reboot, but I am not going to be able to reboot for a while.  The hot fix is not being displayed in the Installed updates window or add/remove programs.
 
My tech had a server that only had 300287 installed.  He also had a problem with 301030.  He removed 300287 instead of 300699.  LiveUpdate stated the install was successful and their is an alert saying 301030 was installed successfully.  After the install and reboot it does not display the Hot Fix in the Installed Updates window.  It also does not display the Hot Fix in add/remove programs.  Running LiveUpdate again says that things are up-to-date.
 
Gary Karasik's picture
Advanced support sent me an email suggesting that a full uninstall/reinstall would fix the problem.
 
1) I don't believe it will
2) I have 9 unrelated servers exhibiting the same symptoms, and I'm not wanting to uninstall/reinstall 9 times.
 
GaryK
Rikun's picture

If anyone tries NGPIT's solution, please post your results.  I tried it but got an error when trying to uninstall the hotfix.  It was something like "Error 1325: Live Update is not a valid short file name."  Anyone know how to fix that?  Maybe I have to try running the Repair option?  Thanks.

Gary Karasik's picture
I installed the HF manually too by telling it to ignore the error. It completed but does NOT show up in Add/Remove. The advanced support tech said that he'd heard that a complete uninstall/reinstall would solve the problem, which 1) I don't believe; and 2) I don't want to have to do 9 times on the 9 unrelated servers I have that all have the same symptoms.
 
GaryK
PhotoTrance's picture
I just tried NGPIT's solution and nothing, same problem.
Gary Karasik's picture
Also just tried removing the already installed hotfixes. Trying to remove 300290 gives the same error as does trying to install 301030. I told it to ignore the 300290 error and continued the removal, then rebooted. Hotfix 301030 still fails to install. Interestingly, with the previous hotfixes uninstalled, Live Update doesn't show that those previously installed hotfixes need to be reinstalled. If they've been uninstalled, shouldn't they need to be reinstalled?
 
GaryK
Rick Lawsha's picture
Add me to the list - won't install here either....
Joseph G Smith Jr's picture
I've run into the same problem with HOTFIX 301030.
 
Running on a Windows 2003 R2 server.
 
I've tried several of the recommendations listed here with no success.
 
Let's hope Symantec comes up with a solution soon.



Message Edited by Joseph G Smith Jr on 04-17-2008 11:01 AM

RossG's picture
I have the same problem with all of my 12.0 sites...   I am wondering wht is the official position of Syamntec is on this?  I heard install and unoinstall is an optiom but this will be so time consuming so I am wondering if anyone has successfuly passed installing this HOTFIX
 
RG
Gary Karasik's picture
"I heard install and unoinstall is an optiom but this will be so time consuming so I am wondering if anyone has successfuly passed installing this HOTFIX"
 
I'm waiting until this is confirmed. There have been other purported "workaround" scenarios that haven't worked.
 
GaryK
Gary Karasik's picture
Thanks to Ward at Symantec, this is what's working for me:
 
 
Download 300290 and 301030 hotfixes (grumbling over the stupid requirement
Uninstall 300290 only from Add/Remove Programs.
Shut down BEWS12.
 
Gary Karasik's picture
Thanks to Ward at Symantec, this is what's working for me:
 
 
Download 300290 and 301030 hotfixes (grumbling over the stupid requirement to
Uninstall 300290 only from Add/Remove Programs.
Shut down BEWS12.
 
Gary Karasik's picture
Thanks to Ward at Symantec advanced tech support, this is what's working for me:
 
 
1) Download 300290 and 301030 hotfixes (grumbling over the stupid requirement to put in a name and email address which really can't matter since you can put in phony ones).
 
2) Uninstall 300290 only from Add/Remove Programs.
 
3) Shut down BEWS12.
 
4) Manually install 301030.
 
5) Manually install 300290.
 
What didn't work: Uninstalling all hotfixes--could only reinstall 300699. Others failed.
 
Also, uninstalling/reinstalling the entire product did work, although when Live Update ran, it didn't show 301030 as necessary, so this may be dependant on the presence of 300290. If you go the uninstall/reinstall route, do NOT run Live Update after the install completes. Instead, first run the downloaded, standalone 301030, then run Live Update and allow it to reinstall the other three hotfixes.
 
GaryK
SS 2's picture
Here is what worked for me.Uninstall Hotfix 300290 via add/remove, then manually install 301030, then manually install 300290.
 

301030 - http://support.veritas.com/docs/301030

 
 
Mike Oakley's picture
Yes, removing 300290, stopping BE services, then applying 301030 then 300290 in that order has worked for me too, at least as far as installing the fixes & satisfying LiveUpdate goes.  However, I shall still be interested to see if future Hotfixes sit on top of this configuration without further extraneous work from all of us, I wouldn't want to have to uninstall 2 and install 3 by hand etc for ever more.
Joseph G Smith Jr's picture
The recommended fix has worked for me.
 
Thanks to GaryK and Ward at Symantec.
 
Thanks to all.
Gary Karasik's picture
From Mike Oakley: "Yes, removing 300290, stopping BE services, then applying 301030 then 300290 in that order has worked for me too, at least as far as installing the fixes & satisfying LiveUpdate goes.  However, I shall still be interested to see if future Hotfixes sit on top of this configuration without further extraneous work from all of us, I wouldn't want to have to uninstall 2 and install 3 by hand etc for ever more."
 
I just got a follow-up call from Ward. The engineers are working on a patch to fix this. They changed the patch procedure in BEWS12. In 11, if there were a change in a file, the entire file would be replaced, which was creating some big hotfixes. In 12 they are trying to have smaller hotfixes by patching the file itself. Obviously they haven't worked out all the kinks. :smileymad:
Richard Brown's picture
Interesting - I was having the same problems, and just ran live update again.  Instead of 301030, it gave me the option to install 300289, which worked, and there are no other live update issues listed,  Could this be the promised fix?
Gary Karasik's picture
"Interesting - I was having the same problems, and just ran live update again.  Instead of 301030, it gave me the option to install 300289, which worked, and there are no other live update issues listed,  Could this be the promised fix?"
 
Not according to the blurb at the download page--it's a UI fix.
 
Good news is that it installed trouble-free.
 
GaryK