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 ...Can not loginCan not login
Previous
 
Next
New Post
8/30/2007 10:45 PM
 
Hi, we are doing Video Website using DNN 4.4.1. It's greate for us. There is only one error that happens sometimes and then we can not login. But restart IIS will work.
When we click login, there will be an error on login page, where the login control should be: "Module Load Warning
One or more of the modules on this page did not load. This may be temporary. Please refresh the page (click F5 in most browsers). If the problem persists, please let the Site Administrator know."
And the result is users can not log into Our website. This error mostly happens during the daytime.
 1.There will be two errors in IIS log at the time when the login page  start to broken:
 (1)
Event Type:    Information
Event Source:         W3SVC
Event Category:     None
Event ID:          1077
Date:                 8/26/2007
Time:                 5:09:37 PM
User:                 N/A
Computer:      SERVER-01
Description:
A worker process with process id of '2280' serving application pool 'XXXXXX.com' has requested a recycle because it reached its virtual memory limit. 
(2)
Event Type:    Warning
Event Source:         W3SVC
Event Category:     None
Event ID:          1013
Date:                 8/26/2007
Time:                 5:11:07 PM
User:                 N/A
Computer:      SERVER-01
Description:
A process serving application pool 'XXXXXX.com' exceeded time limits during shut down. The process id was '2280'.
 
 
 
 
2.Our solution Implemented:

1.       Increase the number of the connection:
Machine.config:

<
system.net>

          <connectionManagement>

                   <add address = "*" maxconnection = "96" />

          </connectionManagement>

</system.net>

   <system.web>

          <!--<processModel autoConfig="true"/>-->

          <processModel maxWorkerThreads="100" maxIoThreads="100"
minWorkerThreads="50" >

          </processModel>



2.       In App Pool, set a fix time to recycle the IIS and reduce the idle
time:

Set memory recycle limitation as 1024

Recycle worker processes at 4AM every day

Idle timeout to 8 Mins

Startup time limit from 90 to 180

Shutdown time limit from 90 to 180


And we have search the DNN forum but we could not find valuable information.



 

 1.There will be  two errors in IIS log at the time when the login page  start to broken:

 (1)

Event Type:    Information

Event Source:         W3SVC

Event Category:     None

Event ID:          1077

Date:                 8/26/2007

Time:                 5:09:37 PM

User:                 N/A

Computer:      SERVER-01

Description:

A worker process with process id of '2280' serving application pool 'XXXXXX.com' has requested a recycle because it reached its virtual memory limit. 

(2)

Event Type:    Warning

Event Source:         W3SVC

Event Category:     None

Event ID:          1013

Date:                 8/26/2007

Time:                 5:11:07 PM

User:                 N/A

Computer:      SERVER-01

Description:

A process serving application pool 'XXXXXX.com' exceeded time limits during shut down. The process id was '2280'.

 

 

 

 

2.Our solution Implemented:

1.       Increase the number of the connection:
Machine.config:

<

system.net>

          <connectionManagement>

                   <add address = "*" maxconnection = "96" />

          </connectionManagement>

</system.net>

   <system.web>

          <!--<processModel autoConfig="true"/>-->

          <processModel maxWorkerThreads="100" maxIoThreads="100"
minWorkerThreads="50" >

          </processModel>



2.       In App Pool, set a fix time to recycle the IIS and reduce the idle
time:

Set memory recycle limitation as 1024

Recycle worker processes at 4AM every day

Idle timeout to 8 Mins

Startup time limit from 90 to 180

Shutdown time limit from 90 to 180


And none of this will solve this issue.

And we have search the DNN forum but we could not find valuable information, can somebody give some advice?

If you need more information please feel free to ask. Thanks very much!

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Can not loginCan not login


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