SBS IIS nightmares

Hello All,

I have a SBS 2003 server that appears as if IIS and is royally hosed, with no metabase back up or C drive backup no asr or system state backup. Basicly none of the sbs work space sites work I get page cannot be displayed from external clients. I have checked the paths the data and compared permisions and setting to a functional SBS 2003, Browsing the remote directory through iis mmc I get the error Server Error in '/Remote' Application. I have ran the fix reported online  aspnet_regiis -i to reregister with no luck.
Also other problems I am having
Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2114
Date:            10/1/2007
Time:            8:18:05 PM
User:            N/A
Computer:      SERVER
Process INETINFO.EXE (PID=1640). Topology Discovery failed, error 0x80040952.

Event Type:      Warning
Event Source:      ASP.NET 2.0.50727.0
Event Category:      Web Event
Event ID:      1310
Date:            10/2/2007
Time:            11:27:07 AM
User:            N/A
Computer:      SERVER
Event code: 3006
Event message: A parser error has occurred.
Event time: 10/2/2007 11:27:06 AM
Event time (UTC): 10/2/2007 6:27:06 PM
Event ID: 6a450bce28e74d65bc39951e7adaa8b8
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/1/ROOT-1-128358232183593750
    Trust level: WSS_Minimal
    Application Virtual Path: /
    Application Path: C:\Inetpub\companyweb\
    Machine name: SERVER
Process information:
    Process ID: 3768
    Process name: w3wp.exe
Exception information:
    Exception type: HttpParseException
    Exception message: Could not load type 'Backup.MainPage'.
Request information:
    Request URL: 
    Request path: /Default.aspx
    User host address:
    Is authenticated: False
    Authentication Type:  
    Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
    Thread ID: 1
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: True
    Stack trace:    at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
   at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath)
   at System.Web.UI.TemplateParser.ParseInternal()
   at System.Web.UI.TemplateParser.Parse()
   at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType()
   at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider)
   at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders()
   at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
   at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
   at System.Web.UI.PageParser.GetCompiledPageInstance(VirtualPath virtualPath, String inputFile, HttpContext context)
   at System.Web.UI.PageParser.GetCompiledPageInstance(String virtualPath, String inputFile, HttpContext context)
   at Microsoft.SharePoint.ApplicationRuntime.SharePointHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String pathTranslated)
   at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
   at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
 I have checked the permisions on the asp temp folder and they a correct.
Any help would be greatly appreciated

Who is Participating?
If there are that many problems why are you trying to save it?  Reinstalling will take about 5 hours for the base install then you have to restore your data.  It sounds like something is really really wrong and if you every want things back to normal than take your time and do it the right way.

Before you reinstall make sure you do the following:
Backup SharePoint
Backup Exchange
Backup User Folders

Check the IP config and the DNS name
Save any custom policies so that you can reapply them

Here come the links:

This first one is an hour long on how to recover Exchange.  Remember that with SBS you have a ful version of Exchange installed so anything they talk about in this webcast will work for SBS:
***Support WebCast: Recovery Storage Groups and Disaster Recovery in Microsoft Exchange Server 2003***

Here is the step-by-step for Recovery Groups
***How to use Recovery Storage Groups in Exchange Server 2003***

Don't know if you even care to try but....
***How to remove and how to install the Windows Small Business Server 2003 SharePoint Services companyweb Web site***

Now if you don't want to try to save SharePoint than that is ok but you might at least try to save the data.  Yes I know this says Web Edition but it should work for SBS also...
***How to use the SharePoint Portal Server 2003 backup utility on Windows Server 2003 Web Edition-based computers***

You should really take a look at this:
***How to perform a disaster recovery operation of SharePoint Services Companyweb and SharePoint Services Databases***

And lastly I asume you know how to save the users data by backing up the Users folder so I won't waste your time with that here.

Good luck!
Whenever you are using SBS you must always do things through the wizards.  If you try to use the IIS manager, AD Users and Groups, or any other type of Windows 2003 management tools you will create issues.  This is because everything in SBS is so tightly integrated.

To fix your websites you are going to have to reinstall the websites.  There is no other way to go about it.
Here is how to remove and reinstall SharePoint:

You may lose data though....  I would make sure you backup the SharePoint Database before you do this....

If OWA is hosed as well then you have real problems.  It may be time for a more in depth reinstall.

The only other thing I could suggest is that you pay the $200 and call Microsoft.  For the amount of time this is going to take you it would totally be worth a call to them.

Sorry to be the bearer of bad news.

Olaf De CeusterCommented:
Try the following:
Open IIS, right click on default website>properties >ASP.Net tab>Set ASP.Net version to 1.1.4322.
At comand prompt: type iisreset enter.
Run Internet Connection Wizard again: Server Management>To Do List> Point 2.
Also run point 3.
Get back to me with errors in eventlog if still not working.
Hope that helps,
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

DeBugComputerAuthor Commented:

I think I am "up a creek" this is something I inhearited.
Matt trying to uninstall sharepoint using M$ directions fails stating an unsupported version of sharepoint is being used.  @!#$%%^!!!
Olaf trying to run CEICW fails stating it can only be run on SBS server  @!$$%!!!!

There are so many problems it would take all night to list. No ASR no C: Drive backups no system state backups just data drive backup and exchange is backed up using batch file to copy database, sharepoint I have resigned to losing. anyone got any links to some good doc's that may pertain to the recovery and restore of a totaly horked SBS System???
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I agree with brownmattc for the most part... but before you even try reinstalling, I'd suggest that you take some time to learn a bit more about SBS.

Because much of your frustration seems to be coming from not having the right information to begin with...

For instance... you say that you ran "aspnet_regiis -i" but for which version of ASP .NET?  Because your errors indicate .NET 2.0 is installed and that's not what should be on the default site on an SBS.  It needs to be .NET 1.1.

Usually, uninstalling .NET 2.0 and re-registering .NET 1.1 with the following command will do the trick to fix things there:
C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i -enable

Then... "CEICW fails stating it can only be run on SBS server"
well... yeah... so why didn't you run it from the SBS?  In fact, how did you even run it on a different machine?  You should NOT run any of the SBS wizards from their .exe files directly.  Always use the SBS's Server Management Console, where you'll find the CEICW listed in the Internet & Email Snap-in as "Connect to the Internet".

Plus... "No ASR no C:"
SBS doesn't use ASR.  Instead, it has a built-in Backup that uses NTBackup quite effectively.

So before you go off on how this server is configured, make sure that at least you understand how it's supposed to be done so that you can get it working correctly in the least amount of time.

Forced accept.

EE Admin
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.