MIS Systems Thread, Capita support net showing different schools incidents in Technical; Hi,
I was raising a new incident with Capita support net this morning. Half way through I got an application ...
16th December 2013, 11:27 AM #1
Capita support net showing different schools incidents
I was raising a new incident with Capita support net this morning. Half way through I got an application error with the website, so I swore and clicked 'Issues for site' to see if it had recorded anything of the issue I was raising when I was shown a list of incidents I didn't recognise. Looking closer they were issues for another school, one in East Sussex I've never heard of.
Clicking on the incidents themselves just gave me a message saying that I wasn't allowed to view this incident (fortunately), but not good.
Now to report the issue to capita somehow.
16th December 2013, 12:12 PM #2
Best report this on the Supportnet forums if the case system isn't working.
16th December 2013, 12:34 PM #3
I experienced (and reported) that a couple of years ago. IIRC it tended to happen when Supportnet falls over and you opened the case log link in a new tab.
16th December 2013, 12:46 PM #4
Please log a case so we can follow up
16th December 2013, 01:18 PM #5
The url is very random and the system probably gets confused, i think this has happened to me or twice too.
Roll on SupportNet2 i say.
16th December 2013, 01:32 PM #6
- Rep Power
My name is Leigh Davenport and I am the head of Customer Services.
As Phil has already mentioned, you can log a case with the service desk via SupportNet or on 01234 832020. Alternatively you can contact me on my direct number 07920 586631 as I would like to be able to understand and resolve the issues you have experienced.
16th December 2013, 02:07 PM #7
I suspect he's experiencing behaviour similar to that reported in #1110-976823 that allowed us to see #1110-975379 (the latter being a case for another school).
16th December 2013, 02:18 PM #8
Not sure why he needs to log a case personally. Like @pete said this isn't anything new, I was under the impression that the Session ID collision was because the web server failed over\got restart and reissued your session id because you couldn't afford the performance hit of using SQL server for session state so it remembers active sessions after a reboot. Surely your technical team can confirm it restarted sometime before 10:40 today.
By tech_guy in forum General Chat
Last Post: 2nd August 2012, 12:14 PM
By ful56_uk in forum General Chat
Last Post: 17th November 2008, 03:15 PM
By mgwm in forum General Chat
Last Post: 4th April 2008, 10:44 AM
By adamf in forum Windows
Last Post: 21st February 2008, 09:50 AM
By deano in forum General Chat
Last Post: 23rd November 2007, 03:27 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Tags for this Thread