Hi,

 The stack trace (available from the little button on the left) gives details that may help identify the cause of the problem.

 We often have the same problem, and in our cases the underlying internal error message (from the stack trace) is either:

• "Root element is missing." - which usually means that the sdlproj file has become corrupted, or
• "The process cannot access the file 'xxxxx.sdlproj' because it is being used by another process.", for which we are still trying to figure out the cause.

  Besides the fact that our network is a bit unstable at times, does SDL have any other explanations?

Attila

Hi,

 The stack trace (available from the little button on the left) gives details that may help identify the cause of the problem.

 We often have the same problem, and in our cases the underlying internal error message (from the stack trace) is either:

• "Root element is missing." - which usually means that the sdlproj file has become corrupted, or
• "The process cannot access the file 'xxxxx.sdlproj' because it is being used by another process.", for which we are still trying to figure out the cause.

  Besides the fact that our network is a bit unstable at times, does SDL have any other explanations?

Attila

Hi Attila Grozli-Nagy 

Actually, both these error messages can be triggered by many eventualities.

For example "Root element is missing" often indicates that one of many possible settings files or the path to it has become corrupted. As you say, the Stack Trace is the place you can hopefully find this though you can also search for a solution based on whatever function triggered the error.

So, if you search in the SDL Support Knowledge base for the specific error message, you'll get a list of where this has occurred and solutions have been found:

Root element is missing

As a random example, the spellchecker can trigger the root element error and you can navigate to the page on resetting it:

Spellchecker reset

So, this is one of many errors that can be triggered by various components of the software rather than one specific aspect of the software. 

Following the procedures described in the following shortcut can resolve the above and other issues in Studio:

Repairing your installation of SDL Trados Studio

Likewise, you can reset MultiTerm:

MultiTerm 2017 root element missing

With known issues, you can often find resolution by searching in the SDL Support Knowledge pages.

So, we can also search there for 'The process cannot access the file because it is being used by another process':

Process cannot access file ... used by another process

The results can help narrow down how to resolve the issue - or as I said above, you can search 'Knowledge' on the function that triggered the error.

So, the answer to your question "Does SDL have any other explanations?" is "Yes, many" and the Knowledge pages are the place to start looking.

The starting point for this is to click the 'Knowledge' button on the SDL Support Community home page:

CommunityHome

You can reach a whole host of other useful information from the above page so it's a good one to add to your Favourites toolbar.

Hope this helps!

All the best,

Ali