Re: New install, login not accepted

Yeah, that would be my guess. I know I have seen other posts on here about
problems with SQL 2005 but I never really read what the problem or solution
was. I sure don't know what else would be causing it.

Dan

"Jim I." <JimI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D812B6F1-3721-41B5-B1B3-5CA3DD7148AC@xxxxxxxxxxxxxxxx
Thanks again. I have actually done two installs, and come up with the
same
problem. I tried to upgrade the site, which was running with MSDE, to SQL
2005. I had a problem with this, so deleted the WSS sites, and tried to
install SPS. I got to the same point and had the same failure. I then
completely re-built my server (a fresh Windows 2003, SQL 2005, and finally
SPS). I got through the install following the steps in the Admin. Guide
right up to this point, and had the same failure.

Maybe this is an issue with SQL 2005?

Jim

"Dan Marth" wrote:

Jim,

You may want to re-install, when those accounts get messed up it is not
fun
to get them working again. What happens when you install SPS it prompts
for
a admin account, that account needs admin rights to SQL and the local
box,
it then creates then configures all the services and app pools to run
under
that account and it gives only that user admin rights to the portal.
When
the install is done, that user is the only user that can login to the
portal
and create new other admin users.

If somehow that got messed up, you would need to check all the SPS
services,
the app pools (one for SPS and one for central admin) and make sure the
user
is also an admin in SPS, which you can't do because you can't login as
anyone.

I have been there and I have always re-installed after making sure the
user
account I was going to use had full admin rights to every server and
database in the farm (in your case it's just one server) as well as
making
sure I had the correct password for that user account.

Hope that helps,
Dan

"Jim I." <JimI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:28C29B61-B887-4357-8059-810003B3BE83@xxxxxxxxxxxxxxxx
Thanks for the feedback. The SharePoint Server Admin. guide stated the
account should be a member of the Power Users Group, so this is what I
assigned them to. I have, however, added the user to the admin. group
and
it
still did not work.

As for SQL 2005, I have a prospect that is working with this
configuration
and wanted to replicate it.

Any other thoughts?

Jim

"Dan Marth" wrote:

Jim,

Why Power Users Group? I am pretty sure it should be domain admin
with
local admin rights to the web server box and the database server box.
As
far as SQL 2005, I wouldn't have went there...........I am sure how
compatible it is with SharePoint. Maybe someone else can shed some
light
on
that subject.

Thanks,
Dan
"Jim I." <JimI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF5259CF-363D-46DC-9A9C-248A3DA1D3DF@xxxxxxxxxxxxxxxx
A bit more on this problem. I have tried changing the IE settings to
"Automatically login with current user name and password." I also
do
not
think this is a dns issue, as I do get the login box. I have tried
using
the
IP address in the url, and get the login box fine, but the user name
and
passwork are still not accepted.

I think this might to related to the Application Pool, but am not
sure
how
to resolve it.

Jim

"Jim I." wrote:

I have installed SPS on a fresh Windows 2003 R2 installation. I
installed
Windows 2003 and SQL 2005, updated the Windows patches, and then
installed
SPS. This is a stand alone server. When installing SPS, I entered
the
admin
account when prompted. This is a Windows user account, a member of
the
Power
Users group.

I can log onto the comupter with the account, but it is not
accepting
it
for
SPS. Any suggestions?

Thanks,
Jim








.

Relevant Pages

  • Re: New install, login not accepted
    ... install SPS. ... I got through the install following the steps in the Admin. ... a admin account, that account needs admin rights to SQL and the local box, ...
    (microsoft.public.sharepoint.portalserver)
  • Re: New install, login not accepted
    ... a admin account, that account needs admin rights to SQL and the local box, ... the install is done, that user is the only user that can login to the portal ... If somehow that got messed up, you would need to check all the SPS services, ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Full Text Indexing security
    ... The NT Authority\System account is a system account, ... By removing the BuiltIn\admins no admin will be able to administer SQL ... Looking for a SQL Server replication book? ... > exec sp_defaultdb N'NT Authority\System', ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Guest Account being enabled
    ... Therefore....I'm clueless when it comes to SQL. ... the SA account is using SQL and the password is stared. ... >>I have a User Account named Administrator. ... >>>When you say rename the Admin account....do you mean ...
    (microsoft.public.security)
  • Re: Running SQLServer and SQLServer Agent as Power User
    ... > We're trying to limit the number of user accounts with Admin level permission ... > on our Win2K servers, ... Or does this account NEED to be local admin ... although not all sql feature are available. ...
    (microsoft.public.sqlserver.security)