We are trying to configure OOF on an Exchange Server. We are talking about Outlook 2010 with Exchange server 2010.
If i navigate to https://mail.[server]/ews/exchange.asmx i see the following page:
Server Error in '/EWS' 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 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".
<!-- 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 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>
I already recreated EWS, OWA and OAB, without any effect.
There is no proxy active in the organisation.
There are no internet restrictions.
Help
Related
What is the reason for the error page I get when I run my webapp in Visual Studio. The URL is http://localhost:5000/
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Reason: http://localhost:5000 refers to the root of the webserver. So, for the above request, it tries to read the root folder of the server. However, IIS (express) by default doesn't allow you to view the file system. Therefore it shows above error.
Most probably you don't need to access the root of the server, instead you might need to access your webapp (ex: http://localhost:5000/myapp).
However, if you know exactly what you are doing then you can enable IIS to show the root directory (file system) using the following config in the Web.config of your application
Important: Below config should not be activated in a production or any
publicly reachable environment which is obviously a high critical
security issue.
<system.webServer>
<directoryBrowse enabled="true" />
<modules runAllManagedModulesForAllRequests="true"></modules>
</system.webServer>
Two things are usually the issue when I get this error:
1st: I never defined a standard document and changed it at some point - therefore the standard document that is automatically defined by the IIS in this case, doesn't exist
2nd: I didn't enable index search
You might want to try this. You can change those settings in the IIS settings directly.
I'm trying to upload my webapp to the provider. I can see only the default "Runtime error" message, telling me to turn off customErrors to view more about the error. I changed config file and still nothing. I made changes:
<system.web>
<customErrors mode="Off"/>
</system.web>
and nothig. When I upload other webapp to the same place everything is working fine. What other reason could couse the problem?
Your server might have a configuration that overrides your application settings and disables trace output, custom errors, and debug capabilities.
Find your machine.config file, which is located here by default:
..\Microsoft.NET\Framework\framework_version\CONFIG or
..\Microsoft.NET\Framework64\framework_version\CONFIG
In the machine.config file, there is a tag: . When this is set, the ability to view detailed error information is taken away. Note that this setting will override the web.config setting . Set it to false by using
<deployment retail="false" />and try again.
I have two web services, of old school, asmx. Both is in the same sub folder, which have anonymous authentication, in a MVC web application that have windows authentication.
When I browse one of them I get expected result, I can Invoke the service, but when I browse the other I get "HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers.".
I then rename the second one and everything works fine. Even if I remove the second asmx file I get Unauthorized, instead of "Resource not found".
I have searched the registry and the file system for references to the file name, but find nothing. I deleted ASP.NET Temporary Files, but that did not help.
Any trouble shooting suggestions?
This was not easy to find, but in inetpub\temp\appPools\ there was a folder named as the application pool. In that folder there is "copy" of parts of the IIS config.
At some point we must have accidentally marked the actual asmx file, instead of the folder when we changed autentication. So it contained a special configuration section for just the file. Like:
<location path="Web/Services/ServiceName.asmx">
<system.webServer>
<security>
<authentication>
<anonymousAuthentication enabled="false" />
</authentication>
</security>
</system.webServer>
</location>
When we removed that section it worked again :)
I have a problem with deploying the 3 tier lightswitch web application on the server.
On the local server IIS7 everything works perfect but when i deploy it to the vps which also runs IIS7 it gives me this error when i try to navigate to the page:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
I have published a package on the disc, uploaded it to the server, installed the application under Default Website with success. But when i navigate to the application it shows that error...
This is what is shown as a problem area:
Config Source
141: </system.serviceModel>
142: <uri>
143: <schemeSettings>
It is part of the web.config file. When i open it and go there i see this:
<uri>
<schemeSettings>
<add name="http" genericUriParserOptions="DontUnescapePathDotsAndSlashes" />
<add name="https" genericUriParserOptions="DontUnescapePathDotsAndSlashes" />
</schemeSettings>
</uri>
and add part is underlined which gives me further explanation of the error:
web.conf error: the element 'schemeSettings' cannot contain child element 'add' because the parent element's content model is empty.
I tried looking on the internet for the solution but no luck...
Thank you!
I have found what was the problem.
On the IIS i had DefaultAppPool selected for the application. When i changed it to ASP.NET v4.0 error was gone. This can be done in application basic settings.
Open IIS Manager, select the application, in the right column of explorer click Basic Settings, click button Select and choose ASP.NET v4.0, click Ok.
That was it for me. Hope it helps someone...
Works fine on the local machine, but when deployed this error message pops up:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070021
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File \\?\C:\inetpub\foo\web.config
Requested URL http://foo.net:80/
Physical Path C:\inetpub\foo
Logon Method Not yet determined
Logon User Not yet determined
Config Source:
71: </modules>
72: <handlers> <--- This part is highlighted on the error page.
73: <add name="CassetteHttpHandler" path="cassette.axd" preCondition="integratedMode" verb="*" allowPathInfo="true" type="Cassette.Aspnet.CassetteHttpHandler, Cassette.Aspnet" />
More Information:
This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
Any ideas on what I can do to solve this issue?
The way I solved this error was by going into the IIS Management window and selecting Feature Delegation and setting Read/Write to Handler Mappings and Modules.
Everything is working fine now.