Authorization rejected: User 'Default' does not exist
Thread poster: Peter Zauner

Peter Zauner  Identity Verified
Australia
Local time: 14:41
Member (2010)
German to English
+ ...

Moderator of this forum
Nov 19, 2013

All,

I have just migrated Across from a PC to a laptop and have difficulties with the remote client login from one of my customers.
I get an “Authorization rejected: User 'Default' does not exist.” error whenever I try importing a CWU file.
I have removed the client’s Softkey from the old Across version on the PC.
On my request, the client has provided me with a new Softkey. The client has also provided me with a LoginName (peter.zauner) and a LoginPswd.
What looks odd is the fact that after importing the Softkey, the first of the two lines in the login window (presumably the one for the user name) shows ‘Default’. But it is grey-out and I cannot change it.
The login window for another client shows the username that this client has assigned to me in the top line.
How do I resolve this discrepancy between user names when I have no access to the line?
Who has any suggestions what I could try next?

Thank you.

Peter


 

Åsa Campbell  Identity Verified
Australia
Local time: 14:11
Member
English to Swedish
Incorrect Softkey Nov 20, 2013

Hi Peter,

From my experience it sounds like there is a problem with the softkey, it should have your username instead of 'default', I suggest you check again with your client.

Asa


 

AAV
Local time: 10:41
Wrong .cap file Nov 20, 2013

Most likely your client has provided you wrong softkey file.
To be completely sure, you can open .cap with any text editor and check, which username does it contain (however, I wouldn't suggest change it manually in the file, this won't work).


 

Peter Zauner  Identity Verified
Australia
Local time: 14:41
Member (2010)
German to English
+ ...

Moderator of this forum
TOPIC STARTER
cap file Nov 20, 2013

AAV, Åsa,

many thanks for your suggestions - you were both correct.
I talked to my client and after a few more attempts of setting up the softkey we got it working. So it turned out is was pretty much out of my control while I had been wondering what I was doing wrong.

The two lessons that I have learned are:

1. Migrating Across required new softkeys for each of my clients. I'm pretty sure that is not mentioned in any documentation and is probably not intended. It meant for me that I missed out on a few jobs. If I had know what to expect I might have chosen to migrate at a different time.

2. It looks like creating a Softkey is not always that straightforward. I wonder if there are ways that Across could make the process easier or offer some testing or quality control options.

Peter

[Edited at 2013-11-20 13:02 GMT]


 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Authorization rejected: User 'Default' does not exist

Advanced search






SDL MultiTerm 2019
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2019 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2019 you can automatically create term lists from your existing documentation to save time.

More info »
CafeTran Espresso
You've never met a CAT tool this clever!

Translate faster & easier, using a sophisticated CAT tool built by a translator / developer. Accept jobs from clients who use SDL Trados, MemoQ, Wordfast & major CAT tools. Download and start using CafeTran Espresso -- for free

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search