Windows 10 with a .Net Framework 3.5 problem?

I have a lawyer client who's having a problem with a 3rd party program, CaseMap, and .Net Framework 3.5.

His Windows 10 computer was a free upgrade from Windows 7, and is attached to a Server 2012 R2 domain.

When he tries to do a search in CaseMap he gets an error from CaseMap telling him there's a problem with .net 3.5.

I've done various uninstalls and reinstalls of .net 3.5 to no avail. CaseMap has also been uninstalled and reinstalled multiple times, including the last time allow it to reinstall .net 3.5. None of this has worked!

CaseMap tech support has told my client to reinstall Windows 10. This of course would be expensive because the free Windows 10 upgrade is no longer available, plus there'd be my time to basically setup a new computer.

I've attached CaseMap error message DotNet.jpg, and the detail, DotNet2.jpg.

BTW, I know nothing about CaseMap, so my client, a very computer knowledgeable guy, takes care of the CaseMap installations and talking to their tech support.

Am I certain it's not really a CaseMap problem? Of course not!

We've run out of ideas, and would appreciate any suggestions.

Thanks

Mark
DotNet1.JPG
DotNet2.JPG
markperl1Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ashok DewanFreelancerCommented:
Install both programs run as administrator.
Make sure to uninstall pre-installed CaseMap with it's setup files not from program and features
1) After Installation the .net 3.5 framework, go to program and features and turn on the feature from there.
https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10
 
2) Set CaseMap compatibility to Windows 7 or windows XP after installation of CaseMap. You set it by right click and going to properties.
3) Check both version 32 bit as well as 64bit of CaseMap. May any of them work. But not install them together.
0
markperl1Author Commented:
Ashok

OK will give that a try. It's the Friday night here, so it will be a couple of days before we can try it.

Thanks
Mark
0
RaminTechnical AdvisorCommented:
Download this file file:
http://www.mediafire.com/file/gaflwfg9tth889o/microsoft-windows-netfx3-ondemand-package.cab

Copy it to the root of your Windows partition, probably C:\
Open a command prompt as Administrator

Copy below line and paste it to Command prompt:
Dism.exe /Online /Enable-Feature /FeatureName:NetFX3 /source:C:\ /LimitAccess
Hit Enter.

If none of above suggestions worked then Reset / Reinstall Windows,  then enable.net 3.5 before installing any updates.

                                                                                       * * * * *

Try  Windows 10  Repair Install with an In-place Upgrade. you can keep all your programs and settings and will not lose anything.

    Go to the Windows 10 Media Creation Tool from this link:
https://www.microsoft.com/en-us/software-download/windows10
 
Click on Download Tool Now, save it on desktop,  then run it as Administrator, accept license agreement, then Choose Upgrade This PC Now, let Windows to Update drivers. make sure that Keep Personal Files and Apps  is Selected  and let the Windows do the rest.

Note: The Procedure takes at least one hour.
1
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Obaid ur RehmanTechnical and Operations ManagerCommented:
Hello Mark,

Get more info from the Event Log to get further insights of the issue.

EOleSysError is the exception class for errors that occur during an attempt to invoke a method or property of an OLE automation object. When the IDispatch Invoke method fails, EOleSysError is raised. Objects invoked through IDispatch can return the error code—an OLE status code or SCODE—indicating the reason for the error.

It could be related to the security policy settings for COM during upgrade. If you have KB3206632 (https://support.microsoft.com/en-us/help/4004227/windows-10-update-kb3206632) installed, please uninstall it and then check.
0
Hello ThereSystem AdministratorCommented:
First I suggest you to go to Programs and Features -> on left there is Turn WIndwos features on or off ->
a) .NET 3.5 is selected: untick -> OK -> tick it back
b) .NET 3.5 is not selected: tick -> OK
0
JohnBusiness Consultant (Owner)Commented:
Download, install and run .NET Framework Setup Verifier.

This checks and repairs the .NET Framework (all versions to 4.7.1)

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
0
markperl1Author Commented:
I'll work on the low hanging fruit first.

To: Hello There
Thanks, but have already tried that to no avail.

To John Hurst
Here's a snip from the .NET Framework Setup Verifier you suggested:
[01/13/18,08:43:33] Install state for .NET Framework 3.5: installed with service pack 1.
[01/13/18,08:43:33] Install state for .NET Framework 4 Client: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4 Full: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.5: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.5.1: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.5.2: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.6: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.6.1: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.6.2: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.7: installed with no service packs.
[01/13/18,08:43:33] Install state for .NET Framework 4.7.1: installed with no service packs.
[01/13/18,08:43:33] Not adding product '.NET Framework 1.0' because it is not currently installed
[01/13/18,08:43:33] Not adding product '.NET Framework 1.1' because it is not currently installed
[01/13/18,08:43:33] Not adding product '.NET Framework 1.1 SP1' because it is not currently installed
[01/13/18,08:43:33] Not adding product '.NET Framework 2.0' because it is not currently installed
[01/13/18,08:43:33] Not adding product '.NET Framework 2.0 SP1' because it is not currently installed
[01/13/18,08:43:33] Not adding product '.NET Framework 3.0' because it is not currently installed
[01/13/18,08:43:33] Not adding product '.NET Framework 3.0 SP1' because it is not currently installed
[01/13/18,08:43:33] Not adding product '.NET Framework 3.5' because it is not currently installed

