Author Archives: A Tech named Bob

Magento – Forbidden 403

by

0

Symptoms: When you attempt to browse to your Magento installation or Magento directory you receive a 403 Forbidden Error.

Solution: This is a normal web server response when the requesting user does not have the rights to access the content it is trying to access. To resolve this issue check the following information:

1. Check the owner of the folder for /httpdocs/ and all subdirectories for the magento installation. The correct owner should be as follows:  username:usergroup

In a Plesk 11.5 hosted environment this would be:  yourusername:psaserv

If the user is root (which often happens with command line installation) change the owner of the files in httpdocs or the subfolder with the magento installation using SSH and type:  chown -R yourusername:psaserv httpdocs/*

xmap blank screen Joomla 3.2

by

0

Problem: XMAP displays a blank screen when you click on the sitemap in Joomla 3.2.* and higher, or it displays a Internal 500 error.

Solution: XMAP references a component that is no longer required in versions later than 3.2.*

Remove or comment out the following line from /components/com_xmap/helpers/xmap.php

REMOVE OR COMMENT OUT:  require_once(JPATH_SITE .’/includes/application.php’);

It should be in the top 7 lines of the php script.

igdpmd64.sys Blue Screen

by

0

Symptoms: The computer continues to receive a blue screen with an error in the file igdpmd64.sys at random times.

Solution: There is a known conflict between Microsoft Update KB2670838 and Hybrid Video cards which results in the system becoming unstable and displaying the notorious “Blue Screen of Death”.

1. Go to Control Panel > Add Remove Programs > Show Installed Updates

2. Locate KB2670838 and uninstall

3. Reboot the system

The system should now be stable.

JFolder::create: Infinite loop detected

by

0

SYMPTOMS: You are trying to install a plugin or component using the extension manager in Joomla 1.5 or higher and receive JFolder::create: Infinite loop detected

SOLUTION: Your TMP directory is not set correctly. In many server configurations open_basedir is set to a specific folder in your php.ini settings. Try changing the tmp directory path from /var/www/yoursite/httpdocs/tmp to just /tmp in the Joomla global configuration.

RSA server certificate CommonName (CN) `plesk’ does NOT match server name!?

by

0

Problem: RSA server certificate CommonName (CN) `plesk’ does NOT match server name!?

Solution: The RSA certificate is being referenced back to the server’s control panel, as such, the domain name doesn’t match the server name. Please note this message is harmless and can be ignored.

STEP 1:

1. Under your Plesk Control Panel, go to Websites & Domains > Secure Your Sites > Add SSL Certificate

2. Name your certificate

3. Make sure the domain name matches your site, remove www.

4. Click Self-Signed, your SSL Certificate has now been generated. Please note, this is a self-signed unsecure certificate, do not use this for PCII.

STEP 2:

1. Under your Plesk Control Panel, go to Websites & Domains, Click on Show Advanced Operations on the bottom of the screen.

2. Select Website Scripting and Security

3. Under Security, make sure Enable SSL Support is checked, in the pull down select the certificate you just created.

4. Click OK.

This should resolve the error message 🙂


Windows Small Business Server (Windows SBS) Update Services is not running because it automatically turns off if you customize Windows Server Update Services (WSUS).

by

0

Problem:  In the Server Management Panel of SBS 2003 the server is reporting that update services are not running because it automatically turns off if you customize Windows Server Update Services.

Solution: This message was a pain to troubleshoot because at first glance the settings were not altered.  However, if you installed WSUS 3.0 (update services 3 upgrade) you can replicate the same issue.

This is the link to the correct Microsoft solution for resolving this issue: http://support.microsoft.com/?kbid=945985

Use Method #1, after applying Steps 1-4 and confirming the update service is running, return to Server Management > Update Services and click “refresh”

If you receive a Bad Request error, then your Internet Information Service for the default site is not running.. Go to Server Management > Advanced Management > Internet Information Service > Server > Web Sites >  Default Web Site  – Ensure the IIS is running for that site.