Home Forums Discussions Problems KB954430 Windows Update and AC Error 1306

Hi fellow AC users:
I just want share my story of Windows Update updating KB954430 update.

Problem:
Our MAIN comp was failing to start AC and its other programs such as Amazing Utilities, Amazing Backup, etc. We have version 5.0.26.
When I double click AC shortcut or access it through programs menu, AC application was trying to install and was poping up Error 1306 window. Exact message was:
"Error 1306. Another application has exclusive access to the file 'C:\AmazingCharts\codes.ldf'. Please shutdown all other applications, then click Retry."
with Retry and Cancel button.
Clicking Retry was going nowhere. Clicking Cancel was generating "Fatal error during installation." message window.

Even after restarting the comp problem persisted.

Background:
A day before I tried to run Windows Update. "Security Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB954430)" update was failing to install. It was not installing for some reason.
Its FIX involved deleting MSXML4.dll and MSXML4r.dll files under %systemroot%\system32 folder.
After deleting above files I ran Windows Update which installed KB954430 update.
BTW, this happened on 5 of our networked client comps and MAIN comp. All of our comps have Win XP pro.
FIX installed KB954430 update on all of our client comps but not on MAIN comp. It looked like FIX went through fine on MAIN comp as there were no error messages while installation. Rerunning Windows Updat did not show any pending updates.

Now, next day morning AC was failing to start and creating above mentioned "Problem".

Solution:
Upon looking into %systemroot%\system32 folder MSXML4.dll and MSXML4r.dll files were missing and "Add or Remove programs" list did not have KB954430.
I was mislead by Window Update info. It did not report KB954430 installation failure. I did not bother to check for these DLLs as there were no error
Any how, I manually downloaded and installed this particular update which installed above DLLs. This time I verified existence of these DLLs in %systemroot%\system32 folder and listing of KB954430 under Add or Remove Programs list.

Bingo! AC was running like race horse.

Rao,

That update keeps popping up, and it will not install. I also went to Windows to search for the manual install. I thought I did, but I am not sure.

PLEASE...can you leave out all the exciting stuff and narrow it down to the point where you had the problem with XML Core Services 4.0 SP2?

Please give step by step instruction. I know it is straightforward, but I don't want the problem you had, and I am thankful you posted it.

Can you give the link for the one you manually downloaded. I am also running XP Pro on all machines and everyone has the yellow shield telling me I have this update.

Thanks in advance.

use KB973688 from the microsoft site. It supersedes the above fix and actually solves the "problem". My office worked with Microsoft tech support a long time and thought we had fixed the problem many times, but it kept returning. In fact, keep ahold of the above hotfix because I needed to use it again when updating AC, but it is relatively painless to install. I suspect AC has an older version of Msxml that it installs on some win XP machines as my one Vista (boo) machine was not plagued by this problem.

Thanks Rao and mkweiss.

I have Win XP pro on all my PCs.
0. Login as administrator user.
1. Go to Start > Settings > Control Panel > Add or Remove Programs > Select "MSXML 4.0 SP2 KB954430" installation and click Remove button.
2. Go to %SystemRoot%\System32 and select MSXML4.DLL and MSXML4R.DLL files and delete them.
3. Go to Microsoft Download Center.
I went to Google and typed "KB954430 download" and clicked on Microsoft link (first link).
This should open
"Security Update for MSXML 4.0 Service Pack 2 (KB954430)" web page.
http://www.microsoft.com/downloads/...f69-83d0-932c430abd14&displaylang=en

Click DOWNLOAD button on this page to download msxml4-KB954430-enu.exe file.
Use this exe to install KB954430 update.

4. Go to %SystemRoot%\System32 folder. You should see MSXML4.DLL and MSXML4R.DLL files.

Thanks for the detailed instructions.

We have the same problem with these recurring updates, on multiple machines, different operating systems, different manufacturers. The "fix" fixes it, until the next AC update, when it again starts wanting to reinstall repeatedly. AC support insists their install has nothing to do with MSXML 4.0. But if it looks like a duck...

Have you tried marking the box to ignore the update?

Bert,
I must admit, after the last round there were a couple of machines I marked to ignore the update. (Felt like I needed to go to confession, though.) My concern is that if AC's install is actually tweaking MSXML 4.0, and the update doesn't get done properly, then the security vulnerability the update addresses remains. But then I'm paranoid... I wonder if there are a bunch of folks with this problem who just never notice that the same update is being installed daily.

I guess I am not as paranoid. Eventually, they won't even support Microsoft XP Pro. For me, I don't think it is AC, because I can't get it to install period. So, I just turned it off.

