Access is denied (from internet, 2008 RC0)
Jan Kucera
I've just installed Windows Server 2008 RC0 with Team Foundation Server.
First of all, Share Point services put themselves on the 80 port. Is there
any problem with just changing the port?
Okay, now the problem: I can access the site from local computer and I
want to do so from internet as well. So I assigned an address to the site in
IIS7, left it on the 80 port. Now, when I open the browser and log on, it
shows me this exception:
------------------------
Access is denied.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Access is
denied.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[COMException (0x80070005): Access is denied.
]
System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) +451
System.DirectoryServices.DirectoryEntry.Exists(String path) +190
Microsoft.SharePoint.Administration.SPMetabaseObject.get_Exists() +132
Microsoft.SharePoint.Administration.SPWebApplication.Lookup(SPFarm farm,
Uri requestUri, Boolean fallbackToHttpContext, SPAlternateUrl& alternateUrl,
SiteMapInfo& hostHeaderSiteInfo, Boolean& lookupRequiredContext) +1181
Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean
contextSite, SPUserToken userToken) +2609
Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean
contextSite) +74
Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext
context) +261
Microsoft.SharePoint.WebControls.SPControl.GetContextWeb(HttpContext
context) +25
Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object
oSender, EventArgs ea) +322
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
+92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +64
--------------
I use Windows authentication. What am I doing wrong? Or how could I
configure the SharePoint Services to by accessible from internet?
Thanks,
Jan
Mike Walsh
using it go to the beta newsgroups for that product.
Once it has been released, you are welcome to post questions on using
WSS 3.0 with it here - but not before.
Mike Walsh
WSS FAQ http://www.wssfaq.com
no private e-mail questions please
Jan Kucera
Server, since both WSS 3 and IIS7 are released.
Jan
"Mike Walsh" <englant...@hotmail.com> wrote in message
news:eSiw#UtHIH...@TK2MSFTNGP05.phx.gbl...
Mike Walsh
WSS 3.0 on the platforms for which it is specified. That is today
Windows Server 2003.
As soon as Windows Server 2008 is a released product then installing WSS
3.0 on that (which will a) use the same download that we use today for
WSS 3.0 installations on Windows Server 2003 and b) presumably have
Windows Server 2008 included by Microsoft in the list of supported
products) will be supported in the SP newsgroups.
Until then, why not install Windows Server 2003 and install WSS 3.0 on that.
If you then have questions in that environment (even if they are the
same ones as here) then we'll be glad to deal with them.
But people running betas know the rules for betas - if in doubt the
problem lies with the product that is in beta.
Mike Walsh
Jan Kucera
> problem lies with the product that is in beta.
>
Yes Mike. I am just completely new to the SharePoint Services and don't know
where to ask. I agree with you and I'd be glad if you could point me to the
place where you think it is appropriate to ask.
Jan
Mike Walsh
2008 is that you can amend the port number you do the initial install on.
What is certain is that you can at any time create another top-level
site that uses a different port.
The main problem however may well be something that only affects Windows
Server 2008.
Certainly you can access a WSS 3.0 site from the Internet provided the
server running it is accessible from the Internet and DNS is set up
correctly.
One thing you need to do (again in a normal environment ..) is to
specify Alternate Access Mappings if you want to be able to access
internally linked pages once you have got entry from the Internet to the
default.aspx page.
(Central Admin; Operations and it's on the top right)
Mike Walsh
WSS FAQ http://www.wssfaq.com
no questions by e-mail please
Mike Walsh
That should have been "my memory of the installation procedure .... for
Windows Server ****2003*****" !
Mike Walsh
Mike Walsh
(P.S.) It seems likely that IIS7 isn't available outside Windows Server
2008 at the moment and so that would mean it hasn't been released either!
Can you give a source that says it's released software ?
Mike Walsh
Frode Aarebrot
Actually, IIS7 is available with some versions of Windows Vista,
although it is not installed by default. However there doesn't seem to
be any clarity if this is a final version or a beta (or RC). IIS.net
still refers to IIS7 as a beta product (RC0), but all the documentation
about IIS7 in Windows Vista mentions nothing about it being a beta.
http://technet2.microsoft.com/windowsserver/en/library/10aac45e-e993-42a2-bf93-275375d662631033.mspx?mfr=true
http://msdn.microsoft.com/msdnmag/issues/07/03/IIS7/default.aspx
This is a bit on the sideline of the original topic, and I don't meant o
be nitpicking but I just thought I'd clarify.
Frode A.
Mike Walsh
In between the post saying it was released and me replying I checked
with a Microsoft contact but I presume he was thinking only of Server
software and not of Vista.
Mike Walsh (If anyone started nitpicking it was me!)
Jan Kucera
to be) the same product, on server or on Vista.
Well still, is there any "beta" newsgroup or forum? Since I still think this
is more WSS question than Widows one, or at least that people from Windows
will need people from WSS to look into it either way, don't they? :)
Jan
"Mike Walsh" <englant...@hotmail.com> wrote in message
news:eTv56r7H...@TK2MSFTNGP02.phx.gbl...
Mike Walsh
Windows Server 2003. Until Windows Server 2008 is in production that's
all that's available here.
Again in a mix of beta and other products, you assume any problems are
caused by the beta product unless you can duplicate using a full set of
non duplicate products.
If you feel your problems are with WSS 3.0, install Windows Server 2003
and reproduce them in that environment.
Neufusion
Microsoft RECOMMENDS posting to the microsoft public newsgroups about
their BETA product:
---
http://technet2.microsoft.com/windowsserver2008/en/library/6c504a47-4a82-459f-8755-fe59630f4e1d1033.mspx?mfr=true
Contact Us
Is this guide helpful? Does the Windows Server 2008 product
documentation meet your needs? Let us know how we're doing:
· Post to our newsgroup:
microsoft.public.windows.server.documentation
---
Where are you getting these rules from that you are enforcing against
the public newsgroup users?
Jan asked several times for the beta newsgroups you are referring to,
why do you continually refrain from providing them?
Sorry you had to spend time dealing with this Jan... It's something he
likes to do:
http://groups.google.com/group/microsoft.public.sharepoint.portalserver/browse_thread/thread/c3c6a774922de7f1/6e64eb7fa671b9fc#6e64eb7fa671b9fc
On Nov 4, 3:24 am, Mike Walsh <englantilai...@hotmail.com> wrote:
> Windows Server 2008 is still a beta product so questions on problems
> using it go to the beta newsgroups for that product.
>
> Once it has been released, you are welcome to post questions on using
> WSS 3.0 with it here - but not before.
>
> Mike Walsh
> WSS FAQhttp://www.wssfaq.com
> > Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object
> > oSender, EventArgs ea) +322
>
> > System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> > +92
> > System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> > completedSynchronously) +64
>
> > --------------
>
> > I use Windows authentication. What am I doing wrong? Or how could I
> > configure the SharePoint Services to by accessible from internet?
>
> > Thanks,
> > Jan- Hide quoted text -
>
> - Show quoted text -
Mike Walsh
the product that is in beta and it is their decision for their newsgroup.
I'm only repeating standard practice that if there is a problem with a
system with many products where one is in beta, the beta is judged to be
the cause of the problem.
Hence the requests to do the same things in a non-beta environment and
then ask the question if the same problem appears with the SharePoint
product in that *non-beta* environment.
It seems perfectly reasonable to me.
Mike Walsh
Neufusion
around everyone else to do. Why did Microsoft break your rules Mike?
Aren't you going to yell at them?
Yeah betas usually have problems, but thats why we have newsgroups
like these to have people help us figure that out.
Beta, RC, SP1, SP2, it doesnt matter. This is a Sharepoint GENERAL
newsgroup for asking general questions about sharepoint.
When are you going to answer these question that you keep ignoring?
> > Where are you getting these rules from that you are enforcing against
> > the public newsgroup users?
>
> > Jan asked several times for the beta newsgroups you are referring to,
> > why do you continually refrain from providing them?
On Nov 7, 9:03 pm, Mike Walsh <englantilai...@hotmail.com> wrote:
> They are recommending posting to a *Windows Server* newsgroup. That's
> the product that is in beta and it is their decision for their newsgroup.
>
> I'm only repeating standard practice that if there is a problem with a
> system with many products where one is in beta, the beta is judged to be
> the cause of the problem.
>
> Hence the requests to do the same things in a non-beta environment and
> then ask the question if the same problem appears with the SharePoint
> product in that *non-beta* environment.
>
> It seems perfectly reasonable to me.
>
> Mike Walsh
>
>
>
> Neufusion wrote:
> > That's funny Mike,
>
> > Microsoft RECOMMENDS posting to the microsoft public newsgroups about
> > their BETA product:
> > ---
> >http://technet2.microsoft.com/windowsserver2008/en/library/6c504a47-4...
> > Contact Us
> > Is this guide helpful? Does the Windows Server 2008 product
> > documentation meet your needs? Let us know how we're doing:
> > · Post to our newsgroup:
> > microsoft.public.windows.server.documentation
> > ---
>
> > Where are you getting these rules from that you are enforcing against
> > the public newsgroup users?
>
> > Jan asked several times for the beta newsgroups you are referring to,
> > why do you continually refrain from providing them?
>
> > Sorry you had to spend time dealing with this Jan... It's something he
> > likes to do:
> >http://groups.google.com/group/microsoft.public.sharepoint.portalserv...
> >> - Show quoted text -- Hide quoted text -