Re: Problems after SP2
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Jun 2008 12:26:06 -0400
Can you RDP into the server from a domain-joined client PC over the LAN? Or from the remote PC after connecting over VPN?
Can you connect to RWW and then remote to a client PC, or is this effecting clients and server?
"Dabbler" <Dabbler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:105D4F44-AB43-4D74-882F-AD7324A7CE13@xxxxxxxxxxxxxxxx
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
>>>>>
>
>
.
- Follow-Ups:
- Re: Problems after SP2
- From: Michael Appelmans
- Re: Problems after SP2
- References:
- Problems after SP2
- From: Michael Appelmans
- Re: Problems after SP2
- From: Dave Nickason [SBS MVP]
- Re: Problems after SP2
- From: Michael Appelmans
- Re: Problems after SP2
- From: Dave Nickason [SBS MVP]
- Re: Problems after SP2
- From: Michael Appelmans
- Re: Problems after SP2
- From: Dave Nickason [SBS MVP]
- Re: Problems after SP2
- From: Dabbler
- Problems after SP2
- Prev by Date: Re: Unable to change Outlook2003 mail format
- Next by Date: Re: Error Sending Using Outlook RPC over HTTP
- Previous by thread: Re: Problems after SP2
- Next by thread: Re: Problems after SP2
- Index(es):
Relevant Pages
|