Server farm configuration not complete (server farm configuration not complete)

Since the moss beta version has not been updated, I got a moss 2007 trial version last week. After the configuration is properly installed, a"! The server farm configuration is incomplete!. As a result, I naturally thought of configuring server services. After I started several major services, I still had such a prompt, looking at the so-called incomplete task list in the management site, I also have a glimpse of it, so I directly created an application.ProgramWhen you create a portal, everything is normal and the website can be used normally after it is created. Of course, this is not a serious prompt on the website (there are exclamation points on both sides !!).

The use process is still normal, until the workflow is used, the form session status is unavailable.

In SharePoint 2003. it is a pity that the session is enabled in config. config can no longer find a trace of the Session. After several seconds of being depressed, it suddenly came to an whimsy: Is V3.0 more friendly? How does one set the session through the view? Even if I had a blind stroll on the operation and management pages, I guessed it. This is the Office Sharepoint Server Shared Services → configure session state on the Application Management page, A large text in alert color: Warning: Some application will not function correctly without session state enabled. A shared service provider must be created to enable session state. unfortunately, this is not editable, but the prompt is enough (of course, by the way, it will be more friendly if those are not). Return to the Office Sharepoint Server Shared Services Section, the first option creates many associations: Create or configure This farm's shared services, which was previously thought to be done by configuring services on server, because there are a lot of services in it and there is a view that guides the user to start, on the create or configure this farm's shared services page, there is an SSP management list. If it is not the session above, you can see the description of this page after you click it: use this page to manage shared services providers (SSPs ). SSPS provide the infrastructure-databases, web services, and Admin pages-for shared services. from this page, create New SSPS, control which SSP is used by each web application, and reconnect the pieces of an SSP as part of database recovery. hey, you can see the thin spot by combining the previously seen warning in session configure.

Create SSP now. There are some twists and turns in the middle. during creation, you need to start some services in services on server, such as search indexing, and create servers, applications, and the long-overdue "my site "... Although the week ends, the light is gradually shining. The final result is shown in the figure.

Then, the message "session state is not available" for the approval workflow disappears. Looking back, we can see that the task shown in the first figure has also been added. However, the Administrator tasks: read first-click this link for deployment instructions has a certain nonsense nature. I even clicked this task and read it carefully, in addition to wasting time... Of course, the above is also nonsense, huh, huh, because if there is an installation wizard, SSP should not be this depressing problem if you know it...