This method made several problems before. And everytimes we found a workaround 
inside the office. But in general this function is implemented right inside the test 
tool itself.

Normaly an office shutdown must be made asynchronous. Because a terminated 
office cant provide any information about the success of this operation.

But in such asnychronous use case the test tool lib "sts" itself hinder the office on 
shutdown. Because it increased the dispatch level of the application so it thinks 
that there exists some external requests running inside the office. E.g. a running 
command line request.

So there was a try to implement FileExit() synchron. But then it happens that some 
global resources was already removed but references and used later (because the 
synchronous call stack must be finished before the office process was realy 
removed from memory!).

The test tool must find a way to execute FileExit() asynchronous in a manner "fire 
and forget" and poll from outside(!) to find out if the operation was successfully.

see #61403# too