Pages: Previous12345678Next
Current Page: 4 of 8
Re: [Solved] #2002 error
Posted by: zaqali (1.22.66.---)
Date: June 26, 2013 04:18PM

Hi,

I am unable to open phpmyadmin. Local host is running but when I click on phpmyadmin it shows error

--------------------------------------------------------------------------------------
Error

MySQL said: Documentation
#2002 - No connection could be made because the target machine actively refused it.

The server is not responding (or the local server's socket is not correctly configured).

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

Also, the wamp server only turns to orange and not green.

Please help!!!

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: Sagarthapaliya (27.34.10.---)
Date: June 27, 2013 02:17AM

HI JUST GET TEAMVIEWER AND CONTACT EITHER ROSE FOLLY OR STEVEN MARTIN THANKS

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: RiggsFolly (---.as13285.net)
Date: June 27, 2013 10:40AM

The probelm is probably becasue the MySQL Service has not started.

The wampmanager icon shoudl be Green if both Apache and MySQL have started.


Look in mysql error log and also the windows event viewer for an error message from MySQL

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: sql beginner (101.63.147.---)
Date: July 02, 2013 12:27PM

hi Steven Martin

i m also having the same problem plz help me......i did lot of things to slove this problem but i cnt.....it gives me the following error message........thanks in advance......


Welcome to phpMyAdmin


Error
MySQL said:

#2002 - No connection could be made because the target machine actively refused it.

The server is not responding (or the local server's socket is not correctly configured).

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: RiggsFolly (---.as13285.net)
Date: July 02, 2013 03:24PM

Install TeamViewer and I will troubleshoot for you.

Install TV, then run it.

Do this before attempting a connection.

How to Configure Team Viewer so it does not require port 80 or 443

Run TV
Extras -> Options -> Advanced -> Press the Advanced Button -> Advanced Network Connections

Check the checkbox saying [ Dont use incomming port 80 (recommended for web servers only ) ]
Stop and restart TV.

Then
Send me a Private Message containing the TV ID and PASSWORD so I can connect.
Leave TV running as it will change the password each time you restart it.

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: sql beginner (115.244.224.---)
Date: July 02, 2013 07:26PM

thanks RiggsFolly ........thanks alot......

Options: ReplyQuote
Re: #2002 error
Posted by: chiinook (---.25.46.176.dyn.estpak.ee)
Date: July 26, 2013 09:41AM

I too was receiving a 403 error when I tried to access phpMyadmin. I allowed all in phpmyadmin.conf file and now am receiving the same #2002 error.

My log file reads as follows:
130726 0:58:32 [Note] Plugin 'FEDERATED' is disabled.
130726 0:58:32 InnoDB: The InnoDB memory heap is disabled
130726 0:58:32 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130726 0:58:32 InnoDB: Compressed tables use zlib 1.2.3
130726 0:58:32 InnoDB: Initializing buffer pool, size = 128.0M
130726 0:58:32 InnoDB: Completed initialization of buffer pool
130726 0:58:32 InnoDB: highest supported file format is Barracuda.
130726 0:58:32 InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: [dev.mysql.com]
InnoDB: File name .\ib_logfile0
InnoDB: File operation call: 'aio read'.
InnoDB: Cannot continue operation.

I have tried to research solutions but haven't yet met with any success.

I have Team Viewer and can set up a connection for anyone who can help.

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: RiggsFolly (---.as13285.net)
Date: July 26, 2013 12:19PM

Install TeamViewer and I will troubleshoot for you.

Install TV, then run it.

Do this before attempting a connection.

How to Configure Team Viewer so it does not require port 80 or 443

Run TV
Extras -> Options -> Advanced -> Press the Advanced Button -> Advanced Network Connections

Check the checkbox saying [ Dont use incomming port 80 (recommended for web servers only ) ]
Stop and restart TV.

Then
Send me a Private Message containing the TV ID and PASSWORD so I can connect.
Leave TV running as it will change the password each time you restart it.

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: navid.anwar (---.dsl.dyn.ihug.co.nz)
Date: July 27, 2013 02:43AM

Hi All,

Hope everyone is doing well. Let me explain the scenario and the provide the solution that I have done to take my phpMyAdmin back to work.

Scenario / Problem:
I have previous installation of WAMP Server in other partition than the OS installed. Due to New OS install, I have lost the old WAMP installation and then installed the new one in the same directory. I was able to start WAMP server successfully (showing green color in the system tray). Successfully connect to the mysql using command line but I was unable to connect to phpMyAdmin using my browser window and getting the same message i.e. #2002 error

Solution:
I read the post and did the following three steps that are:

1) Open httpd.conf and then change the entry Listen 80 -> Listen 0.0.0.0:80 (it didn't work for me, may be work for you)

2) Search for my.ini file for the previous installation and then remove it or rename it. (it didn't work for me, may be work for you)

3) Open the wamp root directory and then go to 'tmp' directory where you find the old sessions created by you old installation files. Remove all these files from the 'tmp' directory. (it is worked for me and now I get back to my phpMyAdmin panel for the new installation.

NOTE:
Whenever you do any of the above step then restart your wamp server to implement changes.
If still you are facing problem then kindly connect to the moderator of the forum ( stevenmartin99)


Enjoy! and kindly share your experience here to provide help to the new comers.

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: vij490 (123.236.222.---)
Date: August 11, 2013 05:40PM

tried all things on this thread, only thing left is teamviewer.
how do i set up a time with steve or rigs to do the teamviewer?

#2002 - No connection could be made because the target machine actively refused it.

Log:
2013-08-11 21:04:06 7424 [Note] Plugin 'FEDERATED' is disabled.
2013-08-11 21:04:06 7424 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-11 21:04:06 7424 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-11 21:04:06 7424 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-11 21:04:06 7424 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-11 21:04:07 7424 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-08-11 21:04:07 7424 [Note] InnoDB: Completed initialization of buffer pool
2013-08-11 21:04:07 7424 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-11 21:04:07 7424 [Note] InnoDB: 128 rollback segment(s) are active.
2013-08-11 21:04:07 7424 [Note] InnoDB: Waiting for purge to start
2013-08-11 21:04:07 7424 [Note] InnoDB: 5.6.12 started; log sequence number 1625977
2013-08-11 21:04:07 7424 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 7607e1f9-029b-11e3-93dc-cc12f5991cbf.
2013-08-11 21:04:07 7424 [Note] Server hostname (bind-address): '*'; port: 3306
2013-08-11 21:04:07 7424 [Note] IPv6 is available.
2013-08-11 21:04:07 7424 [Note] - '::' resolves to '::';
2013-08-11 21:04:07 7424 [Note] Server socket created on IP: '::'.
2013-08-11 21:04:08 7424 [Note] Event Scheduler: Loaded 0 events
2013-08-11 21:04:08 7424 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: RiggsFolly (---.as13285.net)
Date: August 12, 2013 10:21AM

Install TeamViewer and I will troubleshoot for you.

Install TV, then run it.

Do this before attempting a connection.

How to Configure Team Viewer so it does not require port 80 or 443

Run TV
Extras -> Options -> Advanced -> Press the Advanced Button -> Advanced Network Connections

Check the checkbox saying [ Dont use incomming port 80 (recommended for web servers only ) ]
Stop and restart TV.

Then
Send me a Private Message containing the TV ID and PASSWORD so I can connect.
Leave TV running as it will change the password each time you restart it.


I am on UK time (GMT+1) and available 09:00-16:00 and normally later into the evening.

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: nafti (87.112.130.---)
Date: August 15, 2013 01:09PM

Hi
I am having similar problems as described above please could someone help me?

Thank you

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: yoyozee (41.58.31.---)
Date: September 04, 2013 12:47AM

i have similar issues too. I currently operate windows 8.1 preview on my computer,
each time i try starting myphpadmin i get the error #2002 - No connection could be made because the target.

I have tried all the solutions in this thread. But the error still persists.
Pleas help

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: yoyozee (41.58.31.---)
Date: September 04, 2013 12:48AM

i have similar issues too. I currently operate windows 8.1 preview on my computer,
each time i try starting myphpadmin i get the error #2002 - No connection could be made because the target.

I have tried all the solutions in this thread. But the error still persists.
Pleas help

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: RiggsFolly (---.as13285.net)
Date: September 13, 2013 01:06AM

yoyozee

Please start a new thread and supply more specific information please.

Version of Operating system?
Version of Wamp Server installed?
Version of Apache you are running?
Version of MySQL you are running?
Version of PHP you are running?

What colour is your WampManager icon? ( in the system tray )

post your HOSTS file

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: wrobles (---.dllstx.fios.verizon.net)
Date: September 16, 2013 01:35AM

I'm running Windows 7. I reinstalled WAMP on a different partition and received the following error:
#2002 - No connection could be made because the target machine actively refused it.

To fix it I opened up the MySQL my.ini file and edited the following lines to point toward where WAMP is installed:

# The MySQL server

basedir=D:/Server/wamp/bin/mysql/mysql5.6.12
log-error=D:/Server/wamp/logs/mysql.log
datadir=D:/Server/wamp/bin/mysql/mysql5.6.12/data

These three lines were pointing to the original C:/wamp folder. After I edited them, the problem was solved.

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: RiggsFolly (---.as13285.net)
Date: September 16, 2013 02:26PM

These should all have been set correctly by the install.

So I guess after your install you copied some files from the old install to the new one.
You need to be very careful doing that or you can easily shoot yourself in the foot, like this !!

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: Jeremy K. (---.samoaonline.ws)
Date: September 25, 2013 11:16PM

Stevenmartin99,

am having the same problem. tried a few things and still not working.

here is part of log:

2013-09-26 10:11:59 3852 [Note] Plugin 'FEDERATED' is disabled.
2013-09-26 10:11:59 adc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-09-26 10:11:59 3852 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-26 10:11:59 3852 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-26 10:11:59 3852 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-26 10:11:59 3852 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-26 10:11:59 3852 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-26 10:11:59 3852 [Note] InnoDB: Completed initialization of buffer pool
2013-09-26 10:11:59 3852 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-26 10:11:59 3852 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 5578621 in the ib_logfiles!
2013-09-26 10:11:59 3852 [Note] InnoDB: Database was not shutdown normally!
2013-09-26 10:11:59 3852 [Note] InnoDB: Starting crash recovery.
2013-09-26 10:11:59 3852 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-26 10:11:59 3852 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_drupal7/variable uses space ID: 2 at filepath: .\bitnami_drupal7\variable.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

appreciate if you have time to look. thanks.

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: stevenmartin99 (Moderator)
Date: September 25, 2013 11:38PM

i can only fix this with teamviewer

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

Options: ReplyQuote
Re: [Solved] #2002 error
Posted by: Jeremy K. (---.samoaonline.ws)
Date: September 26, 2013 03:57AM

Steve,

Just send you mail of TV.

Options: ReplyQuote
Pages: Previous12345678Next
Current Page: 4 of 8


Sorry, you can't reply to this topic. It has been closed.