In this case it would be best to report an incident via SupportLine so the issue can be looked at in more detail. In the new incident please provide the Silk Test version & build number, together with a sample script export and files that would allow us to reproduce the issue. Thanks, John.
I face the same issue as well with a driver script i am using (using Silktest 13).
It had always worked until recently.
If i run each script individually it runs. If I run the driver script it runs until some point and then I receive a similar message.
The only change that happened in my workstation before it started to appear is that I was using an access db and then I switched to an sql one.
However it happens even if I use the access one.
As my colleague John has stated above, if you are encountering specific errors that require reproduction and investigation then it is best that you open a new support incident (providing a reproducible example if possible). This can be done from the online portal:
We will of course update the forum with our findings once completed.