I down loaded twice to make sure that I didn't get a corrupt exe. But both times the same thing. The VS debug screen and when I choose No, every thing goes blank and then clears back to the desktop. Running XP media center with 4 meg ram. Never had this problem with any other versions... I'll try killing some things in ram and trying again in the morniing.



Regards,



Robert

Infinint Engine Software

I have the same problems, with the addition that when trying to repair, I have to run the downloaded program, instead of the usual method of going to control panel, add or remove programs and repair, because when doing so I was asked for the source folder for the program, and even clicking on the appropiate folder, it continued to ask me for the folder.

Now it seems to have installed ok.

I'm having the same problems. I'm using the 1:10pm install. I get an error when installing the SF db. I can't do a repair because it prompts for the folder with the setup exe but doesn't like the folder I choose (which is on a network drive). I uninstalled and tried reinstalling with no success.



I'm installing on a Windows XP SP2 box w/4GB of ram. Nothing is running. The database is on another machine, and is an instance of SQL Server 2005. I checked and I have access to the database. I also tried moving the setup file to my desktop, so it wasn't on a network share, but the same problems.

We have reproduced and are fixing this error.  However, you can work around this error as we speak without a new install.  Just run the installation again and choose the Modify or Repair option. 

This is due to the GAC and assemblies already being loaded when the installer program runs.  This has been resolved and we will post a build later today or early tomorrow addressing this issue, but all you need to do is run the setup again.

Thanks for the quick response. I did as suggested and reran the setup program and all is good. I didn't understand that I needed to rerun the setup again (I went to the Add/Remove programs in control manager).

Yes, we are completing testing of an update that will prevent this from happening in the future.  it has to do with the registering of the assemblies into the GAC within a certain scenario.  However, we did reproduce it and have fixed this.  It will be corrected and posted in the My Account area tonight or early tomorrow.