Are you familiar with nsradmin? - it should be able to tell you ...

  - start nsradmin

  - then

. type: nsr task

p

  - now you should be able to see all tasks with their details.

  - use 'q' to quit

  - You can also use the 'visual' mode.

Thank you very much for the reply.

Unfortunately:

nsradmin> . type:nsr task

Current query set

nsradmin> p

No resources found for query:

                        type: nsr task;

nsradmin>

Interesting ... by default there are at least 2 defined.

Another method is to find out the resource file which has appropriate references. Here is the method for NW/Windows:

E:\>findstr /I /S /C:"type: nsr device" E:\nsr\res\nsrdb\*.*

E:\nsr\res\nsrdb\01\a100581b0000000013b6d25bc3d646d7:type: NSR device;

E:\>

Then open the file(s) and continue from here.

If you found the resource you want to delete ...

  -  shutdown NW

  -  rename the file

  -  restart NW

Seems like this system is just going to be a pain.

I shut down the Networker services, using "net stop nsrexecd /y", found the only two files that referenced the IP address of that vCenter, renamed them to xxxxx.bak, and started the services back up.

No change.

the vCenter is still there, and the error remains the same, "This hypervisor is still referenced by task x.x.x.200"

So you are dealing with a Windows system.

Did you ever check the resource files?

It is not a good idea to just rename them right away. As I mentioned: open the file...

It might also be that the system is resolved by the name or whatever. So you might have to run multiple searches to find the right resource.

I just showed you the general guideline.

Yes. I found the files that referenced the IP address of the vCenter I am trying to remove. After confirming that they were the only two files referencing it, I shut down NW and renamed the files, per your suggestion.

I don't see any references to the old vCenter's hostname in any of the files, nor is it in the hosts file. I'm kind of at a loss. I'll have to contact EMC directly, I guess.

Thank you for your help.

I think I finally found the problem. It appears there were two vProxy's pointed at the now non-existant vCenter. I removed those and finally banished the vCenter.