• State Not Answered
  • Replies 1 reply
  • Subscribers 434 subscribers
  • Views 41 views
  • Users 0 members are here
Options
Related

Hello I have purchased Trados Studio 2024 a week ago and everything was OK, but now, when I open a WorldServer Package it asks me Sign in information. When I change from GroupShare Authentication to Windows Authentication, it asks for a security code, and

Salete Cechin

Hello
I have purchased Trados Studio 2024 a week ago and everything was working just fine.

But now, when I open a WorldServer Package it asks me Sign in information.

Error dialog with red cross icon stating 'Failed to get IDP login providers from server' and an OK button.

Sign in screen with fields for server address, login provider set to GroupShare Authentication, username, password, and a Remember me checkbox.

Then I change from GroupShare Authentication to Windows Authentication:

Sign in screen with fields for server address, login provider set to Windows Authentication, username, password, and a Remember me checkbox.

But Trados asks for a security code, and I have no idea at all where I can get it.

Sign in screen with fields for server address, login provider set to Windows Authentication, and a message stating 'To protect your account a security code is required.'

Does anybody have some clue on this?


Thanks in advance.

Generated Image Alt-Text
[edited by: RWS Community AI at 2:43 PM (GMT 1) on 22 Sep 2025]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    I don’t believe the issue lies with the WorldServer package itself, especially if you have been able to open WSXZ in Studio 2024 before. It’s possible that your WorldServer customer is using a connection to MultiTerm for their Termbases and exported the package using the Multiterm “Link only” option instead of “Content.” If that’s the case, opening the WSXZ package in Studio will prompt you to connect to GroupShare.

    If my assumption is correct, a potential workaround would be to ask your customer to re-export the WSXZ package using the “Content” option for MultiTerm. This should allow you to work with the Termbase locally in Studio without requiring a GroupShare connection. 
    emoji
Reply
  • 0

    I don’t believe the issue lies with the WorldServer package itself, especially if you have been able to open WSXZ in Studio 2024 before. It’s possible that your WorldServer customer is using a connection to MultiTerm for their Termbases and exported the package using the Multiterm “Link only” option instead of “Content.” If that’s the case, opening the WSXZ package in Studio will prompt you to connect to GroupShare.

    If my assumption is correct, a potential workaround would be to ask your customer to re-export the WSXZ package using the “Content” option for MultiTerm. This should allow you to work with the Termbase locally in Studio without requiring a GroupShare connection. 
    emoji
Children
No Data