BRONZE PARTNER:
BRONZE PARTNER:
Industry News:
| |
| |
|
|
|
|
|
| List of Common SMS Admin Connection Failed Issues |
|
|
|
By: Rod Trent
Posted On: 6/2/2002
Having trouble connection to the SMS site with the SMS Administrator console? The following list of common issues should help you resolve any connection problems.
All available SQL Connections have been used.
For SQL 7.0 and 2000:
Change the "Maximum concurrent user connections" value to a number that is at least 20 greater than the MaxSqlConnections value, or change the value to 0 for unlimited connections.
For SQL 6.5:
Change the "Current user connections" value to a higher number.
User is not in the SMS Admins local group on the SMS Site server. Check the SMS Admins group and add the user if necessary.
Class or Instance security not set correctly. Verify the user's security permissions through the SMS Administrator console.
A user account in the domain that has the same name as the SMS site server or the remote SQL Server that hosts the SMS Provider. This problem will cause Windows 2000 computers connecting via the Admin console to fail, but Windows NT computers will work fine. Completely delete the matching user account. The console cannot connect even if you disable the account, and it is not possible to rename the SMS site server without having to reinstall SMS.
User must have Read access permissions to the default SMS.MSC and Explor.MSC. Use Windows Explorer on the affected computer to identify that the user does have the proper file rights.
Default connection protocol for the SQL database has changed. The default connection protocol for SQL server must be named-pipes.
The Remote Procedure Call (RPC) service must be installed and functional. Removing and reinstalling the TCP/IP protocol will reinstall this service.
Connecting user must have WBEM rights to the SMS server where the SMS Provider is located. To fix this issue:
- Start WBEM Permission Editor. On the Start menu, click Run, then type "WBEMPERM" (without the quotation marks) and press ENTER.
- In WBEM Permission Editor, you will see two panes, one for Users, and one for User Groups. Examine the Groups window and check for the SMS Admins group. If found, verify that the Group Name is spelled correctly.
- Select the entry. On the User menu, click Edit Group Properties. Verify that the following options are selected under the Attributes section:
- Enabled (checked)
- Execute Methods (checked)
- Schema Access Level: Write Instance
- If the SMS Provider is on a separate server from the Systems Management Server site server (such as the SQL Server), you must also verify that the SMS Admins group has at appropriate WBEM permissions to the local site server. This is because Systems Management Server first must connect to the site server to determine the location of the SMS Provider. Verify this by performing the steps above on the Systems Management Server site server, but ensuring in the Attributes section of the user group properties that the following options are selected:
- Enabled (checked)
- Schema Access Level: Read Only.
COM is disabled on the connecting computer. To re-enable COM:
- Start Dcomcnfg.exe in the %SystemRoot%\System32 folder.
- If the COM components have not been registered, you receive two prompts to register them. Click Yes for both prompts.
- On the Default Properties tab, verify that "Enable Distributed COM for this computer" is selected.
- Click OK.
|
|
|
|
|
|
