I am using Eclipse to connect AWS Dynamo Db and manage TABLES : by installing aws tool kit. everything will works fine but Dynamo db shows unable to connect, unfortunately here is the solution for this.If you can’t get anything else to work, you can screw with the plugin’s metadata to force an http:// connection and avoid ssl entirely.
Follow the below setps to change the metadata to http://
In your eclipse workspace, open the .metadata directory. Browse to .metadata/.plugins/com.amazonaws.eclipse.core/regions. In there is a file called regions.xml. Edit it, changing the DynamoDB entry from https://... to http://... Then restart eclipse, and you will be connecting to DynamoDB over http:// .
Steps to install AWS tool kit.
1. Install AWS Eclipse tools in a clean Eclipse environment (from Help->Eclipse Marketplace only), with no prior installations of the tools on the test machine. Simply wiping a prior installation might leave working settings, config items behind.
2. Note the DynamoDB (as of this writing) is not included in Help->Eclipse Marketplace distribution.
3. Add in DynamoDB from Help->Install New Software
4. Note that it doesn’t connect after entering credentials.
To resolve that issue please follow steps below –
1. Unregister all the versions of ASP.NET with command “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ua”.
2. Delete the ASPNET account from “Local Users and Group – Users”.
3. Then registere ASP.NET 2.0 with IIS using “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –i”.
4. Give permissions to the ASPNET account using “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ga machinename\ASPNET”.
5. Reset the IIS and that resolved the issue for ASP.NET 2.0.
6. Register ASP.NET 1.1 with IIS as well using command “C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis –i”.
7. Reset the IIS.
Run the following from your command line to reset IIS registry settings for aspnet user.
C:\WINDOWS\Microsoft.Net\Framework\v2.0.50727>aspnet_ regiis -i
After following the above steps we configured virtual directory versions as required and test both ASP.NET 1.1 and ASP.NET 2.0 application.
Everything will work after that.
Error: #2002 – The server is not responding (or local MySQL server’s socket is not correctly configured).
While accessing PhpMyAdmin getting the following error.
#2002 – The server is not responding (or local MySQL server’s socket is not correctly configured).
The mysql socket file is missing from the /tmp directory
1. Create a symbolic link from the original mysql socket file to /tmp
[root@test ~]# ln -s /var/lib/mysql/mysql.sock /tmp
2. Restart MySQL service from WHM
WHM Login >> Main >> Restart Services >>SQL Server (MySQL)
3. Edit the PhpMyAdmin configuration file to use the original MySQL socket file.
Make sure, the correct mysql socket file is mentioned there.
$cfg[‘Servers’][$i][‘socket’] = ‘/var/lib/mysql/mysql.sock’;
$cfg[‘Servers’][$i][‘connect_type’] = ‘socket’;
4.Change the server addr local host to physical IP .
This file is responsible for how Microsoft Windows handles print and fax jobs on your computer. This file is not a critical process and can be safely removed from the Task Manager to free up used memory.
To do this in Task Manager highlight he spoolsv.exe process and click the End Process button.
The abnormal high amount of CPU usage is caused when there are still printer jobs in the Windows spool. To manually remove these print jobs follow the below steps.
1. Click Start, Settings, Control panel.
2. In the Control Panel double-click the Administrative Tools and then Services.
3. Within services locate Print Spooler and right-click it and select Stop.
4. Once this process has been stopped leave the windows open and open My Computer and browse the the below folderc:\windows\system32\spool\PRINTERS
5.In this folder delete all the files in the PRINTERS folder. Once these have been deleted you can right-click the Print Spooler in the Services window and click Start to re-enable the service.
If this does not resolve your issue it’s likely you have an issue with your printer drivers you have installed for your printers.