View Single Post
Absintheminded78
Member
 
Join Date: Jan 2016
Location: Sydney, Australia
Posts: 48

Old April 20th, 2017, 11:33 PM
Quote:
Originally Posted by davidp View Post
I suspect this issue may be due to some sort of corruption with your .NET Framework install on that computer. Several things to try:

1) Try and re-install the .NET Framework 4.0. An installer is available from here:

https://www.microsoft.com/en-us/down....aspx?id=17718

2) If that doesn't work or fix things, try this tool:

https://www.microsoft.com/en-us/down....aspx?id=30135

3) If that doesn't work, try the directions from this answer:

http://stackoverflow.com/a/29078807/618428

In a recent release of Realm Works, we started using a part of .NET that we hadn't used before during the import process. Some users have been having a problem with this that appears to be some sort of corruption of the .NET Framework on the computer.
Interestingly none of the above worked but I noticed in the third option someone referenced a registry key so I cleaned up my registry and bingo, imported ok

Thanks for the help.

Last edited by Absintheminded78; April 20th, 2017 at 11:34 PM. Reason: Spelling
Absintheminded78 is offline   #55 Reply With Quote