Error: 0x800700aa the requested resource is in use, When Copy, or Move

Open Computer manager and check if the file is open from a remote connection, you can then close the sessions. If it's an executable, then run task manager and "end task" the executable.

A little trick I used to use for clean virus files was to remove all permissions from the file and then delete.

Right-click the file, click properties, under the security tab, remove everybody including system wih the exception of your own account.

Reboot the server and then delete the file.

I have checked the Computer Manager and no one is using the files I need to move.  They still will not let me move them.

As you are talking about two file shares...
first at all make sure, the share permissions as well as the NTFS permissions on the files are there. As you want to move, you need delete on the source and write on the target.

If permissions are out of scope (i.e. you can move other files with the exception of a few ones)...
Some reasons, why some files may be blocked:
- A user has opened a file
- The file is open or blocked by a program or service
  i.e virus scan, backup, index service, DFS etc.
- the file is write protected (check the aatibutes)
- a program has accessed the file, but does not release it for any reasons
  (means the program could not process the file in a correct way)
- a protection software blocked the file as regognized as suspicious.
- for pictures also the thumbnail database may be a problem

Keep in mind, that this may happen on every machine, means the service or reason is not on the source directory.

Other reasons may be some struggled data.
- Check the permissions and the ownership of the file
  (sometimes it helps to take ownership)
- Check the name, sometimes such cases happens if the name has special characters
  (try to rename the file)

This is more a common list, I have such cases regularly and sometimes just waiting helps, in other cases I renamend the files and it worked after that.

If you use DFS, it is just possible, that the DFS service hasn't completely snyced the file.

If it doesn't work at all, you may try to move the file from the physical machines source directory to the target share.

I am wondering if this has to do with Backup Exec.  Yes it is to file shares that I want to relocated, I already removed most of the permissions to only myself.  

Could backup exec be causing this?  If so what do I need to do just disable the services during the move?

Usually backup exec touches the files during backup - as long as it works correctly.
But BE uses usually also an agent on the client. A common reason for such issues is, that an application starts to run and after it it doesn't release all the files correctly.
If you have BE in your mind, you can either restart the machine, where it is installed or to stop the BE services as well as agents on other machines.
Maybe the agents are enough.
At least this gives you a hint, if BE is involved.

Even possible, that this is a work together, sometimes deadlock happens, if virus scanners are involved. Have the imagination, that BE touches a lot of files in a short time, what a virus scanner can force to try to touch them too.

Do you have BE realted errors somewhere?

At the end, to be quite sure, which application blocks the files, you may just try to shutdown other services too.

Or there are two tools from sysinternals...
Process Explorer and Process Monitor
Both tools can give you a deep insight, what is going on.
Process monitor can catch everything from a machine, any access, so you have to filter the result down to what you want to see, i.e. a path or files name.

Another option maybe to enable auditing in the security advanced settings. This writes into the security log, whenever a file is accesses.

I have rebooted the machine several times.

All I can think of is BE. But I do not think that is solving my issues either,.

Oh, there may be another issue, because you use Win2003.
The platform 5 (2003 / XP) has a default behaviour, that it keeps loaded DLLs in memory, even if they are relased by the application. The effect of this can be strange as this may also result into a blocking of files if there where touched by this DLL.

Have a look here:
http://www.techzonez.com/forums/showthread.php/4720-Windows-2003-Performance-Tweaks
--> Unloading DLLs
And also there is the instruction to diable indexing....

Unloading DLL is not directly the reason, but can have a secondary effect, if the application doesn't work 100% correctly. If the DLL is release, the files should be released too.
Nevertheless, if there is a (faulty) reference left over, the setting has no effect.  

Another idea would be to investigate, which files are blocked. It is possible that they have a writeprotect or system attibute (check with attrib from the command line).
Can you see someing in common with these files? Same type or something, or just sometimes this, sometimes that?

But as I said, to dig really into the deep, you may have to use the sysinternal tools to see, where is the reference to the blocked files .

Verified with MS