Article ID: 309387 - Last Review: October 25, 2006 - Revision: 4.5 SMS: "Invalid Collection Name" Error Message After You Browse for Valid Collections
This article was previously published under Q309387 On This PageSYMPTOMS
When you create a new direct-member collection, you may receive an "Invalid Collection Name" error message after you browse for valid collections in the Create Direct Membership Rule Wizard. This problem can occur even though you are a member of a group that has proper Systems Management Server-object permissions to the selected collection.
RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:288239
(http://support.microsoft.com/kb/288239/EN-US/
)
How to Obtain the Latest Systems Management Server 2.0 Service Pack Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The post-SMS 2.0 Service Pack 3 (SP3) English version of this fix should have the following file attributes or later:Date Time Version Size File name Platform -------------------------------------------------------------------- 01-Mar-2001 13:40 2.0.1493.3184 1,578,400 Basesvr.dll Intel 01-Mar-2001 13:40 2.0.1493.3184 2,429,200 Basesvr.dll Alpha 01-Mar-2001 10:30 2.0.1493.3143 81,040 Cmprov.dll Intel 01-Mar-2001 10:30 2.0.1493.3143 126,224 Cmprov.dll Alpha 01-Mar-2001 13:30 2.0.1493.3182 121,440 Compmgr.exe Intel 01-Mar-2001 13:30 2.0.1493.3182 171,792 Compmgr.exe Alpha 01-Mar-2001 14:40 2.0.1493.3196 4,198,864 Smsprov.dll Intel 01-Mar-2001 14:40 2.0.1493.3196 11,793,680 Smsprov.dll Alpha STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5. MORE INFORMATION
To install the hotfix, use the appropriate method.
Using the Hotfix InstallerNOTE: This method is for only Intel-based computers.
Manually Update the SMS Site Server
Additional Installation InformationTo update remote site systems, such as SMS administrator consoles, an SMS SQL monitor or SMS provider that is not located on the site server, follow the appropriate instructions:Manually Updating a Remote SMS Administrator ConsoleNOTE: Before you implement this update on your SMS administrator console, you must install it on the SMS site servers in your environment.
Updating a Remote SMS Provider ServerNOTE: Before you implement this update on your SMS provider server, you must install it on the SMS site servers in your environment.
Manually Updating a Remote SMS SQL Monitor ServerNOTE: Before you implement this update on your SMS site database server, you must install it on the SMS site servers in your environment.
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
