Re: Problems after SP2

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

Hi Dave,

Well, I'm back at the client. Installed Exchange SP2, Sharepoint SP1, SBS
SP1, Vista compatiblity etc with the only notable failure being Outlook 2003
SP1 which we don't care about.

RWW still doesn't work. Testing as Domain Administrator, RWW is enabled. BPA
notified that RWW wasn't using ASP.NET v1 so I changed it from ASP.NET v2.
CompanyWeb got the same complaint but the setting is disabled so it's stuck
at v2.

Any other suggestions would be appreciated.

Thanks!

Michael



"Dave Nickason [SBS MVP]" wrote:

For RWW, I'm assuming you've checked the basics? It's enabled on the SBS,
the account you're logging in with has the appropriate rights, nothing
noteworthy in the logs?


"Michael Appelmans" <news@xxxxxxxxxx> wrote in message
news:384112b30baf8caa0152aeeb3a0@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Dave. I went to the site yesterday and did another shutdown which
installed some 34 updates. After that BPA showed only a couple of critical
issues, the only significant one remaining is SBS SP1. Since it failed to
install last time we tried it I think I'll just skip it and forge ahead
with the Swing Migration to the new server.
RWW still does not work, reporting the same error ""Connectivity to the
remote computer could not be established."

Thanks for your suggestions.

Michael



You can install the SBS-specific parts of the service pack even on the
machine that's already at SP2. Just don't install Windows Server SP1
(as opposed to SBS SP1, which is a different thing that also includes
the Windows Server SP). Just skip anything that's already been
installed, or had a newer version installed. As you say, SP's are
cumulative, but we're referring to SBS-specific updates that are not
part of the Windows SP, so they're not included in SP2.

As stated in the KB I posted earlier, any issues caused by Windows
Server SP2 should be fixed by just running WSUS or MU. I agree that
it's unfortunate you have to go to the site, but I recommend only
installing SPs remotely if you're able to get to the server if
necessary. I agree that it shouldn't happen, but I'm not surprised it
did, especially with something as major as a service pack.

I'm thinking that installing the networking updates from the KB is
going to fix everything - please post back your results in case
someone runs into this in the future.

"Michael Appelmans" <news@xxxxxxxxxx> wrote in message
news:384112b309d08ca9e9f891c7bf0@xxxxxxxxxxxxxxxxxxxxxxx

You suggested installing SBS-specific portions of SP1. Can I install
this after I've installed SP2? I though SP's were cummulative? VPN
and remote DCOM+ are working again for eveyone.

RWW still doesn't work. Neither does CrossLoop to desktops, this was
working before (we no longer use Remote Assistance, it's hit or miss
connecting only about half the time we attempt it).

Error: "Connectivity to the remote computer could not be established.
Ensure that the remote computer is on and is connected to the Small
Business
Server network."
Guess I'll have to burn some precious gas and make a trip out to my
client
to try and fix RWW... was hoping to avoid this. Why do service packs
always have to break something that was already working?? I thought
the
whole premise of SBS was that it wouldn't need a nursemaid. Sorry...
can
you tell I'm peeved?
Thanks for any help.

Michael

You need to apply the SBS-specific portions of SP1. You don't need
to actually install Windows Server SP1, but you do need the SBS
parts. See also:

Windows 2003 service pack 2 known issues on Small Business Server
2003 http://support.microsoft.com/kb/555912

You might also consider running the SBS BPA from
http://support.microsoft.com/kb/940439/en-us.
If you're still running into problems after that, please post back
the details of what you see when RWW fails. As for the COM error,
when you click the link in the error message, you usually get
detailed instructions for fixing the permissions. Any help there?

"Michael Appelmans" <news@xxxxxxxxxx> wrote in message
news:384112b309108ca9dbb58affdf0@xxxxxxxxxxxxxxxxxxxxxxx

Installed SP 2 on SBS 2003 Standard with no SP (SP1 failed to
install a long time ago, just tried SP2 due to imminent Swing
Mirgration which requires SPs, SP2 installed succesfully)

Now RWW and a COM+ application doesn't work. COM+ application
returns "error #70 - permission denied" although we haven't done
anything with permissions on the server since SP2 install.

Hope someone can suggest a solution asap.

Michael




.

Relevant Pages

  • RE: SBS2k3 SP1 SP2 mess
    ... It said file not found when attempting to install SBS SP1. ... Windows SharePoint Services 2.0 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Does SP1 install XP SP2 on all workstations?
    ... This newsgroup only focuses on SBS technical issues. ... >Subject: Re: Does SP1 install XP SP2 on all workstations? ... >> be assigned to client computers when you apply SBS 2003 SP1. ...
    (microsoft.public.windows.server.sbs)
  • RE: Webparts error after sp1 install
    ... SBS 2k3 Premium ... server set up to install the intranet. ... server prompted me that the version needed upgradeing to sp1 level. ...
    (microsoft.public.windows.server.sbs)
  • Re: Repair XP SP2 installation with XP SP1 CD-ROM
    ... SP1 doesn't know about the Firewall and Security Center control panel items of SP2. ... Aparently they are more along the lines of applications, and they were rendered non-functional because they apparently depend on SP2 versions of system files, which were replaced by SP1 versions by the SP1 repair install. ...
    (microsoft.public.windowsxp.general)
  • RE: SBS 2003 Updates and Problems
    ... I am not sure if it happened specifically after applying Win2K3 SP1 or SBS ... I haven't uninstalled the service pack on this server yet, ... > strictly follow the documents to install SBS SP1: ...
    (microsoft.public.windows.server.sbs)