Translate
Hi,
whenever I try to connect to Memsource via the plugin using the memsource credentials I got from my client, I get the following error:
Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
regards,
Pascal
Hi,
whenever I try to connect to Memsource via the plugin using the memsource credentials I got from my client, I get the following error:
Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
regards,
Pascal
What version of Studio do we need to test this in?
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Trados Studio 2021 Professional Network
I don't see that error... but I do get an error 403. I have a feeling they changed their API and we need to update this plugin. I also don't think it can be used much or we would surely have seen complaints if this is the response in general. Were you just testing or do you have a genuine need to use this? Helps me prioritise the effort.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I don't see that error... but I do get an error 403. I have a feeling they changed their API and we need to update this plugin. I also don't think it can be used much or we would surely have seen complaints if this is the response in general. Were you just testing or do you have a genuine need to use this? Helps me prioritise the effort.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
In fact I just searched my emails and see this from Dec 2019...
=========================================
We understand that you are still using the Legacy Memsource API for your integration(s).
In the coming months, we will be deprecating our Legacy API and it will no longer be supported. We advise all our users to migrate to our new REST API as soon as possible to avoid disruption your Memsource experience.
Why are we deprecating the Memsource Legacy API?
We want to ensure that all our users are benefitting from our REST API. Compared to the Legacy API, Memsource's REST API has faster response times, is more user-friendly, and is better documented.
How difficult will the migration be?
We have mapped the top-used Legacy API calls to our REST API calls. The mapping is included as part of the Migration Guide here. It also includes technical advice from our Developers who have already carried out the migration. Also, here is a link to a detailed help center article about using our REST APIs.
When will the deprecation happen?
The Legacy API deprecation is due to take place in September 2020. After this point, the Memsource Legacy API will no longer be supported. Only the Memsource REST API will be supported.
Not sure where to start? Check our complete Migration Guide - it includes the Legacy API to REST API mapping document and more general information about the migration. Please let us know if you have any further questions regarding your migration - don’t hesitate to get in touch.
Also, if you do not directly work with the Memsource API, please forward this email and the attachment to the most relevant person within your organization.
=========================================
I'll plan the work in, but it probably won't be very soon.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Yes, I have an increasing need to use it as we get more and more larger memsource projects from some clients. Right now I translate them in Trados but have the Desktop version of memsource open on another screen to check the TM and terminology.
ok - we have this logged as SDLCOM-2287 and will get to it when we can.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I have the same need and the same situation. I cannot log in to Memsource via Trados although the credentials are right. Trados is superior to Memsource (producitivity features, verification, everything), so it is very important to be able to use Trados to translate Memsource jobs.
We are working on this at the moment. The API from memsource changed so the existing plugin will not work. I think we should have something ready soon so you'll see the notification in Studio once we release it.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Just to make sure: has there been a release of a new version yet? I thought I saw an update in Trados but I still cannot connect due to the same error popping up.
Hello Pascal Zotto ,
We recently released (13th Nov) an updated version (3.0.1.0) for Studio 2021- so you should have received notification already.
Lydia Simplicio | RWS Group
_______
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi ,
Ok, then I remembered correctly that Studio installed it. For some reason it does still not work. I tried yesterday, even after uninstalling and reinstalling the plugin, to log in for a small job but got the same error. I will have to wait for the next job though before I can test again and send the error code log.
BTW, did you check my comments under the issue about Protect Data?
Hi Pascal Zotto ,
Please let us know when you get a new project- maybe we can test this at the same time.
With regards to the Protect Data, we aren't able to reproduce or replicate which is making it hard for us to investigate.
If this is reported by others, then we might be able to make comparisons and see what exactly and where the issue lies.
Lydia Simplicio | RWS Group
_______
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi ,
I still get the error: Unexpected character encountered while parsing value: <.Path '', line 0, position 0.