Magento not sending new order confirmation

January 26, 2014 3 comments

I recently set up a Magento 1.8 store and I added PayPal payments as standard payment type.

After setting it up I tried to test a sale trough Megento PayPal integration.Well, here all the problems started and I had the following issues :
– Megento was not sending out Order Confirmation e-mails for new orders.
– PayPal payments were all marked “Pending Payment” even if the order was captured and the money pulled out from the PayPal account.
– Magento was not sending e-mails with the new order confirmation to the admin either. Only PayPal notification e-mails were sent you.

First I thought it is my mail server acting up and I started to make changes and modify all kind of settings, it did not help.
Then I started to look after bugs in the new Magento 1.8.1 , nothing there either.

Then I found this pretty useful post :

Very useful article and I followed the steps one by one, but nothing, still the Magento PayPal payments remained with the status “Pending Payment”. No e-mails sent to the customer, no e-mail sent to the admin.

After trying all kind of stuff for many many hours I finally discovered the problem. My site was not using SSL and there is one “obscure” setting on the PayPal Standard payments in the admin interface of the magento : “Enable SSL verification”. As soon as I turned this to OFF, the orders started changing status, e-mails started to flow, everything was working great.

So in order to have PayPal payments working on my Magento 1.8 I just had to set “Enable SSL verification” to “No”.

Hope this will help also others that has same problems.


Google Doodle – “Rober Noyce” ??? … or is it Robert Noyce

December 12, 2011 Leave a comment

Every now and then Google changes it’s Doodle to something of big importance for the day or week or even the month.

Today’s Google Doodle it supposed to be about Robert Noyce but someone at Google was kinda sleepy when he added the Doodle and instead of “Robert Noyce” , when you click the Doodle you are going to see search results for “Rober Noyce”.

This is how the Google Doodle looks like today :

And this is the search pattern for it :

Happyu Doodling Google and Happy Birthday Rober Noyceūüôā

OWA 2010: An unexpected error occurred and your request couldn’t be handled

December 1, 2011 6 comments

Many of you might have encountered this error “An unexpected error occurred and your request couldn’t be handled” after applying Exchange 2010 SP1. This error will start showing up in OWA 2010 when you are trying to delete some messages or try to move them to another folders. So basically the Exchange it is fully functional but you can not delete any messages in OWA.

This error comes only after applying SP1 to the Exchange 2010.
There are many discussions on the web regarding this error and many solutions are also provided. Some of the people report this problem because of permissions on the folders or on the IIS directories, different permission sets on the IIS folders and so long.

You can find some of the discussions and solution in this links below:

Some of the posts blame Authentication method or even editing the web.config file and altering some of the values in there in order to make it work.

You might also get an Event Error in the event log like :

Event ID:      3
The service ‘/EWS/Exchange.asmx’ cannot be activated due to an exception during compilation.


Event ID:      108
Outlook Web App couldn’t connect Exchange Web Services due to a configuration error.

For me none of this solutions applied.

I was fighting with this error for a few good hours then I decided that I am stupid and I made some mistake somewhere that it was impossible to detect. And since this was a newly installed server and admins with real balls never take backups of newly installed machines I decided to re-install.

After re-installing the machine, I configured the Exchange, assured that everything works as intended and re-installed SP1. SAME ERROR !

After looking at the log files and all this articles one more time (a few hours later) it hit me. What could I have changed at the Exchange (the IIS part that is) to provoke the error.
Then it hit me.
The ONLY thing I changed in my IIS configuration was my HOST HEADERS on my default website.
Went to IIS, removed ANY host headers I had there and then everything WORKED.

So for all you out there, if you have this kind of error, first thing you want to try is to take a look at your host headers and remove any custom host headers then try all the other solutions.

7077 The Advantage Data Dictionary cannot be opened

November 24, 2011 2 comments

7077 The Advantage Data Dictionary cannot be opened, this is one of the errors you might receive when running an application against an Advantage Database Server.

We have a medical application called “√Üskulap” developed in Denmark by Medcom . This application was running just fine on our Windows 2003 server, then we had to move the application and the Advantage Database Server on a newer Windows 2008 R2 Server because the old machine was now out of warranty and it started also to have some small issues. So we decided to move the Advantage Database Server and √Üskulap from the old Windows 2003 machine to a new hardware.

The migration process was quite simple, install a new Advantage Database Server on the new machine, copy all the data from the Æskulap folder to the new server and simply start working from the new share on the new server.

The problem started to appear soon after we started the Æskulap on more than one machine. The issues we encountered were :

– If √Üskulap started we started receiving the “7077 The Advantage Data Dictionary cannot be opened” error.
РWhen the Æskulap started, it started very slow
РÆskulap was very slow, moving between menus and processes inside the application took much more time than usual.

I tried to research the problem on Google and none of the solutions applied to me and as I did not know what else I could do I decided to call the support line.

