This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Authorization rejected: User 'Default' does not exist
Initiator des Themas: Peter Zauner
Peter Zauner Australien Local time: 05:27 Mitglied (2010) Deutsch > Englisch + ...
Moderator dieses Forums
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. ... See more
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?
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Åsa Campbell Australien Local time: 04:57 Mitglied Englisch > Schwedisch
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
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
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).
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Peter Zauner Australien Local time: 05:27 Mitglied (2010) Deutsch > Englisch + ...
Moderator dieses Forums
THEMENSTARTER
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 no... See more
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.
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free