Upgrade broke Visual Voicemail
- I had no problems with No. 2, and No. 1 works for me only before BES activation. If already activate, I can delete and reinstall as many times as I want and I cannot edit the permissions to Allow. But I don't plan it on BES or our IT policies, because nothing has changed other than a new version of VVM.01-26-09 03:14 PMLike 0
- I had 1.19.2 which worked fine on my 9530 Storm with Verizon.
Then I ran the upgrade.
I also go the message "Required permission for Visual Voice Mail cannot be set probably due to IT policy restrictions. Phone needs Allow, Please consult with your admin."
Setting BES to Allow All for this app fixed that problem.
Why did I upgrade?? Guess I trust that it will have been tested.
Talking to Verizon Tech Support.
Tried soft reboot, no cigar.
Tried uninstall, reinstall (current which is 1.19.6), no cigar.
They suggested full restart from scratch, NO WAY.
Checking if there is original software available. No.
They sent me to Blackberry 877-255-2377, where I have to pay to fix their problem? Theirs Verizon, or Blackberry???
So now I've removed it, and no way to add 1.19.2 or 1.19.6.
Will post if I figure it out.
Does 1.19.6 function for anyone?
Verizon, shouldn't you pull software that does not work???
Thanks, Dan01-26-09 04:06 PMLike 0 - I had the same problem, I had finaly just deleted the voice mail app all thogther and redownloaded it. When you do this make sure you don't click on the set permission settings box.01-26-09 08:06 PMLike 0
- I've tried uninstalling and reinstalling about 5 times now. Never works. I really miss having this feature with the 1.19.2 software.
Does anyone know who makes the VVM software? Is it Verizon?
I just hope they are working on a fix or we can somehow find the older 1.19.2 version to reinstall.01-26-09 08:58 PMLike 0 - This issue is being discussed in at least two threads:
http://forums.crackberry.com/f132/90...-issue-142907/
Since it appears to be a BES issue, I would suggest that everyone on BES who has this issue have their BES administrator bug VZW and RIM. Not that I have high hopes, but BES admins are at least a little more compelling than individual complaints. I just want my old VVM back. With all of the reported problems with the Storm -- and I love mine anyway -- this unecessary issue is disappionting.
In the meantime, perhaps we can get a sticky advising BES users not to upgrade to the new VVM.01-26-09 09:59 PMLike 0 - VZ rep called me back today (at last) he really didn't listen to my issues, got me to make a couple of changes to settings and closed my ticket.
But it didn't make any difference.
To recap I have done a WIPE and been removed from the BES, after re-installing VVM it works - but now Enterprise Activation hangs after the calendar.
Wonderful - thx for the VVM upgrade VZ - not.01-27-09 04:32 PMLike 0 - Here is a possible solution posted on the other thread (forums.crackberry.com/f132/90-visual-voice-mail-issue-142907/index3.html) concerning this clusterf@#$. I don't know if this works yet as I just saw it and sent to my IT folks but I wanted to make sure everyone here saw it also.
QUOTE=WildHairZero;1515398]
I'm the BES admin for our company and ran into this issue on my Storm with .90 only AFTER I upgraded to the new VVM.
To fix the issue you have to really dig around on your BES server. We had the "Phone Access" property set to "Prompt User" under our default Application Control Policy. This works for like 99% of applications out there, but I have seen it cause issues from time to time.
The old VVM would cause the prompt dialog to appear that asks for permission to use "Phone Access," the new version of VVM does not make the prompt appear and fails to load. Verizon needs to go back to their software development team and get this issue sorted out. The only way I could get it to work now was to change the policy to "Allow," but that is only a temporary fix and I should never have to do something like that for one dinky application.01-28-09 11:13 AMLike 0 - I have a way to download the old version of VVM, but I can't post the link until I hit 10 posts. Here is No. 10, with the link to follow.01-28-09 02:00 PMLike 0
- After my IT department (understandably) declined to make the changes listed in some of these posts and after spending a fruitless hour on the phone with a Verizon rep (who amazingly told me they do not keep links to previous versions of software), I finally came up with a way to downgrade my Storm to the previous version of VVM (1.19.2).
A friend with the Storm (who, thankfully, is quite the procrastinator) had never gotten around to refreshing his App Center after the VVM update was released. Thus, his App Center still listed 1.19.2 as the current version of VVM.
I had him click on that link, which ultimately directed him to the website where version 1.19.2 can be downloaded. He then copied the address and emailed it to me. After erasing the 1.19.6 version from my phone, I went to the address he sent me on my blackberry and it brought up a download prompt for 1.19.2. I downloaded and installed that version, and now all is well once again.
Here is the web address for the 1.19.2 download:
http://mobile.vzw.com/download/vvm/S...vmail_9530.jad
Hope this helps others with the same problem.01-28-09 02:01 PMLike 0 - After my IT department (understandably) declined to make the changes listed in some of these posts and after spending a fruitless hour on the phone with a Verizon rep (who amazingly told me they do not keep links to previous versions of software), I finally came up with a way to downgrade my Storm to the previous version of VVM (1.19.2).
A friend with the Storm (who, thankfully, is quite the procrastinator) had never gotten around to refreshing his App Center after the VVM update was released. Thus, his App Center still listed 1.19.2 as the current version of VVM.
I had him click on that link, which ultimately directed him to the website where version 1.19.2 can be downloaded. He then copied the address and emailed it to me. After erasing the 1.19.6 version from my phone, I went to the address he sent me on my blackberry and it brought up a download prompt for 1.19.2. I downloaded and installed that version, and now all is well once again.
Here is the web address for the 1.19.2 download:
snip
Hope this helps others with the same problem.01-28-09 02:24 PMLike 0 - After my IT department (understandably) declined to make the changes listed in some of these posts and after spending a fruitless hour on the phone with a Verizon rep (who amazingly told me they do not keep links to previous versions of software), I finally came up with a way to downgrade my Storm to the previous version of VVM (1.19.2).
A friend with the Storm (who, thankfully, is quite the procrastinator) had never gotten around to refreshing his App Center after the VVM update was released. Thus, his App Center still listed 1.19.2 as the current version of VVM.
I had him click on that link, which ultimately directed him to the website where version 1.19.2 can be downloaded. He then copied the address and emailed it to me. After erasing the 1.19.6 version from my phone, I went to the address he sent me on my blackberry and it brought up a download prompt for 1.19.2. I downloaded and installed that version, and now all is well once again.
Here is the web address for the 1.19.2 download:
[url]http
Hope this helps others with the same problem.
Unless they come up with a new version that can print $100 bills, i'm never upgrading!01-28-09 04:17 PMLike 0 -
I'm the BES admin for our company and ran into this issue on my Storm with .90 only AFTER I upgraded to the new VVM.
To fix the issue you have to really dig around on your BES server. We had the "Phone Access" property set to "Prompt User" under our default Application Control Policy. This works for like 99% of applications out there, but I have seen it cause issues from time to time.
The old VVM would cause the prompt dialog to appear that asks for permission to use "Phone Access," the new version of VVM does not make the prompt appear and fails to load. Verizon needs to go back to their software development team and get this issue sorted out. The only way I could get it to work now was to change the policy to "Allow," but that is only a temporary fix and I should never have to do something like that for one dinky application.01-28-09 04:40 PMLike 0 - I had to do three battery pulls after a wipe yesterday because enterprise application kept stalling out. After the third wipe and about 40 minutes it finally finished.01-29-09 09:01 AMLike 0
-
Also if you do a battery pull mid activation do you need to re-initiate it?
Trying not to annoy the IT fols with constant re-activaion requests!
thx01-29-09 09:10 AMLike 0 - I always have the cable attached after I wipe and load a new OS, which avoids having to get a separate password. But the activiation itself is wireless. It picked up where it left off each time I did a battery pull.
Exactly how enterprise activation works and what is done wired and what is done wirelessly is not a topic that I know much about, but if it's hanging on you, a battery pull might be worth a try.01-29-09 10:02 AMLike 0 - Hey folks! Thanks for your tips. I just found this site and this thread when my IT guy forwarded it to me looking for a solution (prior to you all stumbling across a solution).
Eventhough I deleted version .6, it asks if I want to replace .6 with .2, I say yes, then get "download failed". Am I going to have to "wipe"? Always good to "wipe" but a pain when you have to get a new activation password (had some trouble before).
And I'm concerned about having to redo all my settings again... arggg! I'd backup but... I haven't figured out how to manual sync, while synching wireless with the bes...? Desktop manager gives me an error when I try)
Tips on these 2 issues?????
(error on install and doing manual synch while set up for bes)
Thanks!!!!!!!01-29-09 12:06 PMLike 0 - I always have the cable attached after I wipe and load a new OS, which avoids having to get a separate password. But the activiation itself is wireless. It picked up where it left off each time I did a battery pull.
Exactly how enterprise activation works and what is done wired and what is done wirelessly is not a topic that I know much about, but if it's hanging on you, a battery pull might be worth a try.01-29-09 04:08 PMLike 0 - After my IT department (understandably) declined to make the changes listed in some of these posts and after spending a fruitless hour on the phone with a Verizon rep (who amazingly told me they do not keep links to previous versions of software), I finally came up with a way to downgrade my Storm to the previous version of VVM (1.19.2).
A friend with the Storm (who, thankfully, is quite the procrastinator) had never gotten around to refreshing his App Center after the VVM update was released. Thus, his App Center still listed 1.19.2 as the current version of VVM.
I had him click on that link, which ultimately directed him to the website where version 1.19.2 can be downloaded. He then copied the address and emailed it to me. After erasing the 1.19.6 version from my phone, I went to the address he sent me on my blackberry and it brought up a download prompt for 1.19.2. I downloaded and installed that version, and now all is well once again.
Here is the web address for the 1.19.2 download:
Hope this helps others with the same problem.
Appeciate the help.
Long time BB user first time poster on CrackBerry. Be gentle.
FYI, had to remove the link since I don't have enough posts...02-02-09 02:49 PMLike 0
- Forum
- BlackBerry OS Phone Forums
- More BlackBerry Phones
- BlackBerry Storm Series
Upgrade broke Visual Voicemail
LINK TO POST COPIED TO CLIPBOARD