You are currently working on UAT 

"illegal parameter"

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

  • All just healthy discussion, I hope... ;-)
    I also have many other things to do (especially in the last months), but I just tend to "complete" things, i.e. with all connected stuff which makes sense, without any loose ends. Because otherwise the whole thing then may be (almost) useless. So I tend to expect the same from others...
    Regarding the users engagement, I believe we discussed this in the past - the point is that users "lose the faith" if they don't get some reasonable portion of what they are begging for, and in a reasonable timeframe. And that's where the "Rundordner feeling" comes from - there is a ton of ideas around for quite some time already, but implementation of basically none of the important ones is in sight (except for a few ones which were basically implemented already at the time they've been requested).
  • Well, I tried this and it did absolutely nothing to help the situation. I don't think it is anything wrong I'm doing- I'm a very experienced translator working with Studio. I believe there is a bug or something which probably occurred when I implemented the last update. I believe I deserve support rather than referring me to fix the problem myself or purchase a ridiculously expensive support package...
  • Thanks Paul,

    I wasn't sure whether the Ideas site was actively monitored, quickly reviewed once in a while, or whether, say, only Ideas with more than 10 votes were checked ;-)

    By the way, I was thinking of "unique" as specific to an incident, so that if the same error occurred twice, then a different error number would be displayed to the user each time.

    Although the "generic error" might be the same for many incidents, other information collected from the error stack or about the user's Studio settings or system configuration might also be helpful for a specific incident.

    Using a unique number also leaves the door open for a more flexible data collection system in the future.

    With that said, I really have no idea whether Evzen is correct when he says SDL should have designed the system this way in the first place. I'm not in the field anymore.

    Even though I know other programs collect data and display generic error codes, I am not aware of any programs that give the user a unique number that can link their particular incident to the specific database record that was collected for that incident -- while maintaining user anonymity in the database itself.

    If other programs are moving in the same direction, then good. That will give SDL more of an incentive to do the same, which means the days of asking users to send error stacks will soon be over :-)

    Best regards,
    Bruce Campbell
    ASAP Language Services

  • Hi Halli,

    Sorry to "highjack" your thread! I will shut up now :-)

    Best regards, Bruce
  • Bruce Campbell said:
    Even though I know other programs collect data and display generic error codes, I am not aware of any programs that give the user a unique number that can link their particular incident to the specific database record that was collected for that incident

    Mozilla products - see http://kb.mozillazine.org/Breakpad

    And here you can see the stats of submitted reports: https://crash-stats.mozilla.com/

  • Bruce Campbell said:
    If other programs are moving in the same direction, then good. That will give SDL more of an incentive to do the same, which means the days of asking users to send error stacks will soon be over :-)

    Probably not as simple as that.  You'd be assuming that everyone works online all the time, and that they agreed to participate in the feedback program and always send this data back.  Neither are a given and we still have to support our users whether they agree to this or not.

    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

  • I agree. It's not so simple :-)

    And Evzen is right. Now that he mentions it, I have seen things similar to the open-source Mozilla Crash Reporter that he referred to.

    But I have a suspicion it would be rated as "pie-in-the-sky" based on the amount of work involved.

    Something extremely simple like displaying a number before or after data is collected for users who are participating in the feedback program anyway might be cheap enough to be worthwhile even if it doesn't handle all cases -- assuming enough users are signing up for the program.

    And if users started quoting those numbers in the Community, it might be good advertising and convince other users to participate.

    Anyway, it's not a big deal, just an idea that occurred to me when I saw the umpteenth request for an error stack.
  • Hi,
    I'm still not able to fix this problem, and am clueless about computers. There is no "error stack" - only the dialog box I posted, and as I posted- this error doesn't even show on the error list. However, as I've been using Studio for so long (2014, 2015, 2017) I'm absolutely sure I'm not doing anything wrong and the issue started after downloading the latest update. I need help, and I think this help should be provided, other than by sending me to fix it myself or purchase a support package for a problem that is caused by the program itself and not due to using the program incorrectly or doing something that might cause this problem.
    If anyone knows how to contact the people that provide this help, please refer me to them.
    Thanks!!!
  • Hi ,

    As this happened after installing I think you could get free help ... 

    With licensing or installation issues that are stopping you working normally, you can get free help from SDL Support really quickly here:
     
    gateway.sdl.com/liveagentlicensing

    You have two options:

    1. Submit a case using a webform
    2. Use live chat to request a licence reset
     
    Click 'Submit a case' then fill in all the details required on the form and submit it. There is a box to select whether it is an installation or licensing problem. They will help you free of charge.
     
    Make sure your email address is correct or nobody will be able to contact you. You will receive an auto-reply immediately then they will contact you ASAP, usually within 24 hours.
     
    All the best,
    Alison