Enterprise Guided 7.1 fails to start on windows 7 with .NET framwork 4 right after the installation

[yzhou2004]

Does anyone experience the same issue?

[CaseySmith]

This sounds like an issue Technical Support could help with, but out of curiosity, what error are you getting?  Or, are you not getting an error at all?

By the way, Enterprise Guide 7.1 requires .NET Framework 4.5.1, so one thing to check would be to confirm .NET Framework 4.5.1 is installed (though it should have been done by the SAS Deployment Wizard if necessary).

[yzhou2004]

Thanks for the response.  So far SAS tech support is slow to respond.  That's why I am coming up here in case someone knows a fix.

Here is the error message:

SAS Enterprise Guide 7.2 Stops working:

Details:

Problem signature:

  Problem Event
Name:                      
CLR20r3

  Problem Signature
01:                     
seguide.exe

  Problem Signature
02:                     
7.100.0.0

  Problem Signature
03:                     
5418b0bd

  Problem Signature
04:                     
mscorlib

  Problem Signature
05:                     
4.0.0.0

  Problem Signature
06:                     
53b4fc1e

  Problem Signature
07:                     
1205

  Problem Signature
08:                     
9f

  Problem Signature
09:                     
System.TypeLoadException

  OS
Version:                                        
6.1.7601.2.1.0.256.4

  Locale
ID:                                           
1033

  Additional Information
1:                
3df5

  Additional Information
2:                
3df579d950b7f28c0ab9deea9d9f2f8f

  Additional Information
3:                
2996

  Additional Information 4:
29962f9f28f9983b5fd3d83aec299389

[CaseySmith · Accepted solution]

Yes, that error looks like an issue with the .NET Framework installation.  I recommend downloading and installing .NET Framework 4.5.1 (Download Microsoft .NET Framework 4.5.1 (Web Installer) for Windows Vista SP2, Windows 7 SP1, Window...) and see if that fixes the issue.

[yzhou2004]

thanks.  Upgrade to .NET 4.51. solved the issue.  But disappointly EG 7.1 did not solve the issue I experienced in EG 5.1 or 6.1.  I'll start another post.  Thanks much Casey.