The information provided here is somewhat incomplete, however, given the steps you tried to solve, I am going to make some assumptions:
You installed the plugin and configured your RSE attached to the remote project without creating a team profile for it.
The plugin that you chose to use, with best practice, directly implemented the RSE subsystem without implementing your own service level.
Then you completed your work / updated the version of the remote project / or deleted the link to the remote project.
Note. I can’t say for sure what you did, it can be a lot, but the result is that you have connected a volatile resource to your private profile and this resource has become inaccessible.
How to find out?
RSE subsystems that do not implement their service level domain, required to return null from getServiceType () calls, start the stack trace.
The public team profile must be explicitly created, and the private profile is automatically created. more about this here
The UIPlugin component is one call from the workflow, and the RSE UI Plugin interface for the RSE subsystem to the basic RSE API will make this stack trace signature.
The start delegate is trying to start a configuration that has a source search call for your profile that fails - the end of the stack trace.
To understand what is happening, you need to know that each RSE resource is associated with a profile, and these profiles will contain: 1. Connections - including the properties of the subsystem. 2. Filters, filter pools and links to filter pools 3. Other profile data
Profiles can be active or inactive. The remote system explorer displays all connections from all active profiles and, within the connection, allows you to refer to filter pools from any active profile.
However, there is one key point your personal profile cannot be deleted or made inactive.
This means that if you have not created a Team profile that can be disabled. And your RSE plugin does not implement its own level of service for a graceful rejection. And this resource will become unavailable, you will not be able to run the configuration profile - your problem.
So don’t worry about reinstalling the plugin that you can make (or find the best one), just make sure you attach any remote resources to your Team Profile. You can then use the Team view to control which profiles appear in your workspace, making the various profiles active or inactive.
Learn more about this in the RSE Developer Guide.
EDIT: Follow up
Unfortunately, it seems that this is actually the same error that you encountered earlier in another call chain. When you set up the command profile, you did not remove / delete all the components of the RSE plugin. Thus, UI Decorator tried to build for you the look of your remote resource and got a null pointer
This is confirmed by the fact that you could not "see" the RSE plugin in your eclipse opening. At least the eclipse behaves as if part of it is still there, and I suspect it was.
You basically have two options for solving this problem, and they are not very happy.
If you don’t have any serious value blocked in your Eclipse IDE that you cannot get (which you don’t need), the easiest would be to remove eclipse and all the files associated with it, reinstall the clean eclipse, load the RSE, configure Team profile (two will be better), not allowing him to specify the identifier from your personal profile by default, then reconnect the remote system.
If you REALLY feel your hands getting dirty and fixing it through an existing eclipse installation, you can directly write the code to the RSE FYI registry : (NOT trivial) and you cannot run it in Eclipse when you do this. The registry allows you to get and manage almost all your configuration settings, subtypes and profile information.
If I were in a hurry, I would just do 1, If you want to spend time and learn more about RSE and are not afraid to break it, I would do 2.
One more thing. There is a “theoretical” way to get and change / reset your personal profile in the ISystemProfile RSE interface, there are two methods that CAN do this, but so that you know even the best eclipse gurus that I know, I don’t know if this is possible or will be work, however here is the info:
isDefaultPrivate to find a unique developer profile (returns boolean), and setDefaultPrivate can let you inactivate a unique developer profile and set another.
Why can I say because even eclipse API documents end this statement with a question mark ... see here