MySQL Lib on Windows Vista?

MySQL Lib on Windows Vista?

Postby inTrance » Mon 07 Aug 2006 01:17

I try to install your lib on Windows Vista (latest Beta + VS 2005 Pro) but
the setup fails with the error code 1722. There is no additional information
and the Setup log-file is empty. The installation of the demo version works
but I'm not able to compile, because of some error concerning that VS
is unable to find the type CoreLab.MySQL.dll

Do you know if it's possible to install your lib on Vista (especially the
paid version)? And what does this error 1722 mean?

Regards,

inTrance
inTrance
 
Posts: 10
Joined: Tue 04 Apr 2006 17:07

Postby Serious » Mon 07 Aug 2006 06:18

Execute the next command and send us corelab.log file: msiexec /i mysqlnet.msi /l*v corelab.log

Use e-mail provided in the registration letter.
Serious
 

Postby dknapp » Wed 20 Sep 2006 18:44

Has this been resolved yet? I am running into the same issue.

Running :
Windows Vista Business Professional RC1 Build 5600
CoreLab - MySQLDirect .NET Data Provider Professional version 3.50.11 - 03.07.06

I dont have Studio 2005 installed, but I am running Web Developer Express and Visual Basic Express.

thanks
dknapp
 
Posts: 10
Joined: Wed 20 Sep 2006 18:26

Postby dknapp » Wed 20 Sep 2006 20:35

Update:

I have downloaded the latest version, CoreLab - MySQLDirect .NET Data Provider Professional version 3.50.13 - 19.09.06. I still get the same issue as before.

I have tried to install this with the /a (admin) option and get an error reading: "1: This setup requires Internet Information Server 4.0 or higher for configuring IIS Virtual Roots. Please make sure that you have IIS 4.0 or higher." [ Abort / Retry / Ignore ]

So I pressed Ignore and the installer continues and I get a new error message.

"Error 1721. There is a problem with the Windows Installer package. A Program required for this install to complete could not be run. Contact your support personnel or package vendor."

At this time the Status of the installer reads "Registering help".

After you click [ ok ] it rolls the install back and give you a message reading that the installer was interrupted before Core Lab MySQLDirect Data Provider for .NET 2 Professional could be completely installed. Your system has not been modified. To complete installation at another time, please run setup again.

Click Finish to exit the wizard.

The original error message reads:

"Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor."

on a side note: I have tried this installer on a Windows XP Pro machine with out any errors.

Thanks,
dknapp
 
Posts: 10
Joined: Wed 20 Sep 2006 18:26

Postby Alexey » Thu 21 Sep 2006 07:16

Please execute the command which was mentioned above and send me (AlexeyI at crlab dot com) corelab.log file.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby dknapp » Thu 21 Sep 2006 14:32

I forgot to add that I was using a .EXE file not an .MSI file. I did as instructed ( substituting the EXE for MSI ) and have sent the email.

Awaiting further instructions.

Thanks,
dknapp
 
Posts: 10
Joined: Wed 20 Sep 2006 18:26

Postby Alexey » Thu 21 Sep 2006 14:45

Replied you by e-mail.
Waiting for another log file.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby dknapp » Thu 21 Sep 2006 15:01

Ok I resent the email with the new Log file. It is almost 2MB in size.

Thanks,
dknapp
 
Posts: 10
Joined: Wed 20 Sep 2006 18:26

Postby Alexey » Fri 22 Sep 2006 12:21

We are investigating MySQLDirect .NET compatibility with Windows Vista.
You'll be notified on results as soon as possible.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

UPDATE

Postby dknapp » Tue 31 Oct 2006 17:58

I have upgraded from Windows Vista RC1(5600) to Windows Vista RC2(5744) and thought I would send an update. The install still fails the same as before.
dknapp
 
Posts: 10
Joined: Wed 20 Sep 2006 18:26

Postby Alexey » Thu 02 Nov 2006 09:19

This is low priority issue until Windows Vista is released. We will investigate this problem soon.
Last edited by Alexey on Thu 07 Dec 2006 10:06, edited 1 time in total.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Vista is released now

Postby joshmouch » Sun 19 Nov 2006 15:27

So Windows Vista has been released now to MSDN and volume license customers. Is there a resolution to this problem? I have the same error.
joshmouch
 
Posts: 12
Joined: Sat 11 Dec 2004 05:54

You must be misinformed on Vista release dates.

Postby joshmouch » Sun 19 Nov 2006 16:14

Looking throughout the forums, the common response to the Vista problems is that it is low priority because Vista isn't out yet. That the response only two days ago.

However, Vista RTM *is* out now, so the priority should perhaps be bumped up to "simmer"?

Once posted solution is to install to XP and copy the files. I am willing to do this, but which files need to be copied to maintain the Policy settings (e.g. an application I am using is expecting version 3.2, but I have version 3.5 installed)? I do not see a policy.3.2.CoreLab.Mysql.dll in the GAC that I could copy.
joshmouch
 
Posts: 12
Joined: Sat 11 Dec 2004 05:54

Licensing using the Vista work-around

Postby joshmouch » Sun 19 Nov 2006 17:10

Also, I am getting a licensing exception from MysqlConnection.Open() when I try copying an install from an XP machine to a Vista machine.

The licensing works fine on the XP machine. I saw another post that suggested removing the DLL from the GAC, and a few registry settings. I did that, and still get the licensing error.

This is a project that works in XP (has the license.licx and all that), so the problem is with the fact that I copied the CoreLab DLL's rather than using the install.
joshmouch
 
Posts: 12
Joined: Sat 11 Dec 2004 05:54

Excerpt from MSI log

Postby joshmouch » Sun 19 Nov 2006 19:54

Do you have a workaround for getting the licensing working? I've tried reflecting your binaries, but everything is obfuscated, so can't tell what is going wrong.


And, since no one else posted it, this is the last few lines before the 1722 error occurs. Before this, there are several more errors related to the radio buttons "Typical", "Custom", etc., but I do no think they are related.

From the MSI installation, log:

MSI (s) (18:B0) [14:44:37:509]: Executing op: CacheSizeFlush(,)
MSI (s) (18:B0) [14:44:37:509]: Executing op: ActionStart(Name=RegisterGAC,,)
Action 14:44:37: RegisterGAC.
MSI (s) (18:B0) [14:44:37:512]: Executing op: CustomActionSchedule(Action=RegisterGAC,ActionType=1026,Source=BinaryData,Target="MySQLDirect .NET" "C:\Program Files\CoreLab\MySQLDirect.NET2\" "C:\Program Files\CoreLab\MySQLDirect.NET2\CoreLab.MySql.dll",)
MSI (s) (18:B0) [14:44:38:383]: Executing op: ActionStart(Name=Install,,)
Action 14:44:38: Install.
MSI (s) (18:B0) [14:44:38:385]: Executing op: CustomActionSchedule(Action=Install,ActionType=1026,Source=BinaryData,,)
MSI (s) (18:B0) [14:44:38:477]: Note: 1: 1722 2: Install 3: C:\Windows\Installer\MSIA917.tmp 4:
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action Install, location: C:\Windows\Installer\MSIA917.tmp, command:
MSI (s) (18:B0) [14:44:42:819]: Product: Core Lab MySQLDirect Data Provider for .NET 2 Standard -- Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action Install, location: C:\Windows\Installer\MSIA917.tmp, command:

Action ended 14:44:42: InstallFinalize. Return value 3.
joshmouch
 
Posts: 12
Joined: Sat 11 Dec 2004 05:54

Next

Return to dotConnect for MySQL