Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Publish  DNN 4.4.0 error Publish DNN 4.4.0 error
Previous
 
Next
New Post
1/16/2007 9:54 AM
 

I just finshed the customization for DNN 4.4.0. When I hit the publish website button from the VS2005, the publishing folder is created and populated with DNN files, however, I get an error when the browser is launched with the following syntax "an error occured

I tried to repeat the publishing without applying any customization. The error still occur.

I tried to use host account to install some modules like the forum before publishing. When I do so the VB2005 fail to publish

I did above steps on two different machines to exclude other factors. Still I receive same error messages.

 

 
New Post
2/1/2007 4:38 PM
 

Eslam,

Did you every get a response from anyone or figure out a solution. I am having exactly the same problem. Please let me know.

Thanks

 
New Post
2/2/2007 6:30 AM
 
Hello,
I am having similar issues as well. I unzipped the contents of the Install version to my local machine. After creating the DB and using Start Without Debugging on VS 2005 I could view the portal and all works well. I then used the Publish Web Site on VS 2005 to publish to a local folder, copied the contents of the Published site to my production server. Followed the same procedures to create the and set the connection string to the DB as I did on the local machine, I ran the site and it went through creating the tables and SP until it came to the point where is says Click Here to view portal.

After that I get the following error on the page on a blank page: An error has occurred.
The querystring has: http://www.mydomain.com/Default.aspx?tabid=36&error=Could+not+find+a+part+of+the+path+'C%3a%5cWWW%5cPortalFolder%5cApp_GlobalResources%5cLocales.xml'.&content=0

It is looking for the folder
App_GlobalResources which does not appear when the site is published using VS 2005.

Does anyone know what could be wrong?
Thanks
 
New Post
2/13/2007 7:22 PM
 

Well after banging my head up against a wall for several days, it looks like I figured out why the application won't run. Everythime I seemed to solve one problem, another presented itself. Well, after great labored efforts, this is how I fixed it:

I started by downloading and installing the WebProject plugin from Microsoft. The following link will give you documentation on how to use it and where to download it from. http://msdn2.microsoft.com/en-us/library/aa479568.aspx.

Once I installed it, I right clicked my website project within my DotNetNuke solution and added a web deployment project. The following are my configuration settings (right click on the new deployment project and choose property pages):

Configuration is set to Release with Generate debug information and allow precompliled site to be updated checked. The only projects I build in this configuration is the website and the deployment project.

On Outupt Assemblies I click to Mearge all outputs to a single assembly and check treat as library component.

Under deployment, I clicked Remove the App_Data folder.

Now that that is set up, I needed to modify my solution. I excluded 2 files, which aren't used in my website:  admin\containers\actions.ascx and admin\skins\menu.ascx.

Next, I copied my files from my App_GlobalResoruces folder into the website bin folder.

Finally, I changed the constant pointing to the App_GlobalResources directory to point to the bin. It is in the Localization.vb file under constants (in the DotNetNuke.Library\Localization). Below I show the existing setting and what I changed it to.

 

 

'Public Const ApplicationResourceDirectory As String = "~/App_GlobalResources"Public Const ApplicationResourceDirectory As String = "~/bin"

Once I made these changes, I made sure my solution was set to debug. I built the entire solution. I then right clicked on the website and built the website. After that was done, I switched my Configuration manager to release, which is set to build just the website and the newly created web deployment project. Once that is set, I right clicked the web deployment project and build it. Once built, I copied the files in the release folder to my web server and everything worked.

From what I gathered, it was a combination of the way you build the site and the fact that the localization pointer is wrong (the pointer is set to a directory that disapears on release compile). I hope this helps someone.

 

 

 
New Post
2/15/2007 9:37 PM
 

mtndwell,

Thanks for a detailed procedure.
I want to note that related problems were reported to DNN team:
"Exclude admin\Skins\menu.ascx and admin\Containers\actions.ascx from the project"   (fixed for the next 4.4.2 release)

App_GlobalResources- Exceptions on Precompiled Web Site  -not resolved yet.  

You also may experience error(as I had):
The base class includes the field 'ctlRoles', but its type (DotNetNuke.Modules.Admin.Security.SecurityRoles) is not compatible with the type of control (ASP.admin_security_securityroles_ascx)
See the forum thread and corresponding Gemini issue: "Cross-references of controls in Security and Users folders causes errors on "Published" site"

Michael Freidgeim http://geekswithblogs.net/mnf
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Publish  DNN 4.4.0 error Publish DNN 4.4.0 error


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out