Closed Bug 1688395 Opened 3 years ago Closed 3 years ago

Microsoft Terminology Service API: Server Error

Categories

(Webtools Graveyard :: Pontoon, defect, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mathjazz, Assigned: mathjazz)

Details

Attachments

(1 file)

We're using Microsoft Terminology Service API in Machinery. In the last couple of days we started noticing that the endpoint (referenced in the Getting Started section of the document linked earlier) often responds with a Server Error (Runtime Error).

It seems to be working OK for a few minutes, then errors again, works again, and so on. I've sent an email to the Language Portal Feedback to inform them of the issue in case they aren't aware yet. What worries me a little bit is that https://www.microsoft.com/en-us/language seems to work as expected.

The thing is that our internal method to call the service also breaks if the server responds with 500. We should fix that, but make sure we still get notified if the service doesn't work as expected.

Error response isn't very helpful:

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>
Assignee: nobody → m
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

(In reply to Matjaz Horvat [:mathjazz] from comment #0)

I've sent an email to the Language Portal Feedback to inform them of the issue in case they aren't aware yet.

They've informed me that they are looking into it.

Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: