|
|
Originally posted by Jeremym1
I had this same issue about 3 weeks ago with my wife's phone. There was "a batch" of Sprint Treo's that were incorrectly scanned in at the factory. They have been registered as a 2G phone and not a 3G phone. Therefore, the Vision Network will not provision the phone because it does not recognize it as 3G. This is a known problem within Tec Support (Tier 2) and they can fix it with a re-registration of your account. Sprint does not know how many phones were affected by this. The key is to get a tec who knows about the problem and it can be corrected in a couple of hours after a network update to your phone. Thanks, Jeremy
PS-btw, the wife's phone has worked well with Vision ever since
Tom, I replied to you before about the same thing, so here it goes once again.
Error 3000 IS a time-out error message due to the fact that your phone is NOT connecting to Vision.
Anyone saying that it is your account is INCORRECT. There is nothing wrong with your account; yet your account could become affected due to corrective measure that MUST be taken to get you out of the dreaded error 3000 cycle.
Producer, you said the Vision account needs to be reset; that is incorrect; you cannot reset something that the phone is not doing in the first place. Resetting is the same as provisioning.....read on.
Jeremym1, you are correct; there is a batch of Treo 600's (amount unknown) that were configured within SPRINTS database as 2G phones; which means a 2G phone CANNOT access Vision. 2G phones are capable of wireless web; which is NOT Vision.
Because of this problem, the information regarding your specific Treo 600 must be fixed/changed WITHIN SPRINTS DATABASE. You can exchange and get another Treo....if you just have to do it that way; chances of rec'g one with the same problem is hit or miss.
Now, lets get back to that resetting of your account that was mentioned; think about this, if the problem is NOT your phone, then what is the probability that re-provisioning you is going to work. Well, if we're all on the same page here; then you know the answer to that; one and for those that dont know...allow me help you out.
Re-provisioning your account is NOT the answer. Remember the database thinks your phone is 2G (wireless web) and not 3G (Vision). You can have your phone provisioned 1,000,000 and as long as the database thinks it is a 2G phone, well lets just say you have a better chance of eating filet migon in the desert than you do using your phone.
Ok, so now we know that the fix needs to be done on the Sprint side of things; the database needs to reflect that your Treo is capable of Vision. Once that problem is corrected, THEN you can be re-provisioned.
How do I know all of this?....experience  My account was reset...in doing this, it wiped out my username and set me back to the name my account was provisoned with when I started using Sprint 5 years ago; that meant anything that had been associated with the username I had been using for those 5 years was now gone.
I called tech support....they told me, not a problem, we can fix that for you. What ended up happening turned into a nightmare for me and that is how I have come to know so much about this issue. When Tier 2 walked in the door, the first voice they had to greet them each morning for 2 weeks was MINE!
The first tech who told me not a problem re-entered my user name....but its not that simple. Because mine had been wiped out, it was now hung up in the system some where and I was told it would take 30-45 days for it to clear out; not good when that name is also connected to email. Anytime a username is changed, yes, that change also takes place in email.
My problem became more intensive than what tech support is accustomed too, so I was determined to learn everything I needed to learn; just in case something like this were to happen and I would have info to provide for others.
In closing (talking like the CEO I am....in my own mind) ,
It is NOT your phone, per se, it is Sprints database that tells them what your phone is supposed to do.
Only talk with Tier 2, lower level reps dont have a clue how to fix this.
Stay on them to make sure the database is being worked on and NOT your account.
And one last thing, I had to edit this b/c I forgot to mention it before; the SPRINT update does NOT fix error 3000!
Hope I have been of help......waving as I step away from the podium.
|
|
|