I found it a bit confusing because first it said it was installed, then it said it wasn't?

It's definitely a problem on this workstation, since the others in the office work just fine.
0
JohnBusiness Consultant (Owner)Commented:
We have mentioned Repairs earlier here.  Try a non-destructive Windows 10 Repair Install to correct this. Keep Everything.

https://www.microsoft.com/en-us/software-download/windows10

Windows 10 is running, so click on the Download button (not Upgrade Button, select Open (Run) but NOT Save. Allow the program to run. Allow drivers to update. Then select Keep Everything.
0
markperl1Author Commented:
Yes, thought that might be the next step. It'll take me a day or so to report back.

Thank you!
0
Hello ThereSystem AdministratorCommented:
Using dism.exe should solve your problem if you have the ISO: dism.exe /online /enable-feature /featurename:NetFX3 /Source:D:\sources\sxs /LimitAcces
without ISO: dism.exe /online /enable-feature /featurename:NetFX3 /all
0
markperl1Author Commented:
Will work on this on Saturday and report back.

Thank you to all who've contributed to date!

Mark
0
markperl1Author Commented:
To Hello There & Ramin
I just tried the DISM .net 3.5 installation to no avail.

To Ramin & John Hurst
I just tried the Windows 10  Repair Install with an In-place Upgrade, but still get the CaseMap/.net 3.5 error. I ran this after I'd just tried DISM installation, so .net 3.5 was still installed when I did the Repair Install. Should I try it again, but after I remove .net 3.5 through Windows Features?
0
JohnBusiness Consultant (Owner)Commented:
You might give it another try. After that, do Windows Updates again. Then try re-adding .NET 3.5 via Windows Features.
0
markperl1Author Commented:
John

In an earlier post Ramin suggested enabling .net 3.5 BEFORE doing Windows Update after the Repair Install, and you're suggesting to do it AFTERwards.

????????
0
JohnBusiness Consultant (Owner)Commented:
You said "Should I try it again, but after I remove .NET 3.5 through Windows Features? "  So I was responding to that. I thought it could be reasonable approach, although I have not had to do this.
0
markperl1Author Commented:
Misunderstanding...

I was referring to the sequence of adding the .net 3.5 after the Repair Install...before or after doing Windows Update.

You said, "After that, do Windows Updates again. Then try re-adding .NET 3.5 via Windows Features."

Ramin said, "...Reset / Reinstall Windows,  then enable.net 3.5 before installing any updates."
0
JohnBusiness Consultant (Owner)Commented:
Try the repair install and then ensure .NET is there and working.
0
markperl1Author Commented:
OK. Thanks

Will be outa town for a bit, so it may be a week or so before I can get back to my client to try again.
0
markperl1Author Commented:
Through Windows Features I uninstalled .NET 4 and 3.5, then did another Windows 10 repair install. After repair installation was complete, reinstalled all .NET versions through Windows Features.

Received the same error as reported initially when trying to Search within CaseMap. CaseMap thinks .NET 3.5 is not installed.

.NET Framework Setup Verifier log was the same as reported in an earlier post. I still don't understand these 2 lines:
Install state for .NET Framework 3.5: installed with service pack 1.
Not adding product '.NET Framework 3.5' because it is not currently installed

????????

Thanks
Mark
0
JohnBusiness Consultant (Owner)Commented:
At this point, you need to run Windows 10 Repair Install and Keep Everything.
0
markperl1Author Commented:
John

I've run 2 Windows 10 Repair Installs.
The first was with with .NET 3.5 and 4 already installed. The second was with .NET 3.5 and 4 uninstalled.

Given the 2 Windows 10 Repair Installs I've already done, I don't understand your "Keep Everything" suggestion or even the necessity of running another Repair Install.

BTW, each of these Repair Installs takes over 2 hours.

Mark
0
JohnBusiness Consultant (Owner)Commented:
If you have done the repair, your only option now is to back up and reinstall Windows. .NET Framework works fine in a proper Windows 10 machine.
0
RaminTechnical AdvisorCommented:
And before installing any Windows update install that 3rd party program, CaseMap.
0
markperl1Author Commented:
Windows Feature says it's there, but is there a way to ensure .NET 3.5 is working?
0
JohnBusiness Consultant (Owner)Commented:
Did you try the .NET Framework Setup Verifier further back here?  That will tell you if it is installed and working (and make corrections at the same time).
0
markperl1Author Commented:
John

Please check my earlier posts. I've run the Verifier a couple time with the same results, results I've found confusing. The I read the results, they seem to say it's installed, but later on that it's not. I've asked about this, but never received a reply.

Thanks
Mark
0
JohnBusiness Consultant (Owner)Commented:
If you have done all this and a couple of Repair Installs and nothing is working, you need to back up and reinstall Windows.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
markperl1Author Commented:
Yes, no other choice than to reinstall Windows 10.

Thank you to all who chipped in!

Mark
1
JohnBusiness Consultant (Owner)Commented:
You are very welcome and I was happy to help you with this.
0
markperl1Author Commented:
And I REALLY appreciated you sticking with me John! :-)

None of us can do ALL of this on our own, and it helps all of us to know there's always someone to whom we can reach out.
0
JohnBusiness Consultant (Owner)Commented:
Thanks again and I am usually around here to help people.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.