Hello, Stojan,

Thanks for the question. Few days I don't have time for remote sessions, but maybe can help anyway.

First of all, can you please tell us versions you are using (both Studio and TBM Connector)?

Then, try to open this folder:

C:\Users\YOUR_USER\AppData\Roaming\SDL\Sdl Trados Studio\15\Plugins\Packages

In my case, I have this:

Do you have Business_Manager_Connector.sdlplugin file there? If not, probably you're using the wrong version? For example, for Studio 2019. Or maybe you have 2 connector plugin files there, but with different names?

I just tested with 2 Studio 2021 versions, and it worked:

- 2021 SR2 - 16.2.8.9097

- 2021 SR2 - 16.2.9.9198

Hope some of provided info will be helpful.. Let us know please )

Hello, Eugene,

Thanks for your prompt reply.

Upon checking the contents of the folder C:\Users\YOUR_USER\AppData\Roaming\SDL\Sdl Trados Studio\15\Plugins\Packages, I didn’t find any files at all in that folder. It is completely empty.

The registered and activated version of my Trados Studio 2021 Professional is Trados Studio 2021 SR2 - 16.2.9.9198

I don’t know where to look up the version of my TBM6. I downloaded it from the App Store (Trados Business Manager Connector), activated it with the activation number I received to my account, and the version no. isn’t listed there. I even don’t know where the file has been saved on my PC if it was saved at all.

I installed the TBM6 in the default Documents folder, not in the C:\Program Files (x86) folder.

However, in my Documents folder, there are 2 folders:

SDL Trados Business Manager with the TradosDatabase sub-folder, containing 4 files:

               bmanager_lite.sdf

               errorLog.txt

               tbmdb_20220117.sqlite

               tbmdb_20220118.sqlite

Trados Business Manager v6 where the TBM6 is installed.

Perhaps you could tell me, where can I manually download the correct TBM6 file to put in in my folder C:\Users\YOUR_USER\AppData\Roaming\SDL\Sdl Trados Studio\15\Plugins\Packages?

I’m quite discouraged, since I payed for the application (TBM6) and can’t fully exploit it (integrate it into Trados).

Please reply soon.

Thanks and rgds

Stojan Brajkovič

Hello, Eugene,

thanks for your efforts.

I'm awaiting the new version.

Stojan Brajkovič

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

Incorrect link. Fixed.

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:

Hope you can find the reason why.

Thanks and have a nice weekend,

Stojan

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:

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.

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:

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

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..

Hello, Stojan,

Wanted to ask how things are going? Any success?

Hello, Stojan,

Wanted to ask how things are going? Any success?

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

Wow!

Fantastic! Anyway, curious why it didn't work. As we can't recommend to re-install Windows when other user will get same issue ))