MySQL Bugs: #46257: Install Windows XP 64bit, svctag.xml

Bug #46257	Install Windows XP 64bit, svctag.xml
Submitted:	17 Jul 2009 5:27	Modified:	31 Jul 2009 15:55
Reporter:	Carl-Johan Wik	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / NET	Severity:	S1 (Critical)
Version:	6.1.0	OS:	Windows (xp 64bit)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	install

Description:
I have downloaded and tried to install the MySql Connector/Net .msi package. The progress bar reached the end and then a popup says:

"Failed to open XML file C:\Program Files(x86)\MySQL\MySQL Connector Net 6.1.0\svctag.xml, system error; -214702786"

I have tried diffrent versions of the package, ex. 6.0.4 and it says the same thing.

I have tried to change the location during install and it still says the same thing.

I have made sure that the file in not readonly.

Downloaded the code, but as the install package/code is not part of the download was it not possible to try to look at what is wrong in the WiX.

Log:

msiexec /i mysql.data.msi /l*v c:\temp\a.log

See attachment.

How to repeat:
Download package 6.1.0 .msi.

Install: Typical, Custom or Complete.

Wait until error message.

Suggested fix:
As thee WiX setup project is not part of the source code is it hard to make an suggestion.

Log file .msi install.

Attachment: a.log (, text), 375.84 KiB.

Forgot to mention.

As I couldn't find documentation was it not possible for me to install the .dll manually.

Missing file

Attachment: svctag.xml (text/xml), 1018 bytes.

Orca analysis of the MSI

Attachment: cNET-610-Orca.zip (application/force-download, text), 5.14 KiB.

Interesting. The file is installed. 

* I run install.
* Messagebox with error message popup.
* I don't click ok.
* I go to C:\program files(x86)\MySQL\... and look then I can see the file.

* Then I click ok and the install rollback and the file is removed.

Thank you for the tip about orca, forgotten about that one.

I open the .msi package in orca and look at the file table, I can see svctag.xml file there. 

File          Component_     FileName
XmlSettings   Registration   svctag.xml

Did you missing in some other way?

SS from Win2K8SE x64

Attachment: Bug-46257.jpg (image/jpeg, text), 29.59 KiB.

Hi Carl and thanks for your report.

I was not able to repeat it on XP 32bit and Win2K8SE x64 boxes. svctag.xml is there and installed. However, I am setting the report to "Verified" on the basis that the attached Orca analysis shows some errors (although most of them irrelevant) and some potential errors in c/NET MSI. There is a same problem reported for c/NET 6.0.4 MSI in http://forums.mysql.com/read.php?38,267731,267731#msg-267731.

Reggie, will you please check the attached Orca log and see if anything needs to be fixed.

As for manual install, you can always point your code to c/NET binaries but then again, you won't be able to use integration in VS, for example.

My final guesses are:
  o You're out of space on your disk
  o Download is corrupted, please check MD5
  o svctag.xml file is corrupted and/or you do not have privilege on the "Program Files" folder
  o Some process (AV or such) is holding lock on svctag.xml file

Google matches:
http://support.microsoft.com/default.aspx?scid=kb;en-us;834484
http://consumerdocs.installshield.com/selfservice/viewContent.do?externalId=Q108158&sliceI...
http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId...

Forgot to mention, I always use complete install. Further more, XP 32bit SP3 box has only VS2005Pro while W2K8SE x64 box has both VS2008 and 2008Pro installed.

Thank you for looking into this!

Tried some more things.

  o You're out of space on your disk
Have 30 gig left on drive.

  o Download is corrupted, please check MD5
Check and is ok.

  o svctag.xml file is corrupted and/or you do not have privilege on the "Program Files"
I am adminstrator on machine. During the error message can I see the file on disk and the permission on the file is full control for me. I can open the file. See attachement.

  o Some process (AV or such) is holding lock on svctag.xml file
Not sure about this one, but the Process Explorer from Microsoft dont report that the file is locked.

svctag.xml file during MessageBox with error message.

Attachment: svctag.xml (text/xml), 1.27 KiB.

Yup, xml file corrupted just like described in forum posts:
<cpuManufacturer>⪀nuineIntelGenuineIntel,GenuineIntel,GenuineIntel</cpuManufacturer>

How can I get hold of the source code for the WiX project?

(I am sorry, I am new to the MySQL world.)

I have downloaded the source but the WiX project was not there. If I can get hold of the WiX project can I have a look at it and see if I find something.

Please point me in the right direction how to find the "svn/trunk".

Carl, check on Bug#42411. Download some SVN client (I use TortoiseSVN) and check the repository. Latest development code is always in /trunk (6.1.x now) while wix files are under /install. Other branches are self explanatory.

Is it possible that this issue only shows up on multi-core systems?

I can reproduce this on 32-bit and 64-bit Windows XP Pro SP2 but only on multi-core systems.

2-cores: (Failed)
<cpuManufacturer>櫘nuineIntelGenuineIntel</cpuManufacturer>

4-cores: (Failed)
<cpuManufacturer>៨nuineIntelGenuineIntel,GenuineIntel,GenuineIntel</cpuManufacturer>

1-core: (Installed fine)
<cpuManufacturer>GenuineIntel</cpuManufacturer>

That might be the difference. For me it was the same.

64bit XP, 4-cores: (Failed)
64bit XP, 1-core: (Installed fine)

Carl & Colin, unfortunately, it is not so easy. My primary box that has never failed is Q6600... What could be the true reason, Reggie might know.

I've got this problem with a single core using 6.0.4

6.0.3 works fine.

we believe this is caused by the same underlying problem as bug #45474.  Leaving that one open as we work on it.

Bug#46543 was marked as duplicate of this report.

if someone doesnt want to register, theres another way to fix this:

1) grab the sources & svn client & wix
2) modify registration.wxs and comment out from line 34 to 50
3) rebuild and install.

Try reinstall Microsoft XML Parser (MSXML).

My solution: install an older version of the connector or upgrade your .NET framework version.