You are currently working on UAT
Hi, I've been using Studio forever- for the past two years (or so) the 2017 version.
Suddenly, for no apparent reason, at some point, usually towards the end of the document, when typing I get an error message "illegal parameter", following which everything freezes and I can't do anything but save the document and close the software. Has this ever happened to anyone? How can this be resolved?
Thanks, Halli
Hello Halli Rosenbach ,
Unfortunately this error is not providing very much information.
Could you please post the full error stack-
Also, it might help if you could let us know what exactly are you doing when the error message appears.
Is this happening to all files?- or to just one in particular?
Are you translating in 'Single file' mode or a 'project'
Oana Nagy | QA Engineer | RWS Group
Hi, as I feared, the error occurred again-see the message which unfortunately is in Hebrew...but means "illegal parameter". As you can see the message does not appear in the messages...PLEASE, HELP...
Oana Nagy | QA Engineer | RWS Group
Hi Steven,
Paul mentioned somewhere that Studio 2019 sends error information to SDL whenever it encounters an error (if the user has enrolled in a Studio "improvement program").
If the error stack is included in this information, then SDL might be able to eliminate the step where you or another SDL employee asks the user to send the error stack.
Studio might, for example, query SDL for a unique error number before it sends the error information and then display this error number to the user.
If this change were made to Studio, then the user would just have to provide the unique error number in order for you or anyone else at SDL to access all of the information in your database for that particular error.
Just an idea that might make chasing down errors easier for everyone involved, especially the user :-)
Best regards,
Bruce Campbell
ASAP Language Services
Paul Filkin | RWS
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 Paul,
Done: community.sdl.com/.../display-unique-error-number-to-user-for-troubleshooting
Although I have more faith in you than I do in the "Ideas" site, which might be a round filing cabinet for all I know ...
Best regards,
Bruce Campbell
ASAP Language Services
Hmmm, to be honest, I don't quite get why should USERS come up with such ideas...
This is clearly an SDL's software architect's role to set this up... and in fact I would expect this to be already set up, right together with implementing the background reporting. Why would anyone NOT implement it in such way?
Bruce Campbell said:in the "Ideas" site, which might be a round filing cabinet for all I know ...
Exactly my feelings about the Ideas...
Most of the ideas are apparently completely out of scope of the community developers (in other words, the reported bugs, shortcomings and feature improvements must be fixed/implemented by the core team, not the community developers), i.e. it is effectively a "Rundordner"...
Bruce Campbell said:in the "Ideas" site, which might be a round filing cabinet for all I know ...
Exactly my feelings about the Ideas...
Most of the ideas are apparently completely out of scope of the community developers (in other words, the reported bugs, shortcomings and feature improvements must be fixed/implemented by the core team, not the community developers), i.e. it is effectively a "Rundordner"...
Translate
