I was wondering if I could get some help with an issue I'm having with Engage.
I've inserted some Engage interactions, but when I try to edit from Presenter, I get a pop up that says that Presenter was unable to open the project file (I've attached a screenshot below). I can, however, access it directly through Engage.
Any suggestions on what I should do or help with what I can do to fix this?
Are you working with files on any external sources (USB drive, network drive, etc.), by any chance? First, try to make sure that you're working with local files.
Here's some additional information:
If you are experiencing unexpected issues using Articulate software, here are some tips for managing your files which can help prevent issues.
1. Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior.
2. You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
3. Avoid using special characters, accents or symbols in your file names.
Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the followingMicrosoft article.
______________________________________________
If the files are local, are you able to create a new, blank Engage interaction and edit it through Presenter?
Thanks very much for getting back to me and for the additional information.
I just wanted to see if we could narrow it down and it looks like we have. I wasn't sure if it was an issue with the file itself, or if the problem lies within Presenter or PowerPoint.
Do you know what version of Office/PowerPoint you have installed? We'll want to make sure that you're using the 32-bit installation of Office and not the 64-bit installation. If you need help finding this, just let me know.
I knew you were going to ask me that! I should have written it in the last thread - sorry!
I'm using Office/Powerpoiint 2010, and it is indeed the 32-bit installation. I'm on Windows 7 Professional. I hope, I hope, I hope it's not the file. eek!
No problem! And don't worry, I don't think it's the file, at all. If it's opening through Engage itself, it should be OK.
If you're able to, please take a look at this knowledge base article and follow the steps outlined for Windows 7 (should be the second section in the list).
Let me know if the issue continues after taking the steps in the article.
Thanks for getting back to me, I appreciate the update!
I'm very happy to hear everything seems to be working now. However, if you do continue to experience crashing, please let us know. Perhaps our support team can help resolve that issue, if it becomes a nuisance.
8 Replies
Hi Lauren,
Are you working with files on any external sources (USB drive, network drive, etc.), by any chance? First, try to make sure that you're working with local files.
Here's some additional information:
If you are experiencing unexpected issues using Articulate software, here are some tips for managing your files which can help prevent issues.
1. Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior.
2. You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
3. Avoid using special characters, accents or symbols in your file names.
Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the followingMicrosoft article.
______________________________________________
If the files are local, are you able to create a new, blank Engage interaction and edit it through Presenter?
Thanks!
Hi Christine,
Thanks for the quick reply!
Nope, I'm not working off an external source. To be more precise:
1. I'm working off my C: drive.
2. The path and output are fewer than 260 characters (71 to be exact).
3. There are no special characters, accents or symbols in my file names
I cannot create a new, blank Engage interaction through Presenter (I get the same popup), but I can through Engage.
Any suggestions? Thanks!
Hi Lauren!
Thanks very much for getting back to me and for the additional information.
I just wanted to see if we could narrow it down and it looks like we have. I wasn't sure if it was an issue with the file itself, or if the problem lies within Presenter or PowerPoint.
Do you know what version of Office/PowerPoint you have installed? We'll want to make sure that you're using the 32-bit installation of Office and not the 64-bit installation. If you need help finding this, just let me know.
Also, what version of Windows are you running?
Thanks!
Hi Christine,
I knew you were going to ask me that! I should have written it in the last thread - sorry!
I'm using Office/Powerpoiint 2010, and it is indeed the 32-bit installation. I'm on Windows 7 Professional. I hope, I hope, I hope it's not the file. eek!
Thanks again...
Hi Lauren!
No problem!
And don't worry, I don't think it's the file, at all. If it's opening through Engage itself, it should be OK.
If you're able to, please take a look at this knowledge base article and follow the steps outlined for Windows 7 (should be the second section in the list).
Let me know if the issue continues after taking the steps in the article.
Thanks Lauren :)
Hi Christine,
Thanks so much! I'm waiting for IT to perform these steps. I'll let you know how it goes!
Lauren
Everything seems to be working well, now, except for a bit of freezing every now and again. Thanks so much for your help!
Hi Lauren!
Thanks for getting back to me, I appreciate the update!
I'm very happy to hear everything seems to be working now. However, if you do continue to experience crashing, please let us know. Perhaps our support team can help resolve that issue, if it becomes a nuisance.
I hope you have a great day, Lauren!
Christine
This discussion is closed. You can start a new discussion or contact Articulate Support.