Okay, so you're running the installer that is updating your XPE development environment, right? Or are you attempting to run that on a device before you seal it?
You need to run that installer on the workstation that has the XPE dev environment (and database) installed. The installer is looking for a specific database on a specific instance of Sql Server, so if you have (or somebody else has) changed it, you'll need to read up on how to specify the connection string to use with the installer.
In addition, it's probably trying to connect using your windows account credentials. Make sure you are able to log on to Sql Server, open the DB with the component definitions, and add records to it. Alternatively, if you can specify the connection string you can set a Sql login username and password to use.
Profiler is a great tool for troubleshooting the two issues described above.
Once you have the components installed, you'll have to add them to your image, check your dependencies and then build it.
If you're trying to just install .NET 2.0 on a machine directly (before you reseal it), you will need the packages for Windows Installer on the machine first. There might be some other dependencies; I haven't done it in a long time so I can't remember.
The best way to troubleshoot dependencies on an XPE installation is to put ProcessMonitor from Sysinternals on it. As you run the installer, you'll see where it attempts to find stuff and fails. Take that information back to your XPE IDE and search your components for those files. You then have to add the packages containing those files to your image and try again. Its an arduous process sometimes..,.
The key is to install the .net framework if it is not there - regardless of the OS. Also, just go ahead and install the .Net 3.5 framework if you are going to install one of them.
Anyway, if you are using the built in installer that comes with Visual Studio, this is a real pain in the butt. You would be better off, and saner if you went with a different installer package. Install Shield, Wise, InstallAware will all do it for you. I believe you can also find better guidance on how to do this with Wix and NullSoft Installer.
http://www.improve.dk/blog/2007/06/10/creating-a-dotnet-bootstrapped-installer-using-nsis
How can I detect .NET 3.5 in WiX?
Best Answer
Found Answer.......!!!!!!!
Officially Microsoft Office 2003 Interop is not supported on Windows server 2008 by Microsoft.
But after a lot of permutations & combinations with the code and search, we came across one solution which works for our scenario.
The solution is to plug the difference between the way Windows 2003 and 2008 maintains its folder structure, because Office Interop depends on the desktop folder for file open/save intermediately. The 2003 system houses the desktop folder under systemprofile which is absent in 2008.
So when we create this folder on 2008 under the respective hierarchy as indicated below; the office Interop is able to save the file as required. This Desktop folder is required to be created under
C:\Windows\System32\config\systemprofile
AND
C:\Windows\SysWOW64\config\systemprofile
This worked for me...
Also do check if .NET 1.1 is installed because its needed by Interop and ot preinstalled by Windows Server 2008
Or you can also Use SaveCopyas() method ist just take onargument as filename string)
Thanks Guys..!