When attempting to install any product using SIM the installation fails during 1st Configuration step with error "Object reference not set to an instance of an object."
|Article:TECH174989|||||Created: 2011-11-21|||||Updated: 2012-08-04|||||Article URL http://www.symantec.com/docs/TECH174989|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
During initial installation, SIM fails during step 1 of the Configuration process with the following message:
A critical error occured.
Object reference not set to an instance of an object.
Configuration failed while attempting: Configuring services...
After I press OK button, installation fails.
And the following errors appear in SIM log:
Description: ConfigureNS - task_Completed(): Configuration Task Configuring
services... Failed: Object reference not set to an instance of an object. --->
Object reference not set to an instance of an object. ---> Object reference not
set to an instance of an object.
( Exception Details: System.Web.Services.Protocols.SoapException: Object
reference not set to an instance of an object. ---> Object reference not set to
an instance of an object. ---> Object reference not set to an instance of an
(SoapClientMessage message, WebResponse response, Stream responseStream,
at Symantec.Installation.ServicesTask.EndAsync(IAsyncResult result)
ITMS 7.1 SP1
The IIS not properly configured.
Wrong application pool advanced setting for "Enable 32-Bit Applications".
This issue has been reported to the Symantec Development team. This issue will be addressed in the form of a 'Install Readiness Check' in the next release post ITMS 7.1 SP2.
It was suggested to the customer to make sure the Application Pools have "Enable 32-Bit Applications" setting (under the Advanced Settings in IIS Manager) set to False. For this customer, the Classic .NET pool had the wrong setting.
Invalid value causes the service to run in 32-bit mode.
In this case, the process reads the 32-bit registry node(under "Wow6432Node").
After changing it from True to False, the customer was able to finish the Configuration process.
Note: Make sure that a GPO is not blocking the Administrator group for been part of 'Create Global Objects' policy. Dev mentioned that this is an important feature during installation.
Asked customer to do the following:
1. From the start menu Start -> Administrative Tools -> Local Security Policy
2. Within the Local Security Policy snapin navigate to:
- Security Settings -> Local Policies -> User Rights Assignment
3. Find the Create global objects policy and double click it
4. Select the Local Security Setting tab and click the Add User or Group... button to add the (local) Administrators group.
Article URL http://www.symantec.com/docs/TECH174989