The php mcrypt module, required by Magento, wasn’t present on our Plesk VPS. Here’s how to add it from SSH:
(1) Add the repository. For example, to add EPEL:
rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
(2) Install the php-mcrypt module:
yum install php-mcrypt
Error 0x800CCC0E on clients connecting to a Plesk VPS manifests itself with several descriptions:
Task ‘Checking for new mail in subscribed folders on your_account.com.’ reported error (0x800CCC0E)
Outlook is unable to download folder (null) from IMAP e-mail server for account your_account.com.
Error: Unable to connect to the server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).
Assuming that there isn’t a problem connecting to the server (in my case mail was being sent and received, but IMAP folders would not synchronise) then the problem lies with Plesk limiting the number of mail client connections from a single IP address – four by default. To raise this limit:
Login to Plesk
Under Server Management, Click “Tools & Settings”
Under Mail, Click “Mail Server Settings”
Change the “Maximum number of connections per IP address” to a larger value, e.g. 40.
Click “OK”
After several hours banging my head against the wall over an Outlook error “0x800CCC80; None of the authentication methods supported by this client are supported by your server” I finally found the cause of the problem; I had installed the postfix mail server on the new Plesk VPS host rather than qmail.
Postfix requires TLS encryption on port 587, qmail does not – and the Outlook default is “None”. Changing the encryption required in Outlook is disruptive – lots of clients – and also gives rise to a certificate warning, so I decided to take the cowards way out and replace postfix with qmail.
More here.
I have a Smart UPS 700 which after a battery change shows zero run time and a permanently lit “Trim” LED.
The zero run time is because the battery constant held in EEPROM is wrong – I think that this is maintained by the Smart UPS as the battery capacity fades over time, but isn’t reset when a new battery pack is inserted.
The Trim LED shows that the UPS thinks the supply voltage is too high. It isn’t, so in this case the firmware version in EEPROM is wrong, making the device think it is a US model and expecting a 120V supply.
Both problems can be solved using the APC “black” serial cable P/No 940-0024 and a terminal emulator on the laptop.
Lost the black cable, did you? Here is the wiring:
| UPS Signal Name |
DB-9 Male (UPS end) |
DB-9 Female (PC end) |
PC Signal Name |
| TX / AC Fail | 2 | 2 | Rx, Received Data |
| RX / Shutdown | 1 | 3 | Tx, Transmitted Data |
| Common | 9 | 5 | GND |
| Link 1 & 4 | DCD,DTR | ||
| Link 7 & 8 | RTS,CTS |
Referring to the table below, the correct battery constant (register 0) is 96 (hex) and the firmware version is 52.11.I
Connect the serial cable and using puTTY or similar issue the following commands:
Press Y (Capital Y)
UPS should respond SM
Press 1, wait 2 seconds, press 1 again.
You should see response PROG.
Press 0 (zero).
The UPS should respond with the current constant.
Press + (plus) or - (minus) to increment/decrement the value
Press R (capital R) to reprogram constant value
The UPS should respond Bye
Press Y
The UPS should respond S
Press 0 (zero)
The UPS should respond with the new constant.
Press b.
You will see the current firmware code.
Press either + or - followed by a 1 second pause followed by b to cycle through the firmware versions.
Press R (capital R) to reprogram the firmware version.
The UPS should respond BYE.
Quit the console without resetting the serial port.
That should be all that is required.
Here is the table showing register 0 (battery constant) and Firmware for each UPS model:
UPS Model 4 5 6 0 Hex Firmware
SU250 EE F8 B1
SU400 EE F8 9F E1
SU600 EA F4 9F E5
SU900 F3 FC 9F ED
SU1250 EE FA 9F F5
SU2000 F1 F9 9F FD
SU450,700 28 F2 FA 96 07,RM=47 52.11.I
SU450XL,700XL 28 EE F8 9F 700XL=27 51.9.I
SU1000,INET 35 EF F9 A0 0B 60.11.I
SU1000XL 34 EE FC 9A 2B 61.9.I
SU1400 35 EE FC 9A 70.11.I
SU1400RM 28 ED FA 89
SU1400R2IBX135 08 B4 10 A3
SU1400RMXLI3U 45 F6 F4 80 73.x.I
SU1400RMXLI3U 20 F3 FD 81 73.x.I
SU2200I 35 EE FB AF 90.14.I
SU2200XL,3000 35 EE FB AF 3000=17 90.14.I
SU3000RMXLI3Ublk 35 F3 F4 AF 77 93.14.I
SU5000I white 20 F2 FA 91 1F 110.14.I
SU1400XL,XLI,RM 45 F6 E4 80
SU420I 25 95 09 85 16 21.7.I
SU420SI 0E 95 0A 8C
SU620I 29 99 0B 8A 1A
BP420SI 0E 95 0A 8C 06 11.2.I
BP650SI 10 97 0C 91 0A 12.3.I
Power Stack 250 0C 95 0F B2 26.5.I
Power Stack 450 0D 96 10 99 36 26.5.I
SC250RMI1U 0C 95 0F B3 32 735.a.1
SC420I 0E 95 OA 8C 16 725.1.I
SC620I 10 97 OB 99 1A 726.x.I
SC1000I 08 95 10 94 8A 737.x.I
SC1500I 07 95 14 8F 1E 738.x.I
SU1000XL 17 EE F9 D5
MATRIX 3000,5000 E9 F5 B0
SU700RMI2U 07 B1 0D 92 8A 152.4.I
SU1000RMI2U 08 B5 0D C7 8E 157.3.I
SU1400RMI2U 08 B4 10 A3 92 162.3.I
SUA1000I 07 B5 13 BC 0A 652.12.I
SUA1000XLI 0B BD 0F 7F 4A 681.13.I
SUA750XLI 0A B9 0C 86 46 630.3.I
SUA750I 04 B6 14 82 06 651.12.I
SUA750RMI2U 07 B1 0D 82 86 619.12.I
SUA1500I 09 B9 13 A1 0E 601/653.x.I
SUA1500RMI2U 08 B4 10 A1 8E 617.3.I
SUA2200I 08 B8 12 B3 26 654.12.I
SUA2200RMI2U 09 BC 11 81 A6 665.4.I
SUA2200XLI 0A B7 0F 7F 66 690.x.I
SUA3000RMI2U 04 B9 0E 70 AA 666.4.I
SUA3000RMXLI3U 0A B6 0E 89 xx xxx.x.x
SUOL1000I 06 B6 1B A6
SUOL2000XL 0D BD 14 75 52 416.5.I
SURT1000XLI 0A BB 19 A8 4E 411.x.I
SURT3000XLI 06 B6 0F CC 56 450.2.I
SURT5000XLI 05 BA 15 86 5A 451.13.W
SURT7500XLI 03 BB 20 97 63
SURT10000XLI 06 B8 19 AB 476.12.W
SUM1500RMXLI2U 03 B7 0D A5 62 716.3.I
SUM3000RMXLI2U 03 B7 0D A5 6A 715.3.I
BP500AVR 26 17.1.I
If you use Microsoft authentication when creating a new user, you can end up with an inconvenient user folder name. This can be changed as follows:
ren C:\Users\oldname newname)HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\ProfileImagePath for the old folder name (e.g. c:\Users\oldname). When you have found the relevant SID, change the value for ProfileImagePath to the new folder, e.g. c:\Users\newname
Login using the new username and check all is working correctly.
Device Manager (Windows 7, Server 2008, etc.) hides devices that are not plugged in, even if you click on View / Show hidden devices. To reveal them, do the following:
(1) Start a command window with elevated (administrator) privileges. Start, and in the search box type cmd – without pressing enter, right-click on cmd in the Programs section and click “Run as administrator”.
(2) Type the following into the command window:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 START DEVMGMT.MSC
(3) Click on View / Show hidden devices in Device Manager.
The revealed devices can, with care, be deleted to remove the associated driver.
Assuming that Magento is not actually in maintenance mode (i.e. downloader is not being used) then the following error is the result of a lock file not being removed, probably as the result of an ungraceful exit from the downloader:
Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
To take Magento out of maintenance mode, just delete the file:
maintenance.flag
from the Magento root.
Problem:Eye-Fi center doesn’t appear when I click on it in the tool tray, following an upgrade.
Eye-Fi answer:
Your request (#27954) has been deemed solved.
________________________________________Michal, Apr-20 05:25 (PDT):
Hello Adrian,
As discussed could you please do the following:
– format the card in your camera
– uninstall Eye-Fi software as well as Adobe AIR
– install the latest version of the Adobe AIR from the following link:
http://get.adobe.com/air/
– download and install the latest version of the Eye-Fi software:
http://support.eye.fi/support-resources/downloads/software/eye-fi-manager-desktop-software/Please feel free to contact us again if you have questions or would like further assistance.
Kind regards,
Michal
Eye-Fi Customer Care
… or to put it another way, turn it off and turn it back on again!
Sometimes I think that things haven’t really changed since I did support back in the 1990s.
Update:
The correct solution is to uninstall & reinstall Adobe Air.
I have received a large number of integrity contraint violation errors relating to the catalogindex_aggregation_to_tag table; it turns out that it is one of three tables are related to the Layered Navigation cache:
catalogindex_aggregation
catalogindex_aggregation_tag
catalogindex_aggregation_to_tag
which quickly become huge even if tagging is not actively used.
The solution is to Disable Cache Control (beta) Layered Navigation” i the admin panel under “Cache Management” and then refresh the cache.
All three tables are then emptied and perforamnce is significantly improved.
There is a lesson to be learnt about using beta code, I guess…