Re: SBS Client Application Launcher ERROR Message - Manual Test Results

From: Mike Stokke [MSFT] (mstokke_at_online.microsoft.com)
Date: 02/12/04 

Date: Thu, 12 Feb 2004 10:45:32 -0800

The problem with the inpage error in this case is probably due to it running
an application across the network and then the application needs to load
more of itself. When it get to that point, it tries to go back across the
network. However, the network seems to have dropped off and so the
connection is lost. At this point, the program throws an error because it
can't load what it needs. This is probably the same reason why applnch.exe
failed. According to the logs, it seems to lose the application when it
goes across the network to install various items. The outlook log files
would be located in the %temp% folder on the client. You might try pinging
your server with the -l 65500. This will attempt to ping the server with
some data so you can see how the latency is working for data transfers.
Alternatively, is there some kind of firewall on this network or NAT at work
on your internal network? Second, if you have an antivirus on the client,
you may try disabling until the applications install because this could also
be intercepting the network transfers. 

-- 
Mike Stokke
-------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
"dhibbeln" <dhibbeln@nospam.com> wrote in message
news:e0rE9XX8DHA.3112@tk2msftngp13.phx.gbl...
> Mike
>
> I ran the command line  as you suggested (see below) via cut and paste to
> start|run
> and got back:
>
> *****************
> \\SBS2003\ClientApps\Outlook2003\setup.exe
> Error performing inpage operation
> ***********************
>
> No new log files created on WKS.
>
>  Mapped a drive to \\sbs2003\clientapps and did dir /s: got lot of files.
> See edit of dir below.
>
> **********************
>  Directory of \\sbs2003\clientapps
>
> 02/11/2004  10:12 PM    <DIR>          .
> 02/11/2004  10:12 PM    <DIR>          ..
> 01/30/2004  04:43 PM    <DIR>          activesync
> 02/11/2004  10:12 PM                28 clientapps.text
> 02/03/2004  07:26 PM    <DIR>          Connection Manager
> 01/30/2004  04:36 PM    <DIR>          FaxXP
> 01/30/2004  04:44 PM    <DIR>          ie6
> 01/30/2004  05:02 PM    <DIR>          outlook2003
> 01/30/2004  06:05 PM    <DIR>          SBScert
> 01/30/2004  04:43 PM    <DIR>          ShadowCopy
> 01/30/2004  04:44 PM               482 Shared Fax Client.lnk
> 01/30/2004  04:36 PM               452 tsclient.lnk
> 01/30/2004  04:36 PM    <DIR>          w2ksp4
> 01/30/2004  04:40 PM    <DIR>          wxpsp1
>                3 File(s)            962 bytes
>
>                 3 File(s)        586,325 bytes
>
>  Directory of \\sbs2003\clientapps
>
> 01/30/2004  05:02 PM    <DIR>          .
> 01/30/2004  05:02 PM    <DIR>          ..
> 01/30/2004  05:02 PM    <DIR>          FILES
> 01/30/2004  05:02 PM         3,429,888 OUTLS11.msi
> 07/25/2003  02:31 PM             6,581 README.HTM
> 07/15/2003  12:57 AM           416,824 SETUP.EXE
> 02/20/2003  08:06 PM            19,697 SETUP.HTM
>                4 File(s)      3,872,990 bytes
> *********************************
> Did ping test and got back:
>
> ********************************************
> Pinging sbs2003.Hibbeln.local [192.168.20.50] with 32 bytes of data:
>
> Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
> Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
> Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
> Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
>
> Ping statistics for 192.168.20.50:
>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 2ms, Maximum = 2ms, Average = 2ms
> ******************************************
>
> My next steps, unless you have some other idea, are
>
> 1) Do diags on WKS NIC and Server NIC
>
> 2) do a load from \\sbs2003\connectcomputer to a new box.
> This will rull out any  "box with with an attitude issue".
>
> 3) If it fails on the new box, I will take out a cross-over cable and
> connect
> direct to the server to rule out any switch/cable plant issues. My test
> network
> is a frankenstein monster and one never knows....
>
> Will advise later this afternoon (Thursday 12 Feb)
>
> "Mike Stokke [MSFT]" <mstokke@online.microsoft.com> wrote in message
> news:OhykG1P8DHA.2480@TK2MSFTNGP10.phx.gbl...
> > Can you verifiy that the server shares exist for \\sbs2003\clientapps
and
> > that outlook2003 exists in that share?  Next, can you try running this
> > command line manually
> >
> > "\\SBS2003\ClientApps\Outlook2003\setup.exe"
> > TRANSFORMS="\\SBS2003\clients\setup\sbsdefault.mst" /qn
> > Reboot=ReallySuppress /wait INSTALLLOCATION="C:\Program Files\Microsoft
> > Outlook" /Lv "C:\DOCUME~1\NADINE~1.HIB\LOCALS~1\Temp\verbose.log"
> >
> > It appears that we failed to launch this application and seemed to
> terminate
> > unexpectedly after that.  Are you having any issues with the network
> > dropping off from this client machine?  Since the application runs
across
> > the network, dropping the connection could be an issue here.
> >
> >
> > -- 
> > Mike Stokke
> > -------------------
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "dhibbeln" <dhibbeln@nospam.com> wrote in message
> > news:%23Og8WTP8DHA.2556@TK2MSFTNGP09.phx.gbl...
> > > Mike,Thanks the directions to the log files. I will be taking a look
at
> > them
> > > in a few minutes to see if I can figure them out.....<grin>
> > >
> > > I went digging around and found computer in AD and also user. Things
> > looked
> > > okay there.
> > > I forgot to mention  that I had attached to the domain prior to useing
> the
> > > client connect wizard,
> > > but I had removed computer and user from domain and converted back to
> > > workgroup before using the wizard. System load was XP with SP1 and all
> > > patches and drivers from windows update. Only app loaded other  then
> that
> > is
> > > MS Baseline Security Analyzer.
> > >
> > > I found some logs files at \\ <server> \clients\response\ <clientname>
> > > app.dat
> > > this file is attached as apps.zip.
> > >
>
>

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • RE: Private addresses on public network
    ... anybody accesses those computers from an external network," -- even when the ... JavaScript delivered to the client that causes the client to retrieve ... the attacker, the request results in another JavaScript response that tells ... Moving beyond a single server ...
    (Security-Basics)