tyutye5p6t
KLASA A
Dołączył: 10 Mar 2011
Posty: 69
Przeczytał: 0 tematów
Ostrzeżeń: 0/5
Skąd: England
|
 Wysłany: Wto 3:24, 17 Maj 2011 |
|
|
Microsoft SQL Servers, expand the server team, distend the
the account namely the application pool is sprinting as to the Security
Right-click
On
You
setup MS Windows SharePoint Services and as presently the Setup procedure
is completed successfully, you configure Windows SharePoint Services
settings in SharePoint Central Administration. You specify
configuration database settings above the Set Configuration Database
Server sheet of SharePoint Central Administration, and then you click
OKAY. Now ashore clicking OK you obtain one of the following misdeed messages.
Login
failed for user 'NT AUTHORITY\NETWORK SERVICE'. (Error code: 18456)
Add
Click
Reason
after this error
The
application pool runs as a definite account. If that account does no
have database production rights in Microsoft SQL Server,[link widoczny dla zalogowanych], this publish may
occur. To be extra characteristic, this publish occurs whether the account is not a
member of the Security Administrators character alternatively of the Database
Creators role.
Logins, and then click New Login.
the Server Role catalogue, click to select the Security
SQL Server Enterprise Manager.
To
determine this issue, you must join one account to the Database Creators
role and to the Security Administrators role in SQL Server. To do
that you absence to follow the given underneath steps:
Restart
the account label in the [b]Name carton. Use the emulating format
The Application Pool Changed page is displayed.
the Server Roles tab.
Microsoft
Login
failed for user 'DOMAINNAME\ACCOUNTNAME'. (Error code: 18456)
Administrators role and to the Database Creators role in SQL Server.
In
the Configure Administrative Virtual Server page of SharePoint
To do this:
style="margin-bottom: 0in;">Error
number 18456 is very prevalent in MS SQL Server and it comes up
whenever there is some problem with installation of MS SharePoint
services. This error harvests up in the following scenario:
Administrators[/b] retard box, and then click to select the Database
SQL Server Enterprise Manager.
Quit
Type
Creators check box. Click OK.
Expand
for the account name: DomainName\AccountName.
account as the application pool account,[link widoczny dla zalogowanych], and then click OK.
Resolution
suitable server, and then expand Security.
Start
Central Administration, establish a current applying pool, clarify the
Post został pochwalony 0 razy
|
|
