Re: Error Code 403

I've reinstalled with same results. I have performed the best practices
scan. Everything is fine until it fails connecting to SQL Server--It
says-Microsoft SQL Server does not exist or access denied. Those are the
only issues it had. Everythong else processed normally.

Still get Error 403 access denied on remote access.

Also now the Windows Update Services reports the SQL error as above.

"Merv Porter [SBS-MVP]" wrote:

Sounds like a plan Bart. Don't forget to run the SBS 2003 BPA after (or
even before and after) the reinstall to get a baseline reading on your SBS
configuration.

--
Merv Porter [SBS-MVP]
============================
"Bart" <Bart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7F9C0CD1-23C7-486D-BDD6-0424851D4485@xxxxxxxxxxxxxxxx
I've had to reinstall a coupe of things and probalby messed things up.
Accessing RWW is the only problem I'm having now. I will take you advise
and
reinstall RWW. If I have have a problem after doing that I'll post back.

Thanks.

"Merv Porter [SBS-MVP]" wrote:

While you may be able to fix your RWW problem by installing the
remote.aspx
file in the proper directory, I'd be concerned why it was missing in the
first place. I'd also wonder if something else was missing.

You could do a reinstall of RWW which should correct the mssing file and
any
other problems that might be present:

To Reinstall RWW
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/3a671f95de265047?hl=en&ie=UTF-8&q=%22Setting+Up+RWW%22

You might also want to install, update and run a scan with the SBS 2003
BPA
before you do anything:

Microsoft Windows Small Business Server 2003 Best Practices Analyzer
http://www.microsoft.com/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

--
Merv Porter [SBS-MVP]
============================

"Bart" <Bart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0C244966-5E84-449F-AA18-479FF5468F6A@xxxxxxxxxxxxxxxx
I am missing the remote.aspx file to be located in the C:\Inetpub\Remote
directory which is also shown in the virtual default IIS directory.
Can
someone send it to me. I've determined this need by prior searching of
boards to arrive at this answer. Thanks






.

Relevant Pages

  • Re: Reinstalling SQL 2000 on a failed node
    ... This step tells SQL that it is no longer installed to the failed node. ... You will see some timeout errors since it cannot find the original node or the installation. ... Once SQL sees itself as being installed on one node, you can reinstall it to the other node and patch it to match. ... See "Maintaining a Failover Cluster" in BOL. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Accidently removed monitoring tool and cannot reinstall
    ... David, I checked and could not find a mssql$sbsmonitoring ... I have under Program Files SQL Directories ... Any idea how to reinstall the missing directory ... If this error persists, run the Monitoring ...
    (microsoft.public.windows.server.sbs)
  • Re: Deployment - Active Directory and SQL Server
    ... SQL probably does not have to be ... If that server is heavily used, then adding TS may very well wreck ... >> Domain Server and therefore I agree that the only option is to install TS ... >> but I am very worried about having to reinstall SQL etc... ...
    (microsoft.public.windows.terminal_services)
  • Re: Deployment - Active Directory and SQL Server
    ... SQL probably does not have to be ... You will want to check the resource usage of the server before installing ... > Domain Server and therefore I agree that the only option is to install TS ... > but I am very worried about having to reinstall SQL etc... ...
    (microsoft.public.windows.terminal_services)
  • Re: Lost MSDE sa password
    ... >> Later when you reinstall SQL Server successfully, ... > You're on the right track except replacing the newly installed master ...
    (microsoft.public.sqlserver.security)
Loading