BGLComp Will No Longer Compile - MSXML 4 Bad Install

[scruffyduck]

I have changed the title to include MSXML 4 and made it a sticky since I do think it is a very useful thread

 

[arcueil]

That's great, Jon. I hope that it can help some folks out there.

 

[n4gix]

I am so glad you got it sorted out...

The major lesson to be learned from this is:

"Don't install the ATC Voicepack SDK unless you're prepared for major pain!"

 

[Green51]

Me too ...

Hi all,
Many thanks, Arcueil, for the tip to reinstall MSXML, I spend many hours to find "How these damned softwares didn't work anymore" after I jumped on windows 7. The solution was here, under my eyes ! Everything's right, now ; I can compile and be back to "the office".

Thanks again, Arcueil.

JCP

 

[matt]

Unfortunately I saw this post a little too late...I just installed the ATC Voicepack SDK and it caused this exact problem. I'll try running a registry repair utility and see what happens...

 

[vacica]

ADE compile problems

Hello,
I have the similar problem as arcueil had before, I can't compile any airport and have the same error message. The difference is that few days ago everything was OK and I was able to compile airports normaly. But then something changed and it doesnť work and I don't know why. The only idea I have is that it's somehow connected with the last Windows update because as I remember (but I'm not 100% sure) the problems have begun after that. I've tried exactly the same things like arcueil but with no result, there's still the same error message.
I also tried to drag some xml to bglcomp.exe, first time it worked but when I tried it again it didn't compile the airport.
I have Win7 64bit SP1, FSX SP2, FSX SDK SP2, MSXML4 SP3, ADE 1.50.07

I hope there's some solution of this problem because ADE is really great software

Jarda

 

[chris]

Just to add another msxml 4 problem.
Yesterday I uninstalled FS9.
This also uninstalls msxml 4 but the ADE Environment checker still show it as good.
Exactly the same problem occured as the OP.
The solution was to simply reinstall msxml.msi;

http://www.microsoft.com/en-us/download/details.aspx?id=15697

 

[scruffyduck]

Just to add another msxml 4 problem.
Yesterday I uninstalled FS9.
This also uninstalls msxml 4 but the ADE Environment checker still show it as good.
Exactly the same problem occured as the OP.
The solution was to simply reinstall msxml.msi;

http://www.microsoft.com/en-us/download/details.aspx?id=15697

Thanks Chris - a good addition to this thread.

 

[Gadget]

Thanks to Arcueil

Thank you for your time and effort!! I refer to your post on 23 july 2011 @2100 BGLComp will no longer compile. Not being the most computer savy person. (Just started on Java myself) you saved me countless hours of frustration. Your fix done exactly as you outlined did the trick. I can now enjoy ADE to its fullest.

 

[Winged_Jaguar]

OK I am not going to be much help. The only time I see this error is when MSXML 4 is not properly installed or is missing.

Can you confirm for me that you are loading an airport into ADE and then click File > Compile.

A number of the errors refer to loadFrom.xml. This file only gets created when something (airport etc) is loaded into ADE via XML. I don't think this has anything to do with the problem because I see one faile attempt to compile:


INTERNAL COMPILER ERROR C1003: Failed to create MSXML object! (0x80040154)



I assume from this that you have ADE pointed to your desktop to compile and save your bgl files...... Certainly you loaded an xml file into ADE from there:



I see no save folders though si I assume you have not tried to save a project yet

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

I too have spent many fruitless hours re-installing ADE, MSXML4 and BGLCOMP etc and examining the Registry. I have found a solution. The MSXML4.DLL application does not appear (in some circumstances) to get registered properly as part of the msxml.msi install process (possibly due to some earlier registration). The 'magic spell' on Windows 7 (32 bit) is to go to Start>CMD and execute the following command "REGSVR32 C:\WINDOWS\SYSTEM32\MSXML4.DLL". You should then get a positive 'Succeeded' confirmation back. Hopefully this will save a few people hours of headscratching.

 

