Community in read only mode June 18 & 19
This community will be set in READ ONLY mode for a while on Tuesday June 18 into Wednesday June 19 while we import content and users from our Micro Focus Forums community site. MORE INFORMATION

Are there any known behaviours or issues within Enterprise Analyzer, that would result in damage, corruption or deletion of the RWP (workspace) file?

Are there any known behaviours or issues within Enterprise Analyzer, that would result in damage, corruption or deletion of the RWP (workspace) file?

Problem :

Are there any known behaviours or issues within Enterprise Analyzer, that would result in damage, corruption or deletion of the RWP (workspace) file?

Resolution :

As at the last update date of this article...

There are no behaviours within Enterprise Analyzer that results in .RWP (workspace) file deletion, corruption or damage.

There is nothing known that will cause damage or delete the RWP (workspace) file "automatically".

The RWP (workspace) file can be CHANGED if the user chooses to "Build New Connection" or "Refresh workspace path" from the EA Administrator.

The RWP (workspace) file can be DELETED if the user chooses to "Delete Workspace" from the EA Administrator.

These operations can also be run in batch.

Other than this, the only things that might happen include...

1. User deletes the RWP (workspace) file manually.

2. The Repository (Table "Workspacesettings") can be manually changed putting the Repository out of sync with the RWP (workspace) file. 

3. The RWP (workspace) file can be manually changed putting the Repository out of sync with the RWP (workspace) file.

4. User may create a new workspace using an existing repository and RWP (workspace) file name, overwriting the existing one (this may look like a corruption or damage.)

5.  If the repository is housed on a separate machine to Enterprise Analyzer, User or customer IT department, may change the machine name of a machine housing the workspace Repository, which results in loss of communication between machines. (this may look like a corruption or damage.)

6. If the repository is housed on a separate machine to Enterprise Analyzer, there may be a general loss of communication between machines (this may look like a corruption or damage.).

 

Incident# 2655180

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-12-11 11:51
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.