Configuring a Workspace in Enterprise View does not change the Workspace
Within Enterprise View (EV), from the configuration menu, there is the workspaces option that allows you to change the Workspace that is being viewed. EV does not always change to the new workspace.
Why is this happening and how can this be avoided?
When you select the change option to enter the location of the new Workspace repository file (rwp file) that you want to use, EV will perform validation on the file when you use/press the save button. As part of the save process, EV will restart and present you with the login screen. It is only once that login has been completed will it be clear if the new workspace file is considered valid. If the validation fails, then EV will not change the rwp file it is using.
The validation that EV performs are:
- Ensure that EV can access the database that holds the metrics for the workspace.
- Ensure that EV was the correct permissions to the workspace directory.
So to cover these in more detail:
Ensure that EV can access the database that holds the metrics for the workspace
The first task that EV does is to extract the database information from the rwp file and attempts to connect to the database that supports the workspace. This database holds all the configuration options for EV and all the metrics, surveys etc that EV will report on. If EV cannot connect to the database, or access the tables within that database then EV will not use the new rwp file.
Ensure that EV was the correct permissions to the workspace directory
As part of the configuration information within workspace is the directory that holds the source files that are within the workspace. EV will check to see if it can read that directory. If EV does not have access to that directory, it will not use the new rwp file.
The common reason for both of these issues is the way that the Apache Tomcat service logins into the machine that is running EV. By default, EV is configured to login using a Local System account. This account may well have the correct permissions to directories on the local machine, but if the workspace is located on a remote machine may not have the access to the directory.
More importantly, the local system account is unlikely to have the correct database permissions to access the database used to support the workspace. The solution to this problem is to change the account that is used by Apache Tomcat service to login to an account that has the correct access to the database.
When you use a Microsoft SQL Server or SQL Express server, it is possible to configure the server to use windows authentication as the method to verify that the user can access the server. If you have configured your workspace to use windows authentication as a user connects to the database behind the workspace, then this also needs to be reflected in the user id that Apache Tomcat uses to login when the service starts.
Point to note: The account that is used needs to have local administrator rights.
Please refer to Configuring Tomcat Logon Properties in the Using Enterprise View manual for instructions on how to change the account that EV uses to login.
Incident # 2647204