TBM6 does not integrate into SDL Trados Studio 2021 Professional

I'm the owner of Trados Studio 2021 Professional license and have recently purchased the Trados Business Manager Essential TBM6.

After uninstalling the Trados Business Manager Lite (which wasn't licensed), I installed TBM6 and restarted the PC. After restart, the TBM region with the corresponding buttons was not present in the Projects view as it should be. Can't figure out the reason why though. I've also tried uninstalling Trados Studio and reinstalling it, but nothing changes.

TBM6 is installed correctly, I think. URL: http://localhost:8733/, Application key xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. The software works correctly, I even managed to import data from Json file.

The Trados Business Manager Connector is not present in the Add-Ins Section under Plugins.

Could it be possible to solve the matter via a remote session?

Thanks in advance and rgds

Stojan Brajikovič

Parents Reply Children
  • Stojan,

    Can you please try this version:

    https://www.ibaccs.com/download/Business_Manager_Connector.zip

    The plugin is unsigned.. but please ignore it. Let's see which error you're getting!

  • Hello, Eugene,

    I signed to my Trados account, but I am unable to access the download page for which you provided the link.

    I get the following message:

    403 - Forbidden: Access is denied.

    You do not have permission to view this directory or page using the credentials that you supplied.

    Pls provide a valid link.

    Thanks

    Stojan

  • Hello,

    thanks, the link is now OK. I downloaded and installed the unsigned plug-in. The following error log file was created:

    Error message:
    An error occurred while sending the request.
    Error message, line 2:
    Unable to connect to the remote server

    Stack trace:
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.Internal.AccessTokenHttpMessageHandler.<SendAsync>d__2.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.Internal.LoggingHttpMessageHandler.<SendAsync>d__2.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.HttpConnection.<NegotiateAsync>d__45.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.HttpConnection.<GetNegotiationResponseAsync>d__52.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.HttpConnection.<SelectAndStartTransport>d__44.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.HttpConnection.<StartAsyncCore>d__41.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.HttpConnection.<StartAsync>d__40.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Http.Connections.Client.HttpConnectionFactory.<ConnectAsync>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at Microsoft.AspNetCore.Http.Connections.Client.HttpConnectionFactory.<ConnectAsync>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.SignalR.Client.HubConnection.<StartAsyncCore>d__58.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.SignalR.Client.HubConnection.<StartAsyncInner>d__50.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.SignalR.Client.HubConnection.<StartAsync>d__49.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    at BaccS_Connector.Ribbon.<Connect>d__4.MoveNext()

    The connection to Trados Studio was not established.

    I set a blank password, just as I did when I installed and activated my TBM6:

    Trados Studio plugin settings window showing fields for Application URL, Tenant, Application key, User name, User password, Project templates path, and Folder to store projects.

    Hope you can find the reason why.

    Thanks and have a nice weekend,

    Stojan

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 10:44 AM (GMT 0) on 4 Mar 2024]
  • Hello, Eugene,

    I tried to uninstall TBM6 completely, but then my Trados Studio 2021 encountered a problem. When I started my instance of Trados Studio, the following message appeared:

    Error dialog box in Trados Studio with a red cross icon, displaying the message 'Unexpected character encountered while parsing value: E. Path '', line 0, position 0.' with an OK button and links to Knowledge Base and Community.

    If I close the dialog, Trados doesn't start, just exits. So, I'm currently unable to use Trados Studio at all.

    How do I solve this? I tried to uninstall and reinstall Trados Studio 2021 SR2 (latest version), but it doesn't solve anything.

    Rgds

    Stojan B.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 10:44 AM (GMT 0) on 4 Mar 2024]
  • Hi Stojan,

    But how could I know why Trados gives an error?? If you remove new TBM Connector plugin version, the same happens?

    Also check that only one TBM Connector is placed in the packages folder (probably, there are different versions under different file names).

  • Hello, Eugene,

    I really don't understand what could've happened. I always had only one instance of TBM connector plugin installed on my system.

    Now this dialog appears:

    Error dialog box with a red 'X' icon indicating 'One or more errors occurred.' with options for 'Knowledge Base' and 'Community' and an 'OK' button.

    I'm unable to start Trados Studio at all. Even after repeating reinstall multiple times.

    What do I do? I would really appreciate some help via remotely accessing my computer. If you have any experience, what do you recommend? Have some urgent projects to complete and really don't know what to do.

    Any help will be welcome.

    Thanks and rgds

    Stojan

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 10:44 AM (GMT 0) on 4 Mar 2024]
  • Hello, Stojan,

    So disappointing when some issue which looks simple, takes so much time to solve.

    I think it's worth to ask help from Studio guys.

    From my perspective, I would do 2 actions:

    1. Open a folder where all plugins are installed, and remove all plugins (don't delete, but move them to some external folder).

    2. In this error dialog, click first button to show error details (or second to export it to a file), and send send here or to Studio support, depending from where the error comes.

    I think that clearing plugins folder will help..

  • Hi, Eugene,

    Yes, I have good news. 

    I had to format my hard drive and reinstall Windows, as it was impossible for me to clean all the mess I created through my futile efforts to make the whole thing work.

    When I reinstalled Trados Studio 2021, the latest version of TBM6 and the TBM connector, everything worked like a charm.

    You needn't bother further with debugging of your connector plugin, as it is obviously working just fine.

    I just want to thank you for all your kindness and readiness to help.

    Kind regards and have a nice day,

    Stojan Brajkovič, freelance translator EN, GER