-
Partition Wizard
-
Partition Manager
- 4 Ways to Fix «Server Error in ‘/’ Application»
4 Ways to Fix «Server Error in ‘/’ Application» [Partition Manager]
By Linda | Follow |
Last Updated December 28, 2022
Have you encountered «Server Error in ‘/’ Application«? The causes of the error may be various. In this post, MiniTool Partition Wizard lists some common reasons of this error and offers you corresponding solutions.
«Server error in ‘/’ application» issue is an application error on the server that prevents the website from running. And this error is usually related to IIS and ASP.NET.
- IIS (Internet Information Services): It is an extensible web server service created by Microsoft for use with the Windows NT family. It is a kind of web server. Once a website is created, it must have a web server. Thus, others can browse your website.
- NET: It is a category library provided by Microsoft in the .NET Framework for developing Web applications. It can run on the IIS server with .NET Framework installed, and use HTML, CSS, JavaScript and server scripts to create web pages and websites.
«Server error in ‘/’ application» issue may be caused by various reasons. Some of the most common reasons include:
- IIS has some problems and needs to be restarted.
- It’s just a 404 error. The resource you are looking for is missing or has been renamed.
- You are accessing a file with a file extension that does not have permissions to be run on the server
- You are using a version of .NET Framework incompatible with some programs, features, and file types.
If you don’t know what causes your «Server error in ‘/’ application», please check the error description on the error page.
[Solved] 9anime Server Error, Please Try Again on Windows
How to Fix «Server Error in ‘/’ Application»
To fix the «server error in ‘/’ application», you can use the following methods.
Fix 1. Restart IIS
- Click the Start button in the lower left-hand corner and then choose Administrative Tools
- Click Internet Information Services (IIS) Managerto launch it.
- In the IIS manager, select the server in the left-hand window pane and then click Restart on the left-hand side.
Fix 2. Update the URL
If the «server error in ‘/’ application» is a 404 error, you just need to correct the URL in the link that triggers this error.
Search Google or Type a URL, What Is It & Which to Choose?
Fix 3. Add the MIME Type
If a file does not have permissions to be run on the server, you should first check if you are calling the correct file name. For example, is there a typo in the file extension? If the file name is correct, then you may need to add the MIME type of the file extension to the server.
If don’t know the MIME Type of a file extension, you can search it online. Then, you can add the MIME type in the IIS Manager through the following steps:
- Open the IIS Manager
- In the left-hand window panel, expand your server > Sites > Default Web Site.
- In the central pane, double-click MIME Types.
- Under the Actions column on the right, click .. button. This will open a window.
- In the pop-up window, fill in the File name extensionand MIME Type, and then click OK.
Fix 4. Verify the .NET Version
- Open IIS Manager
- Expand the server in the left-hand window panel and choose Application Pools.
- Right-click on an app and choose Basic Settings…
- In the pop-up window, select the .NET version from the drop-down menu, and then click OKto confirm your choice.
Top 5 Ways to Fix .NET Framework 3.5 Missing in Windows 10
About The Author
Position: Columnist
Author Linda has been working as an editor at MiniTool for 1 year. As a fresh man in IT field, she is curious about computer knowledge and learns it crazily. Maybe due to this point, her articles are simple and easy to understand. Even people who do not understand computer can gain something.
By the way, her special focuses are data recovery, partition management, disk clone, and OS migration.
-
Partition Wizard
-
Partition Manager
- 4 Ways to Fix «Server Error in ‘/’ Application»
4 Ways to Fix «Server Error in ‘/’ Application» [Partition Manager]
By Linda | Follow |
Last Updated December 28, 2022
Have you encountered «Server Error in ‘/’ Application«? The causes of the error may be various. In this post, MiniTool Partition Wizard lists some common reasons of this error and offers you corresponding solutions.
«Server error in ‘/’ application» issue is an application error on the server that prevents the website from running. And this error is usually related to IIS and ASP.NET.
- IIS (Internet Information Services): It is an extensible web server service created by Microsoft for use with the Windows NT family. It is a kind of web server. Once a website is created, it must have a web server. Thus, others can browse your website.
- NET: It is a category library provided by Microsoft in the .NET Framework for developing Web applications. It can run on the IIS server with .NET Framework installed, and use HTML, CSS, JavaScript and server scripts to create web pages and websites.
«Server error in ‘/’ application» issue may be caused by various reasons. Some of the most common reasons include:
- IIS has some problems and needs to be restarted.
- It’s just a 404 error. The resource you are looking for is missing or has been renamed.
- You are accessing a file with a file extension that does not have permissions to be run on the server
- You are using a version of .NET Framework incompatible with some programs, features, and file types.
If you don’t know what causes your «Server error in ‘/’ application», please check the error description on the error page.
[Solved] 9anime Server Error, Please Try Again on Windows
How to Fix «Server Error in ‘/’ Application»
To fix the «server error in ‘/’ application», you can use the following methods.
Fix 1. Restart IIS
- Click the Start button in the lower left-hand corner and then choose Administrative Tools
- Click Internet Information Services (IIS) Managerto launch it.
- In the IIS manager, select the server in the left-hand window pane and then click Restart on the left-hand side.
Fix 2. Update the URL
If the «server error in ‘/’ application» is a 404 error, you just need to correct the URL in the link that triggers this error.
Search Google or Type a URL, What Is It & Which to Choose?
Fix 3. Add the MIME Type
If a file does not have permissions to be run on the server, you should first check if you are calling the correct file name. For example, is there a typo in the file extension? If the file name is correct, then you may need to add the MIME type of the file extension to the server.
If don’t know the MIME Type of a file extension, you can search it online. Then, you can add the MIME type in the IIS Manager through the following steps:
- Open the IIS Manager
- In the left-hand window panel, expand your server > Sites > Default Web Site.
- In the central pane, double-click MIME Types.
- Under the Actions column on the right, click .. button. This will open a window.
- In the pop-up window, fill in the File name extensionand MIME Type, and then click OK.
Fix 4. Verify the .NET Version
- Open IIS Manager
- Expand the server in the left-hand window panel and choose Application Pools.
- Right-click on an app and choose Basic Settings…
- In the pop-up window, select the .NET version from the drop-down menu, and then click OKto confirm your choice.
Top 5 Ways to Fix .NET Framework 3.5 Missing in Windows 10
About The Author
Position: Columnist
Author Linda has been working as an editor at MiniTool for 1 year. As a fresh man in IT field, she is curious about computer knowledge and learns it crazily. Maybe due to this point, her articles are simple and easy to understand. Even people who do not understand computer can gain something.
By the way, her special focuses are data recovery, partition management, disk clone, and OS migration.
автор: Александр Шарафан
При работе в управляемом приложении через веб сервис пользователь иногда получает сообщение:
Server Error in ‘/’ Application
С совершенно не вразумительным текстом описания ошибки и рекомендацией как поступить при этом.
Как решать указанную проблему?
Разделим саму проблему на две части:
Проблема Веб сервиса и проблема 1С.
Проблему 1С можно обнаружить и устранить, если запустить режим отладки Тонкого клиента и проверить работу управляемых форм, ответственных за место в котором происходит ошибка.
Здесь мы будем рассматривать половину относящуюся к Веб серверу.
В некоторых источниках пишут что указанная ошибка является характерной для хакерских атак, но в нашем конкретном случае о такой атаке речь идти не может, т.к. проблема возникает при обращении к сервису не из вне сети, а из интранет.
В переводе на русский язык ошибка звучит как: «Ошибка приложения вызванная на сервере. Текущие настройки сервера для этого приложения ошибочны, приложение было остановлено по соображениям безопасности в привентивном режиме.»
Рекомендация данная ниже отключает режим вывода сообщений, но не дает ответа как устранить причину появления ошибки, при условии правильности работы кода 1С во всех других режимах.
немного манипуляций и страница дает уже более понятную информацию:
Если ранее проблема была не понятна, то сейчас более понятно что ошибка относится именно к веб серверу и что вызывается именно привентивным прекращением работы приложения веб сервером.
Проблема же заключается в том, что .net имеет режим валидации исполняемого сервером кода, вот эта валидация и приводит к появлению указанной ошибки.
Для устранения ошибки рекомендуется выполнить настройки вебсервера:
1. ValidateRequest = «False»
например,если в конфигурационном файле у вас уже есть:
<% @ Page Language = «VB» AutoEventWireup = «False» Codebehind = «MyForm.aspx.vb» наследует = «Proj.MyForm»%>
то должно стать:
<% @ Page Language = "VB" AutoEventWireup = "False" Codebehind = "MyForm.aspx.vb" наследует = "Proj.MyForm" ValidateRequest = "False"%>
В более поздних версиях Visual Studio значение этого свойства можно получить на странице свойств, поэтому просто установите » ValidateRequest » на » False«. Любым способом установки можно получить тот же результат.
Примечание:
1.1. Если вы используете. NET 4, то вам необходимо добавить requestValidationMode = «2.0» в HttpRuntime раздел конфигурацииweb.config файла. Например:
<httpRuntime requestValidationMode=»2.0″/>
Если у вас еще нет раздела HttpRuntime в web.config, то это можно сделать такие настройки в разделе <system.web>.
Чтобы глобально выключить проверку запросов добавьте следующую строку в вашем web.config файла: <pages validateRequest=»false» /> раздела <system.web>.
2. Установить EnableEventValidation = «False» запретим проверку корректности события.
3. Установить EnableViewState = "False"
и
4. Установить нужное значение в ExecutionTimeout. В моем случае строка выглядит так: ExecutionTimeOut = «20»
Это верно для: NET 1.1,. NET 2,. NET 3.5 и. NET 4.0
Использованы материалы интернет форумов и сайтов:
автор Александр Шарафан
- Remove From My Forums
-
Question
-
We recently migrated to Office 365 Government E3.
All employees in our SharePoint group have been able to access SharePoint without issue… until this morning.
Admin users are able to select the SharePoint app from the Office 365 homepage and be directed to our organization’s SharePoint sites (https://xxxxxxxxxx.sharepoint.com/_layouts/15/sharepoint.aspx).
When any other (non-admin) user attempts these steps, they receive the following message:
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».<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>Notes: The current error page you are seeing can
be replaced by a custom error page by modifying the «defaultRedirect» attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
An admin and a regular user can attempt to access SharePoint on the same workstation, and, still, only the admin can view it.
I have read through forums regarding this message and they all say that it is an IIS issue. We installed IIS on 1 server this morning, which is when people started to report the issue. I stopped IIS on the server, but the issue remains. But, since we aren’t
hosting SharePoint ourselves and accessing it through a 365 subscription, I don’t think this should matter anyway.I also read that the web.config files should be edited at the following directory: C:inetpubwwwrootwssVirtualDirectories…
We don’t have that directory on the server that is running IIS (or on any other server, for that matter). The furthest
the directory goes is C:inetpubwwwroot-
Edited by
Tuesday, June 5, 2018 5:00 PM
-
Edited by
Answers
-
The Microsoft Support team opened a ticket for this issue and it has been «resolved». They had grant permissions to all of the users again.
Here it is, Barney style:
1.) Go to your site page (https://xxxxxxx.sharepoint.com/SitePages/Home.aspx(
2.) Click on the Settings gear icon on the top right, go to Site Settings
3.) Click on Site Permissions
4.) Grant permissions to your users
So simple, but something that I didn’t even think about because they could still access SharePoint via OneDrive and direct URL.
THANK YOU, DALE AND ETHAN!
-
Marked as answer by
davisa216
Wednesday, June 6, 2018 9:48 PM
-
Marked as answer by
Server Error in Application. A potentially dangerous Request./ Серверная ошибка в приложении. Потенциально опасный запрос.
Может кому пригодится в работе.
При работе в управляемом приложении через веб сервис пользователь иногда получает сообщение:
Server Error in ‘/’ Application
С совершенно не вразумительным текстом описания ошибки и рекомендацией как поступить при этом.
Как решать указанную проблему?
Разделим саму проблему на две части:
Проблема Веб сервиса и проблема 1С.
Проблему 1С можно обнаружить и устранить, если запустить режим отладки Тонкого клиента и проверить работу управляемых форм, ответственных за место в котором происходит ошибка.
Здесь мы будем рассматривать половину относящуюся к Веб серверу.
В некоторых источниках пишут что указанная ошибка является характерной для хакерских атак, но в нашем конкретном случае о такой атаке речь идти не может, т.к. проблема возникает при обращении к сервису не из вне сети, а из интранет.
В переводе на русский язык ошибка звучит как: «Ошибка приложения вызванная на сервере. Текущие настройки сервера для этого приложения ошибочны, приложение было остановлено по соображениям безопасности в привентивном режиме.»
Рекомендация данная ниже отключает режим вывода сообщений, но не дает ответа как устранить причину появления ошибки, при условии правильности работы кода 1С во всех других режимах.
немного манипуляций и страница дает уже более понятную информацию:
Если ранее проблема была не понятна, то сейчас более понятно что ошибка относится именно к веб серверу и что вызывается именно привентивным прекращением работы приложения веб сервером.
Проблема же заключается в том, что .net имеет режим валидации исполняемого сервером кода, вот эта валидация и приводит к появлению указанной ошибки.
Для устранения ошибки рекомендуется выполнить настройки вебсервера:
1. ValidateRequest = «False»
например,если в конфигурационном файле у вас уже есть:
<% @ Page Language = «VB» AutoEventWireup = «False» Codebehind = «MyForm.aspx.vb» наследует = «Proj.MyForm»%>
то должно стать:
<% @ Page Language = «VB» AutoEventWireup = «False» Codebehind = «MyForm.aspx.vb» наследует = «Proj.MyForm» ValidateRequest = «False»%>
В более поздних версиях Visual Studio значение этого свойства можно получить на странице свойств, поэтому просто установите » ValidateRequest » на » False». Любым способом установки можно получить тот же результат.
Примечание:
1.1. Если вы используете. NET 4, то вам необходимо добавить requestValidationMode = «2.0» в HttpRuntime раздел конфигурацииweb.config файла. Например:
<httpRuntime requestValidationMode=»2.0″/>
Если у вас еще нет раздела HttpRuntime в web.config, то это можно сделать такие настройки в разделе <system.web>.
Чтобы глобально выключить проверку запросов добавьте следующую строку в вашем web.config файла: <pages validateRequest=»false» /> раздела <system.web>.
2. Установить EnableEventValidation = «False» запретим проверку корректности события.
3. Установить EnableViewState = «False»
и
4. Установить нужное значение в ExecutionTimeout. В моем случае строка выглядит так: ExecutionTimeOut = «20»
Это верно для: NET 1.1,. NET 2,. NET 3.5 и. NET 4.0
Использованы материалы интернет форумов и сайтов:
http://www.cryer.co.uk/brian/mswinswdev/ms_vbnet_server_error_potentially_dangerous.htm
http://social.msdn.microsoft.com/Forums/en-US/windowsazuresecurity/thread/3dbedb02-e6b6-4e44-8a94-39225f2b41c4
http://forums.asp.net/t/1775186.aspx/1
http://forums.asp.net/t/1825664.aspx/1
http://www.west-wind.com/weblog/posts/2010/Aug/19/RequestValidation-Changes-in-ASPNET-40
Always check for issues at the website’s administrator’s end
by Matthew Adams
Matthew is a freelancer who has produced a variety of articles on various topics related to technology. His main focus is the Windows OS and all the things… read more
Updated on August 4, 2022
Fact checked by
Alex Serban
After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server… read more
- The Server Error in ‘/’ Application runtime browser issue arises when they try to sign in to accounts or open pages.
- This troubleshooting guide includes resolutions that might fix the Server Error in ‘/’ Application runtime for Google Chrome users.
- Also, find out how to fix the Page(s) Unresponsive error in Chrome.
- Easy migration: use the Opera assistant to transfer exiting data, such as bookmarks, passwords, etc.
- Optimize resource usage: your RAM memory is used more efficiently than Chrome does
- Enhanced privacy: free and unlimited VPN integrated
- No ads: built-in Ad Blocker speeds up loading of pages and protects against data-mining
- Download Opera
Some Google Chrome, and other browser, users have posted on support forums about a Server Error in ‘/’ Application runtime issue that arises when they try to log in or open certain website pages.
Consequently, users can’t log in to or open specific web pages.
The error message states:
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.
Some Server Error in ‘/’ Application runtime errors has different descriptions. However, they still occur in much the same way. Another Server Error description states:
An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception.
Some users have been able to fix the Server Error in ‘/’ Application runtime error for Chrome with the resolutions listed in the following sections.
Why do I get Server Error in ‘/’ Application?
The Server Error in ‘/’ Application. Runtime error on Chrome and other browsers can be due to an internal server issue.
In this case, there’s nothing that you can do other than apprise the administrator and wait for the problem to be resolved.
While Chrome is a pretty responsive browser, for the most part, issues can arise when it’s undergoing maintenance, or in the rare scenario when its servers have problems.
If the error is encountered on all websites, it’s likely an issue at your end with the saved cookies, corrupt browsing data, or misconfigured Chrome settings.
Now that you know what causes this runtime error in Chrome, let’s head to the most effective solutions for it.
Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.
We will show you how to update your browser, reconfigure it for better performance and remove unnecessary clutter like cached files that can cause errors/bugs.
Quick Tip:
If you keep having problems with Chrome, try a more responsive browser, such as Opera. It’s built on Chromium as well, which means all your favorite Chrome extensions are compatible.
Not only that but Opera is updated very frequently, leaving no room for errors/bugs when you browse. It’s also very lightweight and packed with modern features.
Opera
Browse the web securely, block ads, connect to VPN, and more!
How do I get rid of Server Error in ‘/’ Application?
1. Is the website down?
Check if there are any kind of outages for the website the Server Error runtime issue arises by opening the Downdetector website.
Select your country on the drop-down menu, and then input a website to check in the search box on Downdetector.
Downdetector will tell you if there are any notable outages for the website (web service). If it says that user reports indicate possible issues at the website, wait a day or two before trying to log in again.
2. Delete cookies for the page you can’t log in to
- First, open the website where the Server Error in ‘/’ Application issue arises.
- Click the padlock button on the left side of Chrome’s URL bar, and select Cookies.
- Double-click the listed website where the issue arises.
- Select Cookies and click Remove to delete them.
- Next, click on the Done button.
Once done, check if the Server Error in ‘/’ Application – The resource cannot be found issue in Chrome is fixed. If not, head to the next method.
3. Clear Chrome’s browser data
- Launch Chrome, and press Ctrl + Shift + Del to open the Clear browsing data utility.
- Select the All time option from the Time range drop-down menu.
- Next, select all three data options here, and then click the Clear data button.
4. Reset Google Chrome
- Paste the following path in the address bar and hit Enter:
chrome://settings/reset - Click on the Restore settings to their original defaults option.
- Click Reset settings in the confirmation prompt that appears.
Once done, verify if the Server Error in ‘/’ Application issue in Chrome is resolved. In case it persists, head to the next method.
5. Remove credentials
- Press Windows + R to launch Run, enter Control Panel in the text field, and click OK.
- Click on User Accounts.
- Then click Manage Windows Credentials under Credential Manager.
- Select a listed generic credential to expand it, and click Remove to delete the credential.
- Click Yes in the Delete Generic Credential prompt window that opens.
- Similarly, delete all the listed generic credentials.
If the previous methods haven’t worked, this one should fix the Server Error in ‘/’ Application issue in Chrome.
6. Reinstall Google Chrome
- Press Windows + R to launch the Run command, type appwiz.cpl, and click the OK button.
- Select Google Chrome, and then click on Uninstall.
- Follow the on-screen instructions to complete the process.
- Restart Windows after you’ve uninstalled the browser.
- Now, download Google Chrome once again, and run the setup to install it.
The above resolutions will fix Server Error in ‘/’ Application for some Chrome users. If you still see the error, consider emailing the website about the issue or try opening and logging in to the site with an alternative browser.
Also, find out how to fix the Page(s) Unresponsive error in Chrome. Tell us which fix worked for you in the comments section below.
