Web Messages Error checkAccess.do

[KCC35]

When logging into Web Messages (integrated messaging) on Apple products (ipad) through the My Verizon web page, I receive the following error:  checkAccess.do.  This also happened in November, but after a couple of weeks, the web messages returned to normal.  On January 12, 2017, at approximately 7:30AM EST, the error is appearing again.  I have logged on to a different computer using Explorer, and this error does not occur.  I have submitted feedback in the web messages "submit feedback" section also.  Verizon, will you please get this fixed?

[vzw_customer_support]

KCC35,

We appreciate you bringing this to our attention. What software version is the tablet running? Was there a recent update performed? 

DerekR_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

[KCC35]

Safari.  I have not yet run the latest update for Safari 10.2 in fear that it would cause a problem with Verizon's web messages.  Unfortunately, not installing the update made no difference, and the error occurs anyway.  I've checked all weekend.  It has not been fixed.  Please use whatever fix took place in November, and then make sure this never happens again.  Integrated web messages is an amazing idea.  We can check our messages anywhere, anytime, unless there is an error, or course.  We don't need an app on a device.  We only need the Internet, and that has been the most beneficial experience Verizon has provided its customers, except when it doesn't work.  Please make it work soon!

[deloused]

When your clear you're history/cache in Safari does the error message still occu?

[KCC35]

Yes.  This isn't a personal device issue.  This is happening with several Apple users.

[deloused]

I totally understand from seeing the forums that the issue is affecting multiple Apple users, but not all.

Because it's an error message regarding Java Script it could be do to a change Verizon made to their site, & a browser may need to refresh to read it properly, or it could be that the Verizon site is rejecting the request due to that, or because the ISP used at the time may be sending the request incorrectly, or that an Apple or Safari security update has changed some functionality or has caused the JavaScript setting in Safari to default to off, as that setting could affect it also.

While you you should definitely be able to access the site as you wish, keep in mind you have been using an App on your device (Safari) to access your messages thru the internet. If you prefer not to use the Verizon Messages App instead to access your messages thru the internet it's totally your choice of course, but it would offer more functionality, and cuts out some of the extra 'middleman' variables that can cause issues. Hopefully it gets resolved permanently again! 

[KCC35]

I firmly believe this is a change to the MyVerizon web app site.  My personal device(s) did not run any updates.  I tried the Verizon Messages app twice in the past.  It's so much easier just to log on to an account online, especially when logging in to view messages for multiple numbers (business, personal, additional lines).  With multiple Apple products in the home, the web app is certainly the way to go.  I just don't understand what Verizon (or the third party that runs the site) is doing to cause the issue.  It's as if Verizon runs some sort of update over night, and when I wake up, it doesn't work.  The worst timing is over a weekend, too.  Come on, Verizon! 

[CHRYOU9]

This is certainly an issue with verizon's messages web app via a mobile device and not an actual device issue.  It doesn't matter what device-phone or tablet, doesn't matter what browser, or software.  This was corrected previously so it seems as if Verizon could locate the previous work ticket and resolve it much quicker this time.  It would be nice to find a permanent solution as it is a major inconvenience. Major. 

[KCC35]

I am receiving the check access.do message again as of March 9, 2017.  Is anyone else?

[KCC35]

I am receiving the checkaccess.do message again as of March 9, 2017.  Is anyone else?  I don't understand why this keeps happening every few months, when for years, this service hasn't caused any issues.