By Michael Reese - 5/1/2008
I am getting an error installing the latest version. It seems that the first installation failed with an Add-In-manager error similar the the "80070002" experienced by someone else. Then I tried to reinstall the version and got a .Net Framework Installation Utility error with the following errorEventType : clr20r3 P1 : installutil.exe P2 : 2.0.50727.1433 P3 : 471ebfbb P4 : mscorlib P5 : 2.0.0.0 P6 : 471ebc5b P7 : 1295 P8 : 14 P9 : system.io.filenotfoundexception Everthing is stuck now?
|
By Michael Reese - 5/1/2008
That's using VS 2005 and 2008. The last error occured during the installation of the strataframe database.
|
By Trent L. Taylor - 5/1/2008
We actually haven't changed anything in this regard. InstallUtil is a .NET application that is used by MSI to launch installer programs. The installation has a .NET Installer program that runs to install the databases an structures. I have seen this in the field before in some of the following scenarios: - Corrupt .NET installation
- Corrupt WMI installation (rare and most fatal)
- Insufficient permissions
- Corrupt MSI installation
The problem that you are running into isn't specific to the SF install but rather the InstallUtil.exe program that is used to launch the installer. You might try uninstalling SF altogether and try again....but more than likely you will have the same results. Be sure that you have admin permissions when installing as well. If the install fails after a complete SF uninstall and re-install, then you can start weeding through some of the other items I mentioned. Note: The most likely culprit is a .NET framework issue. This is also the most elusive. Other things (including VS) will appear to work, yet there is a core framework install issue. I have seen this a number of times...and it is always a little tricky getting it back together as well. Automatic Updates are a very common cause of this issue...we see it often.
|
By Edhy Rijo - 5/1/2008
Trent L. Taylor (05/01/2008) Automatic Updates are a very common cause of this issue...we see it often. Michael, If you don't find the fix to the problem, you may want to try Windows Restore to restore your registry state at a point you could try reinstalling SF again. Not related to SF, I have seen this type of issues with Windows Updates which may corrupt the registry entries that may cause this kind of unknown errors, then after using Windows Restore you can go to Windows Update and reinstall whatever may be missing. Keep in mind that Windows Restore may remove registry entries for any program installed in the period of the restore point and you may need to reinstall it. Good luck!
|
By Michael Reese - 5/2/2008
Wow, Seems wierdIt all started with the add-in-manager error after the install. When I tried un-install/re-install, I got the .net manager error. Then when I tried to fix through the ad/remove programs, I got the Strataframeinstaller error stating that it counld not find the path "Microfour\Stratframe.addin" The .addins file must be manually deployed. Michael
|
By Edhy Rijo - 5/2/2008
Michael,You can also try the MS Windows Installer Clean Up utility to get rid of any damage installation. This is a must have utility. http://support.microsoft.com/kb/290301
|
By Trent L. Taylor - 5/2/2008
Did you get StrataFrame fully uninstalled or is it still in the Add/Remove programs section? If you have it fully removed, then try the install again, but it does sound like you have a .NET and/or an MSI issue.The reason that the add-ins would have failed is because the installutil.exe failed to launch the installer...so it is kindof an uphill battle once there are some core issues like this. I would try to do everything else before your uninstall and reinstall the .NET framework...this can be bad mojo sometimes...especially when things are already broken.
|
By Michael Reese - 5/2/2008
Thanx Guys,Still trying to get it to work. This is my 4th un/install of SF. Ran RegCure as well. I am moving in the direction of a .net replacement. Have 1.1,2.0SP1, 3.0 and 3.5 installed. Cannot remove the .Net framwork (2.0) via the ad/remove programmes? Will keep trying Michael
|
By Michael Reese - 5/2/2008
BTW, after the SF un-install, should I remove the SF folders as well? There seems to be few of them left behind in the Microfour folder including assemblies?
|
By Michael Reese - 5/2/2008
Ok, fixed it.After uninstalling SF, I removed all folders and SF databases. Then reinstalled SF without a problem?? Does recompiling the source code to use Infragistics 8.1 and running the afterbuild make a difference with updates? Thanks again for your help.
|
By Trent L. Taylor - 5/5/2008
After uninstalling SF, I removed all folders and SF databases. Then reinstalled SF without a problem?? Removing the folders shouldn't have made a difference unless there were some type of permission issue...but I am glad you got it working! Does recompiling the source code to use Infragistics 8.1 and running the afterbuild make a difference with updates? Nope. The only thing that you would have to take into account is if the next update is not pre-compiled for 8.1. Other than that...nothing to worry about!
|
By Michael Reese - 5/5/2008
Lord!!!I payed a dearly for removing the SF database. Seems all my project BO Mapper config data got wiped. Since I do not know what happened in the first place, I guess I am open to another knee capping when I attempt to install the next version? Michael
|
By Trent L. Taylor - 5/5/2008
Ooo you definitely don't want to ever remove the SF database. You should have this backed up...right You could just restore your SF database so you get your mappings, etc. back....then just open the DDT, select the StrataFrame package file in the Common Files\MicroFour\StrataFrame folder and deploy it to your server.
|