I have seen several posts from months ago on this topic. I am installing VS .Net2003 via Group Policy. I have followed the MS article Deploying Microsoft Visual Studio .NET 2003 by Using Active Directory http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vstchdeployingvsusingactivedirectory.asp. I am installing the pre-req's by GPO also WCECOM.MSI and BOOTSTRAP.MSI. The installation appears to go OK (no errors in event log). upon first launch, Visual Studio opens and Windows Installer pops up, then the VS application closes. I enabled installer logging and see the output MainEngineThread is returning 1603

Second question: is there an MST available to install all components (fat client

Windows Installer ver = 2.00.2600.110
OS = XP Pro SP
IIS not installed (nor do I want it

event log is as follows
=== Verbose logging started: 5/25/2004 7:39:04 Build type: SHIP UNICODE 2.00.2600.1106 Calling process: C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe ==
MSI (c) (28:6C): Resetting cached policy value
MSI (c) (28:6C): Machine policy value 'Debug' is
MSI (c) (28:6C): ******* RunEngine
******* Product: {E05F0409-0E9A-48A1-AC04-E35E3033604A
******* Action: CollectUserInf
******* CommandLine: *********
MSI (c) (28:6C): Machine policy value 'DisableUserInstalls' is
MSI (c) (28:6C): Cloaking enabled
MSI (c) (28:6C): End dialog not enable
MSI (c) (28:6C): Original package ==> C:\WINNT\Installer\6f7b.ms
MSI (c) (28:6C): Package we're running from ==> C:\WINNT\Installer\6f7b.ms
MSI (c) (28:6C): APPCOMPAT: looking for appcompat database entry with ProductCode '{E05F0409-0E9A-48A1-AC04-E35E3033604A}'
MSI (c) (28:6C): APPCOMPAT: no matching ProductCode found in database
MSI (c) (28:6C): Looking for secure file transform: C:\WINNT\Installer\6f7c.ms
MSI (c) (28:6C): Validating transform 'C:\WINNT\Installer\6f7c.mst' with validation bits 0x20
MSI (c) (28:6C): Transform 'C:\WINNT\Installer\6f7c.mst' is valid
MSI (c) (28:6C): Note: 1: 2262 2: Patch 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: _Tables 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: _Columns 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Media 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Patch 3: -2147287038
MSI (c) (28:6C): TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary
MSI (c) (28:6C): TRANSFORM: Applying regular transform to database
MSI (c) (28:6C): Note: 1: 2262 2: _Tables 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: _Columns 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: _Validation 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ActionText 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Condition 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: AppId 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Feature 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: CCPSearch 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Icon 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Complus 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Directory 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: DrLocator 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Environment 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: MIME 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Font 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: IniFile 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: IniLocator 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: IsolatedComponent 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: LaunchCondition 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: LockPermissions 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Media 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ModuleExclusion 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: MoveFile 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ODBCAttribute 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ODBCDataSource 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ODBCSourceAttribute 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ODBCTranslator 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Patch 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: HelpFile 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Registry 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: RemoveIniFile 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: RemoveRegistry 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: SelfReg 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ServiceControl 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: ServiceInstall 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: HelpNamespace 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: HelpFilterToNamespace 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: HelpFilter 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: HelpFileToNamespace 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: HelpPlugin 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: UIText 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: Verb 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: FileSaid 3: -2147287038
MSI (c) (28:6C): Note: 1: 2262 2: MsiFileHash 3: -2147287038

Hello,

Thanks for posting. I will do some research on this issue and get back to
you as soon as possible.

Have a nice day.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi,

1603 means a fatal error here. But I cannot find anything wrong in the log.
If we go to the application event log, we should be able see why Windows
Installer has been triggered. Could you paste the related entries here?

After reviewing the MST file, the INSTALLLEVEL property is already set to
3, which makes all the features and components are installed by default.
Could you double-check this point?

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Felix, thanks for the timely response and opoligies for my delayed response. I have reinstalled the OS again and allowed the VS MSI application package to install. I receive the same error upon launch. I looked the the application event log and there is nothing there. The only way for me to get any logging to occur is to set the debugging level for application installs. In response to the MST file, there really isn't any way for me to verify the installation included all features. I will take your word for is since the INSTALLEVEL property is set to 3

Hi,

Normally, every Windows Installer activity should be recorded in the
application event log, with Source = "MsiInstaller". If we open the System
Information snap-in (by running "msinfo32.exe"), can we see MSI related
entries under "Software Environment" | "Windows Error Reporting"?

If you can submit a service request for Product Support Service, we have
some setup verification tool to verify the installation of VS.Net. That may
be helpful.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.