NU Service – Progress Update

The new web servers are now working successfully in the live environment.
We are continuing to test the upgrade of NU Service. We are still aiming to go live with the upgrade during week commencing 1st June. However this may need to be postponed if the issues that we have found cannot be fixed by then and are not acceptable as a known issue with a workaround.Downtime will be communicated when the upgrade has been scheduled. Please note that this upgrade will not release new or changed functionality.

NU Service – Search box error

We have identified that the search box at the top of NU Service in the analysts view produces the following error when searching with free text.

“There has been an unexpected error. Click Continue to return to the previous page.
Could not find file ‘\\campus\ha\ITSM\LIVE\KB\index\_e.cfs’.”

We have a problem record open (4000074) and are investigating the issue.

I can confirm that the search works when searching on a ticket reference.

NU Service – Progress update

Work to replace the web servers is currently in test stage; it is anticipated that the new web servers will be moved into the live environment (without the need for system downtime) during week commencing 25th May.

We are also in the process of testing an upgrade of NU Service to ensure it is running on the latest version. The aim is to go live with the upgrade during week commencing 1st June. Downtime will be communicated when this has been scheduled. Please note that this upgrade will not release new or changed functionality.

Our next steps after this work is to plan a development cycle to release new and/or improve existing system functionality. The planning for this will entail reviewing our issues and wish list database* that many of you have been contributing too. We acknowledge that improvements to visibility of the history within a ticket is a high priority.

*At the moment this is a private database used by the SP team for planning other purposes and is not suitable for sharing.  We may look at an appropriate way to share some relevant information such as this in the future.

NU Service – System performance – Tests you can do

There are two things that you can do to help us to understand more about the performance issues you experience:

  1. On occasions when you experience issues with NU Service (of any sort) it is useful to know which web server was serving your NU Service session. To find this information delete the end of the URL to leave only https://nuservice.ncl.ac.uk/ within your address bar and type secure after the forward slash. For example:

If an analysts screen froze while they were reading a ticket with the URL: https://nuservice.ncl.ac.uk/LDSD.WebAccess.Integrated/wd/object/open.rails?class_name=ProblemManagement.Problem&key=82377f3f-6007-489d-b3f8-3d30ba4a6210. The URL should be edited to become: https://nuservice.ncl.ac.uk/secure

You will then be presented with a page of code, much of which can be ignored; the only part we are interested in is the first line of text at the top of the page (formatted in BOLD). Examples include: itsmweb3.ncl.ac.uk or itsmweb4.ncl.ac.uk. It is this text that indicates the web server in use at the time of the issues.

Please provide this piece of information together with the date/time of the issues and a description of the issue to the Service Desk.

  1. If you perceive NU Service to be running slow for you, you can use F12 developer tools in Chrome to gather the actual times taken for page loads.
    To find this information, see our ‘how to guide’: F12 Developer tools.
    If you are concerned about load times then please provide details of the times together with the actions you were carrying out on the system and the date/time.

Thank you for any feedback.

NU Service – System performance update

Our investigations and work with technical teams remain ongoing to address issues affecting NU Service performance and reliability.

To address system reliability issues we are building new web servers to phase out and fully replace the old ones. These will be fully tested before adding to the live environment. Any system downtime or affect to users will be communicated in advance.