Thank you.  I've just upgraded to DNN 4.5.3 and tried to export and create a new portal with the exported template.  I'm still getting the following error when the new portal opens:

Could Not Load Skin: /Portals/14/Skins/Testt/Test.ascx Error: The file '/dnn/Portals/14/Skins/Test/Test.ascx' does not exist.

If the exported portal's skin doesn't become a part of the export template then why would this error get thrown?  If a DNN template is just creating a skeleton of the portal then why is it trying to find the skin?  Is there a fix for this?

One company owns the entire dotnetnuke installation and all its various websites and graphics so licensing isn't an issue for us.  What I don't understand is why an error looking for the skin of the exported template is thrown if skins need to be applied separately for a portal using an exported  template?   It's a bit disconcerting to see the error  Am I doing something wrong?  The new portal seems to be an exact copy of the original portal minus the skin.  Is the "skin doesn't exist" error always thrown?   That seems odd to me.  I just need to be able to explain this behavior to others.

Thanks!