I have a very peculiar problem.
(SAS 9.4M5, Web Report Studio 4.4)
An information map was designed based on a straight SAS dataset (not a cube).
That information map can easily be used in Enterprise Guide or verified in Information Map Studio.
But in Web Report Studio (run with the same user), even just using a single column from that information map results in a "Missing Report Element" error.
Since this "suddenly" happened on all information maps/reports in a single tree in the metadata, I have a suspicion that the designer of that reports/maps (who also manages the whole tree) messed up while fiddling around with the metadata permissions.
Does anybody have an idea where I should start searching for a clue?
Maybe the "fiddling" was logged in the metadata-server logs, if the user is known, you should be able to find something useful.
First thought was: folders or maps have been renamed and the iMaps are broken, but the result of such an outburst of creativity should be seen in EG and iMap-Studio, too.
Is there a Show Details button with the error? If so, does it have any more information.
The other place to look is the Web Report Studio log
Lev1\Web\Logs\SASServer2_1\SASWebReportStudio4.4.log
-------------------------------------------------------------------------
Four tips to remember when you contact SAS Technical Support
Tricks for SAS Visual Analytics Report Builders
SAS Visual Analytics Learning Center
@Madelyn_SAS wrote:
Is there a Show Details button with the error? If so, does it have any more information.
The other place to look is the Web Report Studio log
Lev1\Web\Logs\SASServer2_1\SASWebReportStudio4.4.log
Good hint. I should take more care following my own maxims 😉
The log has this to say (I guess it points to the problem):
The Balance algorithm timed out before a server could be found.
Could it be that the spawner has developed a problem?
I think I managed to fix it. I located the two processes that had the Metadata ID of the Pooled Workspace Server (used for the reports) in their commandline, and stopped them. Then I restarted the spawner, and finally validated the PWS through the SMC (the reports wouldn't work before I did that) to start a new PWS instance. After that, the reports started working again.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.