This is an old post, but new installs of AC on XP SP3 still get this issue. AC installs an old 2002 version of MSXML4.dll etc. Windows update tries to install the MSXML4 service pack and either fails or the install is corrupted. The SP2 will then keep trying to reinstall, driving everyone crazy. See
http://forums.techarena.in/windows-update/1080894.htm
Doing the fix for this problem from MS
http://support.microsoft.com/kb/941729/
also does not always work, because after renaming MSXML.DLL to MSXML.OLD, the Windows Update will not find MSXML4 at all and will not offer the SP2 update at all. If AC is relaunched in this situation, it will reinstall the moldy old MSXML4.dll from 2002 again, and you are back where you started.
The only solution is to remove the MSXML4.DLL and MSXML4R.dll files from the system32 folder by hand (or better - rename them with .old), download the KB954430 update directly (not using Windows update), run it, and do a repair. This will install the new (2009) versions of MSXML4.dll and MSXML4R.dll. AC, when launched, will find the new MSXML4 version and fuss about it by checking database integrity. But once it gets done, you are in business and more secure, since you will have the updated KB954430 MSXML4 SP2 installed. The repeated prompts to reinstall this service pack also go away.

Has anybody tried to foward this thread directly to Jon and get his feedback on this situation. Some of my Computers are acting sort of weird as I too have avoided the SP 3 update because of this recuring discussion that never seems to really end with a final great answer. Although it sounds like CRR might have just done that here and now. Still I don't want to have to go around the horn 5 times with all the machines in the office and have the system not cooperating for my wife when I am not in the office to deal with the PIA issue like this one....

Bert as one of our most well versed and respected resident grurus what's your thoughts on all of this? You know I value your feedback and opinion, no offense intended to CRR here who seems to know what he is talking about and has found what one would hope to be the "Final Answer" here....

Thanks,
Paul

The fix listed above for the KB954430 issue is needed every time AC v5 is uninstalled and reinstalled from scratch. Once kb954430 has been repaired by first deleting the offending 2001 msxml4.dll and msxml4r.dll files from the system32 folder and running the .net4 SP2 installer (msxml4-KB954430-enu.exe) again and using its repair mode, windows update will work again.

There are several more high updates to .net4 subsequent to the kb954430 (2008) version. These include the high priority <<Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB973688)>> (7/21/2009) and the optional <<Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008 x86 (KB2468871)>>.

There is now a new one ? the optional <<Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008 x86 (KB2533523)>>. So far, this last one (http://support.microsoft.com/kb/2533523) also fails to install ? there appear to be many people having trouble with it.

Hockeyref's comments are well taken - the patch installs are slow and the whole process can take over an hour for one machine. Going around the horn in a row boat is no fun.

The problem is caused by the .NET package included in the original SQL Server 2005 distributable that is installed by the AC installer; it does not detect an up to date .net 4 sp2 installation and installs the older version over it, making a mess. This whole story - the bad behaviour and the fix - has been confirmed and reconfirmed.

CRR, thanks for noting that this problem is not limited to Windows XP. We have the same problem on Windows 7, Vista, and Windows Server 2008. And we are using AC 6.0.9.

I suspect the lack of greater outcry is more from people not noticing the continual attempt to reinstall these updates.

This error that you are getting is not AC specific. This error happens allot of times when trying to update XML Core Services. The hot fix does work, but the error does come back from time to time. Yes Bert you are correct, in time...not long really, XP will be obsolete, for they will no longer have security updates or support for that operating system.

Yes but if they are endemic of the original genetics of the install program's DNA like blueprints, then in reality it really is OUR Vendor's problem and responsibility to deal with this properly once and for all. As Steve just said above this is happening on all of the various OS's because it is AC herself that is installing an older and not cooperative, does not play well with other version of the piece of the puzzle.

So my question here again is, since you guys seem to actually "Understand" this and can properly explain it and convey the correct stuff to others at AC who would understand likewise, Has anyone, have any of you Tech Savvy folks contacted AC directly and let them know your research and findings? It's time to put this Monkey to bed already... Please....

Paul

I'm confused as to how this would be your vendors (AC) problem. This is an operating system specific error, this in no means, has anything to do with AC software. I deal with XP operating systems all the time with this error.

I am speaking from ignorance here, but how is not our vendor's fault. Just because it is not AC specific, does not mean that AC is not aware of the problem and should take steps to fix it.

If Adobe's latest install produced a buggy product due to an error by Microsoft, I doubt they would just tell their customers, well this is Microsoft's issue. They would have already discovered the problem during their one of hundreds of installs and deemed the product not ready to be released.

TJI,

Hi, welcome to the AC userboard. I am just curious. Why did you refer to vendor as "your vendor" and not "our vendor?" Is it because you are just starting here?

Hi Bert,

Yes I am new here.

The problem is, AC does not do patches, they do new installs, which is being worked on to implement patches for things such as this.

If AC needs to run on latest service pack for system requirements, and XML core service is a service pack 2 issue, I see that more of a problem that their IT person should b working on to get them updated.