After discussing the issue with you and accessing the affected machine, it seems that the error was due to contract server being down for a short amount of time. That is because I was able to run attach on the affected machine in a later time and it worked as expected.
However, we understand that this error message is not ideal. We already have code that will improve that error message and it will be delivered on Pro client v32.
Finally, if this type of error keeps happening on your side, let us know and we can then better investigate this issue.
Hi Patricia Domingues,
After discussing the issue with you and accessing the affected machine, it seems that the error was due to contract server being down for a short amount of time. That is because I was able to run attach on the affected machine in a later time and it worked as expected.
However, we understand that this error message is not ideal. We already have code that will improve that error message and it will be delivered on Pro client v32.
Finally, if this type of error keeps happening on your side, let us know and we can then better investigate this issue.