Connectivity Problem using LSEG.Data from C# to LSEG Workspace Desktop

tony10

We have a C# application that is using the LSEG.Data and LSED.DataContent (version 2.0.0.0, image version v4.0.30319) libraries. We have two problems at the moment: 1. Cannot connect to the LSEG Workspace Desktop, and 2. Error starting the LSEG Workspace Desktop if it is not running.

1. LSEG.Data.Core.ISession session = DesktopSession.Definition().GetSession();

By examining the RDPLog_<n>.log file/s we can see that sometimes there is connection:

Host: localhost:9000/api/rdp/streaming/pricing/v1/WebSocket (Path: [])

and sometimes there is not:

Host: localhost:/api/rdp/streaming/pricing/v1/WebSocket (Path: [])

Can anyone explain why the port 9000 is sometimes missing when the URL is constructed?

2. When our application determines that the LSEG Workspace Desktop (LWD) application is not running, it attempts to start the LWD using System.Diagnostics.Process.Start(…). Using this method, the following "unexpected error" pops up:

Can anyone advise how to prevent this pop-up?

Thanks

Tony

—-oooOOOooo—-

Jirapongse

@tony10

Thank you for reaching out to us.

Ensure that the LSEG Workspace desktop application is running properly before using the LSEG Data Library.

It may not be recommended to start the LSEG Workspace programmatically, as the application is designed primarily for desktop users rather than automated processes. Instead, consider connecting directly to the LSEG Data Platform.

However, I can start the LSEG Workspace by using the following code.

var path = Environment.GetEnvironmentVariable("LOCALAPPDATA");

var proc = Process.Start(path+"\\Refinitiv\\Refinitiv Workspace\\RefinitivWorkspace.exe");

tony10

Thank you for that answer. but:

1. Although the LSEG Workspace Desktop launches into the login/startup screen, even with your solution, we still get the "unexpected error" popup with the message "..broken pipe..". Do you not think that this type of error should be handled internally by the LSEG Workspace Desktop application itself?
2. Even if the application is designed primarily for desktop users, it still has to operate as a servant to other applications, otherwise why was the Desktop API created?
3. Most of our use for the Desktop is for backup and testing purposes.
4. Furthermore, the Desktop does an automatic logout once a week (Sunday?) and if we have an application connected, we need to do auto-restart (e.g. kill process, start process), which makes it impossible to have an un-attended backup system.

Jirapongse

Yes, please contact the Workspace support team via the LSEG Support to investigate this issue.