I called Profdoc support department and they immediately told me that this is a well known issue and it is a communication problem between the client and ADS server. I told them that this can not be the case because I was getting the 7077 error also when I tried to start the Æskulap from the local machine, there where both Æskulap and the Advantage Database Server was installed.

Then I was told to check my firewall, check the permissions and many other “might be this” solutions. Nothing helped and the guys from Profdoc did not even try to look at some log files or try to start e debugger or something like this … nothing. Even more, they saw that I did not yet activated my¬† Windows license and they started bragging that it is therefore my software is not working and I was told they will cease to give me support until I will activate my windows.
Anyway, after more than one hour on the phone with the Profdoc support line (server management) they gave up and I was on my own.

So my problem was still there, I was still getting the 7077 error sporadically. I observed that if I tried to start Æskulap and got the error, then tried to start it again in a few seconds the error was gone and I could log on.
I started looking for documentation on Advantage Database Server and settings for this and I found out that normally no INI file is needed for it in order to run but it can use an initialization file, ads.ini, to override specific default settings such as the Advantage server type.
Looking on the old server I could see no ads.ini file and I decided to make one myself.

Windows – In order for the ads.ini file to be used, it must be located in the application directory, the Windows directory, the Windows System directory, or the client’s search path.” says the ADS Developer Zone on their site.

My file then looks like this :




I did it like  this with both FQDN and Netbios name because I still have some old machines on the network and I did not want to have any other issues later. All my machines have mapped the S: drive by a GPO.

After I added the ads.ini file everything started working like a charm !

Conclusion:  When running Advantage Database Server on a Windows 2008 R2 server you most likely will need an ads.ini initialization file in order to have a working system. Also after adding the ads.ini file, the Æskulap was much more faster and nobody complained about speed anymore.


RDC Published App and Windows XP Extended Screen

November 24, 2011 Leave a comment

Today I experienced something very strange with the RDP Clinet 6.1 on a windows XP machine running a published application.

Normally you can simply drag your apps from one screen to the other if your extra screen is acting as extension of the main screen. We tried with shortcuts, files, folders and everything works fine. As soon as we try to move the Remote Desktop Published App it simply won’t display on the extended screen and the image will just go out at the end of the main screen.
On the Terminal Server , RD Session Host Configuration on the connection properties, under the Client Settings tab, you can set the “Limit maximum number of monitors per session”. That one was set to 4 so no problem there.
Then we tried changing the Graphic Card drivers, this did not help either. Tried with another Remote Desktop Client, this did not help either. Now remember we are running on windows XP.

After 30-40 minutes we tried to switch the extended screen from the LEFT side of the main screen to the RIGHT side of it, just to try. And Eureka ! It worked.
So in the stupid Windows XP running RDP 6.1, the Remote Desktop Publsished apps will NOT run on the extended screen if the extended screen it is not located on the right side of the main screen.

Interforest Migration with ADMT 3.2 and Exchange 2010 interforest Migration

November 23, 2011 6 comments

Yesterday I had to migrate 25 users from our forest into a brand new forest and I was told to just create all the users on the new forest and export the mails to PST and import them into the new Exchange. But this is not me, I just wanted to migrate them as it is a while since I performed my last interforest migration.

So I prepared the target forest for migration by setting up the trust relationship between our forest and the target forest, delegated the rights on the remote forest for my administrative user and installed ADTM 3.2 on both forests as I was going to experiment migration from both forests.

Now, before you install ADMT 3,2 remember you will have to install SQL Express server. In my case I had the ADMT installed on Domain Controller instead of a member server. If this is your case also then do NOT install SQL Express 2008, just install SQL Express 2005 SP1 because the ADMT 3.2 will not work with SQL Express 2008 installed on the DC.

So first install SQL Express 2005 SP1 then install the ADMT.

Now, if you also plan on migrating the passwords and SID history from one forest to the other you will also need to further prepare the target and source domain for the migration. Please see this Technet article regarding preparation of the domain, and here is the Technet article regarding password migration domain preparation.

You will probably find many more guides on the internet on how to prepare the domain and groups and other small things.
After you install ADMT and you want to migrate also the Passwords then you will have to install also “Password Export Server”.

After you install PES you will have to create a KEY for password encryption. They key needs to be created on the TARGET domain and imported on the SOURCE domain.
So you will need to run this command on the TARGET domain :

admtkey /option:create /sourcedomain:<SourceDomain> /keyfile:<KeyFilePath> /keypassword:{<password>|*}

ADMTKEY example :

admtkey /option:create /sourcedomain:sourcedomain.local /keyfile:c: /keypassword:yourpassword

After you copy the key from the target domain to the source domain you will also have to IMPORT IT ! No article will tell you this. The PES key must be imported on the source domain by this command :

admt key /option:import /sourcedomain:sourcedomain.local /keyfile:key.pes

Only now START the “Password Export Server Service”.

If you are planing to migrate mailboxes as I did, DO NOT use ADMT to migrate them just yet. You will first need to use the Exchange 2010 Prepare-MoveRequest.ps1 script to prepare the source mailboxes for migration.

