Error: The operation could not be completed

[OP1]

When trying to build my solution, I get this error message (right away) in the output window:

"ERROR: The operation could not be completed."

There is no other error message, nor any indication of where this error might come from.Does anyone have an idea of what could be causing this? I am using IVF 10 and VS2005.

Thanks,

Olivier

[Steven_L_Intel1]

Another user who had this problem resolved it by exiting and restarting Visual Studio. It is not a compiler error message.

[IanH]

Quoting - opmkl

"ERROR: The operation could not be completed."

I get this occasionally. After restarting VS 2005 it will go away for a bit, but at some variable time later (minutes to hours to days) it will return. I've not worked out what causes it, but I'm suspicious that it is caused by VS (or some component thereof) accessing the same file by two different paths (to simplify access I have a subst drive to a "My Documents"). But that's just speculation. I'm not sure whether the Fortran VS integration is involved.

IanH

[Steven_L_Intel1]

I did some more web-searching and found the following suggestions (non-Fortran users have been seeing this).

1. Remove and re-add the project to the solution.
2. Open a Fortran build environment command prompt and type "devenv /resetskippings

Personally, I doubt the second one will help here.

[OP1]

Quoting - Steve Lionel (Intel)

I did some more web-searching and found the following suggestions (non-Fortran users have been seeing this).

1. Remove and re-add the project to the solution.
2. Open a Fortran build environment command prompt and type "devenv /resetskippings

Personally, I doubt the second one will help here.

Thank you - I followed the solutions proposed in the previous posts and managed to get rid of this issue. I had to rebuild my entire solution after cleaning all files in the Debug and Release folders for each of my projects. This is a lengthy process and I hope it won't happen again too soon. VS was incapable of doing any compile or build operation when the problem occured.

Olivier

[Les_Neilson]

I think thatall of the cases where I have seen this messagein our buildsit has been due to either mt.exe or rc.exefailing (I forget which one- maybe either one)

In any case just doing a rebuild has fixed the problem - at least for me.

Les