Video Screencast Help

Endpoint Management Community Blog

Showing posts tagged with Wise Packaging
Showing posts in English
B_Raj | 25 Oct 2009 | 0 comments

Msispy is an utility which comes along with Windows installer SDK. If you want to troubleshoot a MSI package in component level or feature level, I will recommend this tool as the best option for repackagers.It provides a nice GUI and command line utilities which makes it very user friendly.

MsiSpy provides a component level view of the products and features installed on a system, using either an MSI Package, or the registry information. Msispy also displays the status of each, and allows you to partially or completely re-install missing or damaged items. You  can also re-configure any product or feature, selecting the install level, and specifying whether to install it locally or run it from a network server.

 Some of the main features are;

  1. It allows you to open an MSI package and display all information about it.
  2. It display information about all the products installed on the computer.
  3. Allows you to load a...
B_Raj | 24 Oct 2009 | 0 comments

This error is due to an error in Directory table of the MSI.

Generally occurs while a directory entry that references something non existent as its parent. If you ignore the ICE 03 validation error (Similar to the below mentioned Eg.) while developing the MSI,During the installation you will be getting the “Internal Error 2705. Directory” error.

Eg: of an ICE 03 error :

Orca validation reports an ICE03 error: “Not a valid foreign key; Table:Directory, Column: Directory_Parent, Key ):newfolder1″

 This error can be fixed by editing the Directory table.The wrong entries in the ‘Directory table’ will be highlighted in red colour.

WiseUser | 23 Oct 2009 | 2 comments
Success = 0
Error: General Detection error = 17301
Error: Applying patch = 17302
Error: Extracting file = 17303
Error: Creating temp folder = 17021
Success: Reboot flag set = 17022
Error: User cancelled installation = 17023
Error: Creating folder failed = 17024
Patch already installed = 17025
Patch already installed to admin installation = 17026
Installation source requires full file update = 17027
No product installed for contained patch = 17028
Patch failed to install = 17029
Detection: Invalid CIF format = 17030
Detection: Invalid baseline = 17031...
WiseUser | 22 Oct 2009 | 0 comments

When we try to install office 2007 which is 32 bit installation on a windows server with terminal services enabled you will be getting the following errors

Error Information :

Loaded Dll : \\sbc-netapp01\Install\microsoft\Sv_office_ent_2007\Enterprise.WW\OSETUP.DLL.
Catalyst version is : 12.0.4518.1014
JobExecutionMode is InstallExecutionMode.
Error: failed MsiEnumProducts ErrorCode: 2(0x2).
Catalyst execution finished: 02/08/2008 10:44:24. Return code: 30015. Exception caught: ErrorCodeOnly.
PERF: TickCount=544812 Name=RunSetup Description=End function

Solution or work around suggested for this problem

  1. Open Terminal Services Configuration.
  2. Click Server Settings.
  3. Right-click Permission Compatibility, and then click Properties.
  4. Click to select the Full Security check box, and then click OK...
WiseUser | 13 Oct 2009 | 2 comments

How to Check for prerequisite Microsoft .Net framework 2.0 installed on the machine before installation ?

1. Define a Property Name as DOTNET2 in the properties section to Null
2. In System Search Add -> Registry and do the following
   Property - DOTNET2
   Operation - Read raw value from registry
   Root - HKEY_LOCAL_MACHINE
   Key -SOFTWARE\Microsoft\.NETFramework\policy\v2.0
   Value Name - 50727
 
3. Go to Launch Condition - Build the condition

DOTNET2="50727-50727"

For Checking .net version 1.0

Regvalue name is SOFTWARE\Microsoft\.NETFramework\policy\v1.1

Value is "3706-4322"

 

WiseUser | 06 Oct 2009 | 1 comment

1. Create your Office customization by running

setup.exe /admin

Which will open up the Office Customization tool

2. Select Create a new Office Professional Plus 2007 option

3. Take the settings as you want in the following set of options available

 a) Setup
 b) Features
 c) Additional Content
 d) Outlook

4. Save the resulting msp in the same directory

5. Run the  setup.exe with following option

 setup.exe /admin office.msp

Tips to update the patches

If we get any updates, say any patches from Microsoft then place it in Updates folder

Setup.exe has a logic to read and execute the newly found msp files from the Updates folder
 

WiseUser | 17 Sep 2009 | 1 comment

How to register a dll using Msiexec.exe /y and Msiexec.exe /z

1. Go to File Section where the file is present
2. Double click the file
3. Goto Self registration tab
4. Selct the registration Method as "Use order Specified below"
5. Hit ok

Goto MSi Script section and you can find corresponding custom action for registeration .

Why we do this type of dll\ocx registration Compared to self reg table is ?

If the dll registration gets wrongly captured in the self reg table then it will throw error upon installation . When we install using the above suggested method then it wont throw any error if dll is not getting registered.

 

nac | 17 Sep 2009 | 1 comment

Many times we interfere with the MSI script sequence in InstallExecute sequence, AdminExecuteSequence, advertised sequence, InstallUISequence, AdminUISequence. Following lists will be helpful in maintaining proper sequence.

It's not necessory that sequence number should be like this only but order is suggested to be the same.

InstallExecuteSequence

Action

Condition

Sequence

LaunchConditions

 

100

AppSearch

 

400

CCPSearch

NOT Installed

500

RMCCPSearch

NOT Installed

600

ValidateProductID

 

700

CostInitialize

 ...
WiseUser | 15 Sep 2009 | 0 comments

Error 1603 is a generic machine-specific issue .

One or more of the following fixes may resolve the error .

This error is known to occur on computers that do not have enough disk space for the installation.

The temp directory is not clean.

A certain file on the machine is locked. To fix this: Close all applications running in the background.

Reboot your computer.

Run the installation again.

 

WiseUser | 14 Sep 2009 | 0 comments

Msi error 1622 during an installation and uninstallation of an msi .

Cause : Error in writing a log file 

Example :  This Error may occur if we give a folder which is not present during installation or uninstallation

Msiexec /i Xtrader.msi /l*v c:\temp\install\ins.log

If you don't have a folder install under c:\temp the msiexec.exe may throw an error 1622

In order to overcome this issue create a folder before installation or uninstallation or use the existing folder say c:\temp .