Open the Exchange Management console on the TARGET domain. Then add the Source Forest by right clicking the “Microsoft Exchange” and say “Add Exchange Forest”. Then add the remote (source exchange) forest.
Let’s say you want to migrate USER1 from S1 forest to T1 forest.

Open Exchange Management Shell on the T1 forest and type :

$LocalCredentials = Get-Credential

$RemoteCredentials = Get-Credential

Input the credentials for the local forest and remote forest.
.Prepare-MoveRequest.ps1 -Identity USER1 -RemoteForestDomainController -RemoteForestCredential $RemoteCredentials -LocalForestDomainController dc.targetdomain.local -LocalForestCredential $LocalCredentials -TargetMailUserOU “OU=YourTargetOU,DC=targetdomain,DC=local” -UseLocalObject

This will prepare USER1 mailbox for migration and prepare an USER1 object on the T1 forest.

Now you can migrate the USER1 from S1 to T1 by using ADMT 3.2 and MERGE objects, migrate SID history and EXCLUDE all this attributes from migration :


After migrating the user fire this command on the Target forest Exchange Management Shell :

New-MoveRequest -Identity “USER1” -RemoteLegacy -TargetDatabase “Mailbox” -RemoteGlobalCatalog “” -RemoteCredential $Remote -TargetDeliveryDomain “targetdomain.local”

Now your mailbox will be migrated.

A very nice guide is presented here on the Exchange Team Blog. but not everything is lined out therefore I made this short guide.

If you have any questions please don’t hesitate to ask.

Force RDC 6 Install – Force KB952155 install – RDC 6.1 Install over RDC 7

November 23, 2011 Leave a comment

I guess many of you have had this problem until now with the new Remote Desktop Client version 7 and Termianl Server Published applications using Windows XP clients.
The problem is that on Termianl Server Published applications the user is unable to choose an option from a drop down menu when running it on a Windows XP client with RDC 7 installed.

I had this problem with the Microsoft Dynamics Axapta and RDC7 , choosing printer under a published application and RDC7 and some drop down menus not working. If the clients are running RDC 6.1 then you can simply apply a Microsoft patch KB968358 and the problem will be fixed. But if you are as unlucky as I am and you have already installed RDC 7 on the clients you can not apply the patch anymore. Or if you deployed the RDC 7 client trough Wsus, you can not choose the uninstall option and if you have 2-3k clients this becomes a serious problem.

Of course I have open a case with Microsoft and I was told plain and simple to piss off as I am to small for them to bother with my problem but I am not the only one and I should just upgrade all my clients to Windows 7, which for me is not an option.

So if you are in the same boat as I am you have only a few options :

1. Uninstall RDC7 (KB969084) on all the machines if you still have the $NtUninstallKB969084$ folder under the Windows catalog.
You can simply make a logon script that will execute something like this :

start /wait %SYSTEMROOT%$NtUninstallKB969084$spuninstspuninst.exe /q

Which will uninstall the RDC 7 quietly.
Then install RDC 6.1 and then apply the KB968358 patch.

2. If you no longer have the %SYSTEMROOT%$NtUninstallKB969084$ folder that means you can not uninstall and somehow you will have to trick the RDC 6.1 installation.
In this case you can just overwrite a few files on the System32 folder and use the brute forceūüôā
You will need to replace the mstsc.exe and mstscax.dll files in the %SYSTEMROOT%system32 folder  and depending on your language locale (in my case Danish / German)
also this mstscax.dll.mui and mstsc.exe.mui within the %SYSTEMROOT%system32da-dk  (da-dk or de-de or any other language you might have)

You can download the RDC 6.1 files from HERE and unpack them on a shared folder on one of your servers. (There is no RDC 6 MSI package available from Microsoft) Then download the KB968358 patch and put it in the same location (the patch will be named WindowsXP-KB968358-x86-ENU.exe or something like this).
Make a logon script that would look something like this:

@echo off

cd %SYSTEMROOT%system32
Echo Renaming Old RDC 7 Files….

ren mstsc.exe mstsc99.exe
ren mstscax.dll mstscax99.dll

cd %SYSTEMROOT%system32da-dk

ren mstscax.dll.mui mstscax99.dll.mui
ren mstsc.exe.mui mstsc99.exe.mui

Echo Copy new files to local machine….

copy \servernamesharenamemstsc.exe %SYSTEMROOT%system32 /y
copy \servernamesharenamemstscax.dll %SYSTEMROOT%system32 /y
copy \servernamesharenamemstscax.dll.mui %SYSTEMROOT%system32da-dk /y
copy \servernamesharenamemstsc.exe.mui %SYSTEMROOT%system32da-dk /y

Echo Starting the patch….

start /wait \servernamesharenameWindowsXP-KB968358-x86-ENU /q

echo Patch Done

Now you can run your published application and everything should be fine.