Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Solution to track the actual fix for problem reported in Solution 14755.
Workaround fix for Solution 14755, resulted in Binder Fast Access services being disabled in CMNBINDF, when used in a Z/OS 1.5 environment. This Solution tracks the actual fix for the problem, once IBM gets the fix for APAR OA08880 sorted out.
CMS-XML Report on empty fields
The solution is to use the 'Use Advanced SQL Condition' option. This option will only appear if you are not at the root level of the report project. Then, you will have to enter the following criteria (tested with MsAccess and SQL databases):
CMS-XML VM: Can I run a difference report on an entire project or project tree?
The Solution below describes a toolbar script to check differences based on workspace.
CMS-XML ChangeMan DS 5.5.0 License Report
License Report is attached to this Solution .
CMS-XML When you re-run a report it uses cached results if parameters are unchanged
SOLUTION : The user should refresh reporting services report itself. This is expected behavior for all reporting tools. This is a feature of SQL Reporting Services.
CMS-XML Creating a report in Visual Studio and get error "Deserialization failed: The element 'TableCells' in namespace...."
When you are using the Solution Explorer instead of right clicking on the Reports area and clicking "Add New Report " cick on the "Add" | "New Item" option instead. From that window click the "Report" option and fill in the report details. For some reason the "Report Wizard" just doesn't work with the Ole DB Provider supplied for Mariner but creating the report from scratch will work fine.
CMS-XML SYNCH10 incorrectly reported when components are staged from development.
Fixed in ZMF 5.5.3 and 5.6.0. Note: SYNCH10 is also incorrectly reported when components, which exist in baseline, are staged via BATCH STAGE. See Solution D5346 , also fixed in ZMF 5.5.3 and 5.6.0.
CMS-XML Crystal Page Server stops responding when calling a report through the WCS
SOLUTION : It was determined that the Cilogger.dll file (the file used to write data to Crystal log files) had been corrupted as the following events were found in the Event Viewer (Start > Settings > Control Panel > Administrative Tools > Event Viewer):
CMS-XML 10.x / 2009Rx / 12.x : How to script the set-up of several User reports in several databases ?
Solution is to look at the demo dmpmcli js scripts : reportsdemo.js and reportslibrary.js (located on the dimensions server here: $dm_root/adminconsole/examples) to write your own script to achive this or to contact Serena consultancy department to do this for you.
CMS-XML DASHBOARD: All reports return a 404 error
Then you will have to manually locate the following file. C:\Serena\ Solutions \Dashboard\dashboard\ Unzip that file to the following folder
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs