Community
Showing results for 
Search instead for 
Do you mean 
Reply

ACT 17 and Office 2016

Accepted Solution Solved
New Member
Posts: 26
Country: United States
Accepted Solution

ACT 17 and Office 2016

What is the compatibility of ACT Pro  17 and Office 2016 (combined with Windows 10 if anyone knows).

 

  I am always scared to update because I don't have time to be an IT guy when I have sales and marketing  to do.

 


Accepted Solutions
Solution
Accepted by topic author Synimagic
‎10-14-2015 07:29 AM
Administrator
Posts: 4,024
Country: United_Kingdom

Re: ACT 17 and Office 2016

Hi Synimagic,
Please check the following Knowledgebase article for info on Office 2016 compatibility:
http://kb.swiftpage.com/app/answers/detail/a_id/38203

View solution in original post


All Replies
Solution
Accepted by topic author Synimagic
‎10-14-2015 07:29 AM
Administrator
Posts: 4,024
Country: United_Kingdom

Re: ACT 17 and Office 2016

Hi Synimagic,
Please check the following Knowledgebase article for info on Office 2016 compatibility:
http://kb.swiftpage.com/app/answers/detail/a_id/38203
New Member
Posts: 26
Country: United States

Re: ACT 17 and Office 2016

Thank you.

New Member
Posts: 26
Country: United States

Re: ACT 17 and Office 2016

OK I tried this on a non critical machine.   I am using the Demo database.

 

I installed ACT 17, then the SP2 update, then the SP2 Hotfix 0

 

It loads but when I hit the email button in toolbar - I get message: Retrieving the COM class factory for component with CLSID ... failed due to the followinig erro --  80040154  Class Not Registered - HRResult - 0x80050154

 

It does record history when I initiate an email from Outlook.

 

When I use thje WRITE / LETTER  it works.

 

Any ideas:

 

Thanks

 

Jeff

New Member
Posts: 26
Country: United States

Re: ACT 17 and Office 2016

Update: I installed the Act-Outlook batch file (had to run as adminsitator) as indicated in http://community.act.com/t5/Act/Error-Message-80040154/td-p/1628

 

I am still getting that error.  I rebooted and tried running ACT in Administrator

Administrator
Posts: 4,024
Country: United_Kingdom

Re: ACT 17 and Office 2016

Hi Jeff,

We'd have to investigate this further. Please call us on 866 873 2006 and speak to one of our support technicians.
New Member
Posts: 26
Country: United States

Re: ACT 17 and Office 2016

So this is still not working.,

 

I talked to two Swiftpage techs who dialed in to my computer who worked on it for about two hours.

We tried doing an Office Refresh

I did a clean uninstall (using RevoUninstaller) of Microsoft Office 365 and ACT and SQL Server

   still have to hunt and peck for leftovers using info in a KB

I tried the ACT-Outlook batch file somewhere here

I tried to the CLSID batch file on this board.

I have tried running as administrator, disabling a Windows Firewall,, adding Act 17 SP2 and Hot Fix 0 

 

Getting frustrated and scared to upgrade a mission critical machines.

 

Incidentially, I tried accessing a database on a server, and it still fails.

 

 

Moderator
Posts: 68
Country: United_Kingdom

Re: ACT 17 and Office 2016

The most common fix for this can be found here: http://kb.swiftpage.com/app/answers/detail/a_id/23311/kw/com%20class

It basically involves re-registering the redemption.dll file or in some cases replacing it entirely.

 

If this makes no difference, another possibility is running both Act and Outlook as Admin. I no in your previous post you mentioed running as admin but I just wanted clarify that both Act and Outlook are being run as Admin.

 

Hopefully this helps. Let me know otherwise.

 

Peter

New Member
Posts: 26
Country: United States

Re: ACT 17 and Office 2016

Opneed both ACT 17 and Outlook 2016 in admin mode and got the same error.

 

When I tried the iix above regsvr32 redemption.dll - it doesn't give me an error but doesn't give me a confirmation like the KB says it should... could that be the problem.

Moderator
Posts: 68
Country: United_Kingdom

Re: ACT 17 and Office 2016

If it doesn't say successfully registered or give you the error then it could be a problem.

Did you replace the dll file with the one on the KB and try registering that?

 

Peter