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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...All 3essentials sites are downAll 3essentials sites are down
Previous
 
Next
New Post
4/16/2015 9:11 PM
 

All of my 3essentials sites are down. They were previously working and I made no changes. I am using their Cloud Server. 

I am able to remote into my windows desktop.

I have reset the server with no resolution.

Support is no help unless I want to pay more.  I'm very disappointed with 3essentials.  I can understand if *I* changed something that caused a site to break, but when all sites on the same server go down, it's clearly an issue with the server they provided.

*rant over*

Anyway, any thoughts on where to get started?  Not all sites have the same error.

Errors are as follows:

This site is currently Unavailable

Please check back later

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator to inform of the time the error occurred and of anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

 

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".



 
New Post
4/16/2015 9:44 PM
 
If you try to access it internally (from the RDP web browser) do you get any additional details?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
4/16/2015 11:17 PM
 

Thanks Chris --

I got a few details including that w3wp.exe the network path was not found

and  The current configuration only supports loading images built for a AMD64 processor architecture.

 

I seemed to get the sites working, no thanks to 3essentials.   I don't know how this changed... or if these are the "wrong fix"

Here's what I did.

1. in IIS Manager, I put "Enable 32-Bit Applications" to True under "Set Application Pool Defaults"

2. I put Start Mode to "AlwaysRunning"

3. Then, for each of my sites... I changed from DefaultAppPool to the mysite.com(domain)(4.0)(pool) under Sites.. Mysite.com..  "Set Application Defaults" and also under "Advanced Settings" for mysite.com

4. I also made sure each IPWG user had FULL CONTROL permissions... which I don't think should have changed, but just to add to what I did.

 

Questions:

-Is there a disadvantage/problem with Enabling 32-bit applications?

-Is there a disadvantage to AlwaysRunning as StartMode? (other than performance, maybe... my sites are not high traffic so that shouldn't be a concern).

-Is there a disadvantage to having each site use it's own App Pool instead of the DefaultAppPool?  (Or is it even possible for all sites to run on DefaultAppPool).  I have 7 DNN installs... so now running on 7 App Pools.

 

 

 

 
New Post
4/17/2015 2:05 AM
 

It's better to run each site in its own app pool so that if something goes awry with a pool, it only affects the site in that pool. If you have your sites in the same pool and the pool goes offline, all your sites are down. I don't know any disadvantage other than using some more memory but that's not something to worry about on a server with enough memory. One of reasons app pool were created was to isolate the sites from each other. In Chrome each tab and each extension runs in its own process so that if one misbehaves, it doesn't affect the others. Same idea with IIS app pools.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...All 3essentials sites are downAll 3essentials sites are down


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