[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 974
  • Last Modified:

You are not authorized to view this page !

I just installed Microsoft Share point portal server 2003. My intranet pages won't come up now. Not even the sharepoint administration page. Everything seems to look o.k. in IIS. When I look at the sharepoint services on the IIS page;the "default web page", "Company web", and all the others listed on this page, I see that they are all running and don't show any errors in IIS. The result when I try to access the "http://companyweb" page locally, I get the error "you are not authorized to view this page" and an error code 403. I am logged on as the administrator of that local server. When I try to access the other management pages I get similar errors such as "This page can not be displayed" error 401.2. I am getting very frustrated so I hope someone can help. I am trying to learn this stuff, but there is a tremendous amount of information to learn. I was running share point services just fine a week ago. It's when I tried to upgrade to portal server that my troubles began. Now I can't get either to work. Right now I have portal server 2003 installed, using it's installation of share point services. Thank You!
0
scottdfreer
Asked:
scottdfreer
  • 5
  • 3
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You installed SharePoint Portal Server on your SBS??  Unfortunately this is NOT a supported configuration because SPS cannot be on the same box as Exchange.

At this point you may have to completely reinstall your SBS, because as far as I know, uninstalling SPS will still leave most everything broken.

If you have a full backup made prior to doing this major installation, then you could just restore that.

One thing to learn is that you should never do ANY installation of a server product without following a known method.  There are deployment manuals for EVERY Microsoft product, and those should be your guiding base.

Jeff
TechSoEasy
0
 
scottdfreerAuthor Commented:
Jeff,

Thank-You. Finally, someone who knows what they are talking about and communicates it clearly. In this forum, I usually get a link to something that doesn't really help me, but I award the points anyhow because the person tried. Allow me to introduce myself. I live in a rural part of Pennsylvania. I have worked with computers since about 1989, but never on a server level until now. I have a full time job as a design engineer, where I use most of the available Microsoft Office products and various engineering software. I am also working on starting a part time business; repairing computers and building new computers, pre-installed with Microsoft products. I am a registered partner with Microsoft and have recently subscribed to the "action pack" program. I have nothing to lose with this particular server, as I am just using it for my education. There is no important data on it. I will start over based on your advise and just install SBS 2003. Where would I get the deployment manual you mentioned? I assume somewhere on the Microsoft site. If you know exactly where, could you direct me there? Again, I really appreciate your help and I hope you are available as a resource for me in the future.

Sincerely,
Scott Freer
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Scott,

Pleased to meet you, and thank you for the compliment.  It is true that unfortunately, many responses on EE are from folks that love to just Google and post.  (The worst is when they post a link that shows their search string).

However, that problem is usually a response to the fact that many people who post questions on EE regarding VERY COMMON errors and either didn't bother, or don't know how to properly search for an answer.  Or worse, they post a complete error message with the line:

"For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp"

And never clicked on that link to see what it said... because many, many error events now have rather good documentation associated with them.

Anyhow... enough venting/ranting...

Your particular issue is not one of those.

You'll find deployment manuals titled either "Deployment Guide" or "Getting Started Guide" for most Microsoft products.  For SBS, you'll find most all documentation here:  http://www.microsoft.com/windowsserver2003/sbs/techinfo/productdoc/default.mspx.  Specifically the Getting Started Guide is here:  http://sbsurl.com/start (I use my own redirects to access documents that I use often).

As a Microsoft Partner, you'll also find resources for all products in the partner portal's "Products and Solutions" section:
https://partner.microsoft.com/US/productssolutions

Hope these are good places for you to start... good luck!

Jeff
TechSoEasy
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
FYI, I just came across this page yesterday and thought it may interest you:  http://www.microsoft.com/WindowsServer2003/sbs/techinfo/planning/chartsbs.mspx

Jeff
TechSoEasy
0
 
scottdfreerAuthor Commented:
Hi Jeff,

Thank-You. That chart really spells it out doesn't it? I re-installed SBS on my server and now the sharepoint web pages come up just like they should. The only problem I'm having now is getting the web page to come up on the client computer. Maybe I don't have everything set up right yet, or maybe a lingering problem from before on the client. I'll work on it some more before I post a question here. Unless, you have some advice. Talk to you later. Thanks for all the help.

Sincerely,
Scott Freer
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You haven't set up your client machines properly then... they MUST be joined to the network using http://<servername>/connectcomputer, if you haven't done that then you need to correct by using these steps:

The following needs to be done with the client machine:
1.  Log in with THAT machine's LOCAL administrator account.
2.  Unjoin the domain into a WORKGROUP
3.  Change the name of the computer (this is not an option, you must use a name that is unique and hasn't been used before on your SBS)
4.  Delete or rename the following directory C:\Program Files\Microsoft Windows Small Business Server\Clients if it exists
5.  Make sure that the network settings are configured to get an IP address automatically (DHCP enabled)
6.  Reboot

Then on the server, from the Server Management Console:
1.  Remove the client computers if it still shows in the Client Computer screen on the Server Management Console
2.  Add the client with it's NEW name using the Add Computer wizard

Then, go back to the client machine and join the domain by opening Internet Explorer and navigating to http://servername/connectcomputer

This really should have been in a separate question... but I already had those steps on my clipboard from the last question I answered... so you get a freebie! :-)

Jeff
TechSoEasy
0
 
scottdfreerAuthor Commented:
Thank You very much ! I'll put some extra points in the next question. I hope there won't be any for a while, but it's bound to happen sooner or later.

Scott
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
don't worry about it, I have plenty!  :-)

Jeff
TechSoEasy
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now