The issue you are seeing is due to a Microsoft bug with properly displaying and interacting with the block reservations when the strings are beyond a certain length. Reconfiguring your server as instructed below will side-step the MS problem as the patch MS came out with did not resolve the issue beyond being able to see the block reservations whereas before the page would not draw the block reservations list at all (there is still no ability to edit). The adjustment below will make interacting with the block reservations function normally again. Since the issue is related to IIS and asp, it only needs to be done on the machine running/hosting the Nerve Center. Issuing a change control should update the SignUp server with regard to the block reservations you have cleared, but that may not push back down to the clients. You may need to recreate one and then clear it in order for the clients to realize that the reservation has been cleared as simply deleting it from the database tables does not inform the client of the change (hence the attempt to try to push the update out to the clients via change control).
Workaround for Microsoft Bug Dealing With Block Reservations in the Nerve Center
- On the Nerve Center (SignUp) server, open Windows "Component Services" under START > Control Panel > Administrative Tools > Component Services
- Expand Component Services > Computers > My Computer > COM+ Applications
- Open the Properties window for Pharos Uniprint
- Go to the Activation tab
- Change the Application Type to "Library Application"
- A warning appears, but it's safe to ignore (click OK)
- Restart IIS and "Pharos SignUp Server" service
Steven - thanks for that!! Most helpful, and something we've been working around for (quite) some time, with the understanding it would only be fixed by an upgrade... very much appreciated
Edit: on a side note, it was actually the Nerve Centre web-page which was not updating after the booking had been deleted from the database - was unable to create a new booking as the PCs were still flagged as having a booking already for that time - even though I'd removed both the booking, and the assignment of PCs to that booking, in the database. All good now though, thanks