EricL Posted January 17, 2014 Share Posted January 17, 2014 I was in the middle of typing up a sort of report on this error but I figured it out. I tried all of the things suggested in the pinned threads but they didn't mention to UPDATE THE.NET FRAMEWORK even after doing a repair/reinstallation.I hope this saves some people time! I tried all of the other solutions first. heh. My exact error is attached as a jpg image. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.