http 500 when calling base/teacommerce/GeneratePaymentForm.aspx
Hi!
I just upgraded to Umbraco 6.1.3 and simultaneously upgraded teacommerce from 1.4.2.4 to 1.4.4.5
Everything works fine (after replacing /tcbase with /base) except for calling goToPayment() (base/teacommerce/GeneratePaymentForm.aspx). It throws an 500. What might be wrong?
Below is the order object. As you can see there is a payment method attached to it, so it should not be that.
When you get a 500 error you need to look in the umbraco log (DB or Log file) and your server log to see what the error is. a 500 error is an internal exception which isnt show to the client - so you need to look at the server what the error is.
I found the Error. The 500 was because there was no Dictionary Item in place at the payment provider configuration form.
I later found that none of the Payment Provider configurations had survived the upgrade except for their names and id.But now everything works like a charm again.
Looking at the Order again i can see that the DictionaryItemName field is empty:
http 500 when calling base/teacommerce/GeneratePaymentForm.aspx
Hi!
I just upgraded to Umbraco 6.1.3 and simultaneously upgraded teacommerce from 1.4.2.4 to 1.4.4.5
Everything works fine (after replacing /tcbase with /base) except for calling goToPayment() (base/teacommerce/GeneratePaymentForm.aspx). It throws an 500. What might be wrong?
Below is the order object. As you can see there is a payment method attached to it, so it should not be that.
When you get a 500 error you need to look in the umbraco log (DB or Log file) and your server log to see what the error is. a 500 error is an internal exception which isnt show to the client - so you need to look at the server what the error is.
Kind regards
Anders
Thank you for the quick response (again).
I found the Error. The 500 was because there was no Dictionary Item in place at the payment provider configuration form.
I later found that none of the Payment Provider configurations had survived the upgrade except for their names and id.But now everything works like a charm again.
Looking at the Order again i can see that the DictionaryItemName field is empty:
is working on a reply...