Diane Gardner

Thats fine Jeffrery but I would like the ability to be able to export more than 5 rows.

Thats fine Jeffrery but I would like the ability to be able to export more than 5 rows.

This did used to work well. When I run a Change/Problem/Helpdesk search, the search criteria information is returned to screen. I select the CSV Export option and the export results are returned in the CSV Export window for items less than 5 rows. Anything more than that, its blank. I am able to successfully run exports for Service Management functions with no issues I get the same error with "open requests" - of which there are only 5 items returned the search pane and similar with "requests assigned...

I get this too when trying to export in iTop 2.6.1.4463 and PHP 7.2.17. I am unable to run the Export function to a CSV file. I just get a blank space. Cant find anything in the error logs to pinpoint the problem.

We have done that and the issue still persists albeit the user's dashboard is now set to the default. All shortcuts have also been removed. Attached is the latest IIS logs.

Hi Guillaume. Funny you should say about the dashboards. I was looking at the PHP code against the 500 error which made me think it had something to do with Dashboards too yesturday. Running 2.6.1. Just iTop standard (free) extensions from iTop hub. May not be the latest versions as of today but they were when I upgraded iTop version last year. We hae not really modified the standard PHP files part from currency change to GBP and some other small tweeks to values within the PHP files but no changes...

Hi Guillaume. Funny you should say about the dashboards. I was looking at the PHP code which pointed to Dashboards too yesturday. We are running 2.6.1. We are only running the iTop standard extensions that I have downloaded from the iTop hub (the free ones). The actual PHP code has not been modified apart from currency (to UK pounds) and some other small modifications. Nothing to do with the dashboard area. I would need some help on any database modifications as I am not a MySQL DBA so I would not...

There is reference to the HTTP 500 error in the IIS logs (attached). You will need to look at 10.31.6.30 as this is the users client machine. It does not matter which workstation user logs into because the error occurs on any client. We have not set PHP errors on in the PHP.INI file. Also looking at todays IIS logs I can see the 500 error in \pages\UI.PHP for the WelcomeMenuPage; ConfigManagementOverview;Contact. At the very end I can see the codes of 500 0 0 5343 as well as http://<hostname>:808/pages/UI.php?auth_user=<userid>...