Error 1325 When You Install COM+ Application from Nested .msi File (315079)
The information in this article applies to:
- Microsoft COM+ 1.0, when used with:
- the operating system: Microsoft Windows 2000
This article was previously published under Q315079 SYMPTOMS
If you try to install a COM+ application that contains a long file name from a nested .msi file, the attempt fails, and you receive the following error message:
Error 1325 (Invalid file name)
CAUSE
When you use Component Services Manager to build a COM+ .msi package, Component Services Manager builds an .msi package that contains only a long file name for the files that are listed in the .msi file table. Therefore, if you nest the .msi file that contains the long file name inside another .msi file, the installation fails.
RESOLUTION
To resolve this problem, obtain Microsoft COM+ Hotfix Rollup 18.1. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
313582 INFO: Availability of Windows 2000 Post-Service Pack 2 COM+ Hotfix Rollup Package 18.1
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
---|
Keywords: | kbbug kbfix kbQFE kbWin2000PreSP3Fix KB315079 |
---|
|