Mike Walsh
Guest
|
Posted:
Sat Dec 25, 2004 5:37 pm Post subject:
Re: No access as administrator for SPS 2.0 |
|
|
This is the newsgroup for SharePoint Team Services (v1.0 2001).
The application you have installed is Windows SharePoint Services (WSS) [not
"SPS Team Services 2.0"] and you'll find its newsgroup at
microsoft.public.sharepoint.windowsservices
please post WSS questions there.
(For future reference the included MSDE is in fact WMSDE which is a special
version of MSDE 2.0 for WSS with the usual MSDE 2.0 restrictions removed at
the cost of only being able to use this version with WSS databases (and
search not being available).
[The answer is probably that until you specify in WSS that your Windows
password is allowed to access WSS, you can only access with the Name
(usually Administrator) and Passsword of the WSS Server. But if that doesn't
help please as above post follow-ups to the WSS newsgroup]
Mike Walsh, Helsinki, Finland
STS FAQ at http://www.collutions.com/Lists/FAQ
WSS FAQ at http://wss.collutions.com
Please reply to the newsgroup
"Eric" <evisser@vcontent.nl> wrote in message
news:O%23cpKFf6EHA.3840@tk2msftngp13.phx.gbl...
| Quote: | Installed SPS Team Services 2.0 from the Microsoft website (STSV2.exe) on
Windows Server 2003. Active directory was installed before SPS
installation from my administrators account
Installation of SPS went fine (no errors) with the included MSDE.
Verification in IIS showed the SPS websites under the standard Web Site.
So far so good.
Then Start/Services/Sharepoint Central Administration
Then in a new window, I was asked to connect to localhost:
Username: localhost\administrator (<== already filled out)
Password: xxxx (<=== I entered my Windows administrator password)
Result: again sign in window. after 3 attempts an error web page that I
was not authorized to view.
Q1: is the Windows administrator account useable as a SPS administrator
account or is a new account needed?
Q2: if administrator is is OK - what is the format to enter the account:
localhost\administrator@domain.com or what.
Thanks for any advice.
Rick
|
|
|