Microsoft Office Tutorials and References
In Depth Information
6. In the Database name and Authentication section:
Make sure the database server name is correct. Enter the correct one and the instance if
Leave the default database name as it is or change it if you want.
Leave Windows Authentication, unless your SQL server requires SQL authentication. In
that case, enter the correct username and password in the appropriate fields.
7. In the Failover Server section, leave the field blank, unless you have a failover server
available. If you do, enter its name in the Failover Database Server field.
8. In the Search Server section, select the local server’s name, since that’s where you enabled
Search. It should be the only option in the field.
9. In the Service Application Connections section, leave the default selected.
10. In the Customer Experience Improvement Program section, select the option No.
If all your settings are correct, click OK (either at the bottom of the page or at the top).
A progress box will come up. After that finishes, you’ll get an Application Created notice in
the same box, indicating that, if this is the first time the application pool has been used with
SharePoint, it may take a while for the IIS Web Site associated with this web application to be
propagated to the other SharePoint servers on the farm. In addition, this web application still
needs a site collection before it is finished (Figure 3.46). Remember that without a site collection,
navigating to the web application’s URL will bring up nothing.
The Application
Created notice
Although it is not required, I find it is always a good idea, if I can afford to do so, to open the
command prompt (you may need to use elevated privileges) and run an IISRESET command,
just to make sure IIS is clear about the new web application and all of its settings.
Search JabSto ::

Custom Search