DNN 9.x Internal Server Error
-
Hello all, I recently installed DNN v9.x on a VM with about 250GB RAM, 36vCPU with Windows 2012 R2 OS. Database is installed on a separate VM with 320 GB RAM, 42vCPU and same OS. At first when the site was lunched, everything works ok but as the number of users accessing the site increases, the site begin to throw this error "500 - Internal Server Error". This only last for about 5mins after which when the user freshes the site some couple of times, the error disappears. While this error lasted, utilization across CPU and Memory was around 4%. Any help will be appreciated.
-
Hello all, I recently installed DNN v9.x on a VM with about 250GB RAM, 36vCPU with Windows 2012 R2 OS. Database is installed on a separate VM with 320 GB RAM, 42vCPU and same OS. At first when the site was lunched, everything works ok but as the number of users accessing the site increases, the site begin to throw this error "500 - Internal Server Error". This only last for about 5mins after which when the user freshes the site some couple of times, the error disappears. While this error lasted, utilization across CPU and Memory was around 4%. Any help will be appreciated.
The server configurations look ridiculous. I create anemic VM's starting out to check performance. You have to "tune" VM's; ISP hosts (including MS) will let you abuse VM's as much as you want. It's a $ to them. You said your site was "lunched" ... I agree.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
Hello all, I recently installed DNN v9.x on a VM with about 250GB RAM, 36vCPU with Windows 2012 R2 OS. Database is installed on a separate VM with 320 GB RAM, 42vCPU and same OS. At first when the site was lunched, everything works ok but as the number of users accessing the site increases, the site begin to throw this error "500 - Internal Server Error". This only last for about 5mins after which when the user freshes the site some couple of times, the error disappears. While this error lasted, utilization across CPU and Memory was around 4%. Any help will be appreciated.
Check the application event log on the server to find the details of the error. Without that, anything you do to try to fix the problem will be a blind guess.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
