This Question is Answered
1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)The form has already been processed or no token was supplied, please try again. posted: Apr 3, 2009 1:06 AM
Hi Robert,
Do you know when this issue will be fully resolved and fixed? I'm not only finding this occurring when creating new VMTN documents but also something as simply trying to reply to a user that has left a comment?
I get the same lovely error:
when trying to reply to a few user comments on a VMTN document I create/manager at: http://communities.vmware.com/docs/DOC-8760
I get several emails a month asking why a user is unable to post and some are actually able to post with some major luck but I'm finding out that I can't even respond to my own document, I've tried 20x this morning and finally got reply in but still unable to reply to the other recent questions.
Are there any alternatives or methods of ensuring that I can both comment and reply within a VMTN document or are we left to the mercy of gambling each time when we post and as of now its close to 100:1 odds before you'll be successful?
Thanks for you time
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
http://twitter.com/lamw
If you find this information useful, please award points for "correct" or "helpful".
Do you know when this issue will be fully resolved and fixed? I'm not only finding this occurring when creating new VMTN documents but also something as simply trying to reply to a user that has left a comment?
I get the same lovely error:
System Error
* The form has already been processed or no token was supplied, please try again.
when trying to reply to a few user comments on a VMTN document I create/manager at: http://communities.vmware.com/docs/DOC-8760
I get several emails a month asking why a user is unable to post and some are actually able to post with some major luck but I'm finding out that I can't even respond to my own document, I've tried 20x this morning and finally got reply in but still unable to reply to the other recent questions.
Are there any alternatives or methods of ensuring that I can both comment and reply within a VMTN document or are we left to the mercy of gambling each time when we post and as of now its close to 100:1 odds before you'll be successful?
Thanks for you time
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
http://twitter.com/lamw
If you find this information useful, please award points for "correct" or "helpful".
Unfortunately the problem has not been resolved, I believe Robert and his team is still investigating. I hope it's solved soon, it's quite a annoying and committing a document to either draft or publish will take you at least 20-30 tries if your patience lasts that long.
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
http://twitter.com/lamw
If you find this information useful, please award points for "correct" or "helpful".
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
http://twitter.com/lamw
If you find this information useful, please award points for "correct" or "helpful".
Umm... version 12 was the last one with good info, you might not remember it but because of the trouble i had, you actually made an edit on behalf of me.
I'm not sure what version 11 had anymore...
--
Wil
_____________________________________________________
Visit the VMware developers wiki at http://www.vi-toolkit.com
I'm not sure what version 11 had anymore...
--
Wil
_____________________________________________________
Visit the VMware developers wiki at http://www.vi-toolkit.com
Hey Wil, hopefully I don't run into those issues you've described ... I guess I can consider myself lucky I just get the the form hast been processed yada yada ya.... haven't seen any issues with the version count or content being destroyed (knock on wood)
I got a new VMTN document hoping to publish tonight, so hopefully no issues ... though I know I'll have to play persistent game with the "publish" button tonight
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
http://twitter.com/lamw
If you find this information useful, please award points for "correct" or "helpful".
I got a new VMTN document hoping to publish tonight, so hopefully no issues ... though I know I'll have to play persistent game with the "publish" button tonight
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/
vGhetto Script Repository
http://twitter.com/lamw
If you find this information useful, please award points for "correct" or "helpful".
William,
Well no worries, they are just using my doc for reproducing the issue.. and really that's OK as they have to be able to reproduce and test it in order to resolve.
As for version count, well i hope it can be corrected afterwards and if not, well not a big deal. It just looks a bit odd to see that many revisions on the document, on the good side of things it does mean it gets bumped up all the time
(There's always some advantage somewhere)
The content cannot really be destroyed as there's versioning on the document, so it is always possible to go back to version 12.
Well -at least in theory- as it doesn't work for me LOL
Hope your persistence publish game will be a quick one!
--
Wil
_____________________________________________________
Visit the VMware developers wiki at http://www.vi-toolkit.com
Well no worries, they are just using my doc for reproducing the issue.. and really that's OK as they have to be able to reproduce and test it in order to resolve.
As for version count, well i hope it can be corrected afterwards and if not, well not a big deal. It just looks a bit odd to see that many revisions on the document, on the good side of things it does mean it gets bumped up all the time
(There's always some advantage somewhere)The content cannot really be destroyed as there's versioning on the document, so it is always possible to go back to version 12.
Well -at least in theory- as it doesn't work for me LOL
Hope your persistence publish game will be a quick one!
--
Wil
_____________________________________________________
Visit the VMware developers wiki at http://www.vi-toolkit.com