I figured out how to work around it. Instead of upgrading from 4.3.4 to 4.5.4, I instead upgraded to 4.4.1 first, then to 4.5.4.

The C# files in the \App_Code\Transaction_Log folder seem to be introduced somewhere during the direct upgrade from 4.3.x to 4.5.x.

ieeadmin,

This is not a "localization" language, rather a "compilation" language issue. Before upgrading any DNN installations, check the forums in order to be sure that you are following the right steps. For example this one: http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/76/Upgrading-to-DotNetNuke-451-from-4x.aspx

The issue you are posting is related to a module that has been written in C# and not VB, which is the standard throughout DNN. You must declare the directories containing any files written in other language than VB in order to let the compiler know they should be treated differently.

You do that this way:

1. Open your web.config file.
2. Find the following lines inside of it:

3. Uncomment them and include your Custom Module's directory (maybe in your case is "TransactionLog"):



4. Save and open DNN again.

Hope it works. Best luck!

Saludos,
Alejandro.

---

Spanish Language Packs Paquetes de Idioma en Español		English Language Packs Commercial, Professional English

Hi Alejandro,

I understand that it's not a localization issue - that's what the OP was guessing at. I had the same error message, and it was on a 4.3.4 install that had no 3rd party modules installed (C# or otherwise). The portal was a clean DNN install that I haven't touched in about a year. I use it to test upgrades before I through them on my production portals.

Watching the upgrade from 4.3.x to 4.5.x, the Transaction_Log folder with filename.cs files in it was created during the upgrade process. Going from 4.3.x  to 4.4.1 to 4.5.4 was a workaround for me.

I have about 10 other DNN installs to upgrade, so I'll see if I run into the same issue.

Thanks!