[QUOTE=Yash]
if your DNN site is loading. Checks for certain phrases on your homepage as well as the outofmemory error.
If anything error happens on your site, our staff would be instantly notified. So far absolutely no issues at all. Your homepage is responding in an average of 300ms
[/QUOTE]
This is the way it normal is… we’ll see how it goes tomorrow during the day.
Thanks
[QUOTE=gsaunders]
This is the way it normal is… we’ll see how it goes tomorrow during the day.
Thanks
[/QUOTE]
It just happened 2:45PM Eastern. I checked 2 sites this time and they both were generating errors. The second site generated a different error all together, but it would fail no matter what you did.
Once one site was ok the other site started working as well. Sorry I didn’t get the error on the second site because I accidentally hit refresh one more time and it was working again. Next time I’ll give the error for that one.
we just recorded the first error with it, and have it resolved now.
[QUOTE=Stephen]
we just recorded the first error with it, and have it resolved now.
[/QUOTE]
Stephen, What was the problem?
Thanks
[QUOTE=Stephen]
we just recorded the first error with it, and have it resolved now.
[/QUOTE]
Unfortunately not. Both of the DotNetNuke sites are generating errors again.
The second site is giving the error below. Then about 30 seconds to a minute or so later it is back up with no errors.
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 tag within a “web.config” configuration file located in the root directory of the current web application. This tag should then have its “mode” attribute set to “Off”.
Please check your DNN logs to see if any clues can be found there, that outage did not affect any other sites, so you need to check the local logs, I know one of the domains as it is in the monitoring system, but I can check the other domain as well, if you will send me a PM.
[QUOTE=Stephen]
Please check your DNN logs to see if any clues can be found there, that outage did not affect any other sites, so you need to check the local logs, I know one of the domains as it is in the monitoring system, but I can check the other domain as well, if you will send me a PM.
[/QUOTE]
Well… I have 3 DNN sites all on WIN10 that are doing the same thing. When 1 reports a problem I check all 3 and all 3 have the same problem.
These are 3 totally separate DNN installes and 3 SQL DB’s. They each have different modules in use so I know it is unrelated to a particular module.
Personally I think there is something going on with Win10 on a very intermittant basis, but all I have of proof is my sites keep doing this. Although I only detect maybe 3 times a day it makes me wonder how many other times it might be happening that I miss.
I checked the logs and they only show the error that I see when it happened… plus the same error many more times. It seems that everything started happening on 09/13/05.
I have one of the sites setup at another host with the exact same database and configurations and data, but that site does not report problems at all.
I desparately need to move some folks over that will be using DNN, but now I cannot confidently do so. I need to have some confidence that this memory error is resolved. It all stems back to the following error:
“Exception of type System.OutOfMemoryException was thrown”
I did some searching and found this on microsoft:
Virtual Bytes. The current size, in bytes, of the virtual address space for this process.
The virtual address space limit of a user mode process is 2 GB, unless 3 GB address space is enabled by using the /3GB switch in boot.ini. Performance degrades as this limit is approached, and typically results in a process or system crash. The address space becomes fragmented as the 2 GB or 3 GB limit is approached, and so I recommend a conservative threshold of 1.4 or 2.4 GB, respectively. If you’re running into issues here, you will see System.OutOfMemoryException being thrown, and this may or may not crash the process.
When running on IIS 6.0, a virtual memory limit can be set in IIS Manager. However, setting this improperly can cause problems for ASP.NET. ASP.NET expunges items from the cache to avoid exceeding the Private Bytes limit, but the algorithm uses Private Bytes and the Private Bytes limit in this determination. It does not monitor Virtual Bytes or the Virtual Bytes limit. Given that the difference between Virtual Bytes and Private Bytes is typically no more than 600 MB, you could set the Virtual Bytes limit to a value 600 MB larger than the Private Bytes limit if you are concerned about the possibility of virtual memory leaks or fragmentation. If this is desirable, set a limit for Maximum virtual memory (in megabytes), found on the Recycling tab for the Properties of the application pool.
Version 1.0 of the Framework does not support 3 GB address space in the worker process or the state service. However, see Knowledge Base Article 320353 for instructions to enable 3 GB address space within inetinfo.exe. Version 1.1 fully supports 3 GB address space for the worker process and state service.
I found this in regards to the error:
http://www.dotnet247.com/247reference/System/OutOfMemoryException.aspx
And one more link discussing it:
Help… ;(
I knew about the 2GB limit, and that is why I edited it to not allow it to go over that, I am checking further now, but the problem does not seem to be consistant with the problems faced in the past with this matter.
[QUOTE=Stephen]
I knew about the 2GB limit, and that is why I edited it to not allow it to go over that, I am checking further now, but the problem does not seem to be consistant with the problems faced in the past with this matter.
[/QUOTE]
I appreciate you looking into this as I can’t see there NOT being a problem on the server regarding possibly memory.
I am going to do more research on this error as there seem to be others that have received it in the dotnet world and it usually kept coming back to a contiguous memory problem. If I find anything that may shed some light I’ll post it. Pretty swamped here so I can’t do to much research at the moment.
I just know the EXACT data and configuration at another host does not do this. Of course I am sure there are different loads on the server, different amounts of memory and so on.
If we can’t find a resolution I wonder what the chances of getting all my sites OFF of WIN10 and to another server? I don’t want to do this unless I have no other choice, but trying to plan should we not find a resolution.
Greg
I am now getting this on one of the DNN sites.. not the others.
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the “Refresh” button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
Waited a minute and tried to reload and now it is just waiting… and a little longer it finally went in… BUT EXTREMELY SLOW X(
I am at loss here because I have not seen a single complaint about Win10 nor have any of the other sites we have been monitoring been throwing up errors.
The site you asked us to monitor has 99.7%+ uptime so far (and this is an actual content check test). Can you PM me this other site too so we can monitor it.
You are free to request us to move you to Win11 or another server if you think that will help.
i’ve been monitoring a couple of my sites on win10 sincd this thread started and haven’t noticed anything yet.
[QUOTE=Yash]
I am at loss here because I have not seen a single complaint about Win10 nor have any of the other sites we have been monitoring been throwing up errors.
The site you asked us to monitor has 99.7%+ uptime so far (and this is an actual content check test). Can you PM me this other site too so we can monitor it.
You are free to request us to move you to Win11 or another server if you think that will help.
[/QUOTE]
I promise you that I am not making this up. 
It happened about 3 to 4 times today. If it continues I will probably ask that they be moved, but I want to see if I can figure out what is going on and do more research on the errors that are showing up.
Arghhh
gsaunders, I know you won’t be making this up. Just at loss why its happening only to you. Are you sure there could be nothing in your DNN site causing the application to crash?
There have been only 2 instances that our monitoring system has picked up an issue with your site since it has been monitored. Can you PM me your other site too so we can set them up to be monitored. I would like to see if your sites are crashing together or at different intervals, as well as their frequency
[QUOTE=Yash]
gsaunders, I know you won’t be making this up. Just at loss why its happening only to you. Are you sure there could be nothing in your DNN site causing the application to crash?
There have been only 2 instances that our monitoring system has picked up an issue with your site since it has been monitored. Can you PM me your other site too so we can set them up to be monitored. I would like to see if your sites are crashing together or at different intervals, as well as their frequency
[/QUOTE]
I’m re-doing the other site, because I realized it was still on 3.1.0 instead of the 3.1.1 DNN code. I’ll PM it to you once I get it going again.
An yes… they all crash together. When I see an alert from one site… if I check right away I can see that all 3 were giving the error. I do this from different computers as well. I have 3 in my office and I have each one ready to load up the site at a moments notice when I get the alert.
Thanks
gsaunders,
We have been doing exactly the same thing on the same server (win10) and experiencing the same problems at the same time.
I wish I knew about this forum thread. I wish the tech support guys I have been talking about this with in Live Chat would have told me about it.
Please, tell me how it is going for you now. I too had a DotNetNuke site in version 3.1.0 that I have now upgraded to 3.1.1, but I still get the errors in the DotNetNuke log.
I understand that 97+ percent seems good, I would probably agree if that 3- percent was all in one block. The problem is that this downtime is spread out over the day and therefore disrupts many users of the site. They are trying to do business and turn away in disgust at what they perceive to be an unprofessional set-up.
I would really like to see more discussed about this because the issue certainly hasn’t gone away. I also run a Community Server site on win10 and I will now try to determine if the errors occur there too.
The site gsuanders gave us.. we put that in monitoring at it has had no abnormal downtime in at least the last week.
If you have a site, PM me its URL and I’ll have that monitored too. I have hardly seen any site given outofmemory errors on Win10…
Yes. The System.OutOfMemoryException error can also be found in the log for the Community Server application.
It last happened today.
What is the frequency?
[QUOTE=gsc4]
gsaunders,
We have been doing exactly the same thing on the same server (win10) and experiencing the same problems at the same time.
I wish I knew about this forum thread. I wish the tech support guys I have been talking about this with in Live Chat would have told me about it.
Please, tell me how it is going for you now. I too had a DotNetNuke site in version 3.1.0 that I have now upgraded to 3.1.1, but I still get the errors in the DotNetNuke log.
I understand that 97+ percent seems good, I would probably agree if that 3- percent was all in one block. The problem is that this downtime is spread out over the day and therefore disrupts many users of the site. They are trying to do business and turn away in disgust at what they perceive to be an unprofessional set-up.
I would really like to see more discussed about this because the issue certainly hasn’t gone away. I also run a Community Server site on win10 and I will now try to determine if the errors occur there too.
[/QUOTE]
I am still getting it although not as frequently as before… or at least not that I am detecting. I am currently automatically checking the site every 10 minutes.
I haven’t had a chance to do much more research on the error listed, but there seems to be a number of places that talk about it. I wanted to do some more research to try and find ways to determine what exactly causes the problem to possibly isolating it.
When it does happen all of my DNN sites belly up which makes me wonder if there is a system wide thing with memory or something that happens that may only effect asp.net or maybe something specific to DNN sites and the related code.
I know I have another host that never gets the problem with an identical database and files (I duplicated them)… so it makes me think it is something specific to this server. All of mine are on this one server, so I don’t have any other servers here at jodo that I can say works or doesn’t work on.
I was starting to wonder how I could be the only one with this problem… especially when it effects all of the DNN sites I have instead of just one… not that I have that many, but the point is it effects multiple domains and installs.
Like I said it is not quite as frequent as it was the first few days it was happening… but it is still happening to me nonetheless. I am considering getting them moved to another server… or setting up another account that hopefully will go to another server and then setup a duplicate site to see if I get the same results.
Greg