09-18-2015 03:42 AM
I tried many attempts to find out the cause of the Documents Tab recreating on another drive and to see if act.shared.win32.dll is the only cause.
A. I recovered my backup 8.1 to another drive, then installed Windows 10 to see ACT was working fine and not even have to gac the DLL.
B. My other drive I tried every possible means to make the DLL assemble and came up with one way that I and others initially were unable to remove it with /U switch. I attached screen shot of results so /u then /i worked with no errors but ACT 15.1 Prem still has problem. I even uninstalled and reinstalled ACT no difference.
I pose the question is there another DLL because I don't think this is the only one that could be damaged.
I tried Regsvr32 just to see if it would help, not and in fact I got warning that it did not work.
09-18-2015 06:03 AM
Thank you for the feedback and screen shots. I am going to provide this information to the Act! Development team for further testing and check if any other solutions are available.
09-18-2015 11:02 AM
I have Win 10 on drive A that had a slight different running state of 8.1 than drive B before I upgraded them both to Win10.
Drive A is my standard HGST disc drive that ACT Documents work.
Drive B is my Samsung SSD 840EVO where Documents tab is crashing.
I tried to compare file difference and registry differences but if Developer have suggestion or what copies let me know or areas to check.
I am at the point in spent time where I may just backup Drive A (so we can look back compare differences) do a restore of my Sept 2014 Win 8.1 to it then go straight installing Win 10 upgrade from my CD with the Network disconnected (like I did on drive A that ACT works. For B I had network cable established and I think the stages doing a network download of Win10 to my CDROM upgrade looked or acted different. Through all this pain staking trails that is the only major difference in the two drives, upgrade form CD as far as I can till all is done then connect network let win10 do its update then see if ACT still works.
09-18-2015 11:16 AM
This is interesting. I know as a user I am spending far too much time. Here is my situation just in case it helps the developers a bit further.
Our database resides on a shared drive (raid) on our Windows Server 2012 Essentials. That drive is mapped as drive F: on all of our client machines. (It is important to have the same drive letter on all machines or your customizing will fall apart).
All client machines are now Windows10 Pro. There are 4 of those and they are ALL crashing when using the doc tab.
They are ALSO ALL CRASHING (same cause?) when trying to CREATE CUSTOM COMMAND or CUSTOM MENU.
Using ACT! on my laptop with Windows10 Home and SSD hard drive and the database local on the same C; Drive: CRASHING
Using ACT! on same laptop with Windows10 Home and an attached hard drive hosting the database files mapped as drive F: also CRASHING.
Using ACT! on yet another laptop, also Windows10 Home as above ALSO CRASHING.
Using ACT on any Windows 7, 8 or 8.1 machine working fine.
Developers may look at the custom command to see if there is a common link of cause to the doc tab.??
PLEASE Swiftpage FIX OUR ACT! (swiftly)
09-22-2015 11:57 AM
Past few days I've ran more tests/checks and simplified it to one Drive and when I want to repeat test I go back to a backup that has Win8.1 that was upgraded to Win10 from CDROM AND! I had NOT selected (opened) Windows Settings yet. so ignore past post working with few drives.
1. When I restore my backup of Win10 and start ACT! I have no problem with Documents. ACT document test will crash after I had first selected SETTINGS to view what updates were applied even with no Netwrok access to prevent future updates.
See attached screen capture of the Security updates.
2. I found even in another backup recovery with only Win8.1 the gacutil /i will not remove act.shared.win32.dll. So this problem is before Win10 update. I have noticed when ACT crashes in the Event log a couple of sever Errors one being with KERNELBASE.dll.
3. I did not have antivirus installed or Firewall on so that can't be an issue.
4. Can't reduce recovery time to start test over when ACT is OK using Create Restore Point (Control Panel/System/ System Protection Tab) because my backup copy shows disabled. Even if I did have a good one it seems not Only opening SETTINGS but opening System Protection will then kill ACT documents from working.
5. just for grins I then ran my Toshiba Laptop Service Station program to located as well as I doing manually check for all Win10 updates. After running Win10 update untill all were applied. No help for ACT or Gacutil.
I hope this helps narrow down things since I'm am not verse with gacutil and why even as Admin unable to get this to work to then see if the Document Tab issue is due to the Assembly of dll.
If you like the event log errors let me know I can only screen capture don't see how to save it to a file, unless there is another way?
It would be good to get survey those that fail did they do a Win10 update or clean install and which method update from Disc, from MS download, or downloaded from a shared PC on network. This is how MS lowers their bandwidth downloads of win10 by automatically sharing the installer on a network which I wonder how do they control what installer verison is on PC's.
09-25-2015 12:12 PM
Are you going to fix the problems with ACT! crashing while trying to use Documents tab and Custom Menu tab? I mean in a reasonable time?
Or should I contact your sales department and ask for a refund? I have heard nothing from Swiftpage and feel we are simply being ignored at this time.
I need a working IT environment for my business to run. ACT! is fizzling out in that part right now.
09-25-2015 12:39 PM
Was at our Act user group meeting lead by a certified consultant who also has the same two issues. He has an Apple PC with Parellels to switch into any Win OS and ACT version for trouble shoot. He had to go back to Win8.1 till ACT testers try every environment setting to recreate it. Which is what I've been doing. Interestingly the gacutil /u does not even work on my Win 8.1 PC. If that is what is working for those few with Win 10, I bet it would work if they were originally an 8.1 upgraded to Win 10. I plan on trying some others things like my UEFI, GPT, boot strap ect since I setup my SSD by cloning the Toshiba drive that happens to have all the partions for OS recovery.
If there are some V15 and up working on Win 10 it has to be how we upgrade from 8.1 or a security policy that changed in Win10.
09-25-2015 12:52 PM
The Act! Development team has created a Hot Fix related to the Documents Tab and Act! V17.2, Act! V 17.1, Act! V17.0 and older. Please see the article listed below for details and the download links.
09-25-2015 11:51 PM
In your latest post which only change to the KB# suggests from ACT create the crash/shutdown then run the steps. I still having problems for my ACT Prem V15.1 Win 10. I had to CMD as Admin for gacutil /i to work.
I request clarifiction if I should not have to be in Admin why is that required.
On another boot drive with Win 8.1 to run a test I had to start cmd as admin as well for for gacutil /i
See attached screen shot of what happens because only when I click on close Program ACT will but not on its own.
I guess for V17 and older there is no patch file, but what to do with DocTabfix.exe?
09-26-2015 01:10 PM
Thank you so much for all you are doing here. I spent a lot of time, but must focus on acutally running my business. Lets hope these things get all sorted out soon so we can back to the old normal.