[scruffyduck]

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

I too have spent many fruitless hours re-installing ADE, MSXML4 and BGLCOMP etc and examining the Registry. I have found a solution. The MSXML4.DLL application does not appear (in some circumstances) to get registered properly as part of the msxml.msi install process (possibly due to some earlier registration). The 'magic spell' on Windows 7 (32 bit) is to go to Start>CMD and execute the following command "REGSRV32 C:\WINDOWS\SYSTEM32\MSXML4.DLL". You should then get a positive confirmation back. Hopefully this will save a few people hours of headscratching.

Welcome and many thanks for the update

 

[Winged_Jaguar]

Correction to command

Welcome and many thanks for the update

Many thanks. I've corrected my typo. It should of course have read REGSVR32 C:\WINDOWS\SYSTEM32\MSXML4.DLL. After which BGLCOMP.EXE will recognise MSXML4 and compile.
One quick test to see if BGLCOMP.EXE and MSXML4 are working together is to run BGLCOMP from the command line against an XML file. If BGLCOMP can recognise MSXML4 it will attempt to run through the XML (albeit giving valid compile errors about that file). If it's all working you will no longer get the dreaded INTERNAL COMPILER ERROR C1003. ADE is a great program!

 

[Jalford]

Another fix for the problem

I ran into the same problem today and quickly found this thread. I had not changed or tried to reinstall any files yet except for ADE, thinking that was the problem. So, I just uninstalled the voicepak SDK and voila! ADE is back compiling again, and will leave the SDK out of the picture.

 

[VegasTim]

No msxml 4.0 file found

Same problem here guys, editvoicepack installed, ADE wouldn't compile. I got the latest msxml 4.0 file and went in to delete the old one and found it was gone ... nada, empty folder, nothing to be found anywhere. My 2009 flight sim computer is dedicated to FSX and associated programs only. Vista Home Premium 64 bit, E8400 DuoCore @3.0 w/ Nividia. GTS240 cards.

So I ran registry cleaner, fixing all faults, ran it 3 times until it found no faults, restarted and then installed the new msxml 4.0 and ADE now compiles just fine.

Just a post note - I am now an official ADE junkie! Love this program! Thanks so much to all here for posting solutions that help newbies to SDK's like me.
Super special shout out and thanks to Scruffy Duck for putting up with my emails: thanks dude, you rock.

 

[scruffyduck]

Same problem here guys, editvoicepack installed, ADE wouldn't compile. I got the latest msxml 4.0 file and went in to delete the old one and found it was gone ... nada, empty folder, nothing to be found anywhere. My 2009 flight sim computer is dedicated to FSX and associated programs only. Vista Home Premium 64 bit, E8400 DuoCore @3.0 w/ Nividia. GTS240 cards.

So I ran registry cleaner, fixing all faults, ran it 3 times until it found no faults, restarted and then installed the new msxml 4.0 and ADE now compiles just fine.

Just a post note - I am now an official ADE junkie! Love this program! Thanks so much to all here for posting solutions that help newbies to SDK's like me.
Super special shout out and thanks to Scruffy Duck for putting up with my emails: thanks dude, you rock.

You are most welcome

 

[sfrenchie]

I too just fixed the problem by simply uninstalling the voicepack SDK.
Uninstalling MSXML4 then reinstalling it.

However before doing so, I searched the registry for "editvoice". It found an entry that pointed to an MSXML4 file located in the folder where the SDK was installed. I haven't tried it but chances are it might make everything better by simply changing the path of that entry to the MSXML4 DLL installed in "SysWOW64"

FYI: after uninstalling the EditVoice SDK I still found 6 entries in the registry pertaining to this kit. I exported them (backup) then deleted them.
After clean installation of MSXML4 ADE restarted compiling.

 

[scruffyduck]

Thanks for the update on this Patrick

 

[virtualswede]

Just want to report that a simplified version of your repair, arcueil, worked for me too.

Solved

I was correct all along. It was the registry. Here's what went wrong and how I solved it:

* Upon installation, the ATC Voicepack SDK from Microsoft altered certain values in the registry pertaining to MSXML 4.0. It also added (or copied) two MSXML files to System32. The reason for these changes remains unknown. Ditto regarding its mechanism. Such a scenario is probably extremely rare.

* The above was the reason why BGLComp believed that the MSXML 4.0 installation was either non-existent or faulty, thus producing an identical error in all programs that use bglcomp.exe -- ADE, ExcBuilder and Rwy12.

* The situation with the registry was such that un-installing MSXML 4.0 was not changing anything inside the SysWOW64 folder or properly changing things in the registry, even though add-remove showed that the program had been "un-installed" (i.e. the entry in add-remove goes away). The opposite (i.e. installation) produced the same results.

* With your helpful posting of screenshots of the contents of your System32 and SysWOW64 folders, I was able to determine what should actually be inside those folders vis-a-vis MSXML 4.0.

* Things looked exactly like yours after I deleted the mysteriously added files in System32. However, nothing was working because the un-installs/re-installs were not changing anything inside SysWOW64.

* Although everything seemed normal (albeit MSXML 4.0 not allowing BGLComp to compile), I decided that the problem must be the registry, so I fired up every program that used MSXML 4.0 until I found one that malfunctioned. That malfunction said that "MSXML 4.0 was not properly installed".

* I went for broke and screwed up the registry on purpose by physically removing msxml4.dll and msxml4r.dll from the SysWOW64 folder without unregistering them and placed them on the desktop.

* I ran Uniblue's RegistryBooster in order to find the errors I had just created by taking the step above. It found 17 system errors that it did not pick up before. All of the errors involved MSXML 4.0. I had the program fix those errors and rebooted.

* After the computer rebooted, I went to Command Prompt and unregistered the two DLLs that now resided on my desktop. After that, I threw them out.

* I rebooted again and reinstalled MSXML 4.0 SP3 (the one without the SDK; it's not needed) and the SP3 KB update.

* This time, the install did make changes to the SysWOW64 folder (i.e. the files were placed there) and correctly wrote to the registry.

* I fired up the program that had earlier told me that "MSXML 4.0 was not properly installed" and it did not pop up that message again. The program worked perfectly.

* I went to ADE and it's now compiling. Ditto regarding ExcBuilder and Rwy12. BGLComp.exe is also working if I drag an XML file on top of it.

Thank you all for your help. It provided considerable assistance in guiding my train of thought. Cheers all.

Here were my steps:
1. Uninstall all FS2004 SDK tools, including the dreaded ATC Voicepack
2. Reinstall just BGLComp, this time into C:\FS2004SDK\BGLCOMP_SDK. Verify this is still broken with the ERROR C1003: Failed to create MSXML object! (0x80040154) error.
3. Scan the registry; I used Glarysoft's Registry Repair, found 193 errors.
4. Used Explorer to find all MXSML4s, search string name: msxml4*. It found them in C:\FS2004, C:\Windows\WinSxS (4 and 4r, inside folders with long computer-generated names), and C:\Windows\SysWOW (in that folder, 4 and 4r).
5. Moved the two from SysWOW to a desktop folder.
6. Tried to move the two from WinSxS, and it would not let me, even as administrator. Something about "Trusted Installer" or similar. So I left them.
7. Scanned the registry again, still only 193 errors (different than your result above, where more errors were introduced by moving msxml files).
8. Let Registry Repair do its thing.
9. Tried bglcomp.exe from its home folder, C:\FS2004SDK\BGLCOMP_SDK, and verified I was still getting C1003.
10. Used Windows Add Remove Programs tool to repair MSXML4. Following this, msxml4.dll and msxml4r.dll were back in C:\Windows\SysWOW.
11. Tried bglcomp.exe against the MortonWa.xml sample, and it works.
You good people saved me a lot of time, or more likely, abandonment of any more FS2004 scenery projects!