10-09-2014 11:37 AM - edited 10-09-2014 11:38 AM
ACT!v16 Pro - Outlook 2013 error msg = sorry we're having trouble starting outlook when outlook is already running.
If outlook is not already running, I dont believe my customer gets this error message?
I'm guessing but he may have initially installed outlook2013 for web? then possibly realized he needed the outlook 2013 desktop and installed it? just guessing but what is a resolve please? - No info in the knowledgebase that I could find.
10-10-2014 06:55 AM
If you could please answer my following questions.
First of all i think ther is no old version of outlook visible in the control panel?
Does the Outlook run before the installation of Act!?
Is there anything strange at the Windows Event viewer?
Could you please try to get Outlook working in the safe-mode.
10-10-2014 07:26 AM - edited 10-10-2014 07:29 AM
Thanks for the response.
Not able to understand some of your questions.
Office was installed before ACT!v16 pro.
No change running outllook 2013 desktop in safe mode.
Is there anything strange with Windows Event Log? = YES, it is freekin windows 8.1 or 2? Not looked at the os event log yet.
Have limited time to get on the pc to work on issue remotely and his internet speed is too slow for my remote assist connection.
This is the 2nd time I tackled this issue. He just leaves outlook2013 desktop closed when he is using ACT!v16pro.
I know others have mistakenly installed office 365 online version before they discovered they needed the desktop version instead for ACT!v16 pro...
So because of that, windows thinks there are two versions of outlook installed when the desktop is running and ACT! tries to send a email..
I provided the exact ACT! error message and Swiftpage needs to address the prob in the knowledgebase please..
I fear that the resolve is to do full uninstall of ACT! and MS Office, then do it all over again. Sorry won't happned by my hands.
No other prior versions of ACT! or Office has been installed on his pc.
Later today I plan to install Service Pack 2 to see if that resolves issue.
If servc Pak2 does not resolve issue, I plan to delete preferences.
Any other ideas welcome. thanks again FSBill
10-10-2014 08:26 AM
Try closing Outlook and check the Processes with Task Manager and end any processes for Outlook.
10-10-2014 09:44 AM - edited 10-10-2014 10:22 AM
Thanks for the input Roy,
I think I found the cause but still not sure of resolve?
I noticed user had Microsoft ... Click-To-Run installed on the pc.
Below info is probable cause - but how do I resolve?
cus ACT!v16 Pro will not work with Outlook2013 according to act kb article, if it was instaled via MS Click-To-Run...
How to: Verify Whether Outlook Is a Click-to-Run Application on a Computer
Supported Versions of Microsoft® Office by Version of Act!
There appears to be a way to configure click-to-run in a way that will exclude or remove elements but I know nothing about this newer version of office 2013 and 365 and afraid to test it. Not sure if that will free up the conflict or create bigger mess.
Not sure what all he re-installed to not use click-to-run?
The User confirmed that he contacted microsoft and they sent him procedures to resolve, but it sounds to me like he should have un-installed the MS Click-To-Run stuff? then installed the non-click-to-run version of office 2013? I have not seen the info he received from MS yet.
Any idea as to easiest solution?
Thanks - FSBill
01-16-2015 11:55 AM
An Act! support tech showed me something that worked. I had the issue on a new Win 8.1 machine after installing Act! v17 Pro. I routinely disable UAC, but the tech said that sometimes it doesn't quite update in the registry. He said go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and change the REG_DWORD for EnableLUA from 1 to zero, then restart the system. It worked for me.