RE: SBS Client Application Launcher error

Hi Manuel,

Thanks for your update.

Please perform the following test to isolate the issue:

1. Please use command "whoami /all -> c:\whoami.txt" (no quotation marks)
on one affected client computer before and after changed the user's
permissions with a new created user account. Please collect both files and
mail it to me.
2. Please perform clean boot on the affected client computer, how about the
result?

A Clean Boot will allow us to isolate any device drivers or programs that
are loading at startup that may be causing a conflict with other device
drivers or programs that are installed in your computer.

1) Run MSCONFIG.EXE.
2) In the Services tab, click "Hide All Microsoft Services" and click
"Disable All".
3) In the Startup tab, click "Disable All". Click OK. (This will
temporarily prevent third-party programs from running automatically during
start-up.)
4) Restart the computer and check whether the problem still persists.

If the problem does not occur, it indicates that the problem is related to
one application or service we have disabled. You can use the MSCONFIG tool
again to re-enable the disabled item one by one to find out the culprit.

3. Please double check if the issue will come back after you clear the Temp
folder. And let me know how long time it backs, so that we can find the
issue root cause.

4. If the issue persists, perform a clean boot and clear the Temp folder,
then using Filemon and Regmon utility to monitor the client workstation
till the issue come back again.

Please use the following steps to capture data with these utilities. You
will need to follow the steps below to use the utility.

1. Please visit the following link to download and save the Filemon and
Regmon version for your operating system from the following Web site:
http://www.sysinternals.com/ntw2k/source/filemon.shtml

- Download "Filemon (x86 - 76 KB) - you plan on using Filemon on
WinNT/2K/XP/2K3" if you plan to use Filemon on Windows 2000, Windows XP, or
Windows Server 2003.

The following link for down Regmon utility:
http://www.sysinternals.com/Utilities/regmon.html

2. Familiarize yourself with the Capture and Clear buttons below the menu
bar. You can alternatively use Ctrl+E and Ctrl+X.
3. Stop the capture and clear the current events. This will allow us to
capture minimal activity. There will be some activity that will be
extraneous, but that's okay. We would rather have to much data then not
capture the correct events.
4. Make sure your application is in a state where you are ready to
reproduce the problem (has changed the user permissions, clean Temp folder,
then test to logon the client workstation with the user account).
NOTE: In order to see minimal traffic from the utilities close all other
applications that are not involved in the test.
5. Click the capture button or use Ctrl+E to start capturing data.
6. Reproduce the problem.
7. Stop the capture by clicking the 'Capture' button or use Ctrl+E.
8. Save each capture to a file, zip them up and send them to me for review.
My working mailbox is: v-yanniw@xxxxxxxxxxxxx

Also please check if there is any related error event in the Event Viewer
on the client workstation and let me know.

I appreciate your time! I am happy to be assistance of you.

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: SBS Client Application Launcher error
>thread-index: AcYXKHjx5S/5tYSdTCqoHhtYgns1Gg==
>X-WBNR-Posting-Host: 72.192.240.238
>From: =?Utf-8?B?TWFudWVs?= <Manuel@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <24846D76-B506-45E0-8F34-D8EC712CFDE5@xxxxxxxxxxxxx>
<qazcr8dFGHA.3680@xxxxxxxxxxxxxxxxxxxxx>
<3B72EF24-0A2F-467E-BED2-61D5FE8F1349@xxxxxxxxxxxxx>
<yr3PBFoFGHA.3152@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: SBS Client Application Launcher error
>Date: Wed, 11 Jan 2006 19:30:02 -0800
>Lines: 46
>Message-ID: <59462D1F-1ECF-4A87-9CF3-5EF11528B2AE@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:235985
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi Jenny,
>
>Thank for attempting to help me. Still have this problem that seems lots
of
>other are having too. I'll answer your questions 1 by 1 again.
>
>> 1. On the client machine in the c:\Documents and Settings\username\Local
>> Settings\Temp, please move everything to a "junk" folder. Then reboot
the
>> client computer with the user account, how about the result?
>
>Okay, on one computer this workaround worked but I had already tried that
a
>week before posting here. What I did though is simply deleting the
complete
>user account's folder (which deleted the "temp" too). It seemed to work at
>first but it came back. I tried just the Temp folder like you said and it
>resolved the problem but only on one machine the others that showed the
same
>symptoms remained the same.
>
>> 2. If the issue persists, please try to replace the applnch.exe file on
>> the client side. You can copy applnch.exe file from
>> CD3\SBS\clientsetup\clients\setup
>> And then re-log the computer to see if the issue be fixed.
>
>Nope, didn't work either. I tried this with the machines that didnt get
>fixed with what you told me above. I copied it from the CD, even tried
>copying applnch.exe from a working account's temp folder..all to no avail.
>
>> 3. Have you installed any third party application on client computers?
Such
>> as trend micro firewall. If yes, please disable them to test.
>
>They were originally there but it's antivirus, which I did disable, and
>still the same thing. Either way, it was working fine with the AV enabled
>anyway. It wasn't only UNTIL I changed permissions to one user.
>
>> 4. Please logon one workstation with the user account and manually run
the
>> login script SBS_LOGIN_SCRIPT.bat, can you still receive the error
message?
>
>I tried this the second day of fighting with this error which was about 2
-
>2 1/2 weeks ago. same error. Before you ask, I did check permissions and
it
>was already at full control to all domain users. And even still, I went
ahead
>and setup some test permissions to see if it had anything to do with it,
and
>it doesn't. All other users are fine doing it the same way. It only goes
>crazy after I change permissions with the wizard. And like I said
previously,
>I NEED to be able to change permissions for my managers but SBS is making
>difficult.
>
>Thank you for your time
>
>

.