Apache Friends Support Forum

I've downloaded and installed the latest version of XAMMP (1.8.3), and that went fine. But when I tried to start the MySQL module, I got this error log...

130830 22:52:45 [Note] Plugin 'FEDERATED' is disabled.
130830 22:52:45 InnoDB: The InnoDB memory heap is disabled
130830 22:52:45 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130830 22:52:45 InnoDB: Compressed tables use zlib 1.2.3
130830 22:52:45 InnoDB: Initializing buffer pool, size = 16.0M
130830 22:52:45 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
130830 22:52:45 InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
130830 22:52:45 InnoDB: Log file C:\xampp\mysql\data\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
130830 22:52:45 InnoDB: Log file C:\xampp\mysql\data\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
130830 22:52:48 InnoDB: Waiting for the background threads to start
130830 22:52:49 InnoDB: 5.5.32 started; log sequence number 0
130830 22:52:49 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

Can anyone help me?
Thanks in advance!

I cant see any error there?!

The MySQL module just won't start for some reason. I've uninstalled and reinstalled XAMMP too, thinking that would help. Nothing.

I was able to resolve this problem by closing the Control Panel and reopening using "run as administrator".

htdavis wrote:I was able to resolve this problem by closing the Control Panel and reopening using "run as administrator".

How do you do that?