Visual Studio 2005 Team Edition for Software Developers
I have previously followed the instructions in the Package DB here to create a SMS automated install for the professional version of VS 2005.
As I am installing apps during State Restore in OSD is used the Transform File method with the ADDEPLOY=1 flag. This has worked fine.
The requirement has come up for some of our developers to use the Team Software Dev version. So I have followed exactly the same process as before, create a clean reference machine, install the pre requisites, run the admin install to create a transform file, create the package within SMS.
However this time round, it just doesn't install. I have tried running the command manually and in an SMS package, the Windows installer starts up, looks as if it's installing, then after a couple of minutes just goes away again. No errors, nothing. I have checked and double checked to make sure I didn't make a maintenence mode transform.
Totally pulling my hair out now, does anyone have any ideas? Or has anyone had problems with this version of VS 2005.
Kindest Regards,
Jason.
As I am installing apps during State Restore in OSD is used the Transform File method with the ADDEPLOY=1 flag. This has worked fine.
The requirement has come up for some of our developers to use the Team Software Dev version. So I have followed exactly the same process as before, create a clean reference machine, install the pre requisites, run the admin install to create a transform file, create the package within SMS.
However this time round, it just doesn't install. I have tried running the command manually and in an SMS package, the Windows installer starts up, looks as if it's installing, then after a couple of minutes just goes away again. No errors, nothing. I have checked and double checked to make sure I didn't make a maintenence mode transform.
Totally pulling my hair out now, does anyone have any ideas? Or has anyone had problems with this version of VS 2005.
Kindest Regards,
Jason.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
Jabenedicic
17 years ago
Ok here is what I have managed to pick out of the log files. It doesn't mean too much to me I'm very new to the packaging game.
Any pointers as to what I should be investigating next would be great, I should be ok given a push in the right direction.
(SERVER) MSI (s) (2C:0C) [13:53:50:207]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIC8.tmp, Entrypoint: SetPidProps
(UNKNOWN) 05/11/06 13:53:50 DDSet_Status: LANGID: 1033
(UNKNOWN) 05/11/06 13:53:50 DDSet_Entry: SetPidProps started
(UNKNOWN) 05/11/06 13:53:50 DDSet_Status: PIDSEQ:
(UNKNOWN) 05/11/06 13:53:50 DDSet_Status: PIDRET: 1
(UNKNOWN) 05/11/06 13:53:50 DDSet_Status: EDITIONTYPE:
(UNKNOWN) 05/11/06 13:53:50 DDSet_Error: Error: CA_GeneratePID failed before this CA was called
(UNKNOWN) 05/11/06 13:53:50 DDSet_CARetVal: 1603
(UNKNOWN) 05/11/06 13:53:50 DDSet_Exit: SetPidProps ended
NOTE: Look at few lines above for clues on error
(ERROR) Action ended 13:53:50: CA_SetPidProps. Return value 3.
NOTE: Look at few lines above for clues on error
(ERROR) Action ended 13:53:50: INSTALL. Return value 3. (PROPERTY) Property(C): ACTION = INSTALL
(UNKNOWN) === Logging stopped: 11/05/2006 13:53:50 ===
(CLIENT) MSI (c) (58:68) [13:53:50:503]: Note: 1: 1708
(CLIENT) MSI (c) (58:68) [13:53:50:503]: Product: Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU -- Installation failed.
(UNKNOWN)
(CLIENT) MSI (c) (58:68) [13:53:50:581]: Grabbed execution mutex.
(CLIENT) MSI (c) (58:68) [13:53:50:581]: Cleaning up uninstalled install packages, if any exist
NOTE: Look at few lines above for clues on error
(ERROR) MSI (c) (58:68) [13:53:50:581]: MainEngineThread is returning 1603
(UNKNOWN) === Verbose logging stopped: 11/05/2006 13:53:50 ===
(UNKNOWN) Any pointers as to what I should be investigating next would be great, I should be ok given a push in the right direction.
Posted by:
Jabenedicic
17 years ago
As it is a version downloaded from MSDN is comes with the serial number pre-populated into the setup.sdb file, when I run the Administrator Install mode the serial number is greyed out.
I will have a run through the transform file in AdminStudio and see if the serial number is missing.
Thanks for all your help so far.
I will have a run through the transform file in AdminStudio and see if the serial number is missing.
Thanks for all your help so far.
Posted by:
Jabenedicic
17 years ago
Ok I found something odd in the properties at the end of the document. The PIDKEY value doesn't match the PID in the MST or in the setup.sdb file.
Now to work out where it is getting this different key from.
Now to work out where it is getting this different key from.
Posted by:
Jabenedicic
17 years ago
If I add PID=xxxxxx etc to the command line it works fine.
I will use this method as a temporary solution so that I can get my build out to the developers and work of resolving the real issue in a less pressured time scale.
I will use this method as a temporary solution so that I can get my build out to the developers and work of resolving the real issue in a less pressured time scale.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.