SIM gives http error 401 when trying to install Symantec Management Platform
|Article:TECH121838|||||Created: 2009-12-18|||||Updated: 2012-11-20|||||Article URL http://www.symantec.com/docs/TECH121838|
When attempting an install of Symantec Management Platform SP3, it installs but then gives an error that one or more solutions were unable to configure. It also can abort at the database creation portion of the installation.
SMP 7 (NS 7)
Communication policies sometimes block http communcation when installing with different types of names for the server (FQDN, NetBIOS, or localhost). Also, the common server name may be an alias for the actual server name. This can cause the web installer to attempt to authenticate to the worng server name.
By default the FQDN is used if known. Attempt to use an alternate name such as the netbios name. See example below.
FQDN of server: Server1.Domain1.com
Netbios name of server: Server1
In the location where you find SIM asking for the name of the server and pre-populating the FQDN, change the name to be the NetBIOS and attempt to reinstall.
If you encounter the circumstance where server aliasing is not working correctly, meaning the FQDN of the server is different, or not resolving correctly in DNS, you can edit the following registry locations:
And set it to the actual FQDN of the server instead of the aliased name. This will allow you to use SIM ro repair the SMP configuration if needed. Alternately you can discuss the proper aliasing of the server in DNS with the proper network admins.
Note: The NetBIOS can be different then the fully qualified names first segement.
Article URL http://www.symantec.com/docs/TECH121838