Re: Please help eleviate My frustration
From: Zuma (zuma01_at_hotmail.com)
Date: 07/19/04
- Next message: Eric Phetteplace: "Re: Searching Documents"
- Previous message: van Rens: "Re: Login Problems"
- In reply to: Mike Walsh: "Re: Please help eleviate My frustration"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Jul 2004 18:01:16 +0100
Thanks for the reply Mike,
Answers below:
2.. The information I quote comes from the following MS link
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf20.mspx
I did install using the remotesql=yes switch (mentioned earlier in the full
doc above)
3. I removed the MSDE and Sharepoint using Add remove programs before
installing in again using the remotesql=yes switch
4,. Again I am just quoting information I have read on the MS site
I will check out the information you have pointed me to.
BTW I changed the authentication to mixed (SQL\Windows) and used the SA
login and this worked but I would like to use the windows authentication
Thanks Again Mike
J
"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:us$SX5VbEHA.3204@TK2MSFTNGP09.phx.gbl...
> 1. There are issues with running as a Domain Controller (see the WSS FAQ)
> [my sig]
>
> 2. Where does the mass of text you are quoting from come from ? It doesn't
> seem particularly relevant to a WSS *installation* phase.
>
> You should be following the Admin Guide's instruction for installing WSS
> with SQL Server 2K (which includes remotesql=yes which I don't see
> mentioned
> anywhere in your text)
>
> 3. You say you installed MSDE with no problems. Is this SQL Server
> installation on a new server or at least on a clean server with all
> previous
> installations removed?
>
> If you intend merely to upgrade a WMSDE installation to SQL Server you
> should do this following the steps I outlined in the later thread "Move to
> SQL Server?"
>
> 4. "SQL Server is recommended for its backup features" Hardly. It's needed
> if you want search on your WSS site or if you want to add non-WSS
> databases
> to the same system. Backup tools work for WMSDE too.
>
> Mike Walsh, Helsinki, Finland
> WSS FAQ at wss.collutions.com
> Please reply to the newsgroup
> "Zuma" <zuma01@hotmail.com> wrote in message
> news:#YxgP5QbEHA.996@TK2MSFTNGP12.phx.gbl...
>> Hi,
>>
>> I am trying to get to grips with WSS as it looks like a great product.
>>
>> I have installed successfully using the MSDE but I understand that SQL is
>> recommended for its backup features etc. So I tried to install on a SQL
>> DB
>> but failed
>>
>> Here is the background:
>>
>> 1 Server running W2K3 as a domain controller
>> Running SQL 2K (SP3)
>>
>> Installed (As recommended by MS) and went throgh the following:
>>
> ****************************************************************************
> ***************
>> After Installation
>> After the Setup process is complete, you can configure your
>> administrative
>> virtual server (including specifying an application pool to use for the
>> virtual server processes), connect to your SQL Server computer, and then
>> provide your virtual servers with Windows SharePoint Services. You
>> perform
>> these steps by using the SharePoint Central Administration pages, which
> open
>> automatically when Setup is complete.
>>
>> Configure the administrative virtual server
>>
>> 1.
>> On the Configure Admin Virtual Server page, in the Application Pool
>> section, select Create a new application pool.
>>
>> Note You can also use an existing application pool, but any Web
>> application that is using the same application pool can modify the
>> Windows
>> SharePoint Services databases. This is a potential security risk.
>>
>> 2.
>> Type the name to use for the new application pool, and then specify
>> whether to use a predefined or configurable security account for the
>> application pool.
>>
>> . If you selected Predefined, select the security account to
>> use.
>>
>> . If you selected Configurable, type the user name and
> password
>> to use.
>>
>>
>> It is recommended that you use a domain account, so that the
>> account
>> has rights to both the front-end Web server and the back-end database
>> server. The account you use must have rights to create databases in SQL
>> Server. In other words, this account must be a member of the Security
>> Administrators and Database Creators roles in SQL Server.
>>
>> 3.
>> Click OK.
>>
>>
>> If you have used a domain account that does not already have database
>> creation rights in SQL Server, you can give the account this access in
>> SQL
>> Server Enterprise Manager. This is a one-time only change. Once you have
>> granted database creation permissions to the account used by the Windows
>> SharePoint Services administration virtual server, this account can
>> create
>> databases for any subsequent virtual servers.
>>
>> Grant database creation rights in SQL Server
>>
>> Note To use SQL Server Enterprise Manager, you must be a SQL Server
>> database administrator.
>>
>> 1.
>> On your SQL Server computer, click Start, point to All Programs,
> point
>> to Microsoft SQL Server, and then click Enterprise Manager.
>>
>> 2.
>> In Enterprise Manager, click the plus sign (+) next to Microsoft SQL
>> Servers, click the plus sign (+) next to SQL Server Group, and then click
>> the plus sign (+) next to your SQL Server computer.
>>
>> 3.
>> Click the plus sign (+) next to Security, and then right-click
> Logins,
>> and click New Login.
>>
>> 4.
>> In the Name box, type the account in the form DOMAIN\name.
>>
>> 5.
>> Click the Server Roles tab.
>>
>> 6.
>> In the Server Role list, select the Security Administrators and
>> Database Creators check boxes, and then click OK.
>>
>>
>> After you configure the administrative virtual server (and grant SQL
> Server
>> rights to the new application pool account, if necessary), you must
> restart
>> Internet Information Services (IIS) by typing iisreset on the command
> line.
>> After IIS is reset, you can click the link on the Application Pool
>> Changed
>> page to continue configuring Windows SharePoint Services to work with
>> your
>> remote SQL Server computer.
>>
>> Connect to the remote SQL Server computer
>>
>> 1.
>> On the Set Configuration Database Server page, in the Configuration
>> Database section, enter the server name and database name to use.
>>
>> 2.
>> Under Database connection type, select Use Windows integrated
>> authentication (more secure, recommended).
>>
>>
>>
>> 3.
>> Click OK.
>>
>>
>>
> ****************************************************************************
> ***********************************************************
>>
>> After the last section I get the following error:
>>
>> "Login Failed for user 'NT AUTHORITY\NETWORK SERVICE' (Error code: 18456)
>>
>>
>>
>> I am lot to hot on SQL and guess the is an authentication error
>> connecting
>> to SQL
>>
>> Please advise on what to check
>>
>> Regards
>>
>> Jason
>>
>>
>
>
- Next message: Eric Phetteplace: "Re: Searching Documents"
- Previous message: van Rens: "Re: Login Problems"
- In reply to: Mike Walsh: "Re: Please help eleviate My frustration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
