|
Home > Archive > Microsoft Content Management Server > February 2004 > The virtual server that is referenced here is not in the config database with SharePoi
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
The virtual server that is referenced here is not in the config database with SharePoi
|
|
| Mark Roberts 2004-02-05, 10:37 am |
| Hi,
I have MCMS 2002 SP1a and SPS2003 running on a 2003 Server.
I have installed the newly released SPS Connector, and get the
following error when clicking on a SharePointDocumentPlaceHolder
control in a new page.
The virtual server that is referenced here is not in the config
database
Stack trace:
[COMException (0x81070552): The virtual server that is referenced here
is not in the config database.]
Microsoft.SharePoint.Library.SPRequestInternalClass.OpenSite(String
bstrUrl, Boolean bGetUrlOnly, String& pbstrServerRelativeUrl, Guid&
pgSiteId, Int32& pOwnerID, Int32& pSecondaryContactID, DateTime&
pdtLastContentChange, DateTime& pdtLastSecurityChange) +0
Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String&
A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7)
[SPException: The virtual server that is referenced here is not in the
config database.]
Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String&
A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7)
Microsoft.SharePoint.SPSite.get_ServerRelativeUrl()
Microsoft.SharePoint.SPSite.get_RootWeb()
Microsoft.ContentManagement.SharePoint.Dialogs.WssDocumentSelectorControl.updateCurrentVirtualServer(Int32
selectedIndex) +251
Microsoft.ContentManagement.SharePoint.Dialogs.WssDocumentSelectorControl.CreateChildControls()
+716
System.Web.UI.Control.EnsureChildControls() +100
Microsoft.ContentManagement.SharePoint.Dialogs.WssDocumentSelectorControl.OnInit(EventArgs
e) +457
System.Web.UI.Control.InitRecursive(Control namingContainer) +241
System.Web.UI.Control.InitRecursive(Control namingContainer) +179
System.Web.UI.Control.InitRecursive(Control namingContainer) +179
System.Web.UI.Control.InitRecursive(Control namingContainer) +179
System.Web.UI.Page.ProcessRequestMain() +174
I have sharepoint and MCMS on different webs on the same server, each
with their own IP address, and DNS entry. The SPS Web Site has IP
address unconfigured (i.e. it's using the IP address of the machine),
whereas the MCMS site has a different IP address configured.
Could it be that I need to configure the connector to point to the
correct Sharepoint Server? Is there any way of telling exactly what
'Virtual Server' is being incorrectly pointed to?
Any assistance would be most appreciated.
Mark.
| |
| Luke Nyswonger [MSFT] 2004-02-06, 4:40 am |
| Hi Mark,
You are receiving this error as a result of an unsupported configuration in
your envrionment.
If you install Microsoft Content Management Server 2002 (MCMS) and
SharePoint Portal Server (SPS) or Windows SharePoint Services (WSS) on the
same computer, you must also install them on the same virtual server. This
is a requirement for this feature of the product. So, MCMS and SPS/WSS can
either be installed on the same virtual server, or different virtual
servers on different boxes, but not different virtual servers on the same
box.
Regards,
Luke [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights. You assume all risk for your use. © 2003 Microsoft Corporation. All
rights reserved.**
| |
| Mark Roberts 2004-02-08, 11:35 pm |
| Hi Luke
I've tried to get MCMS and SPS2003 to run together on the same Virtual Web,
but it doesn't work.
I use WSS to extend the same virtual web as MCMS, which enables SPS2003 ok,
but then I cannot access the MCMS stuff - I get an SPS error ('404 NOT
FOUND')
I've tried to exclude the MCMS root channel from being managed by SPS2003,
and then I get an access is denied error when trying to access the MCMS
page.
Is there a definitive setup process for having SPS2003, MCMS2002 SP1a (and
additional ASP .NET C# Web Applications) running on the same Virtual Web?
Regards,
Mark.
""Luke Nyswonger [MSFT]"" <LukeN@online.microsoft.com> wrote in message
news:ndcUQwN7DHA.1992@cpmsftngxa07.phx.gbl...
> Hi Mark,
>
> You are receiving this error as a result of an unsupported configuration
in
> your envrionment.
>
> If you install Microsoft Content Management Server 2002 (MCMS) and
> SharePoint Portal Server (SPS) or Windows SharePoint Services (WSS) on the
> same computer, you must also install them on the same virtual server. This
> is a requirement for this feature of the product. So, MCMS and SPS/WSS can
> either be installed on the same virtual server, or different virtual
> servers on different boxes, but not different virtual servers on the same
> box.
>
> Regards,
> Luke [MSFT]
>
> **This posting is provided "AS IS" with no warranties, and confers no
> rights. You assume all risk for your use. © 2003 Microsoft Corporation.
All
> rights reserved.**
| |
| Stefan [MSFT] 2004-02-09, 12:35 am |
| Hi Mark,
check out this article for 404, SPS and CMS:
http://support.microsoft.com/default.aspx?id=835248
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Roberts" <markalroberts@hotmail.com> wrote in message
news:eV$xQow7DHA.1040@TK2MSFTNGP10.phx.gbl...
> Hi Luke
>
> I've tried to get MCMS and SPS2003 to run together on the same Virtual
Web,
> but it doesn't work.
>
> I use WSS to extend the same virtual web as MCMS, which enables SPS2003
ok,
> but then I cannot access the MCMS stuff - I get an SPS error ('404 NOT
> FOUND')
>
> I've tried to exclude the MCMS root channel from being managed by SPS2003,
> and then I get an access is denied error when trying to access the MCMS
> page.
>
>
> Is there a definitive setup process for having SPS2003, MCMS2002 SP1a (and
> additional ASP .NET C# Web Applications) running on the same Virtual Web?
>
>
>
> Regards,
> Mark.
>
>
>
> ""Luke Nyswonger [MSFT]"" <LukeN@online.microsoft.com> wrote in message
> news:ndcUQwN7DHA.1992@cpmsftngxa07.phx.gbl...
> in
the[color=blue]
This[color=blue]
can[color=blue]
same[color=blue]
> All
>
>
| |
| Mark Roberts 2004-02-09, 10:37 am |
| Thanks, that helped me out.
Another problem arises from keeping MCMS, SPS and Custom Web Apps on
the same virtual web: Previously, I had a default document
'frontpage/main.aspx' that called webform in a C# web app (frontpage)
to kick off the site.
Now, since SPS is hooked in at ISAPI level, it never gets this far,
and shoots off to default.aspx on the portal server (which is
certainly not what I want)
Besides some awful kludge with putting an iframe or a client-side
redirect in default.aspx on the root of SPS, can anyone tell me how I
can have the default page of a virtual web site hosting SPS be outside
SPS? Or how I can configure SPS to redirect to another page more
elegantly (by using a server.redirect for example)
Thanks for helping me out here 
Regards,
Mark.
| |
| Luke Nyswonger [MSFT] 2004-02-09, 12:35 pm |
| Yep, that is another problem that one must contend with, but that happens
regardless whether CMS is on the machine. As you stated this is the SPS
filter doing that and can only be bypassed by excluding that path. Here is
an article you may be interested in as well:
835250 You receive a "Web Access Failed" error message when you create an
MCMS
http://support.microsoft.com/?id=835250
As far as how to get a single page within a path that is excluded to have
IIS render, I do not think there is any way as you can only include/exclude
"paths" and not files. I haven't tested but you might be able to exclude
the root [(root)] rather than have an explicit inclusion. Since the "sites"
and "personal" paths are already excluded, you can still have portal sites
and other web apps. Not sure though, but this type of question is better
posted in the SPS newsgroup.
Regards,
Luke [MSFT]
**This posting is provided "AS IS" with no warranties, and confers no
rights. You assume all risk for your use. © 2003 Microsoft Corporation. All
rights reserved.**
|
|
|
|
|