• State Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1636 views
  • Users 0 members are here
Options
Related

We have CU7 for 2017 SR1. Will there be a similar 2015 update?

Evzen Polenka

Any ETA for releasing similar fixes for Studio 2015?
In particular I'm interested in these:

  • Fix: Fixed theUnexpected exception when completing task 'Analyze Files': Invalid number of analysis bands. error when creating a package from a project with a server-based termbase.
  • Fix: Package creation no longer fails with the Failed to save project 'NP1' to '[TEMPFILE].sdlproj': Object reference not set to an instance of an object error under certain circumstances.

The point is that due to the issues in Studio 2017 SR1 and later it's really not suitable for mission critical projects... so Studio 2015 is still important.

And I'm wondering if the fix for "Invalid number of analysis bands" fixes also this situation: community.sdl.com/.../9169
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    I discussed this with Daniel and moved it into it's own thread as the two issues you mention were specific to Studio 2017 and were both caused by match repair in batch processing with termbases, so in this context would not be the same problem for 2015. Both of these errors could have other root causes though so it would be good to understand some detail behind the problems you are having... even better if you happen to know the Jira numbers for these issues?

    Thank you

    Paul

    Paul Filkin | RWS Group

    ________________________
    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

  • 0 in reply to Paul
    Sorry, I don't have any Jira numbers.
    All I know is that I was not the first one reporting it here in the forum (at least the analysis bands problem), though I can't find the other posts which I vaguely remember maybe from year 2015 or so...
    The failing package creation was reported e.g. here: community.sdl.com/.../34489
    or here: community.sdl.com/.../34778
  • 0 in reply to Evzen Polenka
    ok - I guess you know what I'm going to ask for next as you already mentioned it in the other posts. Can you help me to reproduce this problem you have come across so that I can reproduce it as well? Then I can make sure the development team have something to work on.

    Paul Filkin | RWS Group

    ________________________
    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

  • 0 in reply to Paul

    Well, as I wrote in the original reports about the packages creation problem, there is unfortunately no reliable way to reproduce it... Studio behaves unpredictably, the packages creation could crash at any of them during repeating of the same wizard (when it crashed, I simply clicked the Back button to get one wizard screen back and then immediately Next to start the packages creation again), sometimes taking 2 tries, sometimes 15 tries until it was able to create all packages in one run without fail.
    It looked like it's happening only if "Create new project TM" option was used during the package creation... and it could be related to the fact that the main TMs (from which the project TM was being created) were rather large - from hundreds of MB to almost 2 GB... but again, there were quite differences between individual languages and the packages creation was failing randomly at various languages, so I don't think there was any direct relation.

    The analysis bands problem can be reproduced using the PowerShell function I sent you previously. I also mentioned it in the email (which basically just repeats what was written in the forum posts).

    I also can't guarantee that one year after the original reports everything works (or fails) exactly the same as before. Too many variables in the environment has changed since...
Reply
  • 0 in reply to Paul

    Well, as I wrote in the original reports about the packages creation problem, there is unfortunately no reliable way to reproduce it... Studio behaves unpredictably, the packages creation could crash at any of them during repeating of the same wizard (when it crashed, I simply clicked the Back button to get one wizard screen back and then immediately Next to start the packages creation again), sometimes taking 2 tries, sometimes 15 tries until it was able to create all packages in one run without fail.
    It looked like it's happening only if "Create new project TM" option was used during the package creation... and it could be related to the fact that the main TMs (from which the project TM was being created) were rather large - from hundreds of MB to almost 2 GB... but again, there were quite differences between individual languages and the packages creation was failing randomly at various languages, so I don't think there was any direct relation.

    The analysis bands problem can be reproduced using the PowerShell function I sent you previously. I also mentioned it in the email (which basically just repeats what was written in the forum posts).

    I also can't guarantee that one year after the original reports everything works (or fails) exactly the same as before. Too many variables in the environment has changed since...
Children
No Data