**
Agreed.
But, Rick.
I did update my data a year ago. I also asked
them a year ago to remove the support contract ID that is now showing up as my
primary ID. Whenever I logged into the website, prior to Friday, it always
displayed my current account as my primary. The old-expired one hasn't
been visible to me for over a year. So why is it now showing up as the
primary?
I even went through the tutorial last week and already knew
about the upcoming changes to our login id and the site.
On the flip side, Chris might be reporting a new
problem. At least I was able to hit the site earlier today.
Now, I can't get in at all.
I received the 3 links he mentioned.
Hold on.... checked again, by going through http://support.remedy.com which of course
redirected me to the new site. I CAN get in that way. Weird,
huh?
I simply believe there are going to be problems for at
least the next 24 hours.
On a positive note, I'm glad they're finally making an
attempt to change this antiquated site.
Thanks,
Michelle
**
Lots of us are. Wrong information about our accounts seems to be the
norm. Why they would have made no known effort to engage the users to
update their data prior to this is beyond me.
Rick
On 10/16/06, Gillman,
Chris <[EMAIL PROTECTED]>
wrote:
**
Listers,
So is anyone else experiencing
really bad problems with the support website. Particularly, logging in? I've
tried everything… using the email address associated to my old loginid,
re-registering, calling support to which I received a "let me put in a ticket"
answer. Nothing works. I get the "ERROR: The User Name/Password combination
you entered is not valid. Please try again. If you have forgotten your
password, select the Forgot my Password link."
Even tried the "Forgot my
Password" link, and it doesn't give me anything. Like I said, I even tried
re-registering, and I can't even get INTO the website. I'm also getting these
IMAGEMAP errors every so often now when I go to the website. Any ideas?
__20060125_______________________This
posting was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___