Re: Chad Gross companyweb wss3 & SQL2000

Tech-Archive recommends: Fix windows errors by optimizing your registry

Costas,

Sorry.. forgot to specify that "Select Windows SharePoint Services search
server" is STILL Greyed out.

Brian

"Costas" wrote:

Brian,

Don't set the 'Search' server at this point. You can do that later. As far
as accessing 'intranet' you'll have to create an A record in the DNS that
points 'intranet' to the IP address of the server. The 'Timer' Service is a
service created by the SharePoint installation that takes care of different
tasks. It requires an account to run and that account must be the same as
the one running the Application Pool. Don't worry at this point as it will
be setup for you.

After you do the above, make sure you can access the site by typing
http://intranet. Then go back to the Central Administration site,
Application Management and select 'Content databases'. Click on the content
database and set the 'Search Server' to the server name that the database
engine is installed

--
Costas


"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2D709C19-78F4-4743-87CE-5285229C7B5B@xxxxxxxxxxxxxxxx
Costas,

I am going to 'in-line' this one.
(Search service needs two Accounts)
please see below.


the 'IIS Web Site' is correct. You want to create a new web site that
will
host your application.

Done!

The load balanced URL should be the same as the name of the host header
you
gave, assuming you selected port 80. You shouldn't have to change
anything
there. If you typed "intranet" as your host header, then the Load
Balanced
URL should display "intranet".

The URL that displayed was 'intranet:80'. I changed it to (just)
'intranet'.

The Application Pool need a new user account that you must create.
Create a
new domain user, give it a password (and make sure you enable the
'Password
never expires' to prevent disconnects) and then make that user account, a
member of the IIS_WPG and WSS_ADMIN_WPG security groups. This account is
very important and it will be the same account for both the Application
Pool
and the Timer Service.

Done! (but Im not sure what the "Timer Service" is)

The database content will be created for you automatically. You can
change
the name if you like, of you can select the default. Windows
authentication
is the recommended method so leave it as it is. and under Search Server
select the name of the server were the databases exist (you should be
able
to see if in the listbox).

OK! I see the content database was added to the SQL server.

Under "Seach Server" I still could not make a selection.. it was greyed
out!

Still can not access //intranet/

I see in the "Administrator Tasks"(in "Central Administration") that "You
must start the Windows SharePoint Services Search service on at least one
of
your front-end Web servers."

When I start the "Search Service" it prompts for:
"Service Account" and "Content Access Account" I am thinking that these
will be the accounts I created ealier in his process... BUT I'm not sure
which is which.
ALSO
Under "Search Database" I guess that "Windows authentication
(recommended)"
should be selected, (not "SQL authentication") YES?


Thanks again,
Brian



"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E72E5E95-5154-41F9-9D19-0D4B6EC22EA7@xxxxxxxxxxxxxxxx
Costas,
OK.. so far so good.

At this point there is NO 'SharePoint - 80' web site OR 'Web
Application'.
Chad does not include instructions on creating a new 'Web Application'.
He proceeds on the assumption that a 'Web Application' was created
along
with a 'Default Website'.

So I want to make sure I get this part right also.

On the "Create New Web Application" page, I should select:

"IIS Web Site"
"Create a new IIS web site" w/ "Description" = 'Intranet' (Not "Use
an
existing IIS web site")
"Port" = '80'
"Host Header" = 'Intranet'

"Load Balanced URL"
"URL" = 'http://Server:80/' ????? (or http://Intranet)
"Zone" = 'Default'

"Application Pool"
"Create new application pool" = 'SharePoint - Intranet'
"Select a security account for this application pool"
"Predefined" = 'Network Service' ??????
OR
"Configurable" "User name" = 'Same as the new user account that
was
added to 'domain users' group' ????? or Administrator

"Database Name and Authentication"
"Database Server" = 'server\SharePoint3'
"Database Name" = 'WSS_Content' ????? will be created
automatically?

"Windows authentication (recommended)" ????? not SQL
authentication.

"Search Server" = 'blank' (because I'm using SQL, right?)


Thanks, I really appreciate the walk though!
Brian

"Costas" wrote:

Brian,

For user name, do not use the Administrator account for security
purposes.
Create a new user account, add it to the 'domain users' group, with no
other
permissions. Make sure you check the 'password never expires'
otherwise
you
you will 'failure to connect to the database' when the password is due
for
renewal.

Under Configuration Settings user NTLM, unless your domain is setup
for
Kerberos authentication. NTLM is the easiest to use within a
SharePoint
environment. Leave Active Directory Account Creation Mode unchecked.

Let me know if you need any help with this

--
Costas


"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:700CD9E2-7F04-4684-A7BD-CCEF13B25FE0@xxxxxxxxxxxxxxxx
Costas,

Just want to make sure I am getting this setup right..

In the "SharePoint Products and Technologies Configuration Wizard"

"Connect to a server farm" = 'No, I want to create a new server
farm'

"Specify Configuration Database Settings"
"Database server:" = 'Server\SQL.intance'
"Database name:" = 'SharePoint_Config'

"Username:" = 'Domain\ADMINISTRATOR" ?????

"Configure Security Settings" = 'NTLM' ?????

"Enable Active Directory Account Creation Mode" = 'Unchecked'
?????

Thanks Costas!
Brian


"Costas" wrote:

Brian,

I don't think the default web site is created when you choose the
'Front-End
Server' option. I don't remember but event if that's the case, you
don't
need it. Just follow Chad's instructions on how to create a new
Web
Application which ultimate will be the one that you will be using.

Just to make sure, if a default site had been created, in IIS you
should
have seen a site with the name 'SharePoint-80' and the Default Web
Site
would have stopped (that's because they both occupy port 80 without
a
host
header)

--
Costas


"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13DFF1E8-F1CC-4FE7-AD04-3C97091849FF@xxxxxxxxxxxxxxxx
Can anybody get me back on track with this?
SBS 2003 SP2 (not R2) & SQL 2000

I am trying Chad Gross's (unsupported) Companyweb & Sharepoint v3
setup,
that can be found here:
http://msmvps.com/blogs/cgross/archive/2007/01/25/companyweb-sharepoint-v3-part-1.aspx

I am trying to integrate a SQL2000 backend to the Sharepoint v3
install,
using:
http://msmvps.com/blogs/cgross/archive/2007/05/28/using-your-sql-in-sbs-r2-premium-as-a-back-end-for-wss-3-0.aspx

I get to Chad's Part 4, that states to go through STEP 3 of the
MS
"side-by-side" setup. In MS's STEP 2 (page 7 under step 4b), I
selected
"Front-End Server".
Now when MS's STEP 3 concludes, it does not seem that a Default
Web
site
is
created.

How can I create the "Default" WSS3 (port 80) site?

Thanks!
Brian





.

Relevant Pages

  • RE: transfer companyweb config db
    ... configuration database for sharepoint services to a new location on the sql ... You may mistake SQL server conception. ... Move the Monitoring Database ... >project web access not working correctly is to use a config database on ...
    (microsoft.public.windows.server.sbs)
  • I broke Sharepoint :(
    ... SBS was installed and the server was up and running including the default ... After 2 days I was looking at SQL backups I relaised that Sharepoint ... database and the other instances were not migrated accross. ...
    (microsoft.public.windows.server.sbs)
  • Re: Service Account Password Change
    ... app pools and changed the passwords, when I got to the sharepoint admin ... the sharepoint domain account didnt have the database admin ... Our dev environment is a domain member server running sharepoint portal ... > Detach from the config database in SharePoint Central Administration ...
    (microsoft.public.sharepoint.portalserver)
  • Steps for Migrating WSS 3.0 from Windows Internal Database to Microsoft SQL 2005
    ... done the stupid things I did when I started playing with Sharepoint ... when I first installed it and assuming that it would find the SQL 2005 ... Windows Internal Database). ... Reboot the server to finish up any uninstall scripts. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: ADP/SQL Server 2000 Security Problem
    ... The server is running Windows 2003. ... I'll also test using a SQL Server account and see what happens. ... it worked in MSDE 2000. ... I have not created any new accounts for the production database. ...
    (microsoft.public.access.adp.sqlserver)