Below are the properties to set to keep column size and width with text wrapping: Column Merge issue http://www-01.ibm.com/support/docview.wss?uid=swg21674298 Set the advanced server property RSVP.EXCEL.XLS2007_COLUMN_WIDTH_CONTROL to TRUE for both BatchReportService and ReportService services. Row Merge issue http://www-01.ibm.com/support/docview.wss?uid=swg21440556 RSVP.EXCEL.XLS2007_ALLOW_WRAPPING_SINGLE_CELL also to be set to TRUE for both BatchReportService and ReportService services. Once done, you can set any column width to be fixed and see same result in Excel as well as HTML. Please note that above properties will not be honored if you have unchecked Grouping repeating cells Report property in Report Properties menu.
Below IBM document explains behavior of copy/move or overwriting impact of objects:- https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.wig_cr.doc/c_gtstd_copy_move_items.html If you copy and overwrite an existing report, the copied report ID and links replace those of the existing report. In this case, you might need to update links, such as links to job schedules. If you move and overwrite an existing report, the existing report ID and links are maintained. In this case, references to the moved entry are broken. However, this doesn't work in all cases and we see drill through links broken in some cases. Best approach in such case is to use cognos deploy method where you update reports in separate folder in same environment and import it to destination location. You can create single export and import tasks to use for all such updates.
Error: DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit. Troubleshooting: Identify which server error is coming from Identify how frequent it is coming and which service throwing it. Identify type of reports (DQM Vs CQM) Cause and Solution: DQM report waiting for a connection with report service longer than the specified timeout. The successful request flow is as follows Run the interactive DQM report -> Get a connection with report service -> DQM report runs on Query service -> Query service gives the output to report service for rendering -> user received the output In this case, the errors are generated at the second step i.e. getting a connection with the report service. This shouldn't be limited only to Query service i.e. your environment seems to be busy interactively which has little to do with the Query servic...