ACDelcoTDS account migration (NASTF)
I am trying to migrate my ACDelcoTDS account to their new system. It's asking for Vehicle Security Credentials. I've entered my VSP info and it's saying 2 things," invalid security code" or "exception during communication with Address Validation service". I've tried multiple times. Not sure if this is on the NASTF end or what. Anyone else experiencing this?
***Update*** I had to use the code in the Authy app, not my password, and it worked. Thanks to John Rogers for the help.
Your address also, must match whatever they're using to verify it with, EXACTLY.
i.e.: I had to enter "Street" in place of "St" - that they pre-filled (migrated) in the address field.
Like it's a matter of National Security or something...
Thanks, had all that correct, just the VSP part. Unsure if i even needed to enter my VSP info? Thanks again
I really like this business of diagnostics and programming. It is acceptable that there are some measures to keep vehicles safe from theft and nefarious code. This is getting really ridiculous. It would be really nice if the OEMs were able to standardize. It seems that we spend a great deal of time fixing software issues, doing updates, filling out forms and not doing what we love to do. That is fixing stuff.
Betting the dealers aren't having to go through these steps in order to program a module. Grrrrrr. So much for similarity!
I have not attempted to access the GM site yet but I'm fairly certain you have to enter your LSID and use the authy code as your password.
You are correct. I was entering my password not the authy code. Once i did, my account migrated. Not even sure i needed to enter my VSP credentials to migrate? Just figured they wanted to know if you're a VSP or not.
Still cant get mine to work.I will call on Monday if there are open.Something with my psc account info not matching.
I just migrated my account. If you're still having trouble I recommend logging into your NASTF SDRM account and make sure the info here matches exactly what you're inputting at acdelco tds. As others have mentioned, you need to put the authy code into the passcode field.
It looks to be that a phone number preface was the problem.I was able to migrate it to the new site and the year programming all vins is available once mine runs out.Now if I can get Benz TRP to work I need to order a ESL.
David nice catch, that was one of the things I saw but forgot to mention. When the website filled in my information it put a zero in at the beginning of the phone number which I had to remove.
Hello, just log in to the new ACDelco account, but it seems like I have to put my VSC credentials.
Im assuming VSC is my LSID?
What do you use for passcode?
little help please!!
Yes, VSC is your LSID number. For the passcode you need to use the authy app to generate the code.
Also, make sure you use a valid email address that you have access to or you won't be able to easily verify the account.
got it working.
Also notice that they chargin tax.
As if there weren't enough problems with the "migration", be aware:
Your e-mail address used when creating the account MUST match precisely or the validation code will not be sent.
Friggin wasted time that's not recoverable.
Jaime is correct, we found this to be the case yesterday. It is case specific. If you used a capital letter in your email originally you have to use the same to login with.
I just learned also, Information migrated into your profile, specifically the e-mail addresses you might use, can only be used a certain number of times (read: maybe once). I have 3 e-mail addresses (personal, business and one shared with my lovely bride) but I have 6 ACDelco accounts... I guess I'll take more of my time, bother the customer support staff and ask for their suggestion(s) how this can be resolved.
Unless someone here has already resolved their own similar problem (?).
More evidence the migration may not have been thoroughly tested prior to roll-out.
Think of this as me just talking out loud. Let's see. What do we know?
1: GM is migrating their website. We've been living in interesting times because of it.
2: Next month, Oracle is charging a licensing fee to all corporate users of Java.
3: Microsoft is ending support for Win 7 in January. GM is pulling support for Win 7 in December.
4: GM is moving away from IE and the Active X component. They're attempting to make their website work with Google Chrome. It does, except on certain days which end in "y". In all fairness, it worked for me today. Twas a bit clunky but it did work. Last week was hit or miss, in the same day.
5: Every computer first used needs to have the GM account verified. Whether, or not, you can log in is beside the point.
6: They are attempting to make these changes at the same time. Group "A" does something on the website. Group "B" comes in and hoses it by implementing the stuff their silo is working on. Etc., etc.
Question time? Don't you think that you should lay low until they get their act together?
It would be my choice to do so in order to restore my health, however, my customers' customers might not like being asked to lay low until the manufacturer of their vehicle gets their crap together.
Your perspective(s) are always welcome, even when they provoke thinking about the situation in a different manner ;-) .
You wrote "5: Every computer first used needs to have the GM account verified.".
THIS mobile guy keeps finding out there's more to the story than what he's already learned (the hard way, thanks to the way this migration was rolled-out). Today, using the same laptop that had been validated from my home, I had to have it validated again - I suspect because the IP address changed when I used my mobile hotspot to flash a module at a customer's shop. What this tells me is I (we mobile guys) will be wasting a lot of my (our) time, repeatedly, every time we go to another location to provide our services. Otherwise we will be having to raise our rates to cover the extra time spent (needlessly - IMHO).
"Whether, or not, you can log in is beside the point.".
Not far from the truth! "That is not our concern, sir" is the answer I got last week to several of my questions about the migration, the subscription charges (and fees) and whether the dealership technicians are having to jump through the same hoops as the aftermarket techs/owners. "That is not our concern, sir". Yes, "Whether, or not, you can log in is beside the point" , as you say.
When ACDelco doesn't credit you for the time you were unable to use the account(s) for which you already paid, the re-re-re-validations or for the time wasted trying to make their software work on systems that pass all their compatibility tests, there eventually is a breaking point where one throws one's arms in the air and screams "take it to the dealer". I believe this response is the intended result of the changes. To say this consequence isn't intended, is to believe the manufacturers/dealers don't care to see any more cars to repair.
Until the owners of the vehicles experience more inconvenience (why'd the module need updating/reprogramming/replacing in the first place???) and increased fees for tasks that we are supposed to be able to do, then boycott/complain to/picket/(whatever) the manufacturer, we in the aftermarket cannot rely on a positive change occurring, especially when there are no teeth in any entity to instigate the needed change. Positive change must not "be their concern", sir.
End of rant.
The only problem with the validation being required with a different IP addy thought is that it's not consistent. I've had it not require. I've had to do a password reset. I've had it require. Perhaps I should touch myself and see if that matters.
One of my coworkers, had to reset 3 times in the same shop. The last time, he had to use Chrome because IE didn't work.
I spoke with a customer today who had an issue last week. (I had to cut it short then because I was committed to be somewhere.) Programming fail. Programming fail. Programming fail. Programming successful. What did he change? Not a damn thing. It was just caca to be him on the website at that particular point in time.
If I was to venture a guess as to what's happening it would be silos. Workgroup A has been tasked with 1 of the changes. Workgroup B is tasked with a different change. Etc., etc. Workgroup A makes a change to the website and validates their work product. Workgroup B makes their change to the website and validates their work product. But it ends up hosing Workgroup A's work product and since they're in a silo, they don't know it. Workgroup A gets bitched at but can document their work. So can Workgroup B but they came in last and blame can be assessed. If anything like I just described is what is happening then it is the result of piss-poor project management.
As far as the rest of your rant? If you're looking for an argument from me then you're in the wrong place.
You painted a vivid but unwanted picture of you touching yourself. lol
No argument requested, nor was one warranted (as evidenced by my admitting "end of rant").
Your guess as to what may be causing the sites' problems is most likely spot-on. Personally, I don't see them being resolved anytime soon. It would be their way of justifying the claim that they needed more security, almost as much security as if we were launching ICBMs.
My prices have increased. That's the end result.