TMS show incorrect service contract status

[Jens Didriksen]

Left work Friday afternoon (May 24th) - TMS showed correct service contract status for all systems; arrived at work Monday morning (May 27th) and TMS now shows incorrect service contract status for 72 systems, showing "No contract" for the majority of them. So what happened to the Cisco back-end server during the week-end?

Last time we had this problem was just after Cisco acquired TANDBERG when they merged the databases, and it took nearly 12 months for them to fix it.

I'll open a TAC case - again - from here, but please vote "I have this problem too" if you're seeing similar issues.

/jens

[Jens Didriksen · Accepted solution]

TAC confirms there's been an issue with the SUS services, and that the service only came back up a "few" hours ago. It can take between 24 and 48 hours to "hopefully" fix itself. So guess it's "wait and see" for a while.

Here's a thought, how about an announcement in this forum when something like that happens?

/jens