Microsoft KB Archive/322507

= You receive an &quot;Invalid Package Definition File&quot; error message when you try to import a .pdf file in Systems Management Server 2003 =

Article ID: 322507

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-



This article was previously published under Q322507





SYMPTOMS
When you try to import a Package Definition File (.pdf file) by using the Create Package from Definition Wizard, you may receive the following error message:

The file you have selected is an invalid Package Definition File. Please select a valid file.



CAUSE
This problem may occur when the following conditions are true:
 * The .pdf file contains more than one setup section. Examples of setup sections include the following sections:
 * Typical Setup
 * Complete Setup
 * Laptop Setup
 * Automated Setup
 * The same CommandName entry appears in more than one setup section.

The CommandName entry appears as the program name in the user interface. The CommandName entry can have any text value.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



WORKAROUND
To work around this problem, modify the .pdf file so that the CommandName entry is not duplicated. We recommend that you set the CommandName value to indicate the type of setup. For example, Typical Setup, Automated Setup, and Uninstall Setup. To change the CommandName entry, follow these steps:
 * 1) Start Notepad, and then open the .pdf file.
 * 2) Modify the CommandName= entry in each section so that none of the entries are duplicated.
 * 3) On the File menu, click Save.
 * 4) In the SMS Administrator console, right-click Packages, point to New, and then click Package From Definition.
 * 5) Click Next, click Browse, and then import the .pdf file.



MORE INFORMATION
The following example text is from a .pdf file that causes this problem. In this example, the CommandName entry is the same for both the Typical Setup and Automated Setup sections. [PDF] Version=1.0 [Package Definition] Product= Version=3.0 Comment= SetupVariations=Typical, Automated, Uninstall [Typical Setup] CommandLine=setup.exe /sms /s CommandName=Install UserInputRequired=False SynchronousSystemExitRequired=False SupportedPlatforms=Windows NT (x86) [Automated Setup] CommandLine=setup.exe /sms /s CommandName=Install UserInputRequired=False SynchronousSystemExitRequired=False SupportedPlatforms=Windows NT (x86) [Uninstall Setup] CommandLine=Uninstall.exe CommandName=Uninstall UserInputRequired=False SynchronousSystemExitRequired=False SupportedPlatforms=Windows NT (x86) [Setup Package for Inventory] InventoryThisPackage=True Detection Rule Part 1=file 1

[file 1] FILE=.exe COLLECT=FALSE The following example text is from a .pdf whose CommandName entries are correct. In this example, the CommandName entry in the Automated Setup section is changed. [PDF] Version=1.0 [Package Definition] Product= Version=3.0 Comment= SetupVariations=Typical, Automated, Uninstall [Typical Setup] CommandLine=setup.exe /u /s CommandName=Install UserInputRequired=False SynchronousSystemExitRequired=False SupportedPlatforms=Windows NT (x86) [Automated Setup] CommandLine=setup.exe /u /s CommandName=Autoinstall UserInputRequired=False SynchronousSystemExitRequired=False SupportedPlatforms=Windows NT (x86) [Uninstall Setup] CommandLine=Uninstall.exe CommandName=Uninstall UserInputRequired=False SynchronousSystemExitRequired=False SupportedPlatforms=Windows NT (x86) [Setup Package for Inventory] InventoryThisPackage=True Detection Rule Part 1=file 1 [file 1] FILE=.exe COLLECT=FALSE

Additional query words: prodsms

Keywords: kbinterop kbsmsadmin kberrmsg kbsoftwaredist kbmisctools kbnofix kbpackage kbbug KB322507

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.