Hello @lukasz.druczak

It seems there is a connection problem between your environment and the RDP Gateway. I strongly suggest you contact the RDP support team to investigate these errors (Gateway Time-Out, internal server error, and Session quota reached) that might relate to the server side. You can submit a support ticket to the RDP support team via https://myaccount.lseg.com/en/productsupport website.

Hi @lukasz.druczak

Are you by chance running another instance of your application using the same credentials? The message is typically associated when another application effectively "steals" your session/access thus invalidating your current session/access. Your credentials are only entitled to a single session.

Hi @nick.zincone , there are times that we need to use the same credentials for non-prod environment, so that would match the times when we see these errors. Can you let us know what we can do about it? Is there any setup that we could use for our account?

Hi @lukasz.druczak

What you can do is try using the email account ID that you would normally use on the API Playgound. This ID was provided to you when you signed up and should be able to use to periodically test in the non-prod environment. Another option is to reach out to you LSEG account manager - they may be able to arrange for an ID.

Hi @nick.zincone, thank you, it worked like a charm.

Could you please tell what does it mean the Playground account can be used periodically? Does it have any limitations compared to the other ID? Would our subscription to news stop working when using the playground account?

Hi @lukasz.druczak

Question: How do I generate app key for our DEV_ playground account and for machine IDs we were given? Should I generate separate app key for each of the IDs?

Answer:

You can use a single app-key with multiple Machine-IDs. The session quota is based on the Machine-ID only.

However, if you need to create new app-key(s), you can do it by clicking the "AppKey Generator" Link on the top left corner of the API Playground page.

Then on the AppKey Generator website, input your app-key name, and check a "EDP API" box for the RDP API as follows:

Hi @wasin.w , thank you.

Do I use the DEV_ playground account to generate key for the Machine IDs? Just wondering how are the DEV_ account and the Machine IDs connected?

hi @wasin.w

We have been using different Machine IDs with shared App Key for our service over the weekend. We have used the IDs (credentials) per environment and not used them anywhere else, so we do not steal sessions and do not get "Session quota reached."

However, we have hit the errors (for let's say ID = 1 and ID = 2) at night on 7th of July at around the same time, just after midnight and once for one ID = 1 on the 8th of July. They were only 3 instances of these errors since Friday, but still they occurred and we have not used the credentials elsewhere.

Can you advise what might have happened? Was there any maintenance or sth?

Hello @lukasz.druczak

I admit that I am not the Data Library - .NET expert, but this error message should not happen if you are using multiple Machine-IDs.

Did you set the TakeSignonControl parameter to True when initialize a session?

var session = PlatformSession.Definition().AppKey(Credentials.AppKey)
                .OAuthGrantType(new GrantPassword().UserName(Credentials.RDPUser)
                .Password(Credentials.RDPPassword))
                .TakeSignonControl(true)
                .GetSession().OnState((state, msg, s) => Console.WriteLine($"State: {state}. {msg}"))
                .OnEvent((eventCode, msg, s) => Console.WriteLine($"Event: {eventCode}. {msg}"));

Example: 1.1 - PlatformSession.cs

@nick.zincone Do you have other ideas?