Re: RPC over HTTPS fails following install of SharePoint Services
- From: Andrew <Andrew@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 6 Apr 2007 09:38:01 -0700
I contacted Microsoft (through their paid problem solving service) and with
them tried various things. There was a short period of time when I managed to
get RPC and Sharepoint 3 working at the same time - this happened just after
I tried installing a brand new database (rather than my old one) onto the web
site. However, I am also switching to a new server and on the new server I
have not been able to make it work at all - having tried and retried all the
things Microsoft suggested.
In the end I have gone for a "workaround" solution - I have set up a second
URL pointing to my firewall so I have abc.no-ip.com and xyz.no-ip.com both
pointing to the same IP address. Then I used Sharepoint to create a new
(extra web site) on my server and adjusted the host header values so that one
is abc.no-ip.com and the other is xyz.no-ip.com. Both servers run under port
80 so they get through firewalls OK but only the default web site has SSL
running (the other has blank in the ssl port).
On the default web site I am continuing to run the RPC service, OWA, etc.
and on the extra web site I am now running the sharepoint service and for now
all seems to be well. The only down side is that the sharepoint service is
not running under SSL (Outlook must have the SSL service).
hope that helps
Andrew
"Eric" wrote:
I have also the same problem. Did you find any solution to keep SharePoint.
Service 3.0 on the same server and have it working?
Eric
"Andrew" wrote:
I also have the same problem - the issue seems to be that Sharepoint Services
3 stops the RPC service working correctly. If I remove the Sharepoint Web
Application from the web site then everything works again OK. Any ideas as to
what could be wrong?
OWA is still working it is just Outlook over HTTPS that has stopped and
there are the exceptions in the event log as detailed by Chris.
Hope you can help
Thanks
Andrew
"Andrew Sword [MVP]" wrote:
Here's a link to help troubleshooting.
http://support.microsoft.com/kb/827330
<Chris.Daunt@xxxxxxxxxxxxx> wrote in message
news:1169151685.720634.123390@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I yesterday did an inplace upgrade of Windows SharePoint Services 2.0
to 3.0 which runs on the same server as Exchange. RPC over HTTPS was
until this point working fine but has not been since. All other
Exchange functionality seems to be OK including OWA access over an SSL
connection. The only error I can find is below (I've changed machine
names and IPs) and help would be greatly appreciated.
------------------------------------------------
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 18/01/2007
Time: 16:22:02
User: N/A
Computer: ExchangeServer
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18/01/2007 16:22:02
Event time (UTC): 18/01/2007 15:22:02
Event ID: 4a4f2c7d4a604b97b212f8f5918e9093
Event sequence: 6
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT-1-128136073211908644
Trust level: WSS_Minimal
Application Virtual Path: /
Application Path: C:\Inetpub\wwwroot\
Machine name: PSI-SRV03
Process information:
Process ID: 3092
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: HttpException
Exception message: Path 'RPC_IN_DATA' is forbidden.
Request information:
Request URL:
https://ExchangeExternalFQDN/rpc/rpcproxy.dll?ExchangeInternalFQDN:6001
Request path: /rpc/rpcproxy.dll
User host address: xxx.xxx.xxx.xxx
User: DOMAIN\username
Is authenticated: True
Authentication Type: Basic
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 6
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at
System.Web.HttpMethodNotAllowedHandler.ProcessRequest(HttpContext
context)
at
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
Boolean& completedSynchronously)
Custom event details:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------
Thanks in advance
Chris
- References:
- Prev by Date: Re: Global Send Delay possible?
- Next by Date: user@xyz.local delivery issue
- Previous by thread: Re: RPC over HTTPS fails following install of SharePoint Services
- Next by thread: Re: Global Send Delay possible?
- Index(es):
Relevant Pages
|
