Hi, I need to export a portal I have in localhost to deploy it in production. But... I export the portal and its contents in Host -- Portals -- Export template. I copy - paste the template and resource files generated in the Portals/_default folder to the corresponding folder in my host. When I choose to create a new portal from my template, DotNetNuke throws an error: "Error parsing Portal Template". When I click again in Host -- Portals the new portal is there. But nothing in the new portal works. Can someone help me with this one? I need to take the portal with all its content from one place to the other. My DotNetNuke version is 4.3.1. Thanks. 

Exactly the same for me, and I'm using DNN 4.3.3 and SQL Server 2005.
I appear to be able to use the supplied portal templates without a problem, so the problem I am guessing is in the creation of the portal template.

This works:
* Creating a plain portal website with a default skin works from a template.
* Creating a plain portal website with a third party skin works from a template.
* Creating a plain portal website with a third party skin + html module works from a template.

This doesn't work:
* Creating a portal website from one of my portals failed with "Error parsing portal template". So it's down to this portal.

I have no way to diagnose it. Error is not trapped at all except when "creating the portal" and showing the error message "Error parsing portal template". Nothing seems to be logged in the event log. Portal is there under the portal list but no portal alias has been created in the dodgy portal that has been created.

Does my portal data need to be cleaned up somehow? (perhaps garbage in the database). Could somebody advise a procedure?

Can people who have experienced similar issues to mine follow my procedure above so at least we know we are consistent in this bug.

I've updated Gemini about the problems with error logging here: DNNP-3688

Cheers

Alex

p.s. this is my 100th post in the forum so I deserve special treatment :)

OK this is just a hunch....

Take a look at the first part of this thread I posted and the error message. This was when I was running 4.0.3:

http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/108/threadid/55511/scope/posts/Default.aspx

I guess that with 4.0.3 the same error is happening but it's being surpressed in 4.3.3!
If I am right (and I definately could be very wrong!) it's all to do with duplicate ModuleID numbers in the template file.
Notice the error message in my instance:
InnerException: Item has already been added. Key in dictionary: '688' Key being added: '688'
Open up the template file and locate the  tags <moduleID></moduleID>.
Do any of these have the same number..? Yes? Is that tag number listed more than once? Yes?

The questions I can't answer at the moment is:
a) Why do I have dupicate moduleID's in my file?
b) Why is it wrong to have duplicate moduleID's (referential integrity I guess)?
c) How do I fix this if this is indeed the problem?
d) Am I completely out on a tangent?

Food for thought perhaps....?

Ta

Alex

p.s. John, how did you manage to locate the error? I've got a source install of DNN 4.3.3 which I am compiling as well. Did you set something in web.config? Also can anybody answer the question what is the difference between developer.config and release.config? (I've always used the developer file as none of my sites have been published in the internet zone yet).