-
1. Re: Updating AIR client
spgray Jul 6, 2011 5:26 PM (in response to joe05xlc)I'm having the exact same problem. Can't log on to the Folio Builder either. Any help from Adobe would be welcomed.
-
2. Re: Updating AIR client
David Ben Jul 6, 2011 6:30 PM (in response to joe05xlc)Did you access your viewer builder from the DPS dashboard? And do you have the latest version of AIR installed? there was an update on July
1st for version 2.7.019530
Side not folio producer tools are at version 1.1.1
-
3. Re: Updating AIR client
eminkadi Jul 25, 2011 11:14 AM (in response to joe05xlc)We are currently having this same problem with our viewer builder. The login and password is correct and we have installed the latest version of Viewer builder and AIR from the pre release site but still getting this error. This has never happened before with our Adobe ID and we were wondering what the problem might be. any feedback would be greatly appreciated
-
4. Re: Updating AIR client
John J MetzgerJul 25, 2011 1:12 PM (in response to eminkadi)
adobe is looking in to the issue. Response will come as we get info.
John
-
5. Re: Updating AIR client
John J MetzgerJul 25, 2011 7:54 PM (in response to joe05xlc)
We are awaiting a new build of viewer builder to address the can not log in issue with a valid user name and password. In the mean time.....
The latest viewer builder client needs to be installed when you get the message like joe05xlc got. You need to delete the existing VB client from your machine, flush your browser cache, log in to the digital publishing portal and download the latest client. Install on your machine.
If you get the "can not log in" error running this new client....follow the reset password wokflow, click on the link sent to your email, set a new password. You should then be able to use this new password to log in to viewer builder...
John
-
6. Re: Updating AIR client
Lisa Shugaar Nov 11, 2011 12:43 PM (in response to John J Metzger)John,
I"ve done all of your suggestions, plus a few more from another forum answer, and I'm still getting the same message.
Are you aware that this problem is still out there? and, can you tell me what else I might do?
thanks--