Re: SBS Client Application Launcher failure

Dear Brandy

Thanks for your response. I deleted the logon script as you suggested and
this cleared the problem.

The actual sequence of events when the problem occurred was as followed:-

On either 15/16th June, I noticed the server had some automatic updates
waiting so I applied these. Our XP workstations also had updates waiting and
these were applied as well, except for one machine.

On the machines to which the updates had been applied, the applnch.exe
failure occurred on login to the domain. The other machine did not display
the error until after I had separately applied the automatic updates.
Therefore, the error did not occur until after the client machine was
updated but I do not know if it would have occurred had the server not been
updated i.e. I don't know if the problem is purely client side or if it
involves both client and server.

I have cleared the error so I don't have it exactly but it was of the
typical form "SBS Client Application Launcher has encountered a problem and
needs to close..." I have attached the event log info.(couldn't get it
through!)

Thank you for your help and I hope my information is of use to others. I
have seen one other report on the net of this problem occurring after a
Windows Xp update (but I can't remember where).

Regards

John





""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:yVT9Yj7eFHA.2052@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello John,
>
> Thank you for posting to the SBS Newsgroup.
>
> From your post, I understand that an installation of an update on one
> particular Windows XP workstation caused errors to appear on all of your
> Windows XP client workstations. If I have misunderstood your concern,
> please let me know.
>
> Due to the lack of information for research, please help to gather the
> following information:
>
> 1. What is the exact error message shown to you? Please paste the full
> content to the Newsgroup. If possible, please capture a screen shot for us
> to easily understand your issue.
>
> 2. What are the specific updates you have applied on the Windows XP
> workstation?
>
> 3. Please explain in detail "Our SBS 2003 server (not SP1) was updated on
> the same day but we noticed that the problem didn't occur until the client
> was updated." Also, what is the exact update you installed on the server?
>
> 4. Do clients log on their workstations as local account or domain
> account?
> If they log on as domain account, please check whether they have
> administrative permission on their workstations?
>
> a) The applnch.exe file (launched by the logon script) will automatically
> load once clients log on their workstations by domain account.
>
> b) Please refer to my following steps to isolate whether it is a user
> permission issue:
>
> I) On the server, go to Server Management\Advanced Management\Active
> Directory Users and Computers \Yourdomain.local\MyBusiness\Users\SBSUsers.
>
> II) Double click one of your client name, go to Profile tab, delete the
> Logon script, click OK.
>
> III) Ask this client to log on workstation as the account which issue
> produced, and see whether the issue occurs again.
>
> I am appreciated your time and looking forward to hearing from you.
>
> Best regards,
>
> Brandy Nee
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>




.

Relevant Pages

  • Re: WSUS Client not yet reported
    ... The client still fails to report. ... Check your server status ... Suggestion 2: Check the IIS settings: ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: FYI for eTrust AV 7.x Users
    ... When I just had my little incident with the redistribution settings on the SBS, my clients were logging successful checks for updates, and the logs indicated that no updates were found. ... That turned out to be because I had not gone back and checked the redistribution server box for 8.x after reinstalling the redistribution server. ... installed the new remote install utility which works the same as v7 did - just edited the .ICF file the way I wanted it and ran the client upgrades from the server. ... I can't remember if it's a separate install, or if you have to click a box when you do the Agent install, but redistribution server is not installed by default. ...
    (microsoft.public.windows.server.sbs)
  • RE: Client machines randomly locking up when printing
    ... constant, it occurs every day but not on all workstations, seems like one day ... > is a server or client side issue. ... click the Copy button and paste the full content to the Newsgroup. ...
    (microsoft.public.windows.server.sbs)
  • RE: WSUS Client not yet reported
    ... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS Client not yet reported
    ... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)