RE: Socket sharing issue on TS2003

Yes, it is installed after TS, and when using "Install Mode".

Patrick, thanks you very much for your input on this issue. Your suggestions
and ideas have been very much welcome.

Regards.

"Patrick Rouse" wrote:

> I'm unaware of anything that can be done, other than to complain to the
> manufacturer of the software. I assume that the client piece of the software
> was installed after terminal server and while the server was in install mode.
>
> --
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
>
> "AdventTech" wrote:
>
> > That's also a good suggestion, and by using ProcExp is how I've found that
> > there's a socket sharing issue. I can detect that with a single login using
> > the app, it's accessing a specific socket to access the DB. When any
> > subsequent TS users attempt to run the app, ProcExp detects a failure when
> > attempting to access the DB with the same socket and the app shuts down. If a
> > remote client (non-TS) runs the app installed locally there is no failure
> > when accessing the DB and the app performs normally, even when other TS and
> > non-Ts users are using the DB.
> >
> > All other conflicting issues (file sharing privileges, registry privileges,
> > etc.) have been resolved, but this socket sharing violation is the blocking
> > issue. Any workarounds or ideas would be greatly appreciated.
> >
> > "Patrick Rouse" wrote:
> >
> > > You might want to run process explorer on the TS to see what's going on.
> > > Maybe it will shed some light on the problem.
> > > Some programs are NOT compatible with TS, although a vast majority can be
> > > tweaked to run adequately.
> > >
> > > --
> > > Patrick Rouse
> > > Microsoft MVP - Terminal Server
> > > http://www.workthin.com
> > >
> > >
> > > "AdventTech" wrote:
> > >
> > > > You're quite right, and that's something that I'm already pursuing as a
> > > > long-term solution to this problem. Publishers MUST be aware of and write
> > > > programs with Terminal Services as part of the feature set. The program is
> > > > Mitchell, offered by Mitchell1, which is a long-time supplier of automotive
> > > > manuals. They've just recently made a major shift from printed material to
> > > > software solution, but their V1 rev is, well, a V1 rev... :-(
> > > >
> > > > However, I'm still in need of a short-term fix for this problem, if one
> > > > exists.
> > > >
> > > > "Patrick Rouse" wrote:
> > > >
> > > > > What is the program and who is the manufacturer? Gotta love a vendor who
> > > > > isn't interested in pleasing their customers. A nice letter to the CEO
> > > > > stating your requirement and their support staff's disinterest in helping you
> > > > > may be in order.
> > > > >
> > > > > --
> > > > > Patrick Rouse
> > > > > Microsoft MVP - Terminal Server
> > > > > http://www.workthin.com
> > > > >
> > > > >
> > > > > "AdventTech" wrote:
> > > > >
> > > > > > I'm trying to get an application to work correctly on a TS 2003 server. I've
> > > > > > tracked down all other conflicting issues, such as registry and folder
> > > > > > permissions, etc. This application is using a specific socket to access an MS
> > > > > > Access database. When this application is installed on remote workstations,
> > > > > > multiple users can connect to the DB and run as advertised. However, if more
> > > > > > than one user attempts to run the same application when logged on through TS,
> > > > > > the application refuses to run because the socket is not available.
> > > > > >
> > > > > > I best guess is that the application is not properly using functionality of
> > > > > > the WinSock 2 API, which I understand should allow for socket sharing, but
> > > > > > only if the app uses the WinSock API correctly. The application publisher has
> > > > > > shown little interest in addressing this problem of TS compatibility.
> > > > > >
> > > > > > There are several other applications that are working correctly when using
> > > > > > TS2003, which indicates to me that the server is working correctly for most
> > > > > > apps.
> > > > > >
> > > > > > Any ideas about how to overcome this socket sharing problem???
> > > > > >
> > > > > > Thanks in advance.
> > > > > >
> > > > > > Server Config:
> > > > > > Windows Server 2003
> > > > > > Terminal Server 2003
> > > > > > Application was installed correctly using Add/Remove Programs.
.

Relevant Pages

  • Re: ClickOnce Nightmares
    ... your app need to install the settings. ... LAN) you could create a logon script that will automatically install the ... DownloadOptions options, ServerInformation& serverInformation) ... FileAccess access, Boolean asyncHint) ...
    (microsoft.public.dotnet.framework)
  • Re: Saving Back-End Data As mdf
    ... complete code of a VB.NET console app. ... It's just an example to illustrate how a connection string is used. ... so it doesn't appear to be a problem with how or what I install. ... you access to the Microsoft Office Online Beta site'. ...
    (microsoft.public.access.formscoding)
  • Re: Run 10.20 App on 11.00 ?
    ... installed on both machines using the vendor's install scripts. ... > if the app links in libc.a then you basically up the creek because you have ... Use chatr to see what the dependent libraries are. ... an industrial control system made by Fisher Control Systems. ...
    (comp.sys.hp.hpux)
  • Re: Windows XP auto updates stinks!!
    ... just use one exploit whereas you have to test all patches. ... you needn't install them. ... so I ignore any updates to it. ... you install an incompatible app ...
    (microsoft.public.windowsxp.general)
  • Re: VS 2005 questions
    ... guilty of forcing developers to install legacy versions of their software. ... I don't want the overhead of a legacy app on my laptop hard drive ... Hopefully by the time the next Visual Studio comes out, ... only one looking forward to being able to install only one Managed code IDE ...
    (microsoft.public.vsnet.general)
Quantcast