Items filtered by date: December 2014

• START > RUN > CERTMGR.MSC
• It will launch a certificate management tool and you can remove the certificate with it.

Solution 1:

This problem is actually listed in the "common problems" section of the installation instructions, but many users only seem to run into it when they start configuring their site after the initial setup. So here we go again:

This is commonly known as the "whitespace problem".

The error message typically looks something like

Warning: Cannot modify header information - headers already sent by (output started at /path/to/geeklog/public_html/config.php:581) in /path/to/geeklog/public_html/system/lib-sessions.php on line 180

(line numbers and file names may vary). The problem is that many editors seem to add additional blanks (spaces) and/or empty lines at the end of a file when you edit it. This so-called whitespace is then sent to the browser when the file is loaded and interferes with the header of a page that Geeklog tries to send to the browser, often causing problems such as login problems.
 

The fix is, obviously, to remove that whitespace from the file. Read the error message carefully. It says "output started at ..." followed by a file name and a line number. That is the file (and line) that you need to edit. Ignore the second file name - that is only a file that included the file that has the whitespace. The first file is the one you have to edit, not the second one.

Since the editor you've been using caused this problem in the first place, you should use another editor to fix the problem and remove the whitespace. See this and this forum thread for some recommendations for editors to use on Windows. Unix/Linux users can't go wrong with vi.

Taken from here: Cannot modify header information - headers already sent by ... - Geeklog

Solution 2:

This error message is commonly seen by programmers starting to use PHP. Understanding why this error occurs will help find the solution.

PHP handles lots of the work of generating web pages for you, without you even having to ask. A web page is composed of two parts, the header and the body.

The header is generally stuff that you don’t need to worry about, is generated automatically, and contains information about the page, the server, related cookies, and so on. The header information is important, but it is not typically seen by the user. Here are some examples:

Date: Mon, 10 Jul 2006 18:51:59 GMT
Server: Apache/2.2.0 (Unix) mod_ssl/2.2.0 OpenSSL/0.9.7g
Content-Encoding: gzip
Content-Type: text/html

Sometimes programmers want to change some of the header values. For example, if the PHP if generating XML output, the Content-Type should be changed to reflect this. Another common example is in redirecting the user’s browser to a different web page using the Location header element as described in this Tech-Recipe.

The header must come first in the response from a web server and is separated from the body by one blank line. The reason this error occurs is that some part of the body of the web page has been sent to the user already when a request is made to set a header value. Because PHP simplifies many things for you, the problem may be hiding in plain site.
 

Here are some guidelines for finding the problem:

1. Find the header() statement that is causing the problem. The error must be at or before this line.
2. Look for any statements that could send output to the user before this header statement. If you find one or more, find some way to move the header statement before them. Complex conditional statements may complicate the issue, but they may also help solve the problem. Consider a conditional expression at the top of the PHP script that determines the header value as early as possible and sets it there.
3. Make sure there is no white space outside of the php start and end tags. While a blank line before the <?php start tag may look innocent, when processed by PHP, it will turn into an echo statement printing out a blank line. This is a common culprit.
4. Make sure you FTP program is set to binary mode. If not this can incorrectly upload text files messing about especially with the carriage returns and possibly could introduce whitespace. If this is the case re-upload all files in the new mode.
5. If using joomla, empty all caches + purge sh404sef urls and make sure the live site setting is correct.

Please note that this solution was written for Prestashop v1.3.x so just bear this in mind when you read them. The solution might still be relevant.

Symptoms

• I have created a new order in my Prestashop but the order’s products are not shown. Also, I can’t change the order status (there is no form). No errors are reported in the php log
• We recently came up with a problem after switching from 1.2.5 -> 1.3 -> 1.3.1 in which we would get new orders from customers but doesn’t show under the Orders tab, nor we get an email that an order has been placed like we usually do. Now the strangest part about it is, if we go into the customer’s profile their order shows under their name but when we click the Actions button to view the order, the order information is blank. The products that they ordered doesn’t show, the status doesn’t properly show so we cant edit the status of the order and the invoice is missing. Original thread
• Invoice not displaying purchased product. Original thread

This error is definitely database related and i suspect a MySQL script failing during the upgrade process.

Solution

1. Backup, Backup, Backup and then test the backup.
2. Upgrade your prestashop through the normal means to the latest version
3. on the same server install a fresh copy of prestashop (seperate database) using the same database prefix that you are using in your prestashop
4. make sure you have remote mysql access to your server (using local xampp will have issues with capital letters)
5. get Navicat for MySQL
6. you will now need to setup a remote mysql connection to your server
7. now compare the 2 databases (tools/structure syncronisation), the source database should be the fresh/new copy of prestashop and the target is the old damaged one. when compared you should see a lot of differences and this is the fault. please make sure the database are the right way round (source/target). DO NOT DROP tables as these will most likely not be present on a fresh database on purpose. (i.e. modules you have installed)
   
   NB the source should be the new/fresh database and the target is the database you want to fix
   
   
8. run the mysql commands to upgrade/syncronise the database
9. run compare again to check that everything has worked.

This is my solution originally posted on the prestshop forum here

Prestashop V1.6.x Update - Orders with missing Products

I have recently had this issue with a prestashop v1.6.0.14 install and i have some further solutions:

• Follow the navicat mysql syncronisation instructions above but instead of upgrading your prestashop installation before syncronisation you can just install a fresh version of prestashop with the same version number. The rest of the instructions are the same.
• Upgrade to the latest Prestashop version. Doing this can fix a lot of issues anyway.
• Disable and clear all prestashop caches. You might have stale or corrupt enteries in your cache so even if you fix the problem the cache still maintains the fault.
• Disable all non-core prestashop modules. One of them might be affecting how an order is being process
• Try different payment methods as the Paypal module has been know to cause this issue. See my other article Diagnose PayPal issues in Prestashop

One or more of the these solutions might work but it does not harm to perform all of them. In any case you should put your shop in maintenance mode and heavily test your site until you find the issue. Customers will prefer to wait a little while rather that never a receive an order they are expecting.

Links

• Back Office not creating orders after successful payment - PayPal - PrestaShop - Mentions inputting dodgy addresses or wiered characters can prevent orders being created, testing in maintenance mode will fail and the number of IPN requests can cause a temporary ban and code fixes to the prestashop paypal module v1.3.7 / PS 1.6.0.9
• Most orders do not appear in back office - Configuring & using PrestaShop - PrestaShop - faulty code dues to an upgrade, there were incompatibilites
• Orders not showing up in Backorders - Configuring & using PrestaShop - PrestaShop - This thread describes how the eBay module was causing orders to fail because ithe module was getting executed in the order process, failing,  which them ultimately failed the order process. There is some advise on what to do in that situation aswell. It mentions that because of a PayPal outage that orders were effectively not authorised until PayPal's servers came back on and authorised the transactions giving the impression of missing orders.
• Missing products and blank orders - Ecommerce x PrestaShop - PrestaShop - This thread describes how to turn error reporting on and how the author used this information to find out that it was his eBay module causing the issue

Many reason can cause this here are a few common ones

• Syntax Error in .htaccess file
• can be caused by modsec rules coming into play

Joomla Related

• livesite is not set properely in configuration.php
• joomsett.conf in administrator is not set properely or not accessible
• empty all caches
• turn off SEF in joomla and sh404sef

Not exact error but daemon tools says that the service or something is not runnin - PLEASE UPDATE

Solution:

• reinstall SPTD using the seperate installer
• reboot PC

Clients not talking to the server (see other solutions aswell)

When you want reinstall a Symantec Endpoint Protection server you must back up the key store. If you do not the clients become disconnected and therefore unmanaged.

To reconnect already deployed clients the key on the client needs to be replaced

1. export the appropiate key from the new server
2. copy to a network location along with syslink replacer
3. run utility to replace key
4. once replaced and the client is talking to the server a green ball will appear on the shield

To deploy a client you can no longer use a normal installer file

Method 1

• Use the admin console to search for unmanaged clients, this process will search you local network on the IP range you specify and will report back to you what AV the clients are running. this process is not 100%.
• You can then deploy a package to them, this will have all the setting required

Method 2

• create and export a client package for the group you want to add the clients to. This package has the server key inbuilt etc..
• put on network location and manually run on each client
• NB: it does not always correctly remove the old version of Symantec Antivirus

sylink replacer tool - visit client PCs and run this program with the sylink.mxl file in the same directory to reconnect client

Thank you for the update on the case. Please find below the download link for the sylink replacer tool.

 To download this utility go to https://fileshare.symantec.com/, and use
the following login ID and password.

Login ID: sylinkreplacer
Password: Syl1nk0!

Download Sylinkreplacer.zip

Once you have downloaded the utility, please follow the instructions
outlined in the following document.

Title: 'Using the "SylinkReplacer" Utility'
Document ID: 2008043412271448
> Web URL:
http://www.symantec.com/business/support/index?page=content&id=TECH105211&locale=en_US

SylinkDrop utility - network sylink replacer via TCP/IP

Here is the information on how to download and run the SylinkDrop utility we discussed.

To download the utility, open the following web page in a browser:
https://fileshare.symantec.com

Log in with the following information:

Login ID: sylinkdrop
Password: Syl!nkdr0p

Once you have downloaded the utility, please follow the instructions outlined in the following document.

Title: 'Using the SylinkDrop utility'
Document ID: 2008053007423248
Web URL: http://www.symantec.com/business/support/index?page=content&id=TECH105034&locale=en_US

Issue  : Clients are not talking to the server

Troubleshooting :
-  Informed that this happened since the database backup and server key backup was not taken before the reinstall.
-  Informed that we would have to replace sylink.xml on the clients to establish the connection.
-  Generated a sylink.xml file from the SEPM.
-  Upgraded the client on the server with the sylink file and confirmed that it is communicating with the SEPM.
-  Sent sylinkdrop and suggested to replace the sylink file on the client using this file.
-  Sent document on best practice for disaster recovery.

Solution : Replaced sylink.xml file on the clients

Case Status : Closed

 Other Useful Articles

Symantec Endpoint Protection 11.0 Top Articles

How to upgrade, how to manually install clients and various other useful articles for basic tasks

Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

This is useful for upgrading issues and if you need to re-install

The Symantec Endpoint Protection Support Tool

This tool can be helpful in diagnosing issues

other password - symantec

Try installing as Laserjet 1300 PCL 5

• Open Control Panel
• Click Printers
• Right click your 1012
• select properties
• select the ports tab, note the port used by your 1012
• Click add a printer
• Select add a local printer
• select use an existing port
• drop down and select the port used by your 1012
• click next
• scroll left column to HP
• scroll right column to HP laserJet 1300 PCL5
• Click next and continue installation

Also look at Windows 7 and HP Laserjet 1012 Driver not working for installing the Host Based driver.

If you have changed the driver to use Virtual USB and it keeps detecting the printer you should

• put the port back to IEEE
• let the printer install and then leave this printer alone
• If you now add a new printer using a virtual USB the printer will not keep redetecting as windows thinks it is still installed properely.

Currently to view the Menu Bar a user can hit ALT on the keyboard to temporarily view the Menu Bar.

To keep the Menu Bar always visible, Open Regedit via Start Menu\Run\Regedit.

• Navigate to the following location:  HKEY_CURRENT_USER\Software\Policies\Microsoft
• Right-Click Microsoft select New then click Key.
• Name this key Internet Explorer
• Right-Click Internet Explorer select New, then click Key
• Name this key Main
• Right-Click Main select New, then click DWord (32-Bit) Value
• Name this value AlwaysShowMenus and set its value to 1

Now hit ALT on your keyboard and the menu bar should remain. To remove, either set the value to 0 or remove the AlwaysShowMenus value.

The fix is easy:

Special characters in the User Name will prevent the install. Create a new admin account with no special characters in it and use this account for the upgrade.