configuration hangs at "Registering SharePoint services..." (step

Discussion:

(too old to reply)

chentiangemalc

2007-03-11 01:28:00 UTC

Installation completes ok of SharePoint Office Server 2007 (trial) on new
installation of Windows 2003. I chose custom installation because I need to
install SharePoint and search index files on different partitions. However
during the configuration process it 'hangs'

Test machine is 2.4 GHz P4 with 2 GB ram . I had previously run the beta
versions with no problem, this is a complete reinstallation of the operating
system now.

Setup hangs at this point : (i had left it over night and it was still stuck
with no error message)

SharePoint Products and Technologies Configuration Wizard

Please wait while SharePoint Products and Technologies is configured.
Performing configuration task 5 of 10.
Registering SharePoint services...

Sucessfully installed service instance: Windows SharePoint Services Search.

~

Event viewer Application log:

Type: Information
Source: Windows SharePoint Services 3 Search
Category: Gatherer
Event ID: 10044

Successfully stored the application configuration registry snapshot in the
database.

Context: Application 'Search index file on the search server'

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

~

Type: WARNING
Source: Windows SharePoint Services 3 Search
Category: Gatherer
Event ID: 10035

Could not import the registry hive into the registry because it does not
exist in the configuration database.

Context: Application '575eb16f-b482-483e-8258-2ce489424ce1'

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

~

Type: ERROR
Source: Windows SharePoint Services 3 Search
Category: Content index server
Event ID: 4127

Content index on Search could not be initialized. Error Access is denied.
0x80070005.Component: 575eb16f-b482-483e-8258-2ce489424ce1

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

~

SYSTEM LOG:

Type: ERROR
Source: Service Control Manager
Category: None
Event ID: 7000

The Office Document Conversions Load Balancer Service service failed to
start due to the following error:
The system cannot find the file specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

~

The Office Document Conversions Launcher Service service failed to start due
to the following error:
The system cannot find the file specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

- CodeDoctor -

2007-03-11 18:31:08 UTC

Permalink

chentiangemalc,

Very strange issue. The only thing that I can think of is that perhaps the
trial has expired. When was the first time you installed it? And did the
time limit run out before entering a valid activation code?

Here is what I had to do to get MOSS installed:

1. Install Windows 2003 Server
(Ensure all hardware drivers for the server are installed and functioning)
2. Install Active Directory (either new domain or existing)
3. Apply all latest service packs and security updates
4. Activate the server's role as an Application server
5. Install the .NET Frameword 3.0
6. Install MOSS (Microsoft Office SharePoint Server) 2007

Also, try to download another version of the MOSS 2007 Trial, the one you
have
may be corrupted.

If you've followed all these steps, it should work.

Hope this helps,

Post by chentiangemalc
Installation completes ok of SharePoint Office Server 2007 (trial) on new
installation of Windows 2003. I chose custom installation because I need to
install SharePoint and search index files on different partitions. However
during the configuration process it 'hangs'
Test machine is 2.4 GHz P4 with 2 GB ram . I had previously run the beta
versions with no problem, this is a complete reinstallation of the operating
system now.
Setup hangs at this point : (i had left it over night and it was still stuck
with no error message)
SharePoint Products and Technologies Configuration Wizard
Please wait while SharePoint Products and Technologies is configured.
Performing configuration task 5 of 10.
Registering SharePoint services...
Sucessfully installed service instance: Windows SharePoint Services Search.
~
Type: Information
Source: Windows SharePoint Services 3 Search
Category: Gatherer
Event ID: 10044
Successfully stored the application configuration registry snapshot in the
database.
Context: Application 'Search index file on the search server'
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
~
Type: WARNING
Source: Windows SharePoint Services 3 Search
Category: Gatherer
Event ID: 10035
Could not import the registry hive into the registry because it does not
exist in the configuration database.
Context: Application '575eb16f-b482-483e-8258-2ce489424ce1'
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
~
Type: ERROR
Source: Windows SharePoint Services 3 Search
Category: Content index server
Event ID: 4127
Content index on Search could not be initialized. Error Access is denied.
0x80070005.Component: 575eb16f-b482-483e-8258-2ce489424ce1
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
~
Type: ERROR
Source: Service Control Manager
Category: None
Event ID: 7000
The Office Document Conversions Load Balancer Service service failed to
The system cannot find the file specified.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
~
The Office Document Conversions Launcher Service service failed to start due
The system cannot find the file specified.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

chentiangemalc

2007-03-12 01:29:00 UTC

Permalink

Ok

No the validation was OK. This was the first time it had been installed on
this rebuild of the OS, and the key was from the microsoft website with 180
day trial.

I actually fixed it by using the default installation (i.e. not custom) To
force the installation off the C: drive I changed the registry keys for
default program installation.

In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
changed ProgramFilesDir to the appropriate value.

Not really something I would want to do on production machine. I am
interested to know though how I would go about troubleshooting this
installation problem ...

I'm thinking it may be related to the SQL configuration but I wasn't sure
how to fix it.

Anyway it would be good for Microsoft to fix the installation program as
without checking the event log no errors are given at all, just keeps going
... maybe forever...

Malc.

Post by - CodeDoctor -
chentiangemalc,
Very strange issue. The only thing that I can think of is that perhaps the
trial has expired. When was the first time you installed it? And did the
time limit run out before entering a valid activation code?
1. Install Windows 2003 Server
(Ensure all hardware drivers for the server are installed and functioning)
2. Install Active Directory (either new domain or existing)
3. Apply all latest service packs and security updates
4. Activate the server's role as an Application server
5. Install the .NET Frameword 3.0
6. Install MOSS (Microsoft Office SharePoint Server) 2007
Also, try to download another version of the MOSS 2007 Trial, the one you
have
may be corrupted.
If you've followed all these steps, it should work.
Hope this helps,