06-26-2017 06:45 AM
Issue: When selecting "Send invitation e-mail" under Schedule Activity, the a Creating Outlook Invitation window appears, as depicted in the attached screen shot.
This is the second functionality of ACT that I have documented in this Community requiring a shut down of ACT.
4. A cursory view of the knowledge base after searching "send invitation e-mail show that this issue dates to 2010.
Obviously, given that this issue dates back to 2010 and this issue continues to the present version, Swiftpage has not resolved this issue over multiple
version upgrades over the past 7 years.
QUESTION: What is the final resolution of this issue such that I can try to use ACT! rather than fix it?
06-26-2017 07:22 AM
We'll need to perform a few troubleshooting steps first of all, as this particular error scenario does not match any of the current known issues we're tracking in this area.
Could you please:
06-26-2017 10:02 AM
First, many thanks for the fast response.
Second, you taught me something new today - Windows Logs.
I uploaded my Events Log. Is this what you need?
Is this what you need?
Many Thank Yous.
I am stuck again with this issue for about 20 minutes. I have to shutdown ACT for the second time today.
06-27-2017 02:10 AM
I'm afraid the error log you've provided is a little too verbose for me to follow. Ideally could you please do the following:
Are there any events after this time? If so, take a quick screenshot of the General tab of each one.
Another couple of questions:
06-27-2017 06:01 AM
This AM the Send Invitation e-mail functionality has worked well. My observation is that this functionality ceases to function sporadically, but with sufficient consistency as to be highly problematic.
When the issue occurs again then I will provide the information that you request.
No, I do not run ACT or Outlook as an Administrator. ACT is run as an Administrator only for the purpose of an Update.
Thank you for your help. It is greatly appreciated, most sincerely.
08-05-2017 07:25 AM
I started this thread on 06/26/2017. The issue persists.
Creating an ACT Activity with Send Invitation E-Mail to Outlook often times results in ACT getting hung up creating the Outlook invitation e-email with the ACT window showing that it is creating the email with the blue dots moving perpetually from left to right. The only way to go back to work using ACT is to shut down ACT.
Erasing from ACT an Activity using Send Invitation E-Mail but the Outlook Calendar invitation had been previously deleted results in ACT launching the window: Deleting Outlook Invitation Finding Corresponding Outlook Invitation to delete…. with blue dots moving perpetually from left to right. The only way to go back to work using ACT is to shut down ACT.
I have identified any number of ACT issues, the sole resolution that I can determine is either:
Is the sole final resolution that Swiftpage hast to offer to us paying customers is either to shut down ACT or the device?
08-07-2017 03:34 AM
This issue has popped up a few times and in cases different ways, it presently is an issue we are tracking with the newer builds of Outlook.
A workaround I have seen work is to ensure that Act and Outlook are connecting correctly by going to 'Write > Email message' making sure that Outlook opens a message. while I believe this has something to do with the NormalEmail.dotm template and recreating it may also help (renaming it to .old from this location: C:\Users\USERNAME\AppData\Roaming\Microsoft\Templates) it is still presently under investigation.
08-09-2017 12:47 PM
I've had this issue for several months. Creating an activity and checking the 'send activity email' crashes ACT!. Accepting an email activity from someone crashes Outlook. It's highly annoying.
08-10-2017 09:07 AM
Were you able to test the work around I provided in my previous post? If it does not work would you be able to provide on the Versions of Act! and Office
08-12-2017 06:15 AM
Should I be experiencing this issue in this environment, an environment previously certified to me by Swiftpage as the environment to use, having spend hours and hours resolving another issue: