Here I am back again with the same problem, not being able to publish (for the web.)
I have installed the latest update: 7, 1509.1408. After having restarted my PC. Made no difference.
I need to publish this to the web so my client can install the project on their web site. Shall I again ask some kind soul in the community to publish it for me and send me the results back?
1. I have opened a support case on this, and they have published my project for me. Thanks Wendy anyway for your help!!
2. I have followed ALL the recommended steps, including the repair steps. So uninstalled everything, ran that batch file, etc. etc. Restarted my PC who knows how many times per the instructions. Even re-installed the .NET framework. I just tried to publish and it fails once again.
There is no polite language that will let me fully express the frustration of doing such time-consuming repair work only to find that it only MIGHT fix the problem --- it seems on Round 1 I got lucky, on Round 2, not so much.
So, shall I keep sending my projects to Articulate to be published?
The software keeps telling me it is sending error messages to Support. How about if someone at Articulate were to actually look at these messages and try to fix the software defect? If that is happening, I have not received any communication to that effect. I have sent this same sentiment to Support as well.
I understand Arthur and yes, you are always welcome to continue working with support although hopefully it would be to get you in working order :)
In regards to error messages that are sent out, those are sent to our development team, but are not tied directly to a user. You would not get direct feedback on that. That is why we advise working with support so that they can look at log files if needed or the error you are receiving and further assist you from there.
4 Replies
Can you attach the .story file Arthur
Hi Arthur! Looks like Wendy has popped in to assist you here.
If you are having difficulties again, I would advise that you conduct the repair as Ashley shared in this thread with you.
Here is an update:
1. I have opened a support case on this, and they have published my project for me. Thanks Wendy anyway for your help!!
2. I have followed ALL the recommended steps, including the repair steps. So uninstalled everything, ran that batch file, etc. etc. Restarted my PC who knows how many times per the instructions. Even re-installed the .NET framework. I just tried to publish and it fails once again.
There is no polite language that will let me fully express the frustration of doing such time-consuming repair work only to find that it only MIGHT fix the problem --- it seems on Round 1 I got lucky, on Round 2, not so much.
So, shall I keep sending my projects to Articulate to be published?
The software keeps telling me it is sending error messages to Support. How about if someone at Articulate were to actually look at these messages and try to fix the software defect? If that is happening, I have not received any communication to that effect. I have sent this same sentiment to Support as well.
-Arthur
I understand Arthur and yes, you are always welcome to continue working with support although hopefully it would be to get you in working order :)
In regards to error messages that are sent out, those are sent to our development team, but are not tied directly to a user. You would not get direct feedback on that. That is why we advise working with support so that they can look at log files if needed or the error you are receiving and further assist you from there.
Thanks for the update Arthur.
This discussion is closed. You can start a new discussion or contact Articulate Support.