In addition to the great information provided, enclosed some general doc on the SAS server/web server dependencies: http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#p0d9d5nzmd8i4yn1usv2l22vpa7t.htm   This might help to see how the servers "relate" to each other and what they are responsible for. As you will see, Workspace Server is not listed as it is a process initiated by the Object Spawner (which itself depends on the Metadata Server).   Thanks Anja ... View more

Hi, Did you make any changes in SAS Management Console, Authorization Manager, Resource Managements, Location ... <server> <OLAP schema>? To make sure I understand you correctly: Your users have to access info maps but are not allowed to access cubes? Are we talking "seeing cubes" or "updating cubes"? Did you make changes on SASTRUST? Has to have RM! What error messages are you getting (if any). Log files might give an indication of what might go wrong. What are the current effective permissions on the folders and its content? When you go on the Authorization tab of an object's properties, Access Control, make sure the Default ACT is the only one applied (Foundation). Goal here is to make sure that you do not have any other ACTs applied. All these points could effect how objects "behave", and consequently, how users can interact with it. If the problem persists, I'd recommend to contact Tech Sup. Thanks Anja ... View more

The behavior you describe could also be caused by conflicting permissions. You mentioned that you already moved data to different folders. If groups applied to folders would include the same users yet with different permissions, you'll have a conflict. (Just an example). Metacoda provides some fantastic features that allow you to see which permissions are applied on which objects. Maybe this could help in evaluating the permission settings. Also, as Madelyn mentioned, checking how the implicit groups SASUSERS and PUBLIC are used is key. Did you modify any of the default roles, such as modifying capabilities? What SAS version are you using? ... View more

Hi there,   in addition to all the great suggestions, you could check whether the Workspace Server log file is enabled. This does not solve the size and "fill up" of the other SAS logs, however, if the Workspace Server log is enabled, it'll eat up lots of space. Check \SAS config dir ...\Lev1\SASApp\WorkspaceServer.   Whether you'll remove/delete log files, consider whether your company might need to keep them for a certain period of time, or, of keeping a certain timeframe might be important for auditing and the like.   This is a blog that might help as well: https://communities.sas.com/t5/SAS-Procedures/How-to-clear-SAS-logs-automatically/td-p/58884   Thanks Anja ... View more