RE: Extending Sharepoint application into SBS Applications Site proble

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi,

I fixed this issue by:

1) running a restore of the ISS settings
2) removing all the files that the sharepoint new site wizard had created
3) replace any changed fiels form backup
4) re-installing RPC
5) adding a 'webserver' key to the RPC registry settings

Richard
"Richard Gascoigne" wrote:

Hi,

SBS 2008 Standard Edition, single server.

we accidentally extended a sharepoint application into the SBS Web
Applications site.

This led to problems with, the RPC over HTTP, OWA and autodiscover. we were
able to sort the OWA problem. This was achieved by restoring the IIS 7
settings for that site from a previous backup.

When we try and connect to autodiscover, we get the following errors in the
event viewer:

----------------------------------------

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 17/06/2009 20:53:16

Event time (UTC): 17/06/2009 19:53:16

Event ID: 52d1a5312b2c40bf961e168c1210bb48

Event sequence: 2

Event occurrence: 1

Event detail code: 0



Application information:

Application domain: /LM/W3SVC/3/ROOT/Autodiscover-2-128897419959523076

Trust level: Full

Application Virtual Path: /Autodiscover

Application Path: C:\Program Files\Microsoft\Exchange
Server\ClientAccess\Autodiscover\

Machine name: xxxxxx



Process information:

Process ID: 8360

Process name: w3wp.exe

Account name: NT AUTHORITY\SYSTEM



Exception information:

Exception type: FileNotFoundException

Exception message: Could not load file or assembly
'Microsoft.Exchange.Diagnostics, Version=8.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system
cannot find the file specified.



Request information:

Request URL: https://localhost:443/autodiscover/autodiscover.xml

Request path: /autodiscover/autodiscover.xml

User host address: ::1

User:

Is authenticated: False

Authentication Type:

Thread account name: NT AUTHORITY\SYSTEM



Thread information:

Thread ID: 8

Thread account name: NT AUTHORITY\SYSTEM

Is impersonating: False

Stack trace: at
Microsoft.Exchange.Autodiscover.Global.Application_Start(Object sender,
EventArgs e)





Custom event details:


--------------------------------

when using OutlookAnywhere, the user name and password and just constantly
asked for. Doing an RPC ping test, we get back a 401 error.


We have checked the configuration, tried to move the HTTP over RPC to a new
site on the server, but still have the issues.

I am assuming that something in the application extension for WSS3, caused a
conflict with the authentification required for outlook anywhere and
autodiscovery.

any help on tracing this would be appreciated.

Thanks,

Richard

.



Relevant Pages

  • Extending Sharepoint application into SBS Applications Site proble
    ... This led to problems with, the RPC over HTTP, OWA and autodiscover. ... An unhandled exception has occurred. ... Thread account name: NT AUTHORITY\SYSTEM ...
    (microsoft.public.windows.server.sbs)
  • Re: ByPassing Proxy for Certain Web Addresses
    ... I think it may be some group policys you have set override the "Exception" ... Settings | Internet Explorer Maintenance. ... This newsgroup only focuses on SBS technical issues. ... you may want to contact Microsoft CSS directly. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP Part II
    ... Connection tab> Enable proxy settings? ... Why is it not using RPC over HTTP....Anyone to help please? ... previous profile; should be profile setting as long as no other ... How do i try to connect RPC over HTTP within the LAN? ...
    (microsoft.public.exchange.admin)
  • Re: IIS 6 & ASPX
    ... >> Server Error in '/' Application. ... >> exist or is not accessible because of security ... settings. ... An unhandled exception occurred during the ...
    (microsoft.public.inetserver.iis.security)
  • Re: How do I restore a corrupted user.config file?
    ... In my experience user settings files inevitably get corrupted at some stage ... However this also fails with an exception if the config file iscorrupt. ... fileName = innerException.Filename; ...
    (microsoft.public.dotnet.languages.csharp)