MySQL on windows server 2008(Build 6001)...

[petter7252]

So I'm trying to install MySQL on the server i get to the point where i gotta do the configuration wizard, but the wizard wont start.

I got detailed info about the error:

 

Activation context generation failed for "C:\Program Files\MySQL\MySQL Server 5.0\bin\MySQLInstanceConfig.exe".Error in manifest or policy file "C:\Program Files\MySQL\MySQL Server 5.0\bin\MySQLInstanceConfig.exe" on line 6. The value "asAdministrator" of attribute "level" in element "urn:schemas-microsoft-com:asm.v1^requestedPrivileges" is invalid.

 

 

 

^-- thats the 5.0 version...

 

 

This is the 4.1 version error:

 

 

 

 

 

 

 

 

 

 

Any idea of how to fix this?

 

 

I'm willing to give you remote access if you wanna try to fix it(pm me)

[AWS]

First thing you could try is to set permissions on the mysql dir to allow write access.

 

I had a different problem when I tried to install mysql on one of the first betas. I found that the service is not being created by the installer.

 

I downloaded the zip without installer and installed mysql manually.

If you need help installing manually see this article I wrote for Windows 2003. The process is the same.

 

If you have any further questions post back.

[petter7252]

How do i do that?

And what folder? where do i find it?

 

I'm open for remote control you know :P

[AWS]

Browse to the mysql dir and set permissions to write and modify on the myql dir.

 

To do that right click the mysql dir and select the security tab at the top.

 

Click the edit button just below the permissions window. Even though administrator should have access set to full control it might not. If you don't want to manually install using the tutorial I wrote, my installs were done via RDP and the tutorial takes that into account, you can try installing at an elevated level. Right click installer and choose run as administrator.

[petter7252]

Ok, so i believe that would work, but i have a question, i see that the my-medium only uses 32-64 mb of ram and that its for systems with 125 mb ram, but what if i got 8 gigs of ram, running iis and a gaming server there MySQL plays a VERY big role...

[AWS]

Use my-huge.ini as a start and you can adjust it as needed. For this server I have 8Gigs like you on the db server and have it set at 512.

[petter7252]

Like this?:

 

[client]
#password	= your_password
port		= 3306
socket		= C:/mysql-5.0.51/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
basedir=C:/mysql-5.0.51
datadir=C:/mysql-5.0.51/data
port		= 3306
socket		= C:/mysql-5.0.51/mysql.sock
skip-locking
key_buffer = 512M
max_allowed_packet = 1M
table_cache = 1024
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

 

 

 

 

I tried that configuration and got an error when I was trying to start mysql:

C:\mysql-5.0.51\bin\mysqld: Too many arguments (first extra is '-console').
Use --help to get a list of available options

[AWS]

use --console as only argumant when starting mysql for the first time.

 

C:\mysql-5.0.51\bin\mysqld --console

 

Your my.ini looks good. If the above doesn't work move my.ini to c:\Windows and see if that works. Once you get mysqld running you can use mysql administrator to set my.ini to mysql dir.

[petter7252]

080220 0:28:19 [Warning] Changed limits: max_open_files: 2048 max_connections:

100 table_cache: 969

080220 0:28:19 InnoDB: Operating system error number 32 in a file operation.

InnoDB: The error means that another program is using InnoDB's files.

InnoDB: This might be a backup or antivirus software or another instance

InnoDB: of MySQL. Please close it to get rid of this error.

[AWS]

Looks like the first install of mysql is running.

 

Check processes in task manager ad see if mysql is running. If it is stop it.

[petter7252]

080220  1:12:41 [Warning] Changed limits: max_open_files: 2048  max_connections:
100  table_cache: 969
080220  1:12:41  InnoDB: Started log sequence number 0 43655
080220  1:12:41 [Note] C:\mysql-5.0.51\bin\mysqld: ready for connections. Version: '5.0.51a-community-log'  socket: ''  port: 3306  MySQL Community Editio
n (GPL)

 

 

 

That warning...nothing to worry about?

[AWS]

Nothing to worry about.

 

Connection limit is a little low.

 

Add this to my.ini and restart mysql.

max_connections = 500

[petter7252]

Ok so now i got a other problem, i cant connect to it with my workstation...

 

1130 - Host 'computername' is not allowed to connect to this MySQL server

 

Using navicat...

 

it works fine on localhost.

 

 

 

GOT IT

 

No worries i got it, i connected local and i managed users, and added user for my ip :D safe and secure...i believe...

[AWS]

As long as you set access by IP and created a user you'll be safe and secure.

[AWS]

I just installed mysql on my 2008 server. One thing I seen different than any install on 2003 is the connection is set to named pipes. I had to force network to get mysql gui tools working.

 

Then I installed php. I'm using the new fastcgi wrapper so once the server goes into production I'll see if the performance is any better than it was in 2003. Sure is easier to get it installed.

[petter7252]

Becaus of an backup error i reinstalled server2008 and now i cant run mysql...i get this error when i try to run it for the first time

C:\Windows\system32>C:\mysql\bin\mysqld --console
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
080301  0:09:34  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
080301  0:09:34  InnoDB: Starting an apply batch of log records to the database.
..
InnoDB: Progress in percents: 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 5
1 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77
78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
080301  0:09:35  InnoDB: Started log sequence number 0 43655
080301  0:09:35 [Note] Recovering after a crash using mysql-bin
080301  0:09:35 [Note] Starting crash recovery...
080301  0:09:35 [Note] Crash recovery finished.
080301  0:09:35 [ERROR] Fatal error: Can't open and lock privilege tables: Table
'mysql.db' doesn't exist

 

 

 

I have tried to uncheck the "read only" tag in the mysql properties, but when i press apply, close the window and open it again, the "read only" tag is checked...whats up with that?

[AWS]

Is the mysql data dir set in my.ini? It could be the new install is not reading my.ini.

 

It could also be NTFS permissions are wacked. Might want to stop the service and replace the mysql db with the one from the zip.

[petter7252]

So how do i fix that ntfs problem?

[AWS]

You have to take ownership of the file. Right click and select security.

[petter7252]

it doesnt work :-O

 

 

I click apply and maybe a second after, it gets unchecked. That is for the "creator owner" group.

[AWS]

Since mysql worked before the OS reload it is probably best you could do is remove everything and reinstall mysql. The mysql db holds the connection information and mysql access info.

 

You should save any db you created and then after install copy them back.

[petter7252]

ahh